Hi,
I have an AT&T HTC One X with no OS. I wiped it when I was trying to flash a custom ROM.
I only have access to bootloader and TWRP. Fastboot is working fine but TWRP is not. It does
mount properly, and adb sideload fails as well. I am using a Windows 7 PC and used a USB 2.0 port.
I installed some HTC Drivers from here:
http://forum.xda-developers.com/showthread.php?t=2217396
but it still says "device drivers failed to install" when I boot into recovery.
When I try to mount, it does not let me mount the sdcard. I see an E: drive on my
PC but it is inaccessible.
I have S-On, my bootloader is unlocked, and I have hboot version 2.14 if that info helps.
Does anybody have any suggestions as to what I can try next?
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
I helped him over teamviewer so I can clarify the situation. He can't mount in TWRP, it must of been a typo. It seems he cleared everything when he was trying to wipe to flash a rom. I believe it was ViperXL. He has no backup and sideload does not work as well. Hopefully that will clear things up a little bit more. I installed some newer HTC Drivers since the ones he had were old. The only thing that works seems to be fastboot at this point.
Sent from my HTC One X using Tapatalk
timmaaa said:
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
Click to expand...
Click to collapse
Sorry it was a Typo, I was not able to mount at all. The error said "unable to mount /sdcard"
Yes I have tried performing a factory reset from bootloader but the phone restarts and comes back to TWRP and then same thing.
I tried installing the ViperXL ROM but was not successful.
I was not able to flash the ROM and I tried to fix that but meanwhile looks like I wiped all what I had on my Phone, so no but I did try to flash a new boot.img after and it didnt work.
I dont think I have any TWRP backup on my phone, even though I tried flashing new TWRP but all failed.
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from here. 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 should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
timmaaa said:
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from . 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 should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
Click to expand...
Click to collapse
So I followed all the above steps as noted; I had TWRP 2.6.3.0 earlier, I flashed the new TWRP 2.6.0.0 from the link you provided.All
successfully done.
-------------------------------------------------------------------------------------------------------
C:\Fastboot>fastboot devices
HT29WW300913 fastboot
C:\Fastboot>fastboot flash recovery "openrecovery-twrp-2.6
.0.0-evita.img"
sending 'recovery' (8000 KB)... OKAY [ 1.530s]
writing 'recovery'... OKAY [ 1.900s]
finished. total time: 3.430s
C:\Fastboot>fastboot erase cache
erasing 'cache'... OKAY [ 0.120s]
finished. total time: 0.120s
C:\Fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.070s]
finished. total time: 0.070s
---------------------------------------------------------------------------------------------------------
I rebooted into recovery, still came up as TWRP 2.6.3.0, then I went to TWRP reboot and chose Recovery, phone rebooted into TWRP 2.6.0.0
Tried mounting (could not select /sd card and /cache(expected as we erased it)) and ADB sideload, got the same errors as before. Unable to mount /sdcard.
Rebooted again and it displayed TWRP 2.6.3.0
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
timmaaa said:
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did
And which recovery is currently installed?
Sent from my Evita
timmaaa said:
And which recovery is currently installed?
Sent from my Evita
Click to expand...
Click to collapse
Its 2.6.3.0, but in recovery when I go into option TWRP reboot and chose Recovery button, phone reboots into TWRP 2.6.0.0 and when I reboot it again, its 2.6.3.0
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
timmaaa said:
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
Click to expand...
Click to collapse
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
tapukakababa said:
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
Click to expand...
Click to collapse
Either one should be fine. If you have S-ON and the phone gets stuck on the HTC screen, you have to flash the boot.img. here's how to do it.
1. On your PC in the ViperXL.zip, take out the boot.img and put it in the directory where you have the adb and fastboot files.
2. Boot into fastboot.
3.Open cmd. Change the directory to the folder where you have those files.
4.type "fastboot flash boot boot.img"
5. Reboot the phone.
The phone should boot.
Sent from my One Xl using Tapatalk
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
timmaaa said:
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
So I flashed the boot image, then copied ViperXL and installed it through TWRP, it failed.
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
timmaaa said:
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
Click to expand...
Click to collapse
No I did not check the MD5, yes I'm on TWRP 2.6.0.0 and the errors it gives are as follows:
unable to mount '/cache'
unable to open zip
Error flashing zip
Always check the md5. It's possibly corrupt.
Sent from my Evita
timmaaa said:
Always check the md5. It's possibly corrupt.
Sent from my Evita
Click to expand...
Click to collapse
Yup redownloaded the file, checked/compared MD5, copied it back to the phone, removed the previous bad copy, flashed ROM successfully..., as per the message but system reboots to recovery.. is that expected?
And I still see both the TWRP's 2.6.3.0 and 2.6.0.0 the phone needs couple reboots in order to get to TWRP 2.6.0.0 but automatic reboot is in TWRP 2.6.3.0 whats the deal here?
I have no idea why your recovery is acting like that. Hopefully someone else can chime in on that.
Sent from my Evita
Related
Hi I recently put ext4 recovery on my sensation, but I just realised earlier backups don't seem to work on it.
Could anyone please help me out trying to reset it to CMW, because that way I can restore my backups without problems.
I tried to flash using fastboot, but when I enter the command "fastboot flash recovery recovery.img"
I get a message": "writing recovery blabla
writing recovery ... FAILED (remote: not allowed)
finished blabla"
When I check my sd card, I see the recovery.img on the root of it.
I reboot into recovery, and it's still 4ext
Please help me!
Thanks,
Sean
Download the PG518IMG.zip
multiupload[dot]com/ECVA5V4ED3
Place it on your SD card
Reboot to boot-loader (Power + Vol down)
//Dennis/
Sent from my HTC Sensation z710e
Hi,
thanks for your answer, but your link isn't available, and I don't believe that doing this will overwrite ext4.
I tried it a few times before.
seanw712 said:
Hi,
thanks for your answer, but your link isn't available, and I don't believe that doing this will overwrite ext4.
I tried it a few times before.
Click to expand...
Click to collapse
Sorry hadn't noticed that...
I've attached the file. You can also try
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
DennisBold said:
Sorry hadn't noticed that...
I've attached the file. You can also try
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi, thanks a lot, you really helped me...
It seems I was wrong, this did overwrite my existing recovery!
Hi all,
I have the att one xl, carrier unlocked. I used it for a month now in my country with no problems, I had it rooted,bootloader unlocked etc.
I used clockworkMod to backup everything and to try to flash this ROM
http://forum.xda-developers.com/showthread.php?t=2075783
I followed the instructions on this page
http://www.teamandroid.com/2013/04/09/update-htc-one-xl-hatka-android-411-jelly-bean-custom-rom/2/
I got to the final step and rebboted phone. After that, problems began. It runs again the clockworkmod recovery and it says it cannot mount the sdcard. I read that i have to flash the stock ROM. I tried that getting the recovery.img from the clockworkmod backup folder nad now when phone reboots,it starts the clockworkmod but when i make i choice on this it goes for rebooting...
Any help please????
xtrg said:
Hi all,
I have the att one xl, carrier unlocked. I used it for a month now in my country with no problems, I had it rooted,bootloader unlocked etc.
I used clockworkMod to backup everything and to try to flash this ROM
http://forum.xda-developers.com/showthread.php?t=2075783
I followed the instructions on this page
http://www.teamandroid.com/2013/04/09/update-htc-one-xl-hatka-android-411-jelly-bean-custom-rom/2/
I got to the final step and rebboted phone. After that, problems began. It runs again the clockworkmod recovery and it says it cannot mount the sdcard. I read that i have to flash the stock ROM. I tried that getting the recovery.img from the clockworkmod backup folder nad now when phone reboots,it starts the clockworkmod but when i make i choice on this it goes for rebooting...
Any help please????
Click to expand...
Click to collapse
First off, I'd use TWRP since it's compatible with all ROMs and CWM has very little compatibility with our phone.
To do that, download TWRP 2.3.3.1 Check MD5
boot to bootloader/fastboot
then fastboot flash recovery twrpfilename.zip
then wipe cache, dalvik, system, factory reset in TWRP
Flash rom.
If you are on hboot 1.14, you then need to extrract the boot.img from the ROM's zip and fastboot flash boot boot.img
As for the not able to mount SDCard, did you factory reset in the bootloader?
Hey my friend thnks for the reply. I'll try all of these right now. If u can please follow the thread, I might have more questions...Thnks again!
I've reache the point where i mount again my sd card and making all thw wipe things...
I' ve installed the rom but after it says that is succesfully installed and rebooting it shows the htc logo and after that...nothing!
The device turns off(or at least i think it is)black screen, no charge little orange light...But when it comes to this mode, I can hear the soun of the pc like when u do connect a device!
What am I doing wrong?
And yes I have hboot 1.14. What is the correct sequence in the actions????
Did you extract the boot.img from the rom and then flash it using fastboot?
Sent from my One X using xda app-developers app
exad said:
First off, I'd use TWRP since it's compatible with all ROMs and CWM has very little compatibility with our phone.
To do that, download TWRP 2.3.3.1 Check MD5
boot to bootloader/fastboot
then fastboot flash recovery twrpfilename.zip
then wipe cache, dalvik, system, factory reset in TWRP
Flash rom.
If you are on hboot 1.14, you then need to extrract the boot.img from the ROM's zip and fastboot flash boot boot.img
As for the not able to mount SDCard, did you factory reset in the bootloader?
Click to expand...
Click to collapse
exad said:
Did you extract the boot.img from the rom and then flash it using fastboot?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yes I did.
Booting in bootloader
going to fastboot and it changes to fastboot usb
typing in command prompt
>fastboot flash boot boot.img
I get
sending 'boot' (6076 KB)...
OKAY [ 0.901s]
writing 'boot'...
OKAY [ 1.528s]
finished. total time: 2.430s
from the bootloader options i choose recovery
phone restarts on twrp
I swipe everything out
I go to install and choose the zip file from the sd card which contains the rom
installation starts ok and it finishes saying all ok
I choose reboot in system from the twrp
(In this point i get a question on fixing root permissions and i choose yes)
after rebboting, htc logo comes up and after that...nothing...
Please help...
xtrg said:
Yes I did.
Booting in bootloader
going to fastboot and it changes to fastboot usb
typing in command prompt
>fastboot flash boot boot.img
I get
sending 'boot' (6076 KB)...
OKAY [ 0.901s]
writing 'boot'...
OKAY [ 1.528s]
finished. total time: 2.430s
from the bootloader options i choose recovery
phone restarts on twrp
I swipe everything out
I go to install and choose the zip file from the sd card which contains the rom
installation starts ok and it finishes saying all ok
I choose reboot in system from the twrp
(In this point i get a question on fixing root permissions and i choose yes)
after rebboting, htc logo comes up and after that...nothing...
Please help...
Click to expand...
Click to collapse
You're wiping after flashing the boot.img... so you need to reflash the boot.img don't wipe anything, just fastboot flash boot boot.img and then reboot the phone.
Okay, I tried putting a new rom on my at&t one xl, and it did something horribly wrong. I was able to get to recovery and it told me I had no operating system, the I tried flashing a new rom again. At this point it restarted the phone got stuck at the splash screen and now I cant even get to recovery just the fast boot and boot loader. Any help would greatly appreciated.
You haven't given any of the vital information required to help you. Please provide the following:
hboot/firmware version
S-on or s-off
Recovery version
What ROM(s) you were trying to flash
What you have done to try to recover
Sent from my Evita
timmaaa said:
You haven't given any of the vital information required to help you. Please provide the following:
hboot/firmware version
S-on or s-off
Recovery version
What ROM(s) you were trying to flash
What you have done to try to recover
Sent from my Evita
Click to expand...
Click to collapse
hboot 1.14.002
s is off
cant remember recovery version since I can't access it
I had viper rom and I was going to cyanogen mod 10.1
and I thought I had a titanium backup but my whole sd card go deleted, so I mounted my sd card and got the rom again and flashed it and at that point I couldn't go back to recovery
Did you read the OP for cm10.1? It states in the requirements that you must RUU up to the latest (3.18) to run that ROM. In terms of your recovery, just flash it again from fastboot.
Sent from my Evita
timmaaa said:
Did you read the OP for cm10.1? It states in the requirements that you must RUU up to the latest (3.18) to run that ROM. In terms of your recovery, just flash it again from fastboot.
Sent from my Evita
Click to expand...
Click to collapse
I must of completely overseen that. and sir the only option I have on my boot is fast boot, recovery, factory reset, clear storage, simlock, image crc, and power down. I don't know how to even flash things at this point.
and only options I fast boot are bootloader, reboot, reboot boot loader and powerdown
That's all you need to RUU, it's an exe file that you just run while your phone is connected in fastboot mode. You'll need top flash your recovery again, then you can flash a ROM.
Download the RUU
Run the RUU
Download recovery
Flash recovery
Flash ROM
The fastboot command to flash the recovery is:
fastboot flash recovery "recovery.img"
(The exact recovery filename, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery on your phone, mount usb storage, copy ROM to phone, flash ROM.
Sent from my Evita
Thanks guys. My kids an idiot and did this today to his phone (my old phone). He got the information from you guys and left it to me to fix when I got home.
timmaaa said:
That's all you need to RUU, it's an exe file that you just run while your phone is connected in fastboot mode. You'll need top flash your recovery again, then you can flash a ROM.
Download the RUU
Run the RUU
Download recovery
Flash recovery
Flash ROM
The fastboot command to flash the recovery is:
fastboot flash recovery "recovery.img"
(The exact recovery filename, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery on your phone, mount usb storage, copy ROM to phone, flash ROM.
Sent from my Evita
Click to expand...
Click to collapse
Cool glad ur all set
Sent from my HTC One XL using xda premium
I have a friend who put twrp and cid 111111111 hboot 2.14 had viper couldnt make calls wiped data and he deleted his sdcard now he has no OS
i was able to flash recovery on his phone but thats where i'm at..
scrizo said:
I have a friend who put twrp and cid 111111111 hboot 2.14 had viper couldnt make calls wiped data and he deleted his sdcard now he has no OS
i was able to flash recovery on his phone but thats where i'm at..
Click to expand...
Click to collapse
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
exad said:
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
Click to expand...
Click to collapse
You're too fast man
Sent from my Evita
I flashed 2.5.0.0
S-Off
I don't know he did have problems with TWRP not being able to write to .twrp file. If he corrupted the sdcard is he fubared
exad said:
S-ON or S-OFF?
What version of recovery did you flash?
Did he corrupt SD card by doing a factory reset in bootloader or just format it?
Click to expand...
Click to collapse
*UPDATE*
I am using adb push ViperXL-3.2.7 /sdcard/ and it appears to be pushing the file so far.
I am able to do this in recovery mode
Tried to install ViperXL failed.
Unable to mount '/sdcard'
Unable to mount storage
TWRP 2.5 is full of bugs. Download TWRP 2.6 from here. 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 enter recovery and try flashing ROM again.
Sent from my Evita
After flashing twrp 2.6 you may have to wipe the SD card within twrp if the SDCARD is corrupt.
problem htc.dialer stops working using viperxl
timmaaa said:
TWRP 2.5 is full of bugs. Download TWRP 2.6 from here. 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 enter recovery and try flashing ROM again.
Sent from my Evita
Click to expand...
Click to collapse
scrizo said:
problem htc.dialer stops working using viperxl
Click to expand...
Click to collapse
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
I had flashed your 2.6 twrp and wiped everything and did what you said then pushed the viperxl on there and installed and did the wipe data do i still need to reflash the cwm touch and etc
exad said:
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
Click to expand...
Click to collapse
did everything you said still the same error with htc.dialer i have a htc onex can i transfer my dialer to his phone?
exad said:
That's because there was CWM touch on there previously.
To fix:
reflash CWM touch
fastboot erase cache
flash cwm older NON touch
fastboot erase cache
reflash twrp 2.6
fastboot erase cache
fasctory reset IN TWRP 2.6
Then wipe everything and flash viper XL
Click to expand...
Click to collapse
No that's the only way to fix it.
Sent from my One X using xda app-developers app
Dang it is not working then. still have the issue with the dialer not working.
exad said:
No that's the only way to fix it.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
If this helps he has build # 3.17
Did you flash the three different versions of recovery?
Sent from my Evita
you mean cwm touch
cwm older
twrp?
timmaaa said:
Did you flash the three different versions of recovery?
Sent from my Evita
Click to expand...
Click to collapse
Yeah
Sent from my Evita
yes I flashed CWM touch
I flashed non touch
I flashed twrp 2.6
factory reset
installed viperxl
wiped data
timmaaa said:
Yeah
Sent from my Evita
Click to expand...
Click to collapse
You should have wiped everything (cache/dalvik cache/factory reset/system) before flashing Viper.
Sent from my Evita
Hi,
I was trying to install the cyanogenmod 11 on my device. I have successfully unlocked the boot loader and installed the clockworkmod recovery, but I copied the zip files into the sdcard instead of the root folder. When I tied to install the cyanogenmod 11 from the recovery mode, I could not find the zip file in the device, so I powered off my phone thinking I could start again, but when I have turned the phone on the screen was stuck on the HTC logo.
And now I do not know what to do. Can you help?
Thanks in advance !
AndySOS said:
Hi,
I was trying to install the cyanogenmod 11 on my device. I have successfully unlocked the boot loader and installed the clockworkmod recovery, but I copied the zip files into the sdcard instead of the root folder. When I tied to install the cyanogenmod 11 from the recovery mode, I could not find the zip file in the device, so I powered off my phone thinking I could start again, but when I have turned the phone on the screen was stuck on the HTC logo.
And now I do not know what to do. Can you help?
Thanks in advance !
Click to expand...
Click to collapse
Did you wipe the device prior to install? Can you still access bootloader and recovery?
If you can get into bootloader, what version of HBOOT does it say? What version of CWM are you using. BTW, in my limited experience TWRP is better for this device. Version 2.7.1.1 works well for me.
jollywhitefoot said:
Did you wipe the device prior to install? Can you still access bootloader and recovery?
If you can get into bootloader, what version of HBOOT does it say? What version of CWM are you using. BTW, in my limited experience TWRP is better for this device. Version 2.7.1.1 works well for me.
Click to expand...
Click to collapse
Yes I did wipe all the data, but I did not installed the pack. I turned off the device.
I can access the bootloader but if I try to get into Recovery it brings me back to the bootloader menu.
The HBOOT version is 2.22.0000, and I have installed the CMM. 6.0.3.6
I have tried to install the TWRP but it did not work.
AndySOS said:
Yes I did wipe all the data, but I did not installed the pack. I turned off the device.
I can access the bootloader but if I try to get into Recovery it brings me back to the bootloader menu.
The HBOOT version is 2.22.0000, and I have installed the CMM. 6.0.3.6
I have tried to install the TWRP but it did not work.
Click to expand...
Click to collapse
6.0.3.6 is really old and problably not compatible with your current configuration.
what do you mean TWRP didn't work? Does it not flash? What message do you get in command window when you try to flash it? If it does flash, can you enter TWRP?
HBOOT 2.22 means you're likely on a new partition layout, that was released around April of this year. You shouldn't use any recoveries or ROMs that were released before summer. And with ROMs, you should find out if they are for new or old layout before you flash them.
jollywhitefoot said:
6.0.3.6 is really old and problably not compatible with your current configuration.
what do you mean TWRP didn't work? Does it not flash? What message do you get in command window when you try to flash it? If it does flash, can you enter TWRP?
HBOOT 2.22 means you're likely on a new partition layout, that was released around April of this year. You shouldn't use any recoveries or ROMs that were released before summer. And with ROMs, you should find out if they are for new or old layout before you flash them.
Click to expand...
Click to collapse
Yeah TWRP doest flash, and I got something like that: recovery.img cannot/won't start. I believe I had the wrong version.
I was thinking to delete the current custom recovery and to install another one...
AndySOS said:
Yeah TWRP doest flash, and I got something like that: recovery.img cannot/won't start. I believe I had the wrong version.
I was thinking to delete the current custom recovery and to install another one...
Click to expand...
Click to collapse
When you flash a new recovery it will overwrite the existing one.
What message exactly do you get when you try to flash twrp?
Is fastboot working properly? Does it say Fastboot "USB"? When you type Fastboot devices in command window, does it show your device?
jollywhitefoot said:
When you flash a new recovery it will overwrite the existing one.
What message exactly do you get when you try to flash twrp?
Is fastboot working properly? Does it say Fastboot "USB"? When you type Fastboot devices in command window, does it show your device?
Click to expand...
Click to collapse
It says that." fastboot is not working proprely" . And yes it does show my device.
AndySOS said:
It says that." fastboot is not working proprely" . And yes it does show my device.
Click to expand...
Click to collapse
Can you paste the results from the command window when you try to flash twrp?
Can you paste the results from the command window when you type "fastboot devices"?
What is your computer OS?
jollywhitefoot said:
Can you paste the results from the command window when you try to flash twrp?
Can you paste the results from the command window when you type "fastboot devices"?
What is your computer OS?
Click to expand...
Click to collapse
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4
error: cannot load 'twrp-2.7.1.2-m4'
and
C:\Android>fastboot devices
HT3ABWA00119 fastboot
And I have Windows 8.1
AndySOS said:
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4
error: cannot load 'twrp-2.7.1.2-m4'
and
C:\Android>fastboot devices
HT3ABWA00119 fastboot
And I have Windows 8.1
Click to expand...
Click to collapse
on your flash command, you forgot to include the file extension. it should be "twrp-2.7.1.2-m4.img"
jollywhitefoot said:
on your flash command, you forgot to include the file extension. it should be "twrp-2.7.1.2-m4.img"
Click to expand...
Click to collapse
It still says the same thing.
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4.img
error: cannot load 'twrp-2.7.1.2-m4.img'
AndySOS said:
It still says the same thing.
C:\Android\Unlock Folder>fastboot flash recovery twrp-2.7.1.2-m4.img
error: cannot load 'twrp-2.7.1.2-m4.img'
Click to expand...
Click to collapse
Where did you get that file? I don't see 2.7.1.2 as an official version for our device.
Try downloading 2.7.1.1 from here:
http://techerrata.com/browse/twrp2/m4ul
jollywhitefoot said:
Where did you get that file? I don't see 2.7.1.2 as an official version for our device.
Try downloading 2.7.1.1 from here:
http://techerrata.com/browse/twrp2/m4ul
Click to expand...
Click to collapse
Still, the same thing
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
error: cannot load 'openrecovery-twrp-2.7.1.1-m4.img'
AndySOS said:
Still, the same thing
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
error: cannot load 'openrecovery-twrp-2.7.1.1-m4.img'
Click to expand...
Click to collapse
Fastboot simply isn't finding the file for whatever reason. can you post a dir of the C:\Android\Unlock Folder?
Do you have Windows set to not show file extension in Explorer? You might want to change it to show extensions to make sure the TWRP file is being saved with the .img extension.
Another thing to try would be to rename the twrp recovery file to just "recovery.img" to reduce the number of variables.
jollywhitefoot said:
Fastboot simply isn't finding the file for whatever reason. can you post a dir of the C:\Android\Unlock Folder?
Do you have Windows set to not show file extension in Explorer? You might want to change it to show extensions to make sure the TWRP file is being saved with the .img extension.
Another thing to try would be to rename the twrp recovery file to just "recovery.img" to reduce the number of variables.
Click to expand...
Click to collapse
I did it. I just had to change to show the extensions. XD
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
target reported max download size of 800227328 bytes
sending 'recovery' (9432 KB)...
OKAY [ 1.179s]
writing 'recovery'...
OKAY [ 2.302s]
finished. total time: 3.489s
AndySOS said:
I did it. I just had to change to show the extensions. XD
C:\Android\Unlock Folder>fastboot flash recovery openrecovery-twrp-2.7.1.1-m4.img
target reported max download size of 800227328 bytes
sending 'recovery' (9432 KB)...
OKAY [ 1.179s]
writing 'recovery'...
OKAY [ 2.302s]
finished. total time: 3.489s
Click to expand...
Click to collapse
ok. cool. Now...once you enter recovery, you need to see if ADB works, or do you have an OTG device? Either way, you need to download a ROM to your computer then either push it to your device using ADB or OTG. I'd probably start out with this stock ROM (http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921) so you can boot back into OS. Once you can boot into OS, you can make a TWRP backup, then flash CM or whatever else you want.
jollywhitefoot said:
ok. cool. Now...once you enter recovery, you need to see if ADB works, or do you have an OTG device? Either way, you need to download a ROM to your computer then either push it to your device using ADB or OTG. I'd probably start out with this stock ROM (http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921) so you can boot back into OS. Once you can boot into OS, you can make a TWRP backup, then flash CM or whatever else you want.
Click to expand...
Click to collapse
Yeah about that... i have already done that and I have insatlled the CM 11 and its currently processing.
Thank you for your help ! XD XD
U just saved my phone
AndySOS said:
Yeah about that... i have already done that and I have insatlled the CM 11 and its currently processing.
Thank you for your help ! XD XD
U just saved my phone
Click to expand...
Click to collapse
ok. cool. no problem. glad you got it working.