I think I just ****ed myself. I'm not sure how to get myself out of this one. Alright, so from the beginning:
- I wanted to upgrade from my Android 4.3 CyanogenMod 10.2 ROM on my HTC One (AT&T Carrier)
- I used Rumrunner to get my device to S-Off to allow myself to use 4.4 based ROM's
- I then updated to 2.6.3.4 TWRP to allow myself to flash 4.4 based ROM's
- I then tested to see if everything worked properly by flashing Mike1986's stable GPe based 4.4 ROM and it ran smoothly.
- Once I realized it ran smoothly, I went back to CyanogenMod by downloading the latest Nightly off their website for the m7att HTC One. I also downloaded the Gapps from their page that was compatible with CM11.
- I went to flash it, and it says that the CM-11 .zip failed because the package is for m7.m7att devices. I then looked at my bootloader and it says M7UL.
The gist is, I'm now stuck in my recovery with no way to put a new ROM on there. I can't boot up into a system because I have none. I can't boot into a system to allow myself to connect to my SD card via USB and I can't download one from the system directly because I don't have one to boot up into. The thing is, M7UL should work with M7ATT so it must just be a problem with Cyanogenmod. It wasn't the Gapps because the problem struck before it even tried to flash them.
What the hell do I do?
Well you can always fastboot to RUU mode and push the stock ruu that should bring you back to normal, or at least boot the stock system
Sent from my HTC One using xda app-developers app
Can you still enter recovery then? If you can access recovery check and see if you still have adb connection by typing "adb devices" in a cmd prompt. If it's still connected as adb device you could push a rom to the sdcard via recovery. Mount the data first under the mount are and then do this command "adb push rom.zip /sdcard/rom.zip"
It will take a good 1-5 minutes before its fully pushed. The cmd prompt will also say nothing until its finished.
Ah, well I'm on Ubuntu so I remedied the issue by installing the ADB package into Ubuntu and then running the commands
Code:
cd /Downloads
adb push rom.zip /sdcard/.
It downloaded it to my SDcard where I flashed it and Gapps and it worked like a charm. Apparently m7att has a problem.
Related
So I've been flashing ROM"s to my HTC One Developer Edition lately, and didn't think when I accidently clicked format internal storage. Coming from an S3, I had an external SD card, so this wasn't a problem.
So the current predicament I'm in is kind of confusing for myself. I'm still rooted, with a custom recovery installed (CWM touch). However I do not have a ROM installed, and the phone boot loops when I try to power it on. I'm able to get to the Bootloader as well as the recovery.
When I plug the phone into my computer, it does not appear as a device. I have tried to adb sideload, but the device is not appearing when I type adb devices.
Is there anything I can do to get this device back up and running? I'm willing to go back to stock if need be.
Flash TWRP recovery and see if your devices is checked, for adb command you don't need adb sideload.
However, if you have an otg cable, you can use it for flashing a custom rom.
If this solution will not work, you need a ruu...
Guich said:
Flash TWRP recovery and see if your devices is checked, for adb command you don't need adb sideload.
However, if you have an otg cable, you can use it for flashing a custom rom.
If this solution will not work, you need a ruu...
Click to expand...
Click to collapse
TWRP now installed,
What do you mean by device is checked?
Sorry, use adb device in twrp and see if your device is on
Sent from One with Tapa4 Beta
Guich said:
Sorry, use adb device in twrp and see if your device is on
Sent from One with Tapa4 Beta
Click to expand...
Click to collapse
Downloaded the driver again for the phone, and it appeared it ADB, I just sideloaded my old ROM, so I'm back up and running.
There a way to close this?
Hello
I have update my HTC One (europe) into 4.2.2 recently.
I have unlocked the bootloader, installed a recovery (ClockWorkMod Touch 6), and root the device.
But after wanted to install a module founded on the net, I blocked the device (without any save obviously), and the device starts but freeze on the screen of HTC logo.
I always have access to the bootloader (and to fastboot) and to recovery CM6.
To reinstall ROM, I found several solutions on the web but none of theses worked :
- I tried to install a RUU ROM and relocked my bootloader before => impossible, error 140 because it considers that my bootloader does not have the good version. Indeed the RUU availables on the web are only 4.1 and apparently the downgrade is not authorized.
- I tried to inject a custom ROM via ADB sideload but there were a new issue : my device is not recognized! DEVICE NOT FOUND. The fastboot command works well, the HTC is detected, but not the ADB command, which is the only one enabling me to copy a custom ROM in the internal memory of the device (I reinstalled the drivers several times obviously).
I dont know what to do anymore, I feel that the device can be saved because I have access to the bootloader, fastboot and recovery.
But I do not see which other method to use to finally be able to replace the exsiting ROM by a new clean ROM
Thank you very much of your assistance.
You need to be in recovery and sideload mode when using the adb command. I'm not sure about CWM but on TWRP sideload mode is located under advanced options.
AT&T HTC One
BaadNewz's InsertCoin 3.0-7
Flar2's Bulletproof 3.4
If you re-locked your bootloader when trying to run the RUU, you will have to go to htcdev again and get a new token and unlock the bootloader again before you will be able to flash anything in recovery.
Thats maybe why you can't sideload in adb.
Also you have the phone device drivers installed on your PC right?
Could also try sideloading and other troubleshooting by using a toolkit:
http://forum.xda-developers.com/showthread.php?t=2242635
crushalot said:
If you re-locked your bootloader when trying to run the RUU, you will have to go to htcdev again and get a new token and unlock the bootloader again before you will be able to flash anything in recovery.
Thats maybe why you can't sideload in adb.
Also you have the phone device drivers installed on your PC right?
Could also try sideloading and other troubleshooting by using a toolkit:
http://forum.xda-developers.com/showthread.php?t=2242635
Click to expand...
Click to collapse
rename the ROM from its original name to "ROM.zip" without the quotes, and then try again ADB
if it didnt work inject TWRP, and copy the ROM to a USB Stick and using a USB OTG ($1) mount the USB Stick in TWRP and install the ROM
it worked %100 for me
I opened the bootloader via htcdev. then i flashed costume recovery and rooted my device. all worked fine.
After flash the latest ARHD from stock Orange rom the phone stuck in the second htc logo.
i flashed boot.img and then the phone stuck in the first htc logo.
i format data in TWRP! i thought it would help but now all my sd data deleted! include the rom and the nandroid backup!
i tried sideload but adb not read my phone! fastboot work though.
i am really stuck please help me. i cant find RUU for my device (3.63.75.3 - Orange spain) :crying:
i have the htc drivers work and htcsync uninstalled.
** edit **
it work! had to delete the drivers and install the universal naked instead and update the sdk then sideload worked!
amitshkuri said:
I opened the bootloader via htcdev. then i flashed costume recovery and rooted my device. all worked fine.
After flash the latest ARHD from stock Orange rom the phone stuck in the second htc logo.
i flashed boot.img and then the phone stuck in the first htc logo.
i format data in TWRP! i thought it would help but now all my sd data deleted! include the rom and the nandroid backup!
i tried sideload but adb not read my phone! fastboot work though.
i am really stuck please help me. i cant find RUU for my device (3.63.75.3 - Orange spain) :crying:
i have the htc drivers work and htcsync uninstalled.
Click to expand...
Click to collapse
lesson one, copy your stock backup to your PC - don't just leave it on your phone
adb only works when your in recovery or booted to OS
Kitkat roms require s-off flash an older version of ARHD like 31.6
sideload the ARHD31 from TWRP and your PC
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload rom.zip
make sure rom.zip is in the same directory as adb/fastboot
ADB Push from Recovery - If Sideload Fails For You
adb push rom.zip /data/media/0/
Hi guys. I recently flashed a boot image via the Flashify app, which had worked in the past. After it flashed, I chose to reboot. Now my phone boots to the bootloader. I can't get fastboot to recognize my device on any PC (which is why I was trying another hboot). I can boot into recovery (cwm touch for now) but restoring roms etc. fails due to "no files found". ADB detects the phone in recovery. Can I repair my phone via adb without fastboot? I had a recent cwm and titanium backup on my sd card.
xpurtwitness said:
Hi guys. I recently flashed a boot image via the Flashify app, which had worked in the past. After it flashed, I chose to reboot. Now my phone boots to the bootloader. I can't get fastboot to recognize my device on any PC (which is why I was trying another hboot). I can boot into recovery (cwm touch for now) but restoring roms etc. fails due to "no files found". ADB detects the phone in recovery. Can I repair my phone via adb without fastboot? I had a recent cwm and titanium backup on my sd card.
Click to expand...
Click to collapse
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.
alray said:
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.
Click to expand...
Click to collapse
I am stuck in the same boat - I can't use fastboot., but I need it to flash a new recovery before updating to cm11. I don't have access to any Win7 computers to use, only have Win8.1. Are there updated drivers for the HTC One yet? Or any way to get fastboot working properly on Win8.1?
Artemicion said:
I am stuck in the same boat - I can't use fastboot., but I need it to flash a new recovery before updating to cm11. I don't have access to any Win7 computers to use, only have Win8.1. Are there updated drivers for the HTC One yet? Or any way to get fastboot working properly on Win8.1?
Click to expand...
Click to collapse
windows 8.1 doesnt work with early hboot version like 1.44 and if irc 1.54.
if you can't access another computer, use a live cd of ubuntu 12.04 32bit (no installation required, only boot from the disc or from a bootalb usb drive) and use fastboot from there.
alray said:
windows 8.1 doesnt work with early hboot version like 1.44 and if irc 1.54.
if you can't access another computer, use a live cd of ubuntu 12.04 32bit (no installation required, only boot from the disc or from a bootalb usb drive) and use fastboot from there.
Click to expand...
Click to collapse
So is it possible to upgrade my hboot to 1.55 (currently 1.54)?
EDIT: Ok, actually, examining things, it looks like this should work:
a) Go to Ubuntu for fastboot, flash new recovery
b) Back to windows, into recovery, wipe everything, push ROM over using adb, clean install of cm11
c) new cm ROM will include updated hboot so fastboot will now work in Win8.1
....that seem logical/like it should work to you? Thanks
Artemicion said:
So is it possible to upgrade my hboot to 1.55 (currently 1.54)?
Click to expand...
Click to collapse
yes, via fastboot :laugh:
EDIT: Ok, actually, examining things, it looks like this should work:
a) Go to Ubuntu for fastboot, flash new recovery
b) Back to windows, into recovery, wipe everything, push ROM over using adb, clean install of cm11
c) new cm ROM will include updated hboot so fastboot will now work in Win8.1
....that seem logical/like it should work to you? Thank
Click to expand...
Click to collapse
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)
alray said:
yes, via fastboot :laugh:
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)
Click to expand...
Click to collapse
Wow, ok, I think that sounds like far too much effort to just update my phone. Guess I'll use the ubuntu fastboot trick once, then just hope I never need to flash anything from fastboot again on this phone. Why is it always such an effort with these damn things? Thanks for the help, won't have a chance to try this for a couple of days but doubtless I'll be back with some other failed horror scenario then.
alray said:
are those computers all windows 8? There some issue with windows 8 and fastboot. better to use 7, linux or mac.
you can restore a backup or install a rom using adb, no need to use fastboot (except for recovery, RUU and firmware flashing)
you can transfer a rom to your sdcard using adb from custom recovery:
Code:
adb push name_of_rom.zip /sdcard/
I recommend you to use twrp 2.6.3.3 instead of cwm (required for arhd rom i.e) when you get fastboot working again.
Click to expand...
Click to collapse
Yeah, that's pretty much the extent of what I knew, but I really appreciate your response. I did manage to get my old Win7 laptop running and with some effort got all the drivers working. I used htc1guru reset, but sadly I did lose the entire contents of my SD, despite its message that nothing would be touched. :-/ Luckily, most photos were auto-backed up by G+ and it's just a few settings and such that I can't get back or figure out. Least of my concerns after having a functional phone!
alray said:
yes, via fastboot :laugh:
yes except c)
a rom doesn't update firmware so hboot will not be updated by flashing a custom rom. If you want to update hboot you must do it via an ota update, a complete ruu install (higher version) or manually flashing the firmware using fastboot. with s-on, you must use signed firmware only (the correct version for your device) and you bootloader must be locked or re-locked to flash it (s-on)
Click to expand...
Click to collapse
Hey, so I'm trying to do this, have got linux up and running and fastboot recognizes the phone, but I couldn't flash the recovery image as the terminal couldn't see it. What location does it need to be in within linux? I put it on the root of the usb drive and it wouldn't work from there...
Artemicion said:
Hey, so I'm trying to do this, have got linux up and running and fastboot recognizes the phone, but I couldn't flash the recovery image as the terminal couldn't see it. What location does it need to be in within linux? I put it on the root of the usb drive and it wouldn't work from there...
Click to expand...
Click to collapse
the answer is always the same, in the same folder you have adb in.
so in ubuntu it should be androidsdk/platform-tools/
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