I have a problem...
I went to update my HTC One M7 to the newest InsertCoin update however I downloaded the wrong rom, downloading the rom for the HTC DNA instead. After an unsuccessful install, the phone would not boot after a wipe or anything, and atm boots straight into the boot loader. I have been unable to side load any file onto the phone and so far S-off attempts have been unsuccessful. Any help would be appreciated.
jackhiggins said:
I have a problem...
I went to update my HTC One M7 to the newest InsertCoin update however I downloaded the wrong rom, downloading the rom for the HTC DNA instead. After an unsuccessful install, the phone would not boot after a wipe or anything, and atm boots straight into the boot loader. I have been unable to side load any file onto the phone and so far S-off attempts have been unsuccessful. Any help would be appreciated.
Click to expand...
Click to collapse
if you have an m7_u or m7_ul - check your fastboot getvar all - try to reflash custom recovery: get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try getting to recovery, if it bootloops back to bootloader, then you have a serious problem
I am able to get into recovery as I already have ClockworkMod Recovery 6.0.4.6 flashed, by can switch to TWRP if it is better? I'm just not sure of what steps to take as I can't load a stock rom on the internal storage (computer isn't recognising device but fast boot is) and I can't take it back to my provider as the boot loader has a tampered warning...
jackhiggins said:
I am able to get into recovery as I already have ClockworkMod Recovery 6.0.4.6 flashed, by can switch to TWRP if it is better? I'm just not sure of what steps to take as I can't load a stock rom on the internal storage (computer isn't recognising device but fast boot is) and I can't take it back to my provider as the boot loader has a tampered warning...
Click to expand...
Click to collapse
you can transfer a rom to your device using adb from twrp recovery. ADB sideload or adb push method.
instructions can be found here: http://forum.xda-developers.com/showthread.php?t=2318497
@nkk71 congrat for your new title :good:
edit: If you have an usb otg cable you can also copy your rom to a usb drive and mount it from twrp
alray said:
you can transfer a rom to your device using adb from twrp recovery. ADB sideload or adb push method.
instructions can be found here: http://forum.xda-developers.com/showthread.php?t=2318497
@nkk71 congrat for your new title :good:
edit: If you have an usb otg cable you can also copy your rom to a usb drive and mount it from twrp
Click to expand...
Click to collapse
Thanks mate.
jackhiggins said:
I am able to get into recovery as I already have ClockworkMod Recovery 6.0.4.6 flashed, by can switch to TWRP if it is better? I'm just not sure of what steps to take as I can't load a stock rom on the internal storage (computer isn't recognising device but fast boot is) and I can't take it back to my provider as the boot loader has a tampered warning...
Click to expand...
Click to collapse
you can also check this: http://forum.xda-developers.com/showthread.php?t=2714783
if adb devices doesn't show anything check FAQ #2 in my guide to fix drivers (disregard the rest)
Related
Hello.
I tried to flash a custom rom on my phone with s-on. I followed the instructions that told me to extract boot.img from the zip and flash it first and then the rom as I had s-on.
But after flashing the phone reboots into recovery. It doesn't go in the system. I can't get the internal sd to mount in the TWRP recovery as well. I tried CWM too but was not able to mount the internal memory.
As I have s-on I can't even flash the stock ruu and because it doesn't go into the system there is no way for me to check USB debugging. I'm screwed.
Can anyone please help me ?
psbhadola said:
Hello.
I tried to flash a custom rom on my phone with s-on. I followed the instructions that told me to extract boot.img from the zip and flash it first and then the rom as I had s-on.
But after flashing the phone reboots into recovery. It doesn't go in the system. I can't get the internal sd to mount in the TWRP recovery as well. I tried CWM too but was not able to mount the internal memory.
As I have s-on I can't even flash the stock ruu and because it doesn't go into the system there is no way for me to check USB debugging. I'm screwed.
Can anyone please help me ?
Click to expand...
Click to collapse
you haven't read the rules :/
first you don't have to flash the boot.IMG separately on HTC One, just flash the ROM via recovery
second it is impossible to mount your SD card in recovery
try sideload
Sent from my HTC One using Tapatalk
kamilmirza said:
you haven't read the rules :/
first you don't have to flash the boot.IMG separately on HTC One, just flash the ROM via recovery
second it is impossible to mount your SD card in recovery
try sideload
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It said in the flashing instructions that if the phone is s-on you have to flash boot.img first.
My phone is s-on so I flashed boot.img first. Now it boots into recovery instead of system.
Also my phone is not detected by adb. So I can't use sideload. It is detected by fastboot but not adb
How can I make it detect adb?
psbhadola said:
It said in the flashing instructions that if the phone is s-on you have to flash boot.img first.
My phone is s-on so I flashed boot.img first. Now it boots into recovery instead of system.
Also my phone is not detected by adb. So I can't use sideload. It is detected by fastboot but not adb
How can I make it detect adb?
Click to expand...
Click to collapse
no ROM for HTC One requires flashing boot.img first while on S-ON
uninstall your previous HTC drivers and HTC Sync Manager, restart your PC
download and install the following: http://download1801.mediafire.com/lbsjht9823lg/e21a0cc4268dg9d/HTCDriver_4.10.0.001.msi
sideload guide: http://forum.xda-developers.com/showthread.php?t=2318497
connect your device, go into recovery and start sideload
make sure you detect your device before starting sideload; "adb devices"
kamilmirza said:
no ROM for HTC One requires flashing boot.img first while on S-ON
uninstall your previous HTC drivers and HTC Sync Manager, restart your PC
download and install the following: http://download1801.mediafire.com/lbsjht9823lg/e21a0cc4268dg9d/HTCDriver_4.10.0.001.msi
sideload guide: http://forum.xda-developers.com/showthread.php?t=2318497
connect your device, go into recovery and start sideload
make sure you detect your device before starting sideload; "adb devices"
Click to expand...
Click to collapse
Ok. Let me try that and see how it goes.
Will get back with the results
Thanks
psbhadola said:
Ok. Let me try that and see how it goes.
Will get back with the results
Thanks
Click to expand...
Click to collapse
Okay I was able to flash the RUU and go back to stock but the phone keeps rebooting
It goes to lock screen and after I swipe to unlock, it is stuck on HTC logo until it reboots back.
Even when I flashed any custom ROMs the same thing happened.
It went to lock screen and after unlocking, it gets stuck on HTC logo.
What can I do?
I just got my new HTC One M6 and now I can't get it rooted. Additionally, I seem to have messed up the internal storage because I get errors when I try to do anything in TWRP and I can't get supersu to install in twrp either. I can't even get anything to show up in any of the folders while in recovery.
Here's info on my phone and what I've done so far:
1) T-mobile, hboot v1.56
2) got unlock token from htcdev and unlocked successfully
3) flashed TWRP 2.6.3.0 recovery using Squabbi's HTC One Toolkit.
4) tried to install supersu using the toolkit and then tried putting supersu.zip on the sdcard manually. Neither worked and resulted in lots of error messages in TWRP.
4) tried to wipe data and everything else but this failed too.
5) tried to make a log file in twrp and this failed
Attached in this e-mail is a screenshot of the error messages i get in twrp when trying to wipe. Any ideas on what I can do to fix the internal storage so I can actually root my htc one?
dingurupa said:
I just got my new HTC One M6 and now I can't get it rooted. Additionally, I seem to have messed up the internal storage because I get errors when I try to do anything in TWRP and I can't get supersu to install in twrp either. I can't even get anything to show up in any of the folders while in recovery.
Here's info on my phone and what I've done so far:
1) T-mobile, hboot v1.56
2) got unlock token from htcdev and unlocked successfully
3) flashed TWRP 2.6.3.0 recovery using Squabbi's HTC One Toolkit.
4) tried to install supersu using the toolkit and then tried putting supersu.zip on the sdcard manually. Neither worked and resulted in lots of error messages in TWRP.
4) tried to wipe data and everything else but this failed too.
5) tried to make a log file in twrp and this failed
Attached in this e-mail is a screenshot of the error messages i get in twrp when trying to wipe. Any ideas on what I can do to fix the internal storage so I can actually root my htc one?
Click to expand...
Click to collapse
The HTC One in an M7 .. the toolkit you used flashed a very old recovery
you need to learn to use adb and fastboot and not a toolkit
flash TWRP 2.6.3.3 from here
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
use this SuperSU (flash it in recovery)
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Do a hard reset of you phone by holding power + vol down for 15 seconds in a will lit room until it reboots to the bootloader
OK, I'll give this a shot. Thanks!
clsA said:
The HTC One in an M7 .. the toolkit you used flashed a very old recovery
you need to learn to use adb and fastboot and not a toolkit
flash TWRP 2.6.3.3 from here
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
use this SuperSU (flash it in recovery)
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Do a hard reset of you phone by holding power + vol down for 15 seconds in a will lit room until it reboots to the bootloader
Click to expand...
Click to collapse
Followed your instructions and it worked. Thanks!!!
dingurupa said:
OK, I'll give this a shot. Thanks!
Click to expand...
Click to collapse
Hi Guys ,
Well, my phone begin to have some problems in playing videos and I decided to flash another ROM on my HTC ONE.
My current ROM is [Elegancia_ONE_22.0.0.zip]
My phone specs:
HTC ONE GSM/3G
RUU VARIANT: x.xx.708.x
BOOTLOADER screen:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
Then I follow the above steps to flash a new ROM:
1. Went into CWM recovery mode [version:recovery-clockwork-6.0.4.6-m7ul.img]
2. Chose the the installation from zip on sdcard [Android_Revolution_HD-One_62.0.zip]
3. Followed the installation steps from ROM ui instalation.
4. After the end of installation, the CWM detected that my ROOT needed a fix/update, so I opted for YES.
5. Rebooted the phone by CWM menu option.
6 . Upon start up Im getting the white screen with green HTC logo *freeze*
7. Okay, it did not work.. tried starting in BOOTLOADER to enter in recovery mode again...
8. Once in BOOTLOADER I choose the RECOVERY option
9. Here's the problem: The phone start CWM but soon, the CWM comes out and the phone continues the boot process, freezing again the white screen with green HTC logo.
10 . My CWM is corrupted as I can see. I can not enter the CWM to flash another ROM.
11 . Tried to flash a new CWM using ADB. The ADB does not recognize the device (nothing is displayed by the command ADB DEVICES, besides the driver is ok)
12 . Tried to make the flash recovery using fastboot . So far so good, he can apparently flash the CWM but upon entering BOOTLOADER again to start from recovery mode, the same problem occurs!
What can I do?
a) My root is corrupted?
b) I can flash another ROM using fastboot?
c) I can try using another recovery img?
Help me please! Thank you!
Flash latest TWRP instead of CWM .... i had few probs with CWM ... since i use TWRP no more pb....
Use my zip or follow this link :
http://forum.xda-developers.com/showthread.php?t=2708134
After flashing recovery reboot on new recovery make a full wipe (sd not need) and reflash your rom .....
good luck ! :highfive:
ps : Could use adb sideload option for flashing problem
raphaelalex said:
Hi Guys ,
Well, my phone begin to have some problems in playing videos and I decided to flash another ROM on my HTC ONE.
My current ROM is [Elegancia_ONE_22.0.0.zip]
My phone specs:
HTC ONE GSM/3G
RUU VARIANT: x.xx.708.x
BOOTLOADER screen:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
Then I follow the above steps to flash a new ROM:
1. Went into CWM recovery mode [version:recovery-clockwork-6.0.4.6-m7ul.img]
2. Chose the the installation from zip on sdcard [Android_Revolution_HD-One_62.0.zip]
3. Followed the installation steps from ROM ui instalation.
4. After the end of installation, the CWM detected that my ROOT needed a fix/update, so I opted for YES.
5. Rebooted the phone by CWM menu option.
6 . Upon start up Im getting the white screen with green HTC logo *freeze*
7. Okay, it did not work.. tried starting in BOOTLOADER to enter in recovery mode again...
8. Once in BOOTLOADER I choose the RECOVERY option
9. Here's the problem: The phone start CWM but soon, the CWM comes out and the phone continues the boot process, freezing again the white screen with green HTC logo.
10 . My CWM is corrupted as I can see. I can not enter the CWM to flash another ROM.
11 . Tried to flash a new CWM using ADB. The ADB does not recognize the device (nothing is displayed by the command ADB DEVICES, besides the driver is ok)
12 . Tried to make the flash recovery using fastboot . So far so good, he can apparently flash the CWM but upon entering BOOTLOADER again to start from recovery mode, the same problem occurs!
What can I do?
a) My root is corrupted?
b) I can flash another ROM using fastboot?
c) I can try using another recovery img?
Help me please! Thank you!
Click to expand...
Click to collapse
raphaelalex said:
Hi Guys ,
2. Chose the the installation from zip on sdcard [Android_Revolution_HD-One_62.0.zip]
Help me please! Thank you!
Click to expand...
Click to collapse
Like it says in the OP of the thread you need TWRP 2.6.3.3 or higher (the part in red):
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
EDIT: or the one mentioned above
(make sure MD5 is correct, that site does not play nice with download managers)
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install the ROM.
right under my f*kng nose!
sorry about that... didn't see this huge warning.
You got me out of the mud :victory:, I've never posted anything on XDA forums, because I do not have experiences to share.
I hope this will be a help for another users anyway..
Im thankful for your help guys! (had already begun to pray.. lol)
:laugh::laugh::laugh:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!
nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?
fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem
rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?
rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this
Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver