Hello all. I just unlocked my bootloader and rooted my phone, or so I thought. Somehow, I did not completely root my phone. Busybox installer would not load. I ran root checker and it said my root was not complete. My questio is, if I were to do a factory reset, would my bootloader relock? Thanks
quicksilver53 said:
Hello all. I just unlocked my bootloader and rooted my phone, or so I thought. Somehow, I did not completely root my phone. Busybox installer would not load. I ran root checker and it said my root was not complete. My questio is, if I were to do a factory reset, would my bootloader relock? Thanks
Click to expand...
Click to collapse
No it wouldn't. Does it say unlocked in purple? Can't remember the specific exploit directions. But you can flash twrp using "fastboot flash recovery twrp.IMG" (obviously change twrp.img to the name or hit tab) and flash a rooted ROM. Haven't done any of the exploits up here, but of you clicked on rooted in my SIG, its a great site you out. Skip to the part after unlocking the bootoader.
Sent from my Carbon-ize Evita using xda-developers app
Herc08 said:
No it wouldn't. Does it say unlocked in purple? Can't remember the specific exploit directions. But you can flash twrp using "fastboot flash recovery twrp.IMG" (obviously change twrp.img to the name or hit tab) and flash a rooted ROM. Haven't done any of the exploits up here, but of you clicked on rooted in my SIG, its a great site you out. Skip to the part after unlocking the bootoader.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Yes. When I have it in bootloader mode, it had changed from locked to unlocked. Thanks for your help.
Did you install custom recovery (CWM or TWRP) and flash SuperSU or SU, or flash a rooted ROM. Because you need to do that to actually have root (after unlocking the bootloader).
redpoint73 said:
Did you install custom recovery (CWM or TWRP) and flash SuperSU or SU, or flash a rooted ROM. Because you need to do that to actually have root (after unlocking the bootloader).
Click to expand...
Click to collapse
That's right. When he said thanks, I thought he figured it out.
Sent from my Carbon-ize Evita using xda-developers app
Also, I believe the only thing that will relock the bootloader, is you relocking it yourself.
redpoint73 said:
Also, I believe the only thing that will relock the bootloader, is you relocking it yourself.
Click to expand...
Click to collapse
I am fairly certain that is correct. An RUU won't run with a bootloader unlocked unless you are S-OFF and still would not relock. nothing else would touch the bootloader.
I followed the instructions and slashed the recovery, twrp I think it was and I got stumped after there. I am relatively new to rooting. I unlocked both my N7 and N4 a week ago with Wugfresh's toolkit and that was relatively simple for and old guy like me. I will most likely have to go to his website and get complete instructions and try it again.
Sent from my Nexus 4 using xda app-developers app
quicksilver53 said:
I followed the instructions and slashed the recovery, twrp I think it was and I got stumped after there. I am relatively new to rooting. I unlocked both my N7 and N4 a week ago with Wugfresh's toolkit and that was relatively simple for and old guy like me. I will most likely have to go to his website and get complete instructions and try it again.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
well i can help you, i recommend going with twrp and flashing a SU zip file. this post is reserved, and will be back to edit...
Edit; Ok, so in this post is two files you need.
http://forum.xda-developers.com/attachment.php?attachmentid=1907931&d=1366808637
and http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Download both of these files.
Put UPDATE-SuperSU-v1.04.zip on the root on your SD card (basically transfer the zip to your phone)
I downloaded the 2.3.3 twrp img file, since that is the most stable for me. If you want to upgrade to 2.5, then be my guess, but others say it is a problem. i have flashed sense roms and aosp roms with no problems. also, pleae read both paragraphs before attempting to do something. if you do not understand, feel free to comment or pm me. i tried to make it as simple as possible.
So first off download the zip, and extract the folder to a simple location (desktop or c:\). i am going to assume you extracted it to c:\. open up a command prompt by going to Start and typing in "cmd" a black window should pop up. type in "cd c:\rootphone." you are already rooted, but it was already the name of my folder. anywho, turn your phone completely off, and go into the bootloader. i assume you know how to do this, since you were able to read off your hboot details. it is the white screen with colorful text. then select fastboot in red. once a usb connection is plugged in, it should turn to fastboot usb. now in the command prompt (black window on the pc), you need to type fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img (hint: you can type open and hit tab, and it will finish it for you). now you have twrp installed. now boot into recovery, and go tap on Install. find the UPDATE-SuperSU-v1.04.zip, tap it, and then slide to flash. your if successful, your phone should be rooted. go ahead hit reboot, and re-run root checker.
To anyone else (i.e. Venomtester or exad) if i have incorrect info, please let me know
Looks good to me lol. But a more simple method to open the command window is to download adb to desktop. Then all they have to do is open the folder and right-click somewhere away from the files and it will give the option to open command window here. That way they can put the images in the folder and never have to leave it. They tend to mess up hunting the folder down from windows cmd.
Sent from my HTC One X using xda premium
Venomtester said:
Looks good to me lol. But a more simple method to open the command window is to download adb to desktop. Then all they have to do is open the folder and right-click somewhere away from the files and it will give the option to open command window here. That way they can put the images in the folder and never have to leave it. They tend to mess up hunting the folder down from windows cmd.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I write guides, I write with assumptions. But I guess you are right.
Sent from my Carbon-ize Evita using xda-developers app
Thanks a lot for the info guys. I will have another go at it when I get home from work tonight.
Sent from my Nexus 4 using xda app-developers app
Well I thought it was a very good guide.
Sent from my HTC One X using xda premium
Venomtester said:
Well I thought it was a very good guide.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks again guys. I have tried several times since last night to get my phone into bootloader mode. I power it off and the push volume down and power and keep holding both. It starts up and the capacitive buttons flash as I get the quietly brilliant screen and the it just goes black with no flashing. I don't know why it will not go any further. I also get an error report every time. Any guggestions? I have tried to use the commands on the tool kit to get it into bootloader mode but no success.
quicksilver53 said:
Thanks again guys. I have tried several times since last night to get my phone into bootloader mode. I power it off and the push volume down and power and keep holding both. It starts up and the capacitive buttons flash as I get the quietly brilliant screen and the it just goes black with no flashing. I don't know why it will not go any further. I also get an error report every time. Any guggestions? I have tried to use the commands on the tool kit to get it into bootloader mode but no success.
Click to expand...
Click to collapse
Ok I got it into bootloader mode. I forgot to let go of the power buton when the screen went black.
OK just re do it again. Hold down power and volume down (or is it up? I get this confused with Samsung sometimes)
Sent from my Carbon-ize Evita using xda-developers app
Down...
Sent from my HTC One X using xda app-developers app
31ken31 said:
Down...
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks. Figured that.
Sent from my Carbon-ize Evita using xda-developers app
Related
hi everybody today i tried to update my HOX with this stock room "stock rooted 2.33.162.2 - odex/deodex and unsecure boot.img with init.d"
my android version is 4.0.4
HTC sense versio 4.0
Software Number 1.88.707.2
HTC SDK API level 4.11
HTC Extension Version 403_1_GA_4
then after i flashed the room the HTC wont boot (just shows me the white HTC screen) and i still have access to the recovery mode (CWM) i downloaded another room to tried to flash the phone (my nandroid bk shows me an MD5 error when i tried to restore) then i dont have any idea about how can i move the new zip file to the cellphone, i am very frustrated because i cant do it anything yet
please somebody help me
Thanks in advance for your help
If you get it working, the first order of business is to ditch CWM and switch to TWRP as it was not properly ported to our device. Are you sure you have a XL? The dual core version? Make sure you have the right ROM for the right device. I can't help you to transfer as you are using CWM and I'm not familiar with mounting. Word on the street is that there is a good chance it'll wipe your entire SDcard
Sent from my One X using xda premium
InflatedTitan said:
If you get it working, the first order of business is to ditch CWM and switch to TWRP as it was not properly ported to our device. Are you sure you have a XL? The dual core version? Make sure you have the right ROM for the right device. I can't help you to transfer as you are using CWM and I'm not familiar with mounting. Word on the street is that there is a good chance it'll wipe your entire SDcard
Sent from my One X using xda premium
Click to expand...
Click to collapse
thanks for your quickly response, well i have an AT&T HTC one X and yes its the dual core version, the phone comes with the CWM, unlocked and rooted, how can i install the TWRP ? because if i connect the phone to the computer doesnt shows me anything (i cane heard the tone when windows detect something new but its all) i tried to use odin but odin doesnt shows me anything and i tried with fastboot and adb but doesnt fount the device connected
from recovery do a factory reset and try again to boot it.... if u have a nandroid backup there is a setting to turn off md5 checking so it will restore......... as long as your using TWRP recovery (which you should be if not) you can mount usb storage and transer whatever you need......
18th.abn said:
from recovery do a factory reset and try again to boot it.... if u have a nandroid backup there is a setting to turn off md5 checking so it will restore......... as long as your using TWRP recovery (which you should be if not) you can mount usb storage and transer whatever you need......
Click to expand...
Click to collapse
i did it but still the same problem i am very frustrated because i cant do anything and i dont have any idea about how can transfer the zip file from my computer to the cellphone
fjej78 said:
i did it but still the same problem i am very frustrated because i cant do anything and i dont have any idea about how can transfer the zip file from my computer to the cellphone
Click to expand...
Click to collapse
you need to download twrp recovery, should be in the stickies, and flash it from hboot.
stick the recovery image in your adb/fastboot folder and rename it to twrp.img, boot phone into bootloader
from cmd prompt, fastboot flash recovery twrp.img
then on device select bootloader, then recovery.....once in twrp recovery you can mount usb and transfer..
no matter what just focus on getting twrp recovery flashed...your fixes will all come after that
18th.abn said:
you need to download twrp recovery, should be in the stickies, and flash it from hboot.
stick the recovery image in your adb/fastboot folder and rename it to twrp.img, boot phone into bootloader
from cmd prompt, fastboot flash recovery twrp.img
then on device select bootloader, then recovery.....once in twrp recovery you can mount usb and transfer..
no matter what just focus on getting twrp recovery flashed...your fixes will all come after that
Click to expand...
Click to collapse
yeah, i can do it i use the one click tool, and i installed another room, but i lost the root how can i root again? and how can i avoid the disclaimer when the phone boot?
BTW thanks you so much for your help
fjej78 said:
yeah, i can do it i use the one click tool, and i installed another room, but i lost the root how can i root again? and how can i avoid the disclaimer when the phone boot?
BTW thanks you so much for your help
Click to expand...
Click to collapse
any custom rom that you flash will be rooted already. As far as the red text goes, that is there to stay until the device gets s-off or you go back to completely stock/use a stock recovery.
18th.abn said:
any custom rom that you flash will be rooted already. As far as the red text goes, that is there to stay until the device gets s-off or you go back to completely stock/use a stock recovery.
Click to expand...
Click to collapse
sorry for the stupid question but what is s-off?
Security-off....see the phones which HTC does allow bootloader unlocking don't really get unlocked. Their unlocking really just partially unlocks and to have a HTC phone with a truly "unlocked" boitloader you have to have s off. Which gives the user full rights over the entire phone....so htcdev unlocked bootloaders aren't really even unlocked, they're simply less restricted.......
Sent from my SCH-R720 using xda app-developers app
18th.abn said:
Security-off....see the phones which HTC does allow bootloader unlocking don't really get unlocked. Their unlocking really just partially unlocks and to have a HTC phone with a truly "unlocked" boitloader you have to have s off. Which gives the user full rights over the entire phone....so htcdev unlocked bootloaders aren't really even unlocked, they're simply less restricted.......
Sent from my SCH-R720 using xda app-developers app
Click to expand...
Click to collapse
And exists a way or method to unlock completely the phone? (something that does not turn my phone on a luxury brick)?
Well a few guys and myself have all bricked our fair share of devices trying.......in the general forum you can follow the development on it in the [DEV]S Off thread...
http://forum.xda-developers.com/showthread.php?t=1639972
Sent from my SCH-R720 using xda app-developers app
18th.abn said:
Well a few guys and myself have all bricked our fair share of devices trying.......in the general forum you can follow the development on it in the [DEV]S Off thread...
http://forum.xda-developers.com/showthread.php?t=1639972
Sent from my SCH-R720 using xda app-developers app
Click to expand...
Click to collapse
thanks for all your help, i will close this post
thank you so much
Hi, this belongs in Q&A. Please keep all question/help related threads in that section only. Thank You.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
I am using Hasoon2000's All-in-One Toolkit to root my HOX. It's worked every time but this time.
Here is my story...
I've been trying to flash the ViperX 2.6 ROM for a couple hours now.
Each time I have gotten stuck in a Bootloop.
Through TWRP, I've wiped the cache/delvik(still didn't fix the problem).
I decided to go ahead and run my device's RUU.(relocked the Bootloader, and ran)
Well now, I try and run his toolkit to root again and the cmd prompt say "device not found".
When I go into the fastboot folder and select the cmd prompt from there and type "fastboot devices", it's able to recognize my device...
Any ideas as to what's going on?
Maybe his toolkit is not working properly...?
BTW, this is my first Android phone. EVER.
Myrder said:
I am using Hasoon2000's All-in-One Toolkit to root my HOX. It's worked every time but this time.
Here is my story...
I've been trying to flash the ViperX 2.6 ROM for a couple hours now.
Each time I have gotten stuck in a Bootloop.
Through TWRP, I've wiped the cache/delvik(still didn't fix the problem).
I decided to go ahead and run my device's RUU.(relocked the Bootloader, and ran)
Well now, I try and run his toolkit to root again and the cmd prompt say "device not found".
When I go into the fastboot folder and select the cmd prompt from there and type "fastboot devices", it's able to recognize my device...
Any ideas as to what's going on?
Maybe his toolkit is not working properly...?
BTW, this is my first Android phone. EVER.
Click to expand...
Click to collapse
ViperX 2.6 is an international ROM.. ViperXL for our phone is 2.1.2
You better be thankful you didn't flash ice cold jelly or you'd have s nice paper weight. Unlock your bootloader and flash twrp again
Sent from my One X using xda app-developers app
Myrder said:
I am using Hasoon2000's All-in-One Toolkit to root my HOX. It's worked every time but this time.
Here is my story...
I've been trying to flash the ViperX 2.6 ROM for a couple hours now.
Each time I have gotten stuck in a Bootloop.
Through TWRP, I've wiped the cache/delvik(still didn't fix the problem).
I decided to go ahead and run my device's RUU.(relocked the Bootloader, and ran)
Well now, I try and run his toolkit to root again and the cmd prompt say "device not found".
When I go into the fastboot folder and select the cmd prompt from there and type "fastboot devices", it's able to recognize my device...
Any ideas as to what's going on?
Maybe his toolkit is not working properly...?
BTW, this is my first Android phone. EVER.
Click to expand...
Click to collapse
Well, first off, there is no version 2.6 of Viper ROM for the HTC One XL, which is our phone. It sounds to me that you have downloaded an international One X ROM. Which, could be bad for you. If the ROM flashed successfully, you've overwritten the boot partition, due in part to how the One X ROMs are flashed. If it wasn't flashed successfully, you may still be in luck.
Now. You say you are stuck in bootloop? If so, do these steps (Feel free to correct me anyone)
- Reboot your phone into bootloader
- Re-Unlock your bootloader
- Reflash TWRP (Custom recovery)
- Boot into recovery and wipe everything (Except phone storage)
- Flash a ROM for the ONE XL. NOT The International ROM
Hopefully you aren't bricked.
HTC_Phone said:
Well, first off, there is no version 2.6 of Viper ROM for the HTC One XL, which is our phone. It sounds to me that you have downloaded an international One X ROM. Which, could be bad for you.
Now. You say you are stuck in bootloop? If so, do these steps (Feel free to correct me anyone)
- Reboot your phone into bootloader
- Re-Unlock your bootloader
- Reflash TWRP (Custom recovery)
- Boot into recovery and wipe everything (Except phone storage)
- Flash a ROM for the ONE XL. NOT The International ROM
Hopefully you aren't bricked.
Click to expand...
Click to collapse
He's not bricked. Adb sees his phone in the bootloader
Sent from my One X using xda app-developers app
absolutelygrim said:
He's not bricked. Adb sees his phone in the bootloader
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh right. Must have missed that not paying full enough attention. Good. Do what I said above. Try running one of the kits in the One XL forum. What bootloader are you on?
Myrder said:
I am using Hasoon2000's All-in-One Toolkit to root my HOX. It's worked every time but this time.
Here is my story...
I've been trying to flash the ViperX 2.6 ROM for a couple hours now.
Each time I have gotten stuck in a Bootloop.
Through TWRP, I've wiped the cache/delvik(still didn't fix the problem).
I decided to go ahead and run my device's RUU.(relocked the Bootloader, and ran)
Well now, I try and run his toolkit to root again and the cmd prompt say "device not found".
When I go into the fastboot folder and select the cmd prompt from there and type "fastboot devices", it's able to recognize my device...
Any ideas as to what's going on?
Maybe his toolkit is not working properly...?
BTW, this is my first Android phone. EVER.
Click to expand...
Click to collapse
When u first time rooted did you use the same pc?
Sent from my HTC One XL using xda premium
HTC_Phone said:
Oh right. Must have missed that not paying full enough attention. Good. Do what I said above. Try running one of the kits in the One XL forum. What bootloader are you on?
Click to expand...
Click to collapse
1.14 since he was using the tool kit
Sent from my One X using xda app-developers app
absolutelygrim said:
ViperX 2.6 is an international ROM.. ViperXL for our phone is 2.1.2
You better be thankful you didn't flash ice cold jelly or you'd have s nice paper weight. Unlock your bootloader and flash twrp again
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Even if I ran the AT&T 2.20 RUU?
HTC_Phone said:
Well, first off, there is no version 2.6 of Viper ROM for the HTC One XL, which is our phone. It sounds to me that you have downloaded an international One X ROM. Which, could be bad for you. If the ROM flashed successfully, you've overwritten the boot partition, due in part to how the One X ROMs are flashed. If it wasn't flashed successfully, you may still be in luck.
Now. You say you are stuck in bootloop? If so, do these steps (Feel free to correct me anyone)
- Reboot your phone into bootloader
- Re-Unlock your bootloader
- Reflash TWRP (Custom recovery)
- Boot into recovery and wipe everything (Except phone storage)
- Flash a ROM for the ONE XL. NOT The International ROM
Hopefully you aren't bricked.
Click to expand...
Click to collapse
Well, glad to know that now... I really like the specs of the ViperX.
abhipati said:
When u first time rooted did you use the same pc?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yes, I am rooting from the same PC.
Myrder said:
Even if I ran the AT&T 2.20 RUU?
Well, glad to know that now... I really like the specs of the ViperX.
Yes, I am rooting from the same PC.
Click to expand...
Click to collapse
As long as you have your unlock token, just follow the part about unlocking your bootloader from fast boot
Sent from my One X using xda app-developers app
Myrder said:
Well, glad to know that now... I really like the specs of the ViperX.
.
Click to expand...
Click to collapse
We have a Viper ROM as well on the One XL, does a good job.
Here's the link:
http://forum.xda-developers.com/showthread.php?t=1868236
Just follow the steps we've mentioned, and download from THAT link above, and you should be good
If you have any other questions, feel free to ask or PM me!
absolutelygrim said:
As long as you have your unlock token, just follow the part about unlocking your bootloader from fast boot
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Done, I just restarted to tool and did it step by step.
successful root.
Any idea which ROM would be the best...?
Myrder said:
Done, I just restarted to tool and did it step by step.
successful root.
Any idea which ROM would be the best...?
Click to expand...
Click to collapse
There is no best rom.
Anyway, you don't need to rerun the tool for root. Just to unlock your bootloader again
absolutelygrim said:
There is no best rom.
Anyway, you don't need to rerun the tool for root. Just to unlock your bootloader again
Click to expand...
Click to collapse
Thanks.. Now I feel really dumb.
This system is SOOO much different than, dare I say it, Apple...
Still learning everything, as you can see.. lol
Also, is there a certain gapps I should flash over, since ROMs are device specific?
Myrder said:
Thanks.. Now I feel really dumb.
This system is SOOO much different than, dare I say it, Apple...
Still learning everything, as you can see.. lol
Also, is there a certain gapps I should flash over, since ROMs are device specific?
Click to expand...
Click to collapse
http://goo.im/gapps
Download for CM 10 if on AOSP (CM10, AOKP, King Kang) but not MIUI or sense
absolutelygrim said:
http://goo.im/gapps
Download for CM 10 if on AOSP (CM10, AOKP, King Kang) but not MIUI or sense
Click to expand...
Click to collapse
How can I tell which I am on?
Sorry for so many questions...
ViperXL is sense, so you dont need gapps
Glad to know.
Thanks.
Sent from my HTC One X using xda app-developers app
Just got the HTC One S( HTC branded S4 edition). I unlocked the boot loader, rooted , flash a recovery , and then installed CM10. Everything went well until the final install , when the Cyanogen Boot was stuck. I have no idea what I did afterwards, but now the SD is unmounted. It doesn't boot up to HTC stock , the HTC developer pages just open and stays on .. I could fastboot. I backed up everything, but somehow everything got deleted.
What to do? I need help!
Sent from my Nexus 4 using xda app-developers app
Sounds to me like you forgot to flash the kernel, then did something else wrong afterwards in the attempt to fix. I have the S3 version, but I had a similar problem with the ROM getting stuck, then my recovery was unable to mount the SD. There are 2 options, one is to use fastboot to re-lock your device, and flash the latest RUU for your CID, or you can adb sideload a ROM if you are using TWRP. I would probably go for the RUU anyway because it is the easiest. Just go into the bootloader, choose 'fastboot', use the command to re-lock the bootloader (I just use the All-In-One Tool) and then run the RUU when the phone is in fastboot mode, the phone will then be good as new (except for the Tampered warning in bootloader, but that can be remedied with the S4 version)
This happened to me just flash TWRP wipe everything and get another ROM on there
Sent from my One S using xda app-developers app
I'll try tonight when I get a chance.. And let you know how it went. Thank you.
Sent from my Nexus 4 using xda app-developers app
ferndom said:
I'll try tonight when I get a chance.. And let you know how it went. Thank you.
Click to expand...
Click to collapse
I was in the exact same situation as you, it worked for me (on the second repeat). If it doesn't work the first time, then just try again.
Ami007 said:
Sounds to me like you forgot to flash the kernel, then did something else wrong afterwards in the attempt to fix. I have the S3 version, but I had a similar problem with the ROM getting stuck, then my recovery was unable to mount the SD. There are 2 options, one is to use fastboot to re-lock your device, and flash the latest RUU for your CID, or you can adb sideload a ROM if you are using TWRP. I would probably go for the RUU anyway because it is the easiest. Just go into the bootloader, choose 'fastboot', use the command to re-lock the bootloader (I just use the All-In-One Tool) and then run the RUU when the phone is in fastboot mode, the phone will then be good as new (except for the Tampered warning in bootloader, but that can be remedied with the S4 version)
Click to expand...
Click to collapse
Thanks to all, especially to member Ami007. Im back and running again. I relocked the bootloader using fastboot, downloaded the correct RUU file that corresponds to my phone, and run the program.. Kudos to all!!!
Hate to start a new thread on something that is probably an easy fix but no one will respond when i replied to hasoons guide. Anyways I am trying to flash a custom recovery but it always gets stuck saying "sending 'recovery' (7992 KB)" I have tried 5+ times and always end up having to hold the power button because nothing will work. The phone is frozen until i unplug the usb, and the terminal on my pc freezes. I also tried the latest version of twrp (2.6) and it said the flash was successful but whenever i go back into recovery it is still stock. My bootloader is unlocked, I have an att one x with android 4.1.1 and software # 3.18 (if it even matters)
Honestly i could care less about the recovery i just need root access. I wont be flashing a custom rom or anything. Can i keep the stock recovery and root my phone?
Austin021296 said:
Hate to start a new thread on something that is probably an easy fix but no one will respond when i replied to hasoons guide. Anyways I am trying to flash a custom recovery but it always gets stuck saying "sending 'recovery' (7992 KB)" I have tried 5+ times and always end up having to hold the power button because nothing will work. The phone is frozen until i unplug the usb, and the terminal on my pc freezes. I also tried the latest version of twrp (2.6) and it said the flash was successful but whenever i go back into recovery it is still stock. My bootloader is unlocked, I have an att one x with android 4.1.1 and software # 3.18 (if it even matters)
Honestly i could care less about the recovery i just need root access. I wont be flashing a custom rom or anything. Can i keep the stock recovery and root my phone?
Click to expand...
Click to collapse
No way to root by stock recovery.
Just study & try with this tool for flashing custom recovery >>>>> http://forum.xda-developers.com/showthread.php?t=1734365
And post it in the Q&A part the next time, thats what its ment for ! And you say att hox, does your bootloader say evita ? If so then you are in the completely wrong forum !!!
Mr Hofs said:
And post it in the Q&A part the next time, thats what its ment for ! And you say att hox, does your bootloader say evita ? If so then you are in the completely wrong forum !!!
Click to expand...
Click to collapse
Yes it says Evita. Sorry, i thought it was the right section.
but seriously can anyone help me? I have tried so many different things to flash a recovery and NOTHING works. When i hold the power + volume down button when the red exclamation mark is showing up the 3 lights on the front flash a few times and the phone reboots. It will not even go into recovery anymore. Do i just have a bad phone or what?
I know you need answers but please continue this in the correct AT&T HTC one XL forum. If somebody comes along and says to flash this and that might even brick your phone completely !
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
I know you need answers but please continue this in the correct AT&T HTC one XL forum. If somebody comes along and says to flash this and that might even brick your phone completely !
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Could you please move the thread over there? Or should i just start a new one?
Ask a mod to close or move this one. Or create a new one there indeed
edit :
thread reported, to move it or close it.
Good luck and all the best.
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
Ask a mod to close or move this one. Or create a new one there indeed
edit :
thread reported, to move it or close it.
Good luck and all the best.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thread is now in the Q&A section.
Just flash the recovery manually using fastboot. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can select recovery from your bootloader to enter TWRP recovery.
Sent from my Evita.
Hi all.
Can anyone lend a hand to help me get my phone rooted again? I had originally rooted it when it first turned up, by using the guide on these forums. Since then I (stupidly) did the OTA upgrade not thinking about losing root. I went from 33r to 38r. The first I knew was when Titanium back up wouldn't back up.
My problem is that neither of my computers (desktop - XP) (Laptop - Windows 7) will now see my phone. They will both make a sound when connecting via the USB cable but neither of them show the phone via My Computer. I've un-installed/installed the drivers again and I have tried putting the phone in Fastboot and clicking on Unlock Bootloader, via the Toolbox V3, but the phone will only "reboot" to the home screen. I'm needing a bit of help from someone who knows what they are doing
Thanks in advance for any help... Foz
Once you unlock the bootloader, I don't think you need to unlock it again. If you lose root after an OTA, I think all you need to do is reflash superuser from recovery. And don't touch those toolboxes. They don't help you learn to solve these problems by yourself.
Sent from my A0001 using XDA Free mobile app
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
OKay
reboot system, back to my normal settings/homescreen.
I have SuperSu on my phone BUT get the warning that no binary is installed and I need to re root, hencmy posting here.
adamfoz said:
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
Click to expand...
Click to collapse
If re-downloading the zip doesn't work you should try a newer SuperSU version.
meekrawb said:
If re-downloading the zip doesn't work you should try a newer SuperSU version.
Click to expand...
Click to collapse
I believe I have the latest version from the play store ( 2.14).
adamfoz said:
I believe I have the latest version from the play store ( 2.14).
Click to expand...
Click to collapse
Should have clarified, you should try a newer version of the zip.
download.chainfire.eu/supersu
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
adamfoz said:
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
Click to expand...
Click to collapse
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
sparkdroid said:
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
Click to expand...
Click to collapse
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
adamfoz said:
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
no flash twrp or any custom recovery in adb and then you can flash the root zip.
I'm following this guide for rooting http://forum.xda-developers.com/showthread.php?t=2788632 .
I'm assuming that I'm doing things ok to a point, as the CMD prompt is saying adb version is 1.0.32 but when i put the phone in fast boot, and type "fastboot devices" the phone will show up in the cmd prompt. Its when I "fastboot oem unlock" and"fastboot reboot", the phone will reboot as normal. No setting up of the phone. All my apps and settings are still there, indicating to me that something is wrong :/
I'm assuming that my drivers are ok otherwise I wouldn't be seeing the above in the cmd prompts but...
Can someone tell me if my mobile should show up in "my computer" ? it has in the past, but no longer does. and I'm wondering if this could have someing to do with my problems??
Thanks again..Foz
If your rooted, you have already unlocked the boot loader unless you relocked it. Did you? If not don't worry about unlock and flash custom recovery and flash supersu zip
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
adamfoz said:
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
All you need to do is flash SuperSU again. It's normal to lose root during an OTA update.
EDIT: didn't read properly. Have you gotten TWRP to flash yet?
Transmitted via Bacon
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
adamfoz said:
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
timmaaa said:
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
Click to expand...
Click to collapse
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
adamfoz said:
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader shouldn't lock again unless you do it yourself. The recovery (unnecessarily because you can uncheck the 'update cm recovery' option in Developer Options to keep your custom recovery) and root (no way around it) are lost during the OTA but the bootloader should remain unlocked. What response do you get when issuing the following command?
Code:
fastboot oem device-info
Please paste the results here.
Transmitted via Bacon
As soon as I'm home, I'll let you know.....
Thanks
Sent from my A0001 using XDA Free mobile app
Is there any way to root without using a pc like I did with my G3 using Stumproot?