Database Develop

Please Help!

Hello,
I've just unlocked the bootloader, flashed twrp recovery, wiped and tried to install a rom but the rom bootlooped (turned out it was corrupt) and now i'm stuck with a 700$ phone and a recovery. I've tried adb sideload (on my mac it doesnt even recognize the command), running fastboot update, but that doesnt work. I'm hopeless and I need some hope. PLEASE HELP!

will748 said:
Hello,
I've just unlocked the bootloader, flashed twrp recovery, wiped and tried to install a rom but the rom bootlooped (turned out it was corrupt) and now i'm stuck with a 700$ phone and a recovery. I've tried adb sideload (on my mac it doesnt even recognize the command), running fastboot update, but that doesnt work. I'm hopeless and I need some hope. PLEASE HELP!
Click to expand...
Click to collapse
There is only one way to fix this and that is ADB sideload. You need to get to a windows PC and bring a good copy of the ROM you want to install. Make sure you have Clockworkmod recovery flashed. And then sideload the rom. Also make sure to keep the rom zip name short and simples too long or spaces can cause it to fail.

nullkill said:
There is only one way to fix this and that is ADB sideload. You need to get to a windows PC and bring a good copy of the ROM you want to install. Make sure you have Clockworkmod recovery flashed. And then sideload the rom. Also make sure to keep the rom zip name short and simples too long or spaces can cause it to fail.
Click to expand...
Click to collapse
Sadly I do not have access to a windows PC . I'm going to try and reinstall the stock recovery, as that may fix my boot image, as that was the part of the rom I flashed that had been corrupted. Thankyou for your response.

will748 said:
Sadly I do not have access to a windows PC . I'm going to try and reinstall the stock recovery, as that may fix my boot image, as that was the part of the rom I flashed that had been corrupted. Thankyou for your response.
Click to expand...
Click to collapse
I have a Mac as well but it's good to have a Windows bootcamp partition for times like this.
Sent from my HTC One using xda premium

(Q) How to S-Off w/ bootloader

I have no OS installed, cant mount data, cant run commands or it tells me "error device not found" I am able to go into bootloader and run some commands, not all though. I cant even sideload anything Ive tried it with the toolkit and other ways. i've tried uninstalling drivers, switching between TWRP and CWM, flashing the ruu stock, many more things. I will DONATE $ to whoever can help me the fastest please!

Cudeh said:
I have no OS installed, cant mount data, cant run commands or it tells me "error device not found" I am able to go into bootloader and run some commands, not all though. I cant even sideload anything Ive tried it with the toolkit and other ways. i've tried uninstalling drivers, switching between TWRP and CWM, flashing the ruu stock, many more things. I will DONATE $ to whoever can help me the fastest please!
Click to expand...
Click to collapse
if you are getting a device not found and cant sideload sounds like it maybe a driver issue. Having TWRP 2.6.0.1 the latest adb.exe and the drivers on a windows 8 machine will let you sideload. I formatted my system once too before and as long as you can get to the bootloader and recover you can recover from it. if you can install a ROM like CM or Stock and then try to S-Off from there
http://forum.xda-developers.com/showthread.php?t=2390821

I have no OS installed, cant mount data, cant run commands or it tells me "error device not found" I am able to go into bootloader and run some commands, not all though. I cant even sideload anything Ive tried it with the toolkit and other ways. i've tried uninstalling drivers, switching between TWRP and CWM, flashing the ruu stock, many more things. I will DONATE $ to whoever can help me the fastest please!
Click to expand...
Click to collapse
Disable any firewall, (including Windows firewall) disable anti virus, if you have it uninstall HTC sync, if Windows still doesn't recognize your device uninstall the HTC drivers reboot your computer and reinstall HTC drivers and try again.
Sent from my HTCONE using xda app-developers app

Cudeh said:
I have no OS installed, cant mount data, cant run commands or it tells me "error device not found" I am able to go into bootloader and run some commands, not all though. I cant even sideload anything Ive tried it with the toolkit and other ways. i've tried uninstalling drivers, switching between TWRP and CWM, flashing the ruu stock, many more things. I will DONATE $ to whoever can help me the fastest please!
Click to expand...
Click to collapse
use diskdrive (2GB) and copy your custom rom there.. and use USB OTG to mount and flash your custom rom from recovery. it works for me..

