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
Related
SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.
pimix2009 said:
SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.
Click to expand...
Click to collapse
I have had the issue of ADB unable to find devices. Don't know if this will help you, but has worked for me. Make sure phone if powered off. Hold the volume down button and press and hold the power button in order to boot into bootloader. Then plug your phone into the computer. You should see the screen change to Fastboot USB. From my experience, that is where you need to be.
YMMV. Good luck.
pimix2009 said:
SO I wiped my whole internal memory after creating a backup of my rom and trying to flash a new one. I quickly press to wipe and I guess i picked to wipe my internal memory too. So now I have No OS on the phone and nothing on the card to flash.
I tried ADB Sideload and all i got it was can't mount system, and cach..Samething happens if I try to backup or mount
I tried to send my zip file through fastboot with the "fastboot flash data " command but at the end I get a failed bootloader checking and I tried the same with system and nothing happen or I count find my zip file when I went back to recovery.
SO can someone help me fix this ? or Is there an RUU i can use?? my phone Hboot is 1.55 and came with Android 4.3 so idk if any old RUU will work
Oh and ADB dont some to work ...I get an error telling that it can't find devices.
Click to expand...
Click to collapse
If you want to sideload you'll need TWRP recovery. Here's a guide. http://forum.xda-developers.com/showthread.php?t=2318497 I myself had trouble finding my device, but than I uninstalled all the HTC drivers I had and installed the "universal naked driver" from here http://forum.xda-developers.com/showthread.php?t=2263822
I have the exact same thing I can't save a ROM to the device to flash it anymore I just want it to go back to stock I don't want root anymore it never works. My bootloader version is 3.04.651.2 which is too high to use the RUU installer. I can't mount the storage to use any of the S-Off Tools to downgrade it. I can't even push files using adb. All because of a ROM....
Sirricharic said:
I have the exact same thing I can't save a ROM to the device to flash it anymore I just want it to go back to stock I don't want root anymore it never works. My bootloader version is 3.04.651.2 which is too high to use the RUU installer. I can't mount the storage to use any of the S-Off Tools to downgrade it. I can't even push files using adb. All because of a ROM....
Click to expand...
Click to collapse
If you dont have a custom recovery make sure you flash one thru bootloader, fastboot. Regardless of you Hboot or bootlaoder number, you can get it unlock at the htcdev.com website. then you have to flash TWRP recovery. After doing then go to recovery....Don't do anything yet, make sure that you computer recognizes your phone. THATS the mistake I made. Open device manager and look for android USB devices if its not there then you need to install the adb drivers. If its there then on TWRP recovery look for adb side... I think its under advance .... then open the command to tour adb folder and type "adb version" you need at least 1.0.21 or higher. then type adb sideload name of rom.zip
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.
I am so scared this happend again i was trying to update my phone to 4.4 the new kit kat OTA and then it didnt work becasue i had a cwm but i didnt have root access on my phone so i downloaded stock 4.4 sense 5.5 and tried to flash it it said aborted so i flashed my old stock rom and then i thought might aswell flash the new rom on top maybe it will update so i then i rebooted and said remove root so i hit yes and then im stuck on the htc screen and i cannot get into recovery i have already got sync installed it says fastboot usb on the phone but cannot find it when typing in fastboot devices someone please help me i am scareed and feeling to cry!
SamoAFG said:
I am so scared this happend again i was trying to update my phone to 4.4 the new kit kat OTA and then it didnt work becasue i had a cwm but i didnt have root access on my phone so i downloaded stock 4.4 sense 5.5 and tried to flash it it said aborted so i flashed my old stock rom and then i thought might aswell flash the new rom on top maybe it will update so i then i rebooted and said remove root so i hit yes and then im stuck on the htc screen and i cannot get into recovery i have already got sync installed it says fastboot usb on the phone but cannot find it when typing in fastboot devices someone please help me i am scareed and feeling to cry!
Click to expand...
Click to collapse
I'd really be willing to help.. but I leave the internet for a week in a few hours... so I won't be able to help you anymore... so after this answer, I can only help you a week later again.
But secondly:
-Download HTC Sync(http://www.htc.com/www/software/htc-sync-manager/)
-Intall it with EVERY component!
-Then uninstall the HTC Sync Manager again, but DON'T uninstall the drivers!!!
-You may proceed a restart to avoid any registry etc. related problems...
-Then connect your phone to the PC and try to get fastboot working...
-Befor you flash a new recovery, type this command:
Code:
fastboot erase cache
-Then flash TWRP(2.6.3.3):
http://techerrata.com/browse/twrp2/m7
(Thanks to your awesome work TeamWin)
-Now you can flash a new OS.. or maybe you can also let a RUU do it's work if you have S OFF..
BUT FOR YOUR OWN SAFETY ONLY FLASH A ROM BELOW 4.4 KITKAT(BEST IS 4.3) BECAUSE 4.4 WITHOUT S OFF WILL OCCURE IN A SOFTBRICK
(Stock OS from here: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html)
(Thanks to @mike1986. for your awesome work)
I hope this worked...
If not... I am back in a week...
A thanks if I brought you a step further would be appreciated
SamoAFG said:
I am so scared this happend again i was trying to update my phone to 4.4 the new kit kat OTA and then it didnt work becasue i had a cwm but i didnt have root access on my phone so i downloaded stock 4.4 sense 5.5 and tried to flash it it said aborted so i flashed my old stock rom and then i thought might aswell flash the new rom on top maybe it will update so i then i rebooted and said remove root so i hit yes and then im stuck on the htc screen and i cannot get into recovery i have already got sync installed it says fastboot usb on the phone but cannot find it when typing in fastboot devices someone please help me i am scareed and feeling to cry!
Click to expand...
Click to collapse
Hey, relax! This happened to me as well, and i found the solution to be very easy. While in bootloader, make sure you connect it to your computer (it should say "FASTBOOT USB", navigate to the ADB folder in the command prompt (on your computer). The easy way is to hold down ctrl and right-click in the ADB folder (assuming you are using Windows) and select open command prompt. Now type "fastboot erase cache". Your issue is now fixed, go into recovery and flash your stock rom if you don't have any relevant backups. And if you want to flash kit-kat, MAKE SURE TO USE TWRP 2.6.3.3 That's it, let me know if you need more help!
PC
SamoAFG said:
I am so scared this happend again i was trying to update my phone to 4.4 the new kit kat OTA and then it didnt work becasue i had a cwm but i didnt have root access on my phone so i downloaded stock 4.4 sense 5.5 and tried to flash it it said aborted so i flashed my old stock rom and then i thought might aswell flash the new rom on top maybe it will update so i then i rebooted and said remove root so i hit yes and then im stuck on the htc screen and i cannot get into recovery i have already got sync installed it says fastboot usb on the phone but cannot find it when typing in fastboot devices someone please help me i am scareed and feeling to cry!
Click to expand...
Click to collapse
Sometimes we have to reboot our PC, shutdown all background/ auto start programs before windows will function properly.
Be sure you have updated your firmware and recovery to 4.4 compatible versions.
flash firmware in RUU mode.
flash recovery in RUU mode.
erase cache in fastboot.
powerdown.
boot into bootloader.
select recovery.
powerdown.
say yes to superuser inststall.
boot into bootloader.
select recovery.
WIPE !!
use OTG or sideload your ROM. then install
Wipe dalvek and cache.
powerdown.
IF YOUR ARE S-ON boot to bootloader once more and flash the boot image from your ROM.
reboot
DONE.
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 was trying to flash LiquidSmooth ROM, installed TWRP recovery, formatted /data and /cache to F2FS and installed the rom, an custom kernel by mourta and PA Gapps.
The phone stucked in LiquidSmooth bootlogo. I tried to boot in recovery unsuccessfully (my Vol - key is kinda broken), the command adb reboot recovery didn't work.
After many tries, I could flash the LG Stock rom, the Kdz program didn't finish the process and the phone rebooted, don't know why.
Tried many other times to flash.
To sum up, I could flash the original firmware, the phone is booting up normally and aparently is working properly, the problem is: I still can't go to recovery to restore my old rom. (The adb reboot recovery comand just reboot the phone). So, I can't root it or flash another custom recovery.
I wish you guys can help me. Sorry if I written something wrong or if the text is too long, I haven't finished my English course yet.
Which stock rom have you flashed? I've tried to use fastboot on a V10 rom couple of weeks ago and I coudn't do it. I think that it works just with V20 roms.
ViniLima said:
Which stock rom have you flashed? I've tried to use fastboot on a V10 rom couple of weeks ago and I coudn't do it. I think that it works just with V20 roms.
Click to expand...
Click to collapse
I'm using now V20A_00_4.1.2.EURO.
I could acess the recovery (original) but adb sideload doesn't work. It says: "Error: more than one device and emulator."
About fastboot, I've already tried to flash the recovery using this, but it just keep with one message, I guess is waiting phone, or something like that.
ssgabriel said:
I'm using now V20A_00_4.1.2.EURO.
I could acess the recovery (original) but adb sideload doesn't work. It says: "Error: more than one device and emulator."
About fastboot, I've already tried to flash the recovery using this, but it just keep with one message, I guess is waiting phone, or something like that.
Click to expand...
Click to collapse
I didn't know that error more than one device and emulator. I can't help you on this error.
About Fastboot still waiting phone, that is phone driver's problem. Try to install P880 fastboot drivers and try again.
Try these drivers: http://forum.xda-developers.com/showpost.php?p=38953792&postcount=17
ViniLima said:
I didn't know that error more than one device and emulator. I can't help you on this error.
About Fastboot still waiting phone, that is phone driver's problem. Try to install P880 fastboot drivers and try again.
Try these drivers: http://forum.xda-developers.com/showpost.php?p=38953792&postcount=17
Click to expand...
Click to collapse
I figued out about the error: "Error: more than one device and emulator."
It's an incompatibility with Bluestacks, after close it, it works, but I had to turn off the phone and couldn't flash.
And about fastboot, I could acess this too (Didn't knew that I needed to be on Bootloader mode). But I can't flash the recovery, it says that my bootloader is locked (using fastboot reboot bootloader).
It isn't, or at least wasn't before it all happen. Using ADB command to reboot in bootloader mode (adb reboot oem-unlock I guess), I can flash the .img of clockwork mod and TWRP without error messages, but I still can't boot into it by adb reboot recovery.
Thanks for trying. Today I could acess Android original recovery by hardware keys and install another recovery and ROM.