Ok, I've looked through the help sections, I've Googled my issue [a few times now], so now time to ask for help. [which may or may not be well recieved.]
I was running Viper 3.2.6 fine for about a month, I loved the rom, however I started getting repeated FCs and errors, so I decided to recover my nandroid backup. That didn't work very well, and my phone started to bootloop... I then decided to re-flash viper, re-install twrp [first 2.4.4.0, then when that version wouldn't work, 2.4.1.0] Now when flashing Viper [any JB version I've tried] all my phone does is hang on the HTC startup screen, then reboot back to TWRP. Not to mention that Viper is the only sense ROM that my phone will accept. I've tried fastboot flashing the boot.img, fastboot erasing cache, and running the Nocturnal SD fix to give myself a clean slate to work with.
I'm S-on and HBoot 2.14. Any help that can be provided would be appreciated.
I would post a logcat, but when I tried it would not output anything since the phone is not getting to the rom boot animation.
Try flashing the boot image separately. Or going s-off. I have had troubles with twrp higher than 2.4 before I went s-off.
I always stayed on 2.3
Sent from my HTC One X using xda premium
---------- Post added at 04:53 PM ---------- Previous post was at 04:49 PM ----------
May sound silly but are you typing the word "boot" in twice when flashing?
Sent from my HTC One X using xda premium
Venomtester said:
Try flashing the boot image separately. Or going s-off. I have had troubles with twrp higher than 2.4 before I went s-off.
I always stayed on 2.3
Sent from my HTC One X using xda premium
---------- Post added at 04:53 PM ---------- Previous post was at 04:49 PM ----------
May sound silly but are you typing the word "boot" in twice when flashing?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
As far as flashing the boot image, I type fastboot flash boot boot.img.
And with the S-Off situation, I looked into that, but most of the tools for that seemingly require a working ROM, as usually they require you to have "usb debugging enabled" Like I stated previously, I've tried to solve the issue myself, to no avail thus far.
Also being hboot 2.14 twrp 2.3.x seems to not have touchscreen.
So you have no working Rom? Or can you flash viper again?
Sent from my HTC One X using xda premium
Magickalhack said:
As far as flashing the boot image, I type fastboot flash boot boot.img.
And with the S-Off situation, I looked into that, but most of the tools for that seemingly require a working ROM, as usually they require you to have "usb debugging enabled" Like I stated previously, I've tried to solve the issue myself, to no avail thus far.
Also being hboot 2.14 twrp 2.3.x seems to not have touchscreen.
Click to expand...
Click to collapse
Pretty sure you can s-off purely from boot loader.
2.3.x has working touchscreen for 2.14 and would solve all your issues. You'd have to wipe everything and reflash viper though
Sent from my One X using xda app-developers app
Also check fastboot device too make sure adb is reading your phone.
Sent from my HTC One X using xda premium
exad said:
Pretty sure you can s-off purely from boot loader.
2.3.x has working touchscreen for 2.14 and would solve all your issues. You'd have to wipe everything and reflash viper though
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Just tried 2.3.1 and no, the touchscreen didn't work, I was looking for a d/l for 2.3.3.x but haven't been able to find one. all of the ones I have found have been removed, or changed to 2.4.4.0
I would be quite greatful if you could point me in the direction of a 2.3.3.x twrp that works.
With S-Off, all the guides I've found by searching XDA [and google, which usually points me back to XDA] state that I need to start with USB debugging enabled, I even tried to start the process in fastboot... still no-go.
So you have no working Rom? Or can you flash viper again?
Click to expand...
Click to collapse
None, Every time I try venom it looks like it flashes just fine, says it's successful, however I just end up looking at twrp again.
Venomtester said:
Also check fastboot device too make sure adb is reading your phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I did fastboot devices I got:
HT26PW300712 fastboot
Click to expand...
Click to collapse
https://dl.dropbox.com/u/19685555/openrecovery-twrp-2.3.3.1-evita.img
MD5: D903047E6E871ACB8F99834C30EB8307
As for the USB debugging. It's just so you can use ADB to boot to fastboot. You can go into bootloader and go to fastboot and then skip step 3. -_-
http://forum.xda-developers.com/showthread.php?t=2155071
Just trust me, Install TWRP 2.3.3.1, reflash viper (wipe everything first, cache, dalvik, system, factory reset) and your fine, or S-OFF and then do it or vice versa, whatever you want.
---------- Post added at 06:17 PM ---------- Previous post was at 06:02 PM ----------
I forgot to add, and I am so sorry, to do fastboot erase cache after flashing twrp 2.3.3.1, just in case.
exad said:
https://dl.dropbox.com/u/19685555/openrecovery-twrp-2.3.3.1-evita.img
MD5: D903047E6E871ACB8F99834C30EB8307
As for the USB debugging. It's just so you can use ADB to boot to fastboot. You can go into bootloader and go to fastboot and then skip step 3. -_-
http://forum.xda-developers.com/showthread.php?t=2155071
Just trust me, Install TWRP 2.3.3.1, reflash viper (wipe everything first, cache, dalvik, system, factory reset) and your fine, or S-OFF and then do it or vice versa, whatever you want.
---------- Post added at 06:17 PM ---------- Previous post was at 06:02 PM ----------
I forgot to add, and I am so sorry, to do fastboot erase cache after flashing twrp 2.3.3.1, just in case.
Click to expand...
Click to collapse
For s-off, if you don't use supercid, it doesn't seem to work, I did not use super cid, since I didn't need to to unlock my bootloader. I tried that method already.
Though, 2.3.3.1 is working; but viper XL 3.2.6 is still fighting with me... Now it's just hanging at the HTC boot screen with the annoying red script.
Magickalhack said:
For s-off, if you don't use supercid, it doesn't seem to work, I did not use super cid, since I didn't need to to unlock my bootloader. I tried that method already.
Though, 2.3.3.1 is working; but viper XL 3.2.6 is still fighting with me... Now it's just hanging at the HTC boot screen with the annoying red script.
Click to expand...
Click to collapse
Did you fastboot erase cache then wipe everything and reinstall viper after installing twrp 2.3.3.1? If so:
http://forum.xda-developers.com/showthread.php?t=2212737
Do this. Then soff then ruu with your bootloader kept unlocked then reinstall twrp 2.3.3.1 then flash viper
Sent from my One X using xda app-developers app
exad said:
Did you fastboot erase cache then wipe everything and reinstall viper after installing twrp 2.3.3.1? If so:
http://forum.xda-developers.com/showthread.php?t=2212737
Do this. Then soff then ruu with your bootloader kept unlocked then reinstall twrp 2.3.3.1 then flash viper
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Followed your instructions to the letter[I actually wiped everything twice before installing Viper.], same result, still hanging at the white HTC screen. I'm going to keep trying though. Thank you for the help thus far.
Magickalhack said:
Followed your instructions to the letter[I actually wiped everything twice before installing Viper.], same result, still hanging at the white HTC screen. I'm going to keep trying though. Thank you for the help thus far.
Click to expand...
Click to collapse
I've seen this before. You will have to s-off and ruu so follow my last post.
Sent from my One X using xda app-developers app
exad said:
I've seen this before. You will have to s-off and ruu so follow my last post.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
The only issue, is that it requires adb; since I cannot get a rom to load; when I adb, it just outputs device not found. I was able to find the file to hex edit using twrp file manager, and edited the right part, but it won't let me over-write the original file... any suggestions?
Magickalhack said:
The only issue, is that it requires adb; since I cannot get a rom to load; when I adb, it just outputs device not found. I was able to find the file to hex edit using twrp file manager, and edited the right part, but it won't let me over-write the original file... any suggestions?
Click to expand...
Click to collapse
You should be able to adb from recovery no?
Sent from my One X using xda app-developers app
exad said:
You should be able to adb from recovery no?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I can adb sideload; but when I try to run the commands it just keeps saying "error: closed" I'll try again though.
Magickalhack said:
I can adb sideload; but when I try to run the commands it just keeps saying "error: closed" I'll try again though.
Click to expand...
Click to collapse
Sorry I hadnt had to do this till now. OK here's what you need to do. In recovery advanced. Go to terminal command select root dir "/". And then do the "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" on your phone. This will pull the file. Mount your SD card in twrp and hex edit the mmcblk0p4 file on your sdcard like in my guide then save it in the same spot, make sure file size matches then go back to terminal command and select the root "/" directory again and type
"dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4" from your phone. This will push the edited file back.
This is a bit more advanced but will work since you cannot adb. Adb just allows you to use the phones terminal remotely. Instead were actually using it on the phone.
Sent from my One X using xda app-developers app
exad said:
Sorry I hadnt had to do this till now. OK here's what you need to do. In recovery advanced. Go to terminal command select root dir "/". And then do the "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4" on your phone. This will pull the file. Mount your SD card in twrp and hex edit the mmcblk0p4 file on your sdcard like in my guide then save it in the same spot, make sure file size matches then go back to terminal command and select the root "/" directory again and type
"dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4" from your phone. This will push the edited file back.
This is a bit more advanced but will work since you cannot adb. Adb just allows you to use the phones terminal remotely. Instead were actually using it on the phone.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
actually, I had considered something similar, I just didn't know what directory I would have needed. I'll try this out and let you know.
Magickalhack said:
actually, I had considered something similar, I just didn't know what directory I would have needed. I'll try this out and let you know.
Click to expand...
Click to collapse
I tested it before telling you so it will work. then you can s-off.
Sent from my One X using xda app-developers app
exad said:
I tested it before telling you so it will work. then you can s-off.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
It's not liking the: adb shell su -c "/data/local/tmp/soffbin3" command. It's outputting: /sbin/sh: su: not found
I flashed SuperSU and I'm getting the same error.
Magickalhack said:
It's not liking the: adb shell su -c "/data/local/tmp/soffbin3" command. It's outputting: /sbin/sh: su: not found
I flashed SuperSU and I'm getting the same error.
Click to expand...
Click to collapse
Sorry man, I fell asleep. You still stuck at this part?
Sent from my One X using xda app-developers app
Related
My cwm cannot find my sd card so that means I can't flash zip files. Can anyone help me get cwm 4.0.0.9? Currently I have cwm 5.0.2.7
Sent from my myTouch 4G Slide using xda premium
What's the error? Is it that weird Lum thing?
Sent from my Bulletproof_Doubleshot using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Also the one your on is the most stable, have you tried messing with your SD? This happens to me every once in a while. I just reboot.
Sent from my Bulletproof_Doubleshot using xda app-developers app
AgentCherryColla said:
What's the error? Is it that weird Lum thing?
Sent from my Bulletproof_Doubleshot using xda app-developers app
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
Also the one your on is the most stable, have you tried messing with your SD? This happens to me every once in a while. I just reboot.
Sent from my Bulletproof_Doubleshot using xda app-developers app
Click to expand...
Click to collapse
I think its the lum thing when using terminal emulator but some told me to flash 5.0.2.7 and I did and it's messed up
Sent from my myTouch 4G Slide using xda premium
Is there a problem with the true official CWM release or are you just wanting to change? And at this point, unless you are trying to apply an "update.zip" file you don't need access to your external card.....unless I am just misunderstanding your issue. ADB will flash your new recovery directly to the correct partition on your internal system memory. Won't it??
BTW Agent.....what is that weird "Lum" thing? I've not run across that term.
its the error with opening sdcards on cwm 6.x
xmc wildchild22 said:
its the error with opening sdcards on cwm 6.x
Click to expand...
Click to collapse
Thank you XMC....I'm always anxious to learn. :good:
Do you have any idea why that type of error would pop up out of the clear blue like that?
WeekendsR2Short said:
Is there a problem with the true official CWM release or are you just wanting to change? And at this point, unless you are trying to apply an "update.zip" file you don't need access to your external card.....unless I am just misunderstanding your issue. ADB will flash your new recovery directly to the correct partition on your internal system memory. Won't it??
BTW Agent.....what is that weird "Lum" thing? I've not run across that term.
Click to expand...
Click to collapse
Can you help me with this step by step
Sent from my myTouch 4G Slide using xda premium
K7Cobb said:
Can you help me with this step by step
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
You really won't have any problems. I promise. It flashes just like any other version of CWM thru adb. Just download it from my "Tools" thread, place it where you normally flash a file from, rename the file to boot.img. Then from your command window on your computer you just do the following string of commands:
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Remember? :good:
flash boot?
WeekendsR2Short said:
You really won't have any problems. I promise. It flashes just like any other version of CWM thru adb. Just download it from my "Tools" thread, place it where you normally flash a file from, rename the file to boot.img. Then from your command window on your computer you just do the following string of commands:
reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Remember? :good:
Click to expand...
Click to collapse
Hang on, isn't he trying to flash his recovery? I've never done it through fastboot, but I can't help but think that flashing a recovery image to the boot partition won't turn out well... There is an option in fastboot to flash recovery, but again, I've never used it.
The way I've always flash recovery images is (in terminal emulator or ADB)
flash_image recovery /sdcard/name-of-recovery.img
As I was looking up this command, I saw someone (well, not just anyone, kornyone) suggest using ROM Manager... Although you would, of course, have to flash an older version of CWM.
My guess could be stupid but try redownloading cwm and reflash cwm recovery ...
Sent from my myTouch_4G_Slide using xda app-developers app
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
K7Cobb said:
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
Click to expand...
Click to collapse
It's an Android command, you need to either run it through ADB Shell or through the Terminal Emulator (You ran it directly in the Windows command line)
Do you have ADB and fastboot setup? If not, go download Android SDK from Google and get it installed. (Be sure to install Platform Tools as well as Tools)
If you haven't setup the Android SDK before, you'll need to install the Java SDK too.
The second two commands he provided are not ADB commands, they should be run directly from the directory where fastboot is installed, which is the Android SDK Install location\platform-tools.
The default Android SDK install location (as of the new version I downloaded yesterday) is C:\Users\(Your Name)\AppData\Local\Android\android-sdk . The old default location was C:\Program Files (x86)\Android\android-sdk . I like that one better. You can use whichever you wish, just be sure you remember where it is.
I can't post links, otherwise I'd link you to a guide. Sorry :/
Nvm thank you all
Sent from my myTouch 4G Slide using xda premium
Sompom said:
Hang on, isn't he trying to flash his recovery? I've never done it through fastboot, but I can't help but think that flashing a recovery image to the boot partition won't turn out well... There is an option in fastboot to flash recovery, but again, I've never used it.
The way I've always flash recovery images is (in terminal emulator or ADB)
flash_image recovery /sdcard/name-of-recovery.img
As I was looking up this command, I saw someone (well, not just anyone, kornyone) suggest using ROM Manager... Although you would, of course, have to flash an older version of CWM.
Click to expand...
Click to collapse
Your way will work but I promise the ADB fastboot flash sequence will too. It's the only way I've ever flashed my recoveries. Always more than one way to skin a cat.
---------- Post added at 10:49 PM ---------- Previous post was at 10:37 PM ----------
K7Cobb said:
@Weekend um says something about reboot is not recognized as an external command,operable program or batch file. Have any idea as to why this shows and could you help with this problem
Click to expand...
Click to collapse
Sorry......I just kinda took something for granted. (as usual)
Before you can run that string I told you about you have to tell your system it is an ADB command. ACTUALLY it's like this:
ADB reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Sorry for my oversight. I hope it didn't cause you much grief.
I do the stuff correct. But when I go to clock work it still says 5027
Sent from my myTouch 4G Slide using xda premium
So when you enter the command it tells you "sending image" and then the time?
After that it tells you "writing image" then the time and then something to the effect of "transfer complete"? If it does then somehow you've gotten the images confused and renamed the 5.0.2.7 image and put that one in your flashing folder and not the 4.0.0.9 image.
It's always your choice what you run on your phone but I still don't understand your opposition to the official CWM release. ANYway....Good Luck in your attempt.
WeekendsR2Short said:
So when you enter the command it tells you "sending image" and then the time?
After that it tells you "writing image" then the time and then something to the effect of "transfer complete"? If it does then somehow you've gotten the images confused and renamed the 5.0.2.7 image and put that one in your flashing folder and not the 4.0.0.9 image.
It's always your choice what you run on your phone but I still don't understand your opposition to the official CWM release. ANYway....Good Luck in your attempt.
Click to expand...
Click to collapse
Omg it does not work Clearly if I'm having problems. Not meant to be taken in a mean way but I keep telling people the same thing
Sent from my myTouch 4G Slide using xda premium
Omg. What is wrong with this???!?!?!?!?!? I need MAJOR HELP!!!
Sent from my myTouch 4G Slide using xda premium
What I'm trying to find out is how in the crap you got 5.0.2.7 on your phone to start with. If you flashed it thru terminal emulator you can put 4.0.0.9 on there the very same way. If you flashed it thru ADB you can put 4.0.0.9 on there the very same way. See what I'm saying? Have you ever flashed anything or did you get it on there thru maybe Rom Manager. I'm just looking for a clue. SEE? I know you're having a problem but we need to more than "it's not working".
K7Cobb said:
I do the stuff correct. But when I go to clock work it still says 5027
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I am running 5.5.0.4 and ROM manager reports the version as 5.0.2.7. Seems to work fine here.
Hastily spouted for your befuddlement
Okay so today I was tinkering with my phone when I accidentally deleted a system file that was crucial. So I went to bootloader and wiped phone (I know that was the wrong thing to do, now). So I have no ROM on my phone. I was able to ADB the ROM I need to my phone on internal storage (not /sdcard) but the problem is whenever I try to flash it, I get the following error over and over in the code area in TWRP "E: failed to mount /sdcard (invalid argument). I've gone to the mount options screen and when I try to select sdcard nothing happens, I can't select it. If it's any help, the ROM I'm trying to flash has the official page here http://forum.xda-developers.com/showthread.php?t=1804223 and the ROM I was on before this whole thing is here http://forum.xda-developers.com/showthread.php?t=1868236 . Any help is greatly appreciated, I really need this phone fixed!
EDIT: Alright, so I flashed stock recovery, relocked, and then used my friend's PC (thanks man!) and now my phone is in perfect working condition. Just re-rooted and re-unlocked the bootloader in like 10 minutes, which is funny because it took me like an hour and a half the first time. Anyways, thank you to all the users on this forum for helping me. Appreciate it!
NEVER Factory Reset or Clear Storage from bootloader it'll screw up your storage inside of twrp. I tried formatting storage afterwards in twrp and in windows and it still didn't help twrp see it. I ended up running the ruu again.
easiest thing to do is run the ruu again, reunlock bootloader, flash twrp and flash rom. then never factory reset or clear storage in bootloader again.
if you find another method let me.
DvineLord said:
NEVER Factory Reset or Clear Storage from bootloader it'll screw up your storage inside of twrp. I tried formatting storage afterwards in twrp and in windows and it still didn't help twrp see it. I ended up running the ruu again.
easiest thing to do is run the ruu again, reunlock bootloader, flash twrp and flash rom. then never factory reset or clear storage in bootloader again.
if you find another method let me.
Click to expand...
Click to collapse
Okay, sorry what what's the ruu and how do I run it again?
EDIT: So is the ruu the stock ROM? I've done some googling and it appears that it's something to do with exe file. I'm on a Mac, but I can get access to a PC if it's necessary.
RollTribe said:
Okay, sorry what what's the ruu and how do I run it again?
EDIT: So is the ruu the stock ROM? I've done some googling and it appears that it's something to do with exe file. I'm on a Mac, but I can get access to a PC if it's necessary.
Click to expand...
Click to collapse
And youll have to learn some simple adb commands tto relock your bootloader..or it won't work someone correct me if wrong
Hi guys yep you'll need to do some adb work to relock for ruu. However... if you still have recovery? You could try flashing a clean ROM. Then flash the cm10 over that. Of course youll need to delete cache,s before flashing cm10. I'd give that a shot first.
(Edit) I just noticed you having the mount issue also... ignore that. Just check you PC it should still show up. And it may ask you to format the drive? Your OK to do that fat32.
Sent from my One X using xda premium
subarudroid, the sdcard partition is fubar that's why he needs to ruu. reread the posts.
subarudroid said:
Hi guys yep you'll need to do some adb work to relock for ruu. However... if you still have recovery? You could try flashing a clean ROM. Then flash the cm10 over that. Of course youll need to delete cache,s before flashing cm10. I'd give that a shot first.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I can't flash any ROM because I keep getting that error mentioned in the original post.
let us know when you relock your bootloader and ruu back to stock
boot into bootloader run "fastboot oem lock" then run the ruu
You still have recovery. Right? You should still be OK. Twrp is not letting you mount SD. Right?
Sent from my One X using xda premium
subarudroid said:
You still have recovery. Right? You should still be OK. Twrp is not letting you mount SD. Right?
Sent from my One X using xda premium
Click to expand...
Click to collapse
He needs to relock bl and ruu ..download aan ruu. That will be ok. If you need help with adb check out gunnymans stickied thread
Easiest way to fix is to connect phone to pc, then select mount, mount usb in twrp and windows will prompt you to format.
Then once that is done you can copy your rom of choice across unmount and flash.
Sent from my HTC One XL using xda premium
thejosh86 said:
Easiest way to fix is to connect phone to pc, then select mount, mount usb in twrp and windows will prompt you to format.
Then once that is done you can copy your rom of choice across unmount and flash.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
A little reading will the trick for u he wiped from bootloader menu and now cannot mount through twrp
Twrp is known for having mount issue. I'm tell in ya if you USB to PC it will still find the SD as long as you have the HTC drivers installed. Unless your twrp is gone? Then you need to ruu.
Sent from my One X using xda premium
subarudroid said:
You still have recovery. Right? You should still be OK. Twrp is not letting you mount SD. Right?
Sent from my One X using xda premium
Click to expand...
Click to collapse
omario8484 said:
He needs to relock bl and ruu ..download aan ruu. That will be ok. If you need help with adb check out gunnymans stickied thread
Click to expand...
Click to collapse
Yes, I still have recovery and twrp is not letting me mount sd card. I'm trying to get the ruu to work, however, I have a Mac and getting it to work in a third party program like Wine or Parallels isn't easy, but I'm making progress. If there's another way to run the ruu on Mac, let me know.
I don't know jack [email protected] about Mac. Wish I had money for one of those. any Mac genius's out there?
Sent from my One X using xda premium
subarudroid said:
I don't know jack [email protected] about Mac. Wish I had money for one of those. any Mac genius's out there?
Sent from my One X using xda premium
Click to expand...
Click to collapse
Twrp is reliable I think u got it mixed up but cwm is known for having mount issues:angel: and @op did y relock bl?
omario8484 said:
Twrp is reliable I think u got it mixed up but cwm is known for having mount issues:angel: and @op did y relock bl?
Click to expand...
Click to collapse
CWM doesn't work at all on the HOX. I'll find the TWRP thread on it for you.
---------- Post added at 08:24 PM ---------- Previous post was at 08:11 PM ----------
I don't want to start any arguments or flame jobs. evidence or help if you will.
http://forum.xda-developers.com/showthread.php?t=1630459
http://forum.xda-developers.com/showthread.php?t=1808068
Here are just a few of several that have the same issue with twrp. Just as I did when I rooted my HOX.
subarudroid said:
CWM doesn't work at all on the HOX. I'll find the TWRP thread on it for you.
---------- Post added at 08:24 PM ---------- Previous post was at 08:11 PM ----------
I don't want to start any arguments or flame jobs. evidence or help if you will.
http://forum.xda-developers.com/showthread.php?t=1630459
http://forum.xda-developers.com/showthread.php?t=1808068
Here are just a few of several that have the same issue with twrp. Just as I did when I rooted my HOX.
Click to expand...
Click to collapse
But that was way back when its young and fresh days now its quite stable
---------- Post added at 03:40 AM ---------- Previous post was at 03:38 AM ----------
And second example was cwm. And cwm does work but not the international version we have an unofficial unreliable build
I was using just a little sarcasm about cwm. that second thread does in fact discuss the problem with twrp as well. I just hate to see rolltribe go though all the trouble of ruu when it may be possible not to do so.
Cheers
Sent from my One X using xda premium
subarudroid said:
I was using just a little sarcasm about cwm. that second thread does in fact discuss the problem with twrp as well. I just hate to see rolltribe go though all the trouble of ruu when it may be possible not to do so.
Cheers
Sent from my One X using xda premium
Click to expand...
Click to collapse
That's what I was aiming for as well - why ruu when there's an easier way that should work providing the right drivers etc are installed.
I wiped my phone via bootloader 3 times in one evening by being to quick on the volume to power trigger and brought it back using what I said above.
Sent from my HTC One XL using xda premium
Hello,
I just want to say that please don't say "you should have read instructions more carefully...etc" its too late for that. I'm just trying to see if its possible to get my HOX working again so its not a brick. So please, if you can help me, I will gladly donate to you.
I have a HTC ONE XL (AT&T). I saw a thread today on XDA saying 2.2 was able to be rooted, so I decide to root my HOX. It took a lot of courage, but I was able to root it and unlock the bootloader.
Everything was going great, I decided to flash CM10, the newest one: cm-10-20121025-EXPERIMENTAL-evita.zip. along with gapps-jb-20121011-signed.
First mistake: I did not backup
Recovery is TWRP v2.3.1.0
I wiped cache, dalvik cache, and system, then flashed CM10
Then i flashed GAPPS
I thought I had everything in the bag, rebooted it and let it do its thing. People say the first boot took long time (~5 mins) I gave it 10 mins. Nothing, its stuck on the boot loop.
Then I retried this 2 other times, same thing.
I panicked and accidentally hit factory reset, and managed to clear everything, both of the flashable files (CM10 and GAPPS) from my HOX, now all i can do is go into TWRP recovery. If i try to reboot into bootloader system or recovery it says "NO OS installed! Are you sure you wish to reboot?"
So please, can anyone help me, this was a very costly mistake, but I'm trying to fix it.
CLIFFS:
-Made mistake of not backing up
-Now only boots to TWRP, no flashable files.
First of all bro, you did everything right in the first place except flash the boot.img seperate using fastboot. That's why you bootlooped bc you had no kernel.
Second, don't worry lol. plug in phone to your computer and enter twrp, choose "mount". Get on your computer and download Rom of choice. Once downloaded, extract Rom and seperate the boot.img. rezip Rom. Transfer Rom onto phone.
fastboot boot.img, then flash the Rom through twrp. Then your golden
Sent from my HTC One XL using xda premium
InflatedTitan said:
First of all bro, you did everything right in the first place except flash the boot.img seperate using fastboot. That's why you bootlooped bc you had no kernel.
Second, don't worry lol. plug in phone to your computer and enter twrp, choose "mount". Get on your computer and download Rom of choice. Once downloaded, extract Rom and seperate the boot.img. rezip Rom. Transfer Rom onto phone.
fastboot boot.img, then flash the Rom through twrp. Then your golden
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hi inflatedtitan,
Thanks for replying, you are a lifesaver, i almost bought another phone... because i thought i was done for.
However, im not sure what you mean exactly as i have not done this flashing before. so i downloaded the rom cm10.
1. so i unizip the rom on my computer
2. copy rom onto phone
3. flash??
thanks please clarify thanks again.
ur a lifesaver.
EDIT: when i hit mount, there are 4 boxes, what do i check (i cant select SD card)? and when i hit mount, it shows up on my computer but asks me to format disk. should i do it?!
As you already factory reseted and lost everything, you should format as the damage is already done lol, it'll get your sdcard back right. But when you extract cm10 on your computer you'll see the boot.img in the folder. Move it to where you have adb and fastboot. THEN rezip Rom and transfer to your phone.
Sent from my HTC One XL using xda premium
---------- Post added at 02:00 AM ---------- Previous post was at 01:59 AM ----------
Do you have fastboot and adb? If so, the boot.img goes here. Fire up command prompt, type this---> fastboot flash boot boot.img
Then proceed to flash the Rom via twrp
Sent from my HTC One XL using xda premium
InflatedTitan said:
As you already factory reseted and lost everything, you should format as the damage is already done lol, it'll get your sdcard back right. But when you extract cm10 on your computer you'll see the boot.img in the folder. Move it to where you have adb and fastboot. THEN rezip Rom and transfer to your phone.
Sent from my HTC One XL using xda premium
---------- Post added at 02:00 AM ---------- Previous post was at 01:59 AM ----------
Do you have fastboot and adb? If so, the boot.img goes here. Fire up command prompt, type this---> fastboot flash boot boot.img
Then proceed to flash the Rom via twrp
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I took a screenshot
http://imgur.com/qcClC
so i copy the boot to the folder with adb and fastboot? and copy cm-10-2012... to my HOX (unchanged)?
Yes exactly, then run fastboot flash boot boot.img
After that is done, open TWRP and run the zip file
Rom will have excluded boot.img . Try it out and see what happens as you recapped. I'm not so sure as your running fastboot through the xfactor program.. but try it out, worst case is you bootloop like last time. If that happens again, you know to download android SDK tools, adb and fastboot and reinstall HTC drivers and start over
Sent from my HTC One XL using xda premium
They are many simple tutorials for rooting but do not know why you guys having hard time. Ok here is
1) You got Android SDK from google + Platform-tools + Google USB Driver -
2) Only for windows - Download htc sync ( It will install necessary htc drivers) - Link
3) Just to check if htc drivers installed properly , open "C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists).
4) In command window type " adb devices" and see output - If you get output then htc drivers installed properly.
You can skip step 3 and step 4 - These steps are only for verification
5) Goto [ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit and follow the instructions there.
6) Once you successfully root your device using above exploit then goto - [How To] Flash Custom recovery and ROMS after 2.20 root complete the steps to flash custom recovery and if you want to flash ROMS
7) To unlock BOOT LOADER use this link - [INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up , follow the instructions under " BOOTLOADER UNLOCK, SUPER CID, AND S-OFF"
You can also goto this link - [ROOT][2.20] One XL Bootloader unlock & Root guide By XsMagical - Very nice tutorial, if you find above links difficult to follow
Note* : During exploit or flashing recovery they talk about using fastboot commands, In order to execute them you need goto C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists) and then execute the commands ..
Advice - Do not flash any roms apart from xda
Sent from my HTC One XL using xda premium
uhh guys so i did the whole fastboot thing, everything looked great. but when i try to go back to recovery, im stuck at the htc quietly brilliant
"this build is for development purpose only
do not distribute..." screen. I cant get back to recovery!?
Sorry for being such a noob, i really appreciate your guyses help.
Try it a couple times, if that doesn't work reflash recovery.
donkeybat64 said:
uhh guys so i did the whole fastboot thing, everything looked great. but when i try to go back to recovery, im stuck at the htc quietly brilliant
"this build is for development purpose only
do not distribute..." screen. I cant get back to recovery!?
Sorry for being such a noob, i really appreciate your guyses help.
Click to expand...
Click to collapse
How long did you stay on that screen? Did you see the cyanogenmod boot animation at all?
Sent from my HTC One XL using xda premium
---------- Post added at 02:42 AM ---------- Previous post was at 02:31 AM ----------
Have you tried holding power and volume down? When phone flashes and goes off, release power button and keep holding volume down till you get to hboot. White screen that says fastboot, recovery, facto reset, etc
Sent from my HTC One XL using xda premium
Any progress bro?
Sent from my HTC One XL using xda premium
you don't delete boot.img from the rom, leave the original zip untouched. just make sure you flash boot.img in fastboot though. whenever i flash something in fastboot i like to run "fastboot erase cache".
NEVER factory reset in bootloader, it will mess up your sdcard.
you should rewipe and reflash everything in twrp. also verify the md5 checksums of cm10 and gapps both the md5 sums are listed at their download locations.
Fixed an gone like a teenager an his car?
WR
Sent from my HTC One X
WarRaven said:
Fixed an gone like a teenager an his car?
WR
Sent from my HTC One X
Click to expand...
Click to collapse
yep that's another thing i've asked all the querying noobs to do, changing the op to [SOLVED] when it is but to no avail :crying:
sry guys it took very long, i followed all your instructions and finally fixed it last night. I went straight to sleep because of work. Thanks again for your help, sorry for late restponse:
my solution: I followed INFLATEDTITAN's instructions. double click the cm10 rom, then take out the boot.img, copy that to where your fastboot files are, SHIFT right click, select CMD (or open cmd and use cd to change directory to folder), then type what he said w/ fastboot, make sure your connected. Then i flashed the cm10 rom, the gapps, reboot, took a couple tries.
Anyways, it works great, so smooth.... on wifi.
I have stragiht talk, and I've been getting really crappy speeds for data, from 5Mbps to 0.16.... down, interestingly, upload has not changed ~1.2 mbps. does anyone have any insight? Why DL is so slow but UL is still the same?
Crappyvate said:
yep that's another thing i've asked all the querying noobs to do, changing the op to [SOLVED] when it is but to no avail :crying:
Click to expand...
Click to collapse
Can you tell me how to edit my post? i can only edit the content, not the title.
Also I have a question on radios. From this thread: (click "this")
I have the latest cm10 nightly build, as I said in my previous post, I am on straight talk. While the radio is showing HSPA+, I'm getting edge speeds (0.16mbps) but good upload speed ~1.2mbps.
Can I use the AT&T 2.2 radio from this list? (near the bottom)
Radios for Latest CM10 versions (with radio in /system/etc/firmware)
I just rooted my phone from 2.2, and want to make sure I'm using the right one.
Thanks.
Sorry bro, can't flash radios and RILs being you have the newer hboot
Sounds like you're into aosp roms. But usually the newer sense Roms are just as amazing and usually are updated with the newer radio. However I'm using old hboot, so I can't confirm that if you flash a Rom, the included radio will also automatically flash. Can anyone reading help with the correct answer?
Sent from my HTC One XL using xda premium
InflatedTitan said:
Sorry bro, can't flash radios and RILs being you have the newer hboot
Sounds like you're into aosp roms. But usually the newer sense Roms are just as amazing and usually are updated with the newer radio. However I'm using old hboot, so I can't confirm that if you flash a Rom, the included radio will also automatically flash. Can anyone reading help with the correct answer?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks, so the only thing i can do at this point is to flash a original HTC ICS rom (basically where i started before root)?
Well like I say, I'm not even sure it'll install the new radio lol. So I'd sit tight till someone replies with the correct advice.
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
I'm in hpsa and that's about what I get too. I'll get a few tests that'll nail about 6 on download speed, sometimes I can't even get 1 lol. I wouldnt worry too much unless it gets super sluggish when you have full service
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
To begin, I have been trying to root my HTC One X and all of the methods I have tried have failed me so far. I have successfully unlocked the bootloader but that is as far as I have gotten. It will fail to push anything to my phone, busybox, superuser, etc.., anything and it will just reboot.
I am on 4.1.1 with build 3.18 and also on ATT network.
Any suggestions or anything else anyone can provide would be helpful!
I can provide more information about my phone if needed.
Thanks in advance!
Have you flashed a ROM yet? Or even put TWRP on it? You'll need those.
RollTribe said:
Have you flashed a ROM yet? Or even put TWRP on it? You'll need those.
Click to expand...
Click to collapse
I need TWRP on it instead of CWM? I tried going with the Touch CWM but nothing worked.
I will have to try TWRP instead then and update!
Thanks!
Update: I am getting the message "is not recognized as an internal or external command, operable program or batch file" when trying to flash TWRP
EdwardsNT said:
I need TWRP on it instead of CWM? I tried going with the Touch CWM but nothing worked.
I will have to try TWRP instead then and update!
Thanks!
Update: I am getting the message "is not recognized as an internal or external command, operable program or batch file" when trying to flash TWRP
Click to expand...
Click to collapse
What command are you using?
Then you're typing the command wrong lol.
Sent from my One X using xda app-developers app
RollTribe said:
What command are you using?
Click to expand...
Click to collapse
I am using the HOX all in one kit and when i select TWRP 2.5.0.0 it opens up cmd and tells me its not a recognized command.
EdwardsNT said:
I am using the HOX all in one kit and when i select TWRP 2.5.0.0 it opens up cmd and tells me its not a recognized command.
Click to expand...
Click to collapse
Firstly, don't use 2.5, use 2.3.3.1 instead.
Secondly, just try flashing the recovery manually. Download TWRP 2.3.3.1, check the md5 is correct, put it in your fastboot working directory, connect phone to pc, open command prompt within your working directory, issue the following command:
fastboot flash recovery openrecovery-twrp-2.3.3.1.img (or whatever the exact recovery filename is)
Wait for it to flash, then issue following command:
fastboot erase cache
Now your recovery should be installed.
Then all you need to do is flash a rooted ROM and you'll be rooted.
Sent from my Evita
timmaaa said:
Firstly, don't use 2.5, use 2.3.3.1 instead.
Secondly, just try flashing the recovery manually. Download TWRP 2.3.3.1, check the md5 is correct, put it in your fastboot working directory, connect phone to pc, open command prompt within your working directory, issue the following command:
fastboot flash recovery openrecovery-twrp-2.3.3.1.img (or whatever the exact recovery filename is)
Wait for it to flash, then issue following command:
fastboot erase cache
Now your recovery should be installed.
Then all you need to do is flash a rooted ROM and you'll be rooted.
Sent from my Evita
Click to expand...
Click to collapse
I got the recovery to install finally, now i am having issues with installing cm 10.1 on there >.<
EdwardsNT said:
I got the recovery to install finally, now i am having issues with installing cm 10.1 on there >.<
Click to expand...
Click to collapse
You'll have to RUU to 3.18 because of the new kernel.
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Be sure to s-off before ruu'ing to 3.18!!!
---------- Post added at 09:31 PM ---------- Previous post was at 09:30 PM ----------
So first do this http://forum.xda-developers.com/showthread.php?t=2155071
And then run the 3.18 ruu
RollTribe said:
You'll have to RUU to 3.18 because of the new kernel.
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Be sure to s-off before ruu'ing to 3.18!!!
---------- Post added at 09:31 PM ---------- Previous post was at 09:30 PM ----------
So first do this http://forum.xda-developers.com/showthread.php?t=2155071
And then run the 3.18 ruu
Click to expand...
Click to collapse
he has 3.18, he shouldn't need to ruu, he can just fastboot flash boot boot.img
exad said:
he has 3.18, he shouldn't need to ruu, he can just fastboot flash boot boot.img
Click to expand...
Click to collapse
Oh forgot about that. @OP, what is the issue you're having with CM10.1?
As exad said you'll need to use fastboot commands to flash the boot image.
Once I flash the boot.img and go back into TWRP to install from SD card, it tells me
"assert failled: getprop("ro.product.device") == "endeavoru" 11 getprop("r
E:Error executing updater binary in zip '/sdcard/cm-10.1.0-endeavoru.zip
Error flashing zip '/sdcard/cm-10.1.0-endeavoru.zip' "
EdwardsNT said:
The tutorial for S-OFF.... I am assuming working directory will be the folder with my fastboot files correct?
Click to expand...
Click to collapse
Yes, but, you don't need to do it, as I forgot you're on 3.18. It's always good to do it, though, because it can protect you from bricks.
Yeah I'd agree it's a good idea to do it. It'll save you from having to manually flash the boot.img every time you flash a ROM.
The best way to achieve s-off is while running a Sense ROM, so flash one of those and then do the s-off method.
Sent from my Evita
Ed, you're flashing something for a different device.
Sent from my HTC One XL using xda premium
EdwardsNT said:
Once I flash the boot.img and go back into TWRP to install from SD card, it tells me
"assert failled: getprop("ro.product.device") == "endeavoru" 11 getprop("r
E:Error executing updater binary in zip '/sdcard/cm-10.1.0-endeavoru.zip
Error flashing zip '/sdcard/cm-10.1.0-endeavoru.zip' "
Click to expand...
Click to collapse
Well looks like you're flashing the quad core one x cm10.1 good thing there's protection built into the rom or youd be bricked right now.
Note, not all roms have this protection so it would be wise to know what you're doing prior to doing it.
jacobas92 said:
It would also help if he flashed something for the xl lol
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I am not using the XL though I have the regular One X.. I don't know if that matters or not.
exad said:
Well looks like you're flashing the quad core one x cm10.1 good thing there's protection built into the rom or youd be bricked right now.
Note, not all roms have this protection so it would be wise to know what you're doing prior to doing it.
Click to expand...
Click to collapse
Well, thankfully this one does have the protection.
I've done flashing and rooting before, but I've never had this hard of a time -.-
Any suggestions on how to fix this issue?
EdwardsNT said:
I am not using the XL though I have the regular One X
Well, thankfully this one does have the protection.
I've done flashing and rooting before, but I've never had this hard of a time -.-
Any suggestions on how to fix this issue?
Click to expand...
Click to collapse
They'll be able to help you here http://forum.xda-developers.com/forumdisplay.php?f=1533
Beat me to it
Sent from my HTC One XL using xda premium
jacobas92 said:
Oh. You're in the wrong place. Go over to the quad-core section, they'll be able to help you.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I thought I was in the right one this entire time, I apologize!
so I've got a interesting situation. A friend managed to softbrick his Mini. I don't know how he got it in this state, but, it has TWRP installed, its copy of android does not boot, and it's S-ON. I played with RUUs for a few hours and couldn't get any of them to work. If I can get any working copy of android on it I can then get S-OFF and fix it. As far as I see there's two routes to fix this.
-Get S-OFF without using android
-Get a android ROM on there without S-OFF.
I pretty much have access to fastboot and twrp that can't flash Roms because of s on. Recoveries also have errors about mounting /system or /cache.
Any help in fixing this would be appreciated.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Adding abit more information, I tried using a RUU but get errors because of firmware version. When I get the rom.zip out of the RUU and try to use fastboot to flash it, on windows I get a error about header errors (error 32). On Linux I get errors about the file is too large.
Also, nomatter what recovery I can try, neither can mount either /system or /cache unless you format them, then after a reboot they cant be mounted again.
I had an issue where my os was completely wiped after a botched update attempt. Lol I went through every possible I could think of or find until I see something about using an external drive. So what I did was use fastboot to flash a recovery, which you already have which is good. And then from there I used an OTG cable, and connected my USB drive to it, which had a ROM zip on it and flashed it. It worked. I am bootloader unlocked but not s-off. But as long as you have a recovery you can do this. I actually wasn't even rooted.
Sent from my One Mini using XDA Premium 4 mobile app
dizzyman1180 said:
I had an issue where my os was completely wiped after a botched update attempt. Lol I went through every possible I could think of or find until I see something about using an external drive. So what I did was use fastboot to flash a recovery, which you already have which is good. And then from there I used an OTG cable, and connected my USB drive to it, which had a ROM zip on it and flashed it. It worked. I am bootloader unlocked but not s-off. But as long as you have a recovery you can do this. I actually wasn't even rooted.
Sent from my One Mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm still worried about the failing to mount /system and /cache errors. Did you have those as well?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
polaric said:
I pretty much have access to fastboot and twrp that can't flash Roms because of s on.
Click to expand...
Click to collapse
You don't need S-OFF to flash roms. As long as you unlocked the bootloader you can fastboot-flash boot, system and recovery. And so you can flash ROMs when in recovery mode.
polaric said:
I'm still worried about the failing to mount /system and /cache errors. Did you have those as well?
Click to expand...
Click to collapse
What HBOOT version do you have?
morschesholz said:
You don't need S-OFF to flash roms. As long as you unlocked the bootloader you can fastboot-flash boot, system and recovery. And so you can flash ROMs when in recovery mode.
What HBOOT version do you have?
Click to expand...
Click to collapse
HBOOT is 2.22
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Well, then it looks like the same issue as in the thread next to this one. So please go over there and perhaps you'll try my next steps written down there: http://forum.xda-developers.com/showthread.php?p=51737651
morschesholz said:
Well, then it looks like the same issue as in the thread next to this one. So please go over there and perhaps you'll try my next steps written down there: http://forum.xda-developers.com/showthread.php?p=51737651
Click to expand...
Click to collapse
I followed that and it got me a working recovery, but both twrp versions and the cwm version won't flash the cm zip, regardless if its modified, if I modify it myself or use a attached update-script. Both recoveries simply say "Failed to flash zip".
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Then you should repeat the flashing and have a look at the recovery log right after it. At TWRP it's located at /tmp/recovery.log (don't know for CWM).
Either do a
Code:
adb shell cat /tmp/recovery.log
or pull it to your pc:
Code:
adb pull /tmp/recovery.log
morschesholz said:
Then you should repeat the flashing and have a look at the recovery log right after it. At TWRP it's located at /tmp/recovery.log (don't know for CWM).
Either do a
Code:
adb shell cat /tmp/recovery.log
or pull it to your pc:
Code:
adb pull /tmp/recovery.log
Click to expand...
Click to collapse
Already tried multiple times, of course. I looked at the log and didnt see anything of value though. I can post it if you like.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
That's what I recommended in another post:
morschesholz said:
Meanwhile you could try flashing CM11. There is an edited updater-script and boot.img over here: http://forum.xda-developers.com/showthread.php?p=51613028
I used it with cm-11-20140403-NIGHTLY-m4 successfully. Maybe the edited script works with newer versions of the CM nightlies as well, but I didn't test that yet.
Click to expand...
Click to collapse
This is the 0403 CM11 nightly I modified to match the new partition layout: https://dl.dropboxusercontent.com/u/5035075/m4kk/cm-11-20140403-NIGHTLY-m4kk.zip
You should be able to flash it with the modified version of TWRP 2.7.0.5