I did this the other day, I recently got a red htc one so I wanted everything cleaned. TWRP 2.6.0.1 breaks USB-OTG support. Just flash TWRP 2.5, get a usb-otg adapter (a couple bucks on eBay if you don't have one). I format my flash drive to fat32, put your rom on, go into mount into TWRP make sure you mount and then install.

Need Help Unbrick My HTC One M7

My HTC One M7 is stuck at HTC logo and will not boot further. I've tried many methods, but cannot repair the phone. It's M7 Europe HTC_001 Firmware 1.29.401.13.
With bootloader unlocked I flash cwm recovery and tried to copy custom rom to flash but phone cannot mount usb storage. I tried to flash stock RUU 1.28.401.7, it won't flash because of hboot error. I tried to flash PN07IMG_1.29.401.13.zip using fastboot flash zip. firmware.;zip, with locked or unlocked bootloader, it won't flash, giving error.
Is there any full RUU 1.29.401.17 or RUU 2.17.401.1 firmware out there for download? I think that's my only solution is to get the same or higher full and not OTA firmware. Would it be possible to ADB push custom rom to phone if it can only power and stuck at logo? Or any other solution, please help, thanks.

There is far from enough info to help you
Have you looked at Hasoon's all in one?
http://forum.xda-developers.com/showthread.php?t=2183942
or mikes thread?
http://forum.xda-developers.com/showthread.php?t=2265618
It reads as though you need to read and ensure you understand before you attempt to resolve this
I like mikes method and both are proven to work
Please use the search option as it works

L0rdNels0n said:
There is far from enough info to help you
Have you looked at Hasoon's all in one?
http://forum.xda-developers.com/showthread.php?t=2183942
or mikes thread?
http://forum.xda-developers.com/showthread.php?t=2265618
It reads as though you need to read and ensure you understand before you attempt to resolve this
I like mikes method and both are proven to work
Please use the search option as it works
Click to expand...
Click to collapse
Thanks for your help but I've tried all that. First phone cannot "mount USB storage" in custom recovery so I cannot copy any file to the phone. Flashing stock RUU is not possible because there is no RUU 1.29.401.13.exe or higher, only OTA. Is it possible to downgrade hboot with s-on and in fastboot mode? Any other suggestion? Thanks.

citifone said:
Thanks for your help but I've tried all that. First phone cannot "mount USB storage" in custom recovery so I cannot copy any file to the phone. Flashing stock RUU is not possible because there is no RUU 1.29.401.13.exe or higher, only OTA. Is it possible to downgrade hboot with s-on and in fastboot mode? Any other suggestion? Thanks.
Click to expand...
Click to collapse
Try ADB push/sideload: http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload

FIX
Hi, I was having the same problem, NOTHING was working, ADB Sideload failing, etc. and the OTG cable arrives tomorrow...my way to fix it?
1.- Went to TWRP Recovery
2.- Wipe>Advance Wipe> Wiped everything
3.- Format Data (option next to Advance Wipe)
4.- Reboot into Recovery(during reboot it said "your device is not rooted, want to root?) Marked yes.
5.- Advance Adb Sideload
6.- Sent CyanogenMod ROM...BANG! worked.
Hope this helps

I've tried to use adb push method but when I put phone to recovery (phone shows red triangle) and run command adb devices, it cannot see the device. Is it because of the drivers? I've installed all drivers and do not see any drivers error in device manager...I really appreciate all the helps from everyone and I spent so much time trying to fix this phone already and I feel I'm so closed now to fix it but just need little more help..Thanks..

L0rdNels0n said:
There is far from enough info to help you
Have you looked at Hasoon's all in one?
http://forum.xda-developers.com/showthread.php?t=2183942
or mikes thread?
http://forum.xda-developers.com/showthread.php?t=2265618
It reads as though you need to read and ensure you understand before you attempt to resolve this
I like mikes method and both are proven to work
Please use the search option as it works
Click to expand...
Click to collapse
Samper27 said:
Hi, I was having the same problem, NOTHING was working, ADB Sideload failing, etc. and the OTG cable arrives tomorrow...my way to fix it?
1.- Went to TWRP Recovery
2.- Wipe>Advance Wipe> Wiped everything
3.- Format Data (option next to Advance Wipe)
4.- Reboot into Recovery(during reboot it said "your device is not rooted, want to root?) Marked yes.
5.- Advance Adb Sideload
6.- Sent CyanogenMod ROM...BANG! worked.
Hope this helps
Click to expand...
Click to collapse
Thanks for your tips and advice..After many hours of trying, my phone is NOW ALIVE. This is how I did it:
1)Find a custom rom from this forum and rename to rom.zip, of course if you use windows like me with .zip extension hidden then just simply rename it rom (to make it simple and short) and copy it to adb shell folder.
2)After unlock bootloader, flash a custom recovery, find it in this forum or here: http://clockworkmod.com/rommanager
3) Boot phone to recovery, and select Install zip from sideload and plug phone to PC. Wait until phone installs all adb drivers..
4) In adb shell type command: "adb devices" without quotes, of course..to make sure adb sees your phone..You should see your devices name.
5) In adb type commad" adb sideload rom.zip..at this point you should see "sending: sideload....1%..wait until it show 100%..some roms like the one I used, Android Revolution HD One 12 (4.2.2) need to install from the screen, just follow instruction on screen and let it finish installation and wola, it's alive again..
I hope this will help someone who have similar problem with this phone. Thanks for the help from everyone.

