Ok so I screwed up.
I'm not a developer but i'm familiar with most of the basics. So my m7 was rooted with android revolution 81.0. I was having unrelated problems with calls and also some other small things like a lock screen delay. I decided I was gonna do a system wipe (which I've done plenty of times before with no problems) but this time I forgot to put the OS on the sd card before the wipe. As of now my phone turns on but stays on the HTC screen unless I force it into bootloader and I can also get into TWRP still. I also noticed I wiped the sd card as well by accident so everything is gone. I tried loading the OS via USB OTG but when i go to mount OTG in TWRP I can't select "USB-OTG".I can only select "system" "cache" and "data" I also tried mounting the phone via the computer but it doesn't show up but it does come up on device manager with a yellow exclamation sign next to it. I've heard you can do something with the ADB Sideload but I have no idea how to do that so if that's the answer please explain in detail.
If someone can get it to where I can mount the OTG then I can handle it from there.
Just some details:
S-on
TWRP version 2.6.3.2
I think i've wiped everyting there is to wipe trying to fix this, (
I've been without a phone for a week now and I'm desperate for any kind of fix. I'd greatly appreciate if someone could steer me in the right direction.
Aceboog33 said:
Ok so I screwed up.
I'm not a developer but i'm familiar with most of the basics. So my m7 was rooted with android revolution 81.0. I was having unrelated problems with calls and also some other small things like a lock screen delay. I decided I was gonna do a system wipe (which I've done plenty of times before with no problems) but this time I forgot to put the OS on the sd card before the wipe. As of now my phone turns on but stays on the HTC screen unless I force it into bootloader and I can also get into TWRP still. I also noticed I wiped the sd card as well by accident so everything is gone. I tried loading the OS via USB OTG but when i go to mount OTG in TWRP I can't select "USB-OTG".I can only select "system" "cache" and "data" I also tried mounting the phone via the computer but it doesn't show up but it does come up on device manager with a yellow exclamation sign next to it. I've heard you can do something with the ADB Sideload but I have no idea how to do that so if that's the answer please explain in detail.
If someone can get it to where I can mount the OTG then I can handle it from there.
Just some details:
S-on
TWRP version 2.6.3.2
I think i've wiped everyting there is to wipe trying to fix this, (
I've been without a phone for a week now and I'm desperate for any kind of fix. I'd greatly appreciate if someone could steer me in the right direction.
Click to expand...
Click to collapse
first thing is first, you need to sort out your driver, so when you see "one " with the yellow exclamation mark in your device manager, right click on it and select update driver, select the 2nd option, browse for driver software, again select the 2nd option which is something like let me choose the driver, it may give you a list after that of the type of device connected, select android devices, then select your latest myHTC driver from the list, it will give you some warning about it may not be the correct driver, are you sure you want to install, select yes.
Next, do you know how to use adb and fastboot ?
Seanie280672 said:
first thing is first, you need to sort out your driver, so when you see "one " with the yellow exclamation mark in your device manager, right click on it and select update driver, select the 2nd option, browse for driver software, again select the 2nd option which is something like let me choose the driver, it may give you a list after that of the type of device connected, select android devices, then select your latest myHTC driver from the list, it will give you some warning about it may not be the correct driver, are you sure you want to install, select yes.
Next, do you know how to use adb and fastboot ?
Click to expand...
Click to collapse
I know it involves the command terminal but no, I've never used it before.
Aceboog33 said:
I know it involves the command terminal but no, I've never used it before.
Click to expand...
Click to collapse
still need help?
madboy_maduka said:
still need help?
Click to expand...
Click to collapse
yes yes i dooo
Aceboog33 said:
yes yes i dooo
Click to expand...
Click to collapse
Sorry I had to leave for work, what you need is adb and fastboot files, so download this link and extract it to your desktop https://www.androidfilehost.com/?fid=23329332407580571
Then download either twrp 2.6.3.3 or 2.6.3.4 from the twrp recovery web site, when it's downloaded, rename it to recovery.img for ease and place it in the same folder as adb and fastboot.
You will then need to open a command Windows within that folder by holding control, shift and right mouse click on any white area within that folder, select open command window here.
Make sure your phone is plugged into the computer, and in the bootloader with fastboot usb showing on the screen.
At this point your drivers must be working as per my other post, then issue the following commands one at a time.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery, your usb otg cable should work now for flashing a Rom, be sure to do a full wipe before flashing, your current recovery sounds too old to me for usb otg support.
---------- Post added at 11:09 AM ---------- Previous post was at 11:00 AM ----------
If your still having problems with usb otg cable at this point, take the Rom which you want to flash and again place it in the same folder on your desktop as adb and fastboot, rename it to Rom.zip for ease, put your phone into recovery and then plug it into the computer, with recovery main screen showing on the phone, once again open a command window on your computer from within the adb and fastboot folder and issue the following command
adb push Rom.zip /sdcard/
Takes about 5 mins and will look unresponsive but it will let you know when it's done, unplug your phone when done, wipe and install.
Seanie280672 said:
Sorry I had to leave for work, what you need is adb and fastboot files, so download this link and extract it to your desktop https://www.androidfilehost.com/?fid=23329332407580571
Then download either twrp 2.6.3.3 or 2.6.3.4 from the twrp recovery web site, when it's downloaded, rename it to recovery.img for ease and place it in the same folder as adb and fastboot.
You will then need to open a command Windows within that folder by holding control, shift and right mouse click on any white area within that folder, select open command window here.
Make sure your phone is plugged into the computer, and in the bootloader with fastboot usb showing on the screen.
At this point your drivers must be working as per my other post, then issue the following commands one at a time.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery, your usb otg cable should work now for flashing a Rom, be sure to do a full wipe before flashing, your current recovery sounds too old to me for usb otg support.
---------- Post added at 11:09 AM ---------- Previous post was at 11:00 AM ----------
If your still having problems with usb otg cable at this point, take the Rom which you want to flash and again place it in the same folder on your desktop as adb and fastboot, rename it to Rom.zip for ease, put your phone into recovery and then plug it into the computer, with recovery main screen showing on the phone, once again open a command window on your computer from within the adb and fastboot folder and issue the following command
adb push Rom.zip /sdcard/
Takes about 5 mins and will look unresponsive but it will let you know when it's done, unplug your phone when done, wipe and install.
Click to expand...
Click to collapse
What the guy above me said was right, the problem I think with your phone is drivers I'll upload a link to adv drivers in my next post, basically using recovery (twrp recommend) wipe /data, /cache & /system. Then go to adb sideload which is in the recovery (it should say something like adb server started). Then using adb devices command check if your computer sees your device if not you gotta install drivers for your computer. In device manager on your computer your device should be something like ADB interface if not drivers are not correctly installed. Right click update drivers I'll link it in ma next post
---------- Post added at 10:30 PM ---------- Previous post was at 10:26 PM ----------
Follow these instructions to install the driver http://visualgdb.com/tutorials/android/usbdebug/manualinstall.php
Aceboog33 said:
yes yes i dooo
Click to expand...
Click to collapse
Use this guide. Saved me one time
http://android-revolution-hd.blogspot.ro/2013/12/how-to-copy-rom-zip.html?m=1
Related
I was changing rom according to instructions and accidentally I have deleted my rom.zip. Now I'm stuck in recovery with nothing to flash and no idea how to push rom.zip to phone memory. I have otg cable. Can anyone come up with a solution or direction to relevant topic ?
Pum4 said:
I was changing rom according to instructions and accidentally I have deleted my rom.zip. Now I'm stuck in recovery with nothing to flash and no idea how to push rom.zip to phone memory. I have otg cable. Can anyone come up with a solution or direction to relevant topic ?
Click to expand...
Click to collapse
Easiest thing would be to put your ROM.zip on your usb and plug it into your phone before entering recovery. I'm not sure if Cwm classic supports otg but Cwm touch and twrp do
Sent from my HTC One using xda premium
redbull123 said:
Easiest thing would be to put your ROM.zip on your usb and plug it into your phone before entering recovery. I'm not sure if Cwm classic supports otg but Cwm touch and twrp do
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
will try. Should I flash it from pendrive or copy to internal and then install ?
I've tried and even it should be possible the device cant mount externel sd what to do now ?
Pum4 said:
will try. Should I flash it from pendrive or copy to internal and then install ?
Click to expand...
Click to collapse
I think it's called external_sd in recovery. Just flash it from there.
Sent from my HTC One using xda premium
---------- Post added at 08:20 PM ---------- Previous post was at 08:11 PM ----------
Pum4 said:
will try. Should I flash it from pendrive or copy to internal and then install ?
I've tried and even it should be possible the device cant mount externel sd what to do now ?
Click to expand...
Click to collapse
Apologies, I've just tried it myself in CWM Touch 6.0.3.1...
Go to Bootloader screen and plug in your cable
enter recovery
install zip from sdcard
choose zip from external sdcard
Works for me...
Sometimes if it doesn't mount I go to 'backup and restore' -> restore from external sdcard -> Go Back -> Go Back -> try it flashing from 'install zip from sdcard' again. (Although I have a nandroid backup on my usb so that may not work for you)
redbull123 said:
I think it's called external_sd in recovery. Just flash it from there.
Sent from my HTC One using xda premium
---------- Post added at 08:20 PM ---------- Previous post was at 08:11 PM ----------
Apologies, I've just tried it myself in CWM Touch 6.0.3.1...
Go to Bootloader screen and plug in your cable
enter recovery
install zip from sdcard
choose zip from external sdcard
Works for me...
Sometimes if it doesn't mount I go to 'backup and restore' -> restore from external sdcard -> Go Back -> Go Back -> try it flashing from 'install zip from sdcard' again. (Although I have a nandroid backup on my usb so that may not work for you)
Click to expand...
Click to collapse
when i try to do that, there is a commend listed: E: Cant mount /external_sd damn it
Pum4 said:
when i try to do that, there is a commend listed: E: Cant mount /external_sd damn it
Click to expand...
Click to collapse
Can you use adb & fastboot commands?
redbull123 said:
Can you use adb & fastboot commands?
Click to expand...
Click to collapse
yes I can, is mini sdk enough ?
Pum4 said:
yes I can, is mini sdk enough ?
Click to expand...
Click to collapse
yeah...
put your rom.zip in your mini-sdk folder
put your phone to the bootloader screen -> select fastboot -> it should now say 'fastboot usb'
hold shift and right-click on your mini-sdk folder -> Open Command Window Here
command: fastboot devices
if your device shows, enter recovery
command: adb devices
if your device shows,
adb push name_of_your_rom.zip /sdcard be sure to put a space before /sdcard. be sure the 'name_of_your_rom' is named exactly the same as your rom.zip
After a while your rom should be on your sdcard, just flash it as normal.
redbull123 said:
yeah...
put your rom.zip in your mini-sdk folder
put your phone to the bootloader screen -> select fastboot -> it should now say 'fastboot usb'
hold shift and right-click on your mini-sdk folder -> Open Command Window Here
command: fastboot devices
if your device shows, enter recovery
command: adb devices
if your device shows,
adb push name_of_your_rom.zip /sdcard be sure to put a space before /sdcard. be sure the 'name_of_your_rom' is named exactly the same as your rom.zip
After a while your rom should be on your sdcard, just flash it as normal.
Click to expand...
Click to collapse
Just did as you said. The tricky part is with opening command line in the specified folder, I would never have guess that you have to hold shift.
Now waiting for the file being moved to sdcard, after push command the _ is blinking as the file is being send right. File is sent XXX bytes in 222.sec
I tried to instal from the sdcard the recovery reboots itself when I press instal from sdcard
Pum4 said:
Just did as you said. The tricky part is with opening command line in the specified folder, I would never have guess that you have to hold shift.
Now waiting for the file being moved to sdcard, after push command the _ is blinking as the file is being send right. File is sent XXX bytes in 222.sec
I tried to instal from the sdcard the recovery reboots itself when I press instal from sdcard
Click to expand...
Click to collapse
Maybe try fastboot screen again,
fastboot erase cache
redbull123 said:
Maybe try fastboot screen again,
fastboot erase cache
Click to expand...
Click to collapse
remote not allowed
Pum4 said:
remote not allowed
Click to expand...
Click to collapse
'fastboot usb' should be on the screen
again, open cmd from your mini-sdk folder
do 'fastboot devices' just to be sure your device is seen
redbull123 said:
'fastboot usb' should be on the screen
again, open cmd from your mini-sdk folder
do 'fastboot devices' just to be sure your device is seen
Click to expand...
Click to collapse
done, entered recovery and when I press instal from sdcard the device is re-booting
the charging led is not lighiting up i fear i will drain it to zero and it will not charge again
Pum4 said:
done, entered recovery and when I press instal from sdcard the device is re-booting
the charging led is not lighiting up i fear i will drain it to zero and it will not charge again
Click to expand...
Click to collapse
ok, can you select install zip from sideload or does it crash?
if you can, select it and command in cmd (from your mini-sdk folder)
adb sideload name_of_your_rom.zip
once its finished sideloading it should begin install on your phone automatically
If you can't do that, try re-flashing your recovery and try everything again.
fastboot flash recovery name_of_your_recovery.img
(in 'fastboot usb') (name_of_your_recovery.img should be in mini-sdk folder)
redbull123 said:
ok, can you select install zip from sideload or does it crash?
if you can, select it and command in cmd (from your mini-sdk folder)
adb sideload name_of_your_rom.zip
once its finished sideloading it should begin install on your phone automatically
If you can't do that, try re-flashing your recovery and try everything again.
fastboot flash recovery name_of_your_recovery.img
(in 'fastboot usb') (name_of_your_recovery.img should be in mini-sdk folder)
Click to expand...
Click to collapse
I pushed sideload:
failed to open driver control: no csuch file or directory (x2)
sideload started now sen the package you want to apply to the device with adb sideload <filename>
in cmd adb devices:
HTXXXXXXX sideload
after command sideload progress is showed but I fear I have deleted sth important on the device ;/
rom was sideloaded but instalation was far to quick and it is still stuck on htc quietly brilliant... I have bricked my device (
Pum4 said:
I pushed sideload:
failed to open driver control: no csuch file or directory (x2)
sideload started now sen the package you want to apply to the device with adb sideload <filename>
in cmd adb devices:
HTXXXXXXX sideload
after command sideload progress is showed but I fear I have deleted sth important on the device ;/
rom was sideloaded but instalation was far to quick and it is still stuck on htc quietly brilliant... I have bricked my device (
Click to expand...
Click to collapse
Just hold down volume down + power button until it reboots. You may have to do it under a bright light. Keep holding them until your fastboot/hboot screen appears.
Try re-flashing your recovery as I said above and try again - if that doesn't work then I'm afraid I'm out of ideas
What ROM are you trying to install??
redbull123 said:
Just hold down volume down + power button until it reboots. You may have to do it under a bright light. Keep holding them until your fastboot/hboot screen appears.
Try re-flashing your recovery as I said above and try again - if that doesn't work then I'm afraid I'm out of ideas
What ROM are you trying to install??
Click to expand...
Click to collapse
just stock 4.2.2... I will try to do that again and if it doesnt work I will try to use ruu method but I wonder do I have to flash stock recovery then ?
Pum4 said:
just stock 4.2.2... I will try to do that again and if it doesnt work I will try to use ruu method but I wonder do I have to flash stock recovery then ?
Click to expand...
Click to collapse
send a link to the page you got the rom. i've never used RUU but I think it flashes stock recovery during the process
redbull123 said:
send a link to the page you got the rom. i've never used RUU but I think it flashes stock recovery during the process
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2281365
http://forum.xda-developers.com/showthread.php?t=2207874
I'm trying to find modeid and cidnum and its pn07100000 and orangb10... dont know which to choose...
I need mz phone tomoorow and Im getting desperate
I have flashed stock recovery and still it bootloops, getting hopeless
Pum4 said:
http://forum.xda-developers.com/showthread.php?t=2281365
http://forum.xda-developers.com/showthread.php?t=2207874
I'm trying to find modeid and cidnum and its pn07100000 and orangb10... dont know which to choose...
I need mz phone tomoorow and Im getting desperate
I have flashed stock recovery and still it bootloops, getting hopeless
Click to expand...
Click to collapse
I don't know anything about RUUs but this is what I would do just to get a working phone:
Flash custom recovery again
Flash Android Revolution 10.2 from here:
http://forum.xda-developers.com/showthread.php?p=38939202
Using adb push or sideload
It's 4.2.2 and close to stock
Sent from my HTC One using xda premium
I am in a massive dilemma at the moment. I recently upgraded my phone using a stock RUU and was unhappy with the way it was working, due to no mobile data. I have been trying to apply a new RUU to my phone but it is not working, I have recently found out that my bootloader is black and that fastboot does not work at all.
When I request a device list in CMD nothing happens and CMD just prints a new directory line, and whenever I issue a command it just says <waiting for device>. I understand that without fastboot I will be unable to install a custom recovery and therefore unable to install a new ROM. I have tried my laptop and a desktop computer and they both do not work, so I'm guessing it is the phone even though I am able to send adb commands.
Any help is appreciated.
Hmm...are you able to boot into the recovery? If yes just restore it with the backup you hopefully have made
Boachti said:
Hmm...are you able to boot into the recovery? If yes just restore it with the backup you hopefully have made
Click to expand...
Click to collapse
Unfortunately there is no custom recovery installed, I can load recovery but it just shows a black screen.
Oh yeah forgot sry
Ehmmm.....
Does the pc make any sound when you plug in your device ?
Boachti said:
Oh yeah forgot sry
Ehmmm.....
Does the pc make any sound when you plug in your device ?
Click to expand...
Click to collapse
Device is recognised while running android and makes a sound, but when in bootloader the computer makes a sound but I get an error message saying that the USB device is not recognised.
hrogers123 said:
Device is recognised while running android and makes a sound, but when in bootloader the computer makes a sound but I get an error message saying that the USB device is not recognised.
Click to expand...
Click to collapse
make sure that you have the latest driver installed and usb debuging has to be on (settings/devoloper options)
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
you said that fastboot isn't working at all so you aren't able to flash for example a custom recovery
you can use adb commands to enter into recovery and to copy a rom zip to your device
then you should be able to flash the custom rom
perhaps this can fix your problem
Boachti said:
make sure that you have the latest driver installed and usb debuging has to be on (settings/devoloper options)
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
you said that fastboot isn't working at all so you aren't able to flash for example a custom recovery
you can use adb commands to enter into recovery and to copy a rom zip to your device
then you should be able to flash the custom rom
perhaps this can fix your problem
Click to expand...
Click to collapse
Drivers are installed and USB debugging is on.
I've already tried adb reboot recovery and it doesn't work just shows a phone with a red triangle so I'm guessing there is no recovery installed, so I'm in an infinite loop.
Can You post a photo of your black boot loader screen please.
Sent from my HTC One using Tapatalk
dear, renew your ADB files and HTC Driver
1-This is ADB files , be sure to extract it in folder (e.x ADB files) in your System partition (e.x C:\)
2-Remove HTCSync, Mobogien, Kies and any mobile softwares then install HTC DRIVER V.4
3-try the FAQ 2 steps in this guide
search for 2) Q: I'm using Windows 7 what should I worry about
if not , try to reset factory your phone > USB debugging is on > try step 3 again
these will help you
gffmac said:
Can You post a photo of your black boot loader screen please.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
http://imgur.com/8ObZ1HN
moha_moha20106 said:
dear, renew your ADB files and HTC Driver
1-This is ADB files , be sure to extract it in folder (e.x ADB files) in your System partition (e.x C:\)
2-Remove HTCSync, Mobogien, Kies and any mobile softwares then install HTC DRIVER V.4
3-try the FAQ 2 steps in this guide
search for 2) Q: I'm using Windows 7 what should I worry about
if not , try to reset factory your phone > USB debugging is on > try step 3 again
these will help you
Click to expand...
Click to collapse
My ADB commands work fine, it is fastboot that doesn't work. I completed your steps anyway and it didn't help.
hrogers123 said:
http://imgur.com/8ObZ1HN
Click to expand...
Click to collapse
with your bootloader photo, you only need to resolve the USB issue, then you can install custom/stock rom easy
hrogers123 said:
Drivers are installed and USB debugging is on.
I've already tried adb reboot recovery and it doesn't work just shows a phone with a red triangle so I'm guessing there is no recovery installed, so I'm in an infinite loop.
Click to expand...
Click to collapse
download this file
rename it > update.zip
edit android-info.txt to meet your phone CID & MID
copy update.zip to your SD card
go to your recovery (red triangle) press Vol up + power once
erase cache
apply from SD card
moha_moha20106 said:
with your bootloader photo, you only need to resolve the USB issue, then you can install custom/stock rom easy
Click to expand...
Click to collapse
Yeah just really confused as to why my computer recognizes the phone while on android o/s but not on bootloader.
Another thing to note is that fact that when I enter FASTBOOT it does not display FASTBOOT USB straight away. I have to press either one of the volume keys and then it switches to FASTBOOT USB.
Here are some pictures of the error message I get in Windows.
moha_moha20106 said:
download this file
rename it > update.zip
edit android-info.txt to meet your phone CID & MID
copy update.zip to your SD card
go to your recovery (red triangle) press Vol up + power once
erase cache
apply from SD card
Click to expand...
Click to collapse
I cannot seem to find the android-info.txt file anywhere.
Just tried it and I get this error message...
-- Install /data/media/0 ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
Write host_mode:0 done
Another update, while checking through the settings on my phone I realised that there are two settings for USB debugging. One is for HTC Sync Manager and the other is from Developer options, shown below;
http://i.imgur.com/I5sV7K5.png
http://i.imgur.com/VJirw7N.png
When I checked My Computer I found that I had two devices connected, HTC One and CD Drive (E
http://i.imgur.com/ELpsgpu.png
I then checked Device Manager to see if their were two devices, and their were.
http://i.imgur.com/dEVGYCO.png
So I'm guessing that when I boot to FASTBOOT it is trying to read the CD Drive and it is unable to read it. I have tried to deselect the HTC Sync debugging but as soon as I do the developer debugging also deselects and vice versa.
hrogers123 said:
I cannot seem to find the android-info.txt file anywhere.
Just tried it and I get this error message...
-- Install /data/media/0 ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
Write host_mode:0 done
Click to expand...
Click to collapse
the android-info.txt in update.zip
---------- Post added at 09:09 AM ---------- Previous post was at 09:04 AM ----------
hrogers123 said:
Another update, while checking through the settings on my phone I realised that there are two settings for USB debugging. One is for HTC Sync Manager and the other is from Developer options, shown below;
http://i.imgur.com/I5sV7K5.png
http://i.imgur.com/VJirw7N.png
When I checked My Computer I found that I had two devices connected, HTC One and CD Drive (E
http://i.imgur.com/ELpsgpu.png
I then checked Device Manager to see if their were two devices, and their were.
http://i.imgur.com/dEVGYCO.png
So I'm guessing that when I boot to FASTBOOT it is trying to read the CD Drive and it is unable to read it. I have tried to deselect the HTC Sync debugging but as soon as I do the developer debugging also deselects and vice versa.
Click to expand...
Click to collapse
uninstall you device from device manager > unplug your phone> restart PC
plug your phone> go to device manager> find your device> right click properties> update driver >search internet for driver
hrogers123 said:
I am in a massive dilemma at the moment. I recently upgraded my phone using a stock RUU and was unhappy with the way it was working, due to no mobile data. I have been trying to apply a new RUU to my phone but it is not working, I have recently found out that my bootloader is black and that fastboot does not work at all.
Any help is appreciated.
Click to expand...
Click to collapse
Your phone appears to be stuck bewteen two firmwares hense the os showing up in red in your bootloader.
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
as opposed to:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot flash zip <name of firmware>.zip <- yes it has to be done twice, the first one will report failed, the second should succeed.
fastboot reboot
Sent from my HTC One using Xparent Skyblue Tapatalk 2
moha_moha20106 said:
the android-info.txt in update.zip
Click to expand...
Click to collapse
I checked the zip and couldn't find it anywhere.
bored_stupid said:
Your phone appears to be stuck bewteen two firmwares hense the os showing up in red in your bootloader.
would I be correct in assuming you did the following commands:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot reboot
as opposed to:
fastboot oem rebootRUU
fastboot flash zip <name of firmware>.zip
fastboot flash zip <name of firmware>.zip <- yes it has to be done twice, the first one will report failed, the second should succeed.
fastboot reboot
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
If your asking about how I installed my current ROM, I downloaded a RUU exe and installed from my desktop.
If your asking me to try those steps now, I can't. FASTBOOT does not respond.
Hi all,
I have an HTC One M8. I bought it used and run a AT&T sim on Straight Talk. Previous owner had rooted it. I was trying to get the 4.4 updates and Sense 6.0.
The phone was already running HD Revolution 12.1 and Android 4.2.2 with TeamWin Recovery Partition v2.5.0.0
I downloaded and installed Android_Revolution_HD-One_71.1.zip.
I've run it several ways:
1. First w/o wiping from TWRP. (Factory reset settings)
2. Installed w/o "Wiping Userdata Partition" and then tried "Wiping Userdata Partition" from the HD Revolution installer.
3. SuperUser by Koush checked.
4. Stops at setting permissions "set_metsdata_recusrsive: some changes failed."
5. Finish
6, Zip Install details say "no MD5 file found".
7. Reboot System and it tells me "Root permissions appear to be lost. Fix root permissions now?" Yes....
Then reboots into white Bootloader screen. Anything selected here takes me to the Recovery page. Anything selected from the REBOOT menu in TWRP takes me to the Bootloader screen.
When this is done it reboots into the white bootloader screen. Any option I pick there takes me to the TWRP recovery.
I'm stumped. Any help /bread crumbs would be appreciated.
Bootloader shows:
**TAMPERED**
**UNLOCKED **
M7_UL pvt ship s-on rh
HBOOT-1.44.0000
RADIO-4A.14.3250.15
OPENDSP-v26.120.274.0202
eMMC-BOOT
May 3 2013, 20:01:28-1
Thanks
TJB
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
TWRP 2.6
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Click to expand...
Click to collapse
I'm actually trying to mount the phone so I can see it from the PC update the TWRP. I downloaded openrecovery-twrp-2.7.1.1-m7.img but can't see how to load it to the phone.
PC sees the phone from Device Manager as a Disk Drive but it doesn't show up as a drive under My Computer.
I have Minimal ADB and Fastboot. Am I on the right track?
TJB
BenPope said:
fastboot erase cache
Then flash TWRP 2.6.3.3
Then reflash the ROM.
Click to expand...
Click to collapse
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
teebright said:
I tried to install openrecovery-twrp-2.7.1.1-m7.img but I can't see HTC from my PC. It shows up as in Device Manager but there's no way to write to it. I have Minimal ADB and Fastboot. Do I need a USB OTG cable. What else can I do from the PC side to see the phone?
Right now I'm just trying to get files to the phone. Am I on the right track?
THB
Click to expand...
Click to collapse
You cannot install like that, they have to be flashed via bootloader.
Do you have ABD installed on your PC?
If not you have two options.
OPTION 1
This guide for Windows 7 machine, this is the quickest way IMHO
Download the adb files for your respective PC from here : http://developer.android.com/sdk/index.html
Once you have downloaded the correct one for your PC (i.e. 32 or 64bit) you will be left with a zip FOLDER named something like this adt-bundle-windows-x86_64-20130522.zip (this is for 64 bit machine), Unzip it somewhere on your pc
Locate the unzipped folder and you should have/see the following inside
• Eclipse
• Sdk
• SDFK manager .exe
Open up the sdk folder and you will find 6 folders inside, cut the 'platform-tools’ folder , then double click my computer and then enter the C: drive of your PC. Paste this folder here in the C: drive and rename it Andriod-adb.
Then right mouse click my computer and go properties, then go and click Advance system settings located on left hand side this will bring up system properties box, click the Environment Variables… tab (it will open further details) and locate the Environment Variables list scroll down until you find path, highlight this then click edit.
Click mouse in here and scroll right to the end after the last entry
Type the following ;C:\Android-adb (noting only adding the first ; if not already there), if it is already there just type C:\Android-adb. Then hit Ok then OK again and your ADB should now be successfully setup.
To test this
From the windows start button, and in the search programs and files box type cmd and enter, this should bring up a command window.
Plug in your device and type adb devices, you should see it locate your phone
OPTION 2
Or try this, extract the attached file to your desk. place your recovery img in here and in a blank spot here hold the shift key down and right mouse click this should bring up list allowing you to "open command prompt here" then follow instructions below..View attachment 2850273
------------------------------------------------------------------------------------------------------------------------------------------------------
Once you have ADB working via either of the above sorted from a
1. Command prompt you should be able to type adb reboot boatloader, if you phone reboots into bootloader go to next step
2. Place the recovery image "openrecovery-twrp-2.7.1.1-m7.img " in the same adb folder as downloaded in option 2
3. Open a command prompt from within this folder and then type fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
4. Once sent it should com back to prompt
5. Type fastboot erase cache, then when completed type fastboot reboot
Good luck
fixed!
I fixed it! Per the recommendation I was trying to upgrade TWRP to 2.6.3.3.
I plugged in the phone to the PC via USB and made sure the phone is in FASTBOOT USB mode from the bootloader menu.
I installed "Minimal ADB and Fastboot" on the PC. Running that from the command line (cmd.exe) you type "fastboot flash recovery " then drag the file in. (watch the youtube video "How to install TWRP recovery on the HTC One M8" by ROOTJUNKIE-it will make more sense). In my case it was the 2.6.3 TWRP.img file. That pushes the update to the phone. I already had the HD 71.1 zip on the phone. I installed that via the TWRP install and from there it booted up normally. Had to setup the phone again but my music/pics were still there. Thanks all for the help!
It's a bit urgent to get solved, I'm at college, and that's the only way to talk with my parents, being 1 or 2 days without answering them would be a problem, since they will start to get worried.
Phone: Motorola Moto G 2014, XT1063
Using Team Win Recovery Project v2.8.0.1
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
DIdn't understand why, but it f**ed up.
Basically I cleaned everything, and in an act of desperation I also lost my sdcard, I've been trying to install the ROM through sideload, but it's not working, I get the error *failed to write data protocol fault no status*, and the phone keeps rebooting, and stuck in the "WARNING BOOTLOADER UNLOCKED"
I appreciate any kind of help, as I said, it's really important to solve this ASAP.
Thanks in advance!
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
gouzzz said:
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
Click to expand...
Click to collapse
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Doppel u r right. follow doppel steps.
doppelhelix said:
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Click to expand...
Click to collapse
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
gouzzz said:
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
Click to expand...
Click to collapse
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
gouzzz said:
EDIT: Now it doesn't charge, or something. I connected it to charge, but it keeps appearing 0% for more than 30 minutes, I can't even access the menu from "Volume Down + Power On"
Click to expand...
Click to collapse
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
doppelhelix said:
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
Click to expand...
Click to collapse
On the MOUNT and UNMOUNT processing I don't see anything on my PC, I don't even know how to unmount it. It only appears Enable MTP and disable.
How am I supposed to load the ROMS?
Tried with sideload but got an errror : "Error executing updater binary in zip .."
Seems like the drivers aren't working properly, I have Windows 8.1, on the site it doesn't talk about it, this might be the problem? Cause I instaled motorola device manager, I scan for drivers but it doens't find anything, and the phone apperas with the yellow triangle on the Device Manager.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
EDIT: I managed to boot the Titan 5.0.2, but now it's stuck in the 4 balls moving around, i waited for about 1hour.
Hello all,
I made a big mistake and wiped my Sd card on my rooted, Unlocked M7. I was able to get recovery(TWRP) back on but for the life of me cannot sideload a Rom on it? At the moment it has no OS. So that means I cannot open usb debugging so I could manually place the ViperOne rom back on the SD. I've never sideloaded anything but after watching many youtube videos and failing ( cannot read ROM.zip) its driving me nuts. Is there maybe an easier way? Maybe something else I can try?
I have tried to load for both desktop and platform tools( both I can see my device).
Splitshot said:
( cannot read ROM.zip)
Click to expand...
Click to collapse
This error is usually caused by the file being in the wrong location. Make sure "ROM.zip" is in the same folder where you have adb and fastboot on your computer.
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
TWRP 2.6.4.0 also include mtp drivers so you can see your device storage on your ocmputer when booted in recovery mode.
Splitshot said:
Hello all,
I made a big mistake and wiped my Sd card on my rooted, Unlocked M7. I was able to get recovery(TWRP) back on but for the life of me cannot sideload a Rom on it? At the moment it has no OS. So that means I cannot open usb debugging so I could manually place the ViperOne rom back on the SD. I've never sideloaded anything but after watching many youtube videos and failing ( cannot read ROM.zip) its driving me nuts. Is there maybe an easier way? Maybe something else I can try?
I have tried to load for both desktop and platform tools( both I can see my device).
Click to expand...
Click to collapse
alray said:
This error is usually caused by the file being in the wrong location. Make sure "ROM.zip" is in the same folder where you have adb and fastboot on your computer.
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
TWRP 2.6.4.0 also include mtp drivers so you can see your device storage on your ocmputer when booted in recovery mode.
Click to expand...
Click to collapse
Like alray said flash TWRP 2.8.4.0 and the phone will be seen in windows and you can just copy the file to the phone and flash it
I already had a "Install recovery v1.2" in my downloads so I tried this because I was unsuccessful with all the other attempts and low and behold it worked. although its an older version of TWRP (2.6.3). would it make a difference not having the latest? now that recovery is there I was hoping to push a ROM then update the recovery through root manager.
I just read alray's last line about the mtp drivers. OK, I will first get my folders working better, upgrade to a newer version TWRP and then push a rom. Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.
Splitshot said:
I already had a "Install recovery v1.2" in my downloads so I tried this because I was unsuccessful with all the other attempts and low and behold it worked. although its an older version of TWRP (2.6.3). would it make a difference not having the latest? now that recovery is there I was hoping to push a ROM then update the recovery through root manager.
I just read alray's last line about the mtp drivers. OK, I will first get my folders working better, upgrade to a newer version TWRP and then push a rom. Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.
Click to expand...
Click to collapse
you don't need adb at all if you load TWRP 2.8.4.0 you just copy the file in windows like to a flash drive
Splitshot said:
upgrade to a newer version TWRP and then push a rom.
Click to expand...
Click to collapse
If you are going to update twrp to 2.8.4.0, you will not need to push or sideload the rom, just copy it to your phone storage using the windows explorer. Navigate to "my computer --> One --> Internal storage" and copy your rom there.
Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.
Click to expand...
Click to collapse
These 2 commands means nothing. :laugh: SO no, there is no difference between these 2 commands, both will fail lol
if you want to use adb push:
Code:
adb push name_of_rom.zip /sdcard
if you want to sideload:
Code:
adb sideload name_of_rom.zip
But like i said, you don't need to use these commands to get your rom on your phone if you are gonna update twrp to 2.8.4.0.
download twrp 2.8.4.0, save it to the same folder where you have adb and fastboot installed on your computer. Open a command prompt from that folder, boot your phone in bootloader/fastboot usb mode.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery mode
you'll now see your phone storage on your computer, copy (drag and drop) your rom.zip to your phone storage.