HTC ONE not started, only htc logo
Hi how are you? I have a one mobile Htc One M7, just not started but show only htc logo. Plase help me!

citifone said:
Thanks for your tips and advice..After many hours of trying, my phone is NOW ALIVE. This is how I did it:
1)Find a custom rom from this forum and rename to rom.zip, of course if you use windows like me with .zip extension hidden then just simply rename it rom (to make it simple and short) and copy it to adb shell folder.
2)After unlock bootloader, flash a custom recovery, find it in this forum or here: http://clockworkmod.com/rommanager
3) Boot phone to recovery, and select Install zip from sideload and plug phone to PC. Wait until phone installs all adb drivers..
4) In adb shell type command: "adb devices" without quotes, of course..to make sure adb sees your phone..You should see your devices name.
5) In adb type commad" adb sideload rom.zip..at this point you should see "sending: sideload....1%..wait until it show 100%..some roms like the one I used, Android Revolution HD One 12 (4.2.2) need to install from the screen, just follow instruction on screen and let it finish installation and wola, it's alive again..
I hope this will help someone who have similar problem with this phone. Thanks for the help from everyone.
Click to expand...
Click to collapse
epic, thank you for the useful post

[Q] Help please stuck on HTC boot screen

I've recently done the conversion to the Google Edition but since my headphone didn't work with it I wanted to go back to Stock.
Unfortunately I completely screwed up...
The current state of my phone is:
I can't boot, only end up at the white HTC logo boot screen
I can't recover my nandroid backup because CWM says "Can't mount SD card"
I can't flash the RUU I found because my firmware is too high...
I can't root / flash a different because I can't transfer any files to my phone
I can't S-off my phone because adb doesn't see it... (Using rumrunner)
I really have no idea what to do and I don't even know how I reached this point. I just flashed the Rom for stock HTC M7 JB and had multiple errors occurring decided to try flashing KitKat which didn't work and suddenly nothing worked anymore.
Does anyone have an idea of what I could try?
Thanks a lot for our help!
Further details:
Unlocked & Tampered recovery
S-On
HBoot 1.55
OS 3.62.401.1

chibi03 said:
I've recently done the conversion to the Google Edition but since my headphone didn't work with it I wanted to go back to Stock.
Unfortunately I completely screwed up...
The current state of my phone is:
I can't boot, only end up at the white HTC logo boot screen
I can't recover my nandroid backup because CWM says "Can't mount SD card"
I can't flash the RUU I found because my firmware is too high...
I can't root / flash a different because I can't transfer any files to my phone
I can't S-off my phone because adb doesn't see it... (Using rumrunner)
I really have no idea what to do and I don't even know how I reached this point. I just flashed the Rom for stock HTC M7 JB and had multiple errors occurring decided to try flashing KitKat which didn't work and suddenly nothing worked anymore.
Does anyone have an idea of what I could try?
Thanks a lot for our help!
Further details:
Unlocked & Tampered recovery
S-On
HBoot 1.55
OS 3.62.401.1
Click to expand...
Click to collapse
let me guess your trying all this from a windows 8.1 pc?

clsA said:
let me guess your trying all this from a windows 8.1 pc?
Click to expand...
Click to collapse
It's Window 7.

chibi03 said:
It's Window 7.
Click to expand...
Click to collapse
Thats great !!
install the HTC Sync and then uninstall it but leave the drivers
next step is boot to recovery
and from their try
adb devices
if it works
adb push this file to your phone
http://forum.xda-developers.com/attachment.php?attachmentid=2481786&d=1388342684
adb push TWRP_2.6.3.3_m7.zip data/media/0/
make sure TWRP_2.6.3.3_m7.zip is in the same directory as adb before push
you flash that from recovery the same you do a rom .. then reboot to recovery to see it
Also note that your s-on and cannot use a kitkat rom
find ARHD 31.6 here and push it the same you did the recovery
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html

clsA said:
Thats great !!
install the HTC Sync and then uninstall it but leave the drivers
Click to expand...
Click to collapse
I have done that but while in custom Recovery my phone isn't recognised. And at the Htc boot screen adb doesn't list the device but Windows sees it as plugged in but not started.

chibi03 said:
I have done that but while in custom Recovery my phone isn't recognised. And at the Htc boot screen adb doesn't list the device but Windows sees it as plugged in but not started.
Click to expand...
Click to collapse
then uninstall all your htc drives and do it again
if you know how to manually install drivers from device manager you can use these

Flash TWRP recovery and push ROM with ADB.
Reboot into TWRP.
Press mount and just choose DATA
Leave it and then push your rom file with "adb push rom.zip /sdcard/.
When its done you will get a message that files are transfered, Now flash rom

Thanks, that worked.
clsA said:
then uninstall all your htc drives and do it again
if you know how to manually install drivers from device manager you can use these
Click to expand...
Click to collapse
Thanks for your help but reinstalling the drivers didn't work.
bihslk said:
Flash TWRP recovery and push ROM with ADB.
Reboot into TWRP.
Press mount and just choose DATA
Leave it and then push your rom file with "adb push rom.zip /sdcard/.
When its done you will get a message that files are transfered, Now flash rom
Click to expand...
Click to collapse
Thank you! that did the trick, I was really worried that I won't be able to fix this but you saved me.

chibi03 said:
Thanks for your help but reinstalling the drivers didn't work.
Thank you! that did the trick, I was really worried that I won't be able to fix this but you saved me.
Click to expand...
Click to collapse
No problem mate.. Good luck

[SOLVED] E: Can't mount /cache/

I'm sorry to do this, but I don't know where to start. Here's what I did to get to where I'm at:
- previously running SlimBean flashed using TWRP
- Downloaded ROM Manager and it recommended installing CWM Recovery
- Followed prompts
- It installed CWM 6.0.4.8
- Booted back into ROM and used ROM Manager to attempt to flash SlimKat 4.4.2 build 6
- CWM wiped dalvik but then got hung up
- Now it keeps saying Can't mount /cache/recovery/command
I'm completely stuck. Can't figure out what to do next. Please help!!!

Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?

Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.

dougeedug said:
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Click to expand...
Click to collapse
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Seanie280672 said:
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
Click to expand...
Click to collapse
I can't quite risk doing this yet. Only as a last, last resort...

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
I can't quite risk doing this yet. Only as a last, last resort...
Click to expand...
Click to collapse
whilst your phone is in recovery and plugged into your computer, open device manager, is there a yellow ! where its says android devices or myHTC ?
IGNORE THIS, You got it working whilst I was typing this.

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed.
Click to expand...
Click to collapse
Use the command "fastboot devices" from the bootloader with "fastbootUSB" highlighted. You can't use adb commands in the bootloader because adb is to interact with android, which is not running while in bootloader. Let me know if you get output with the "fastboot devices" command.
EDIT: I should specify, if you are trying to flash recovery from anywhere but the bootloader using fastboot commands (it sounds like you may be trying to flash recovery with adb commands), you are just doing it wrong. so lets get that sorted first.

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Click to expand...
Click to collapse
you flash a custom recovery with fastboot commands not adb commands.

Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...

cartisdm said:
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
Click to expand...
Click to collapse
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.

Seanie280672 said:
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Click to expand...
Click to collapse
I didn't do so intentionally, but it's possible I did it without paying attention. I'm back to my system now so I'll just live with the loss. I flashed an existing ROM that I had in my Downloads folder once I was able to get into TWRP. It's just weird that folder is empty now.