Database Info

What did I do to my phone? Please help.

On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.

Just to add, I'm getting the message "no OS installed" when trying to reboot in recovery.

ul49 said:
On a mac here. I think I got a bit over my head here with the 2.20 root. I did all of the bootloader unlocking successfully, installed TWRP, and then downloaded CM10, and flashed the boot.img.
Now when trying to boot the phone I get stock on the screen with "This Build is for development only."
I can get into recovery, but don't really know what to do from there. I'm trying to mount, but can't get the computer to recognize the device. Tried a factory reset and it failed. I'm not quite bricked, but sort of stuck and don't know what to do. I'd love to get CM10 working, but at least I want to be able to use my phone.
I'm pretty new to Android so sorry for newbishness.
Thanks anyone for your help.
Click to expand...
Click to collapse
Did you flash the boot.img first, then the ROM?
Can you wipe System?

Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.

ul49 said:
Sorry, what's the difference betwwen boot.img and the rom itself? I only flashed boot.img. I did wipe the system.
Click to expand...
Click to collapse
The boot.img has the kernel in it. If you didn't flash the CM10.zip you have no operating system.
Wipe System, and Factory Reset
Flash boot.img
Flash the CM10.zip, flash google apps, and you should be good after that

Now flash the rom zip from recovery (twrp)
Sent from a slithery smooth phone!

So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help

ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
no,you flash the boot.img in fastboot, and then you flash the rom.zip and gapps.zip from recovery (twrp)

ul49 said:
So to flash the zip file for the ROM and gapps, I just enter fastboot flash boot 'rom.zip' or 'gapps.zip'?
Also, what do I do after I've flashed them?
Thanks so much for your help
Click to expand...
Click to collapse
No, do a clean wipe.
boot your phone into fastboot
download the fastboot files http://www.mediafire.com/?4dx982z93w8z7wk and extract them to your desktop
on your computer, open up cmd and type
cd desktop
cd foldername (the folder that has fastboot.exe)
fastboot flash boot boot.img
reboot into recovery
flash CM10, flash gapps, reboot

I see. The problem is that I seem to be unable to mount my phone and sd card through recovery.

Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.

ul49 said:
Trying to push the zips using adb using './adb push cm10.zip/sdcard' but when I enter this command in terminal it seems to just reload adb, and not push the file.
Click to expand...
Click to collapse
I think you are typing the command wrong
./adb push file /destination
or ./adb push cm10.zip /mnt/sdcard
./adb push cm10.zip /sdcard
whatever the mount point is for the sdcard

Tried that too. It just reloads the opening adb dialogue.

ul49 said:
Tried that too. It just reloads the opening adb dialogue.
Click to expand...
Click to collapse
does ./adb devices return your phone as connected?

Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.

ul49 said:
Well, now it doesn't. Instead of reloading the adb dialogue now, when I try the push command it says device not found. Just came out of nowhere. How do I make it recognize the phone again?
Thanks for bearing with me here. I think I'm really close.
Click to expand...
Click to collapse
I'm not familiar with OS X and android, are there any specific drivers you may need to install?
Are you in your bootloader or recovery?

All necessary drivers were installed. The device was being recognized before, but for some reason isn't now. I'm stuck on the "This build is for development purposes only" screen now since I can't get into recovery or bootloader using adb now since the device isn't recognized...

Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"

ul49 said:
Ok, I'm connected again somehow. Now just trying to figure out this pushing issue. Entered this command './adb push /android/cm10.zip /sdcard and it looked like it was working then said "failed to copy to /sdcard"
Click to expand...
Click to collapse
because it is probably at /mnt/sdcard

Successfully pushed the files. Of course, I've hit another problem. Trying to install the ROM through TWRP and it's failing. Same with Gapps. I'm seeing "unable to mount /sdcard" and unable to mount storage. I've already cleared cache, wiped system, factory reset/

[Q] Bootloop with no Rom installed

Could any one help me please?
I unlocked my bootloader using the One Tool. Installed CWM recovery but I formatted the whole device with no Rom or back up. I then tried to run a RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4) to restore it all back to to stock. But it only send me to a black HTC screen. Nothing else.
When I try to install the stock recovery the One Tool can not find the the phone.
Can anyone help at all please?
Does anyone know how I can bring it at least to a working order?

Vivimagic said:
Installed CWM recovery but I formatted the whole device with no Rom or back up.
Does anyone know how I can bring it at least to a working order?
Click to expand...
Click to collapse
At this point you can adb push a custom rom zip to your sdcard (mount it in recovery first) and flash it. Then boot back into bootloader and fastboot flash the boot.img from the rom.
Alternatively, you can adb push a system.img extracted from a RUU to your sdcard and then dd it into /dev/block/mmcblk0p33

touch of jobo said:
At this point you can adb push a custom rom zip to your sdcard (mount it in recovery first) and flash it. Then boot back into bootloader and fastboot flash the boot.img from the rom.
Alternatively, you can adb push a system.img extracted from a RUU to your sdcard and then dd it into /dev/block/mmcblk0p33
Click to expand...
Click to collapse
Well that is the problem I can't mount the SD card via Recovery! Other. I have also tried to sideload a Rom as well.

Vivimagic said:
Well that is the problem I can't mount the SD card via Recovery! Other. I have also tried to sideload a Rom as well.
Click to expand...
Click to collapse
It is normal that you can't mount your sdcard onto your PC over USB in recovery, but you should be able to just mount it onto the root filesystem, so that you can adb push. Do you get an error message when trying to mount the sdcard in recovery? If you do, there is a sticky for that here in the Q&A forum. It comes down to flashing a stock recovery and then clearing storage or performing a factory reset in bootloader.

touch of jobo said:
It is normal that you can't mount your sdcard onto your PC over USB in recovery, but you should be able to just mount it onto the root filesystem, so that you can adb push. Do you get an error message when trying to mount the sdcard in recovery? If you do, there is a sticky for that here in the Q&A forum. It comes down to flashing a stock recovery and then clearing storage or performing a factory reset in bootloader.
Click to expand...
Click to collapse
Ah ok. I do get a problem with Windows install the HTC MTP drivers when I am in Recovery. Basically I can't turn on USB debugging because there is no Rom to tell it to be in that mode, and that is why it thinks it is an MTP device!
Yes the error on CWM is "E: Can't mount <location>
I think I need to sort out the driver before I can start flashing the stock recovery.
I have tried to return the recovery to stock but it just won't send it to my phone. I can however mount it a disk drive via CWM.

Vivimagic said:
Ah ok. I do get a problem with Windows install the HTC MTP drivers when I am in Recovery. Basically I can't turn on USB debugging because there is no Rom to tell it to be in that mode, and that is why it thinks it is an MTP device!
Yes the error on CWM is "E: Can't mount <location>
I think I need to sort out the driver before I can start flashing the stock recovery.
I have tried to return the recovery to stock but it just won't send it to my phone. I can however mount it a disk drive via CWM.
Click to expand...
Click to collapse
You don't need debugging to use adb in recovery, recovery already has adb. Have you tried "adb push rom.zip /sdcard/rom.zip" while in recovery?

I had the same problem and this post helped me immensly
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
Mine is a US RUU though so you might need to find a European RUU

softbrick woes

Firstly, I am sorry for creating such a noob thread on the forum, but I could really use a hand.
I was flashing a 4.4 ROM (SlimKat), I had wiped /system, /boot, etc. everything but usb storage. I then went to flash the .zip and everything looked alright for about 30 seconds (formatting finished, mounting partitions, etc.) until the installation hit a bump and said there was an error in the ROM .zip, and then aborted.
I have a NANDroid backup on the USB storage, but for some reason CWM refuses to install it claiming there is an MD5 mismatch. USB storage won't mount to my PC (in CWM) for whatever reason, and fastboot won't work in either win7 or ubuntu. I've tried AdamOutler's unbrickable tool with no success, it can't recognise the device and says SBL Injection Failure.
Any ideas? Thanks very much for any help.

mrjimyjohn said:
Firstly, I am sorry for creating such a noob thread on the forum, but I could really use a hand.
I was flashing a 4.4 ROM (SlimKat), I had wiped /system, /boot, etc. everything but usb storage. I then went to flash the .zip and everything looked alright for about 30 seconds (formatting finished, mounting partitions, etc.) until the installation hit a bump and said there was an error in the ROM .zip, and then aborted..
Click to expand...
Click to collapse
What exactly was the error?

There wasn't a real error dialogue, if I remember right it just displayed "ERROR: there was an error in <ROM package.zip> installation aborted" The next line said something like "(code 7)".
Thanks man

Which CWM version were you using?

I was using 6.0.3.1. One of the first things I thought of was updating the recovery, but with no way to mount /sdcard I don't know how I could.

mrjimyjohn said:
I was using 6.0.3.1. One of the first things I thought of was updating the recovery, but with no way to mount /sdcard I don't know how I could.
Click to expand...
Click to collapse
You need at least CWM 6.0.4.3 to install any 4.4 rom. Flash the recovery.img via fastboot.
Download the latest CWM (.img, not .zip) and then also install this: http://forum.xda-developers.com/showthread.php?t=2317790, connect your device to pc, reboot to bootloader (vol up + power button) then enter this in command prompt provided by "minimal adb and fastboot": fastboot flash recovery <recovery img path and filename>.img
This should fix your problem if done correctly.

Thank you very much, I will try that.
I think the problem though, is that my pc cannot recognize the device in any form. Normally I would expect to at least see a "device not working properly" or similar message with the windows "beep", but I get nothing, in fastboot mode or with usb storage mounted in recovery. On a different ubuntu machine it's not recognized either, fastboot - devices and adb -devices both return nothing.

Try having your device drivers set-up through Nexus Root Toolkit. Just follow the "Full Driver Installation Guide" inside the app and delete all samsung drivers and then freshly install drivers needed for your device. This is worth the shot although the problem could be your usb cable, usb port, etc..

Thanks for your help. I actually tried Wug's tool with no luck, but I didn't ununstall the original drivers first so that may have been the problem. I'll also try using a different cords and PCs when I get back home.
Thanks again, and merry christmas!

So I bought a new usb cable and my pc could talk to the device as it was showing up in device manager. I installed the drivers again and got fastboot working, but I'm not really sure how to flash from here. I flashed the new CWM with
fastboot flash recovery <cwm*.zip>
It worked just fine, but how can I flash a rom now? regular .zip rom's can't be flashed through fastboot AFAIK, and looking through my NANDroid backups it looks like none of them have a system.img which seems really weird. Can I flash a system.ext4.tar.a as if it was a system.img?
I would have thought you could transfer files to /sdcard through fastboot but I guess not...

mrjimyjohn said:
So I bought a new usb cable and my pc could talk to the device as it was showing up in device manager. I installed the drivers again and got fastboot working, but I'm not really sure how to flash from here. I flashed the new CWM with
fastboot flash recovery <cwm*.zip>
It worked just fine, but how can I flash a rom now? regular .zip rom's can't be flashed through fastboot AFAIK, and looking through my NANDroid backups it looks like none of them have a system.img which seems really weird. Can I flash a system.ext4.tar.a as if it was a system.img?
I would have thought you could transfer files to /sdcard through fastboot but I guess not...
Click to expand...
Click to collapse
Oh I thought you already put your desired rom inside the sdcard. My workaround for this: flash TWRP via fastboot, mount sd card to pc, move rom.zip to sdcard, then re-flash latest CWM via fastboot. Flash rom through recovery.

I did have it on there originally but I foolishly did a full wipe through fastboot. I tried to mount SD card with cwm but my PC still wouldn't recognise it, does TWRP mount things differently or something? All is good now though, I didn't realise you could use adb while in recovery mode so I could push files that way with sideload. Thanks for your help man, its really, uh, helped.

[Q] Help - Rooting gone wrong

So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!

Akkordinator said:
So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!
Click to expand...
Click to collapse
TWRP has ADB Sideload feature. Means you can flash zips using adb. Of course you can flash a roms this but keep in mind you have to flash the kernel (boot.img) manually immediately after flashing the rom.zip. When flashed Rom.zip by using ADB sideload method make SURE that you direct go into fastboot mode and flash the kernel (fastboot flash boot boot.img) (you can extract the boot.img from your rom.zip)
May be a compatible rom this time? But you're lucky -> Infact you already deleted everything you won't have to perform a wipe before flashing lol

LS.xD said:
Of course you can flash a roms
Click to expand...
Click to collapse
Ok, but I dont know with which command (fastboot flash what? or adb?)

You can use adb sideload as followed:
Start TWRP -> advanced -> ADB sideload + swipe to activate it. Connect your phone to the computer. Open "CMD Commandline" and type "adb sideload ROMNAME.zip"
Of course "ROMNAME" has to match the zip you want to flash. Thats it
In twrp go to "REBOOT" -> "fastboot"
When fastboot usb is ready use CMD commandline again and type "fastboot flash boot boot.img"
Then you can boot android

I whished I could. As I start ADB sideload it keeps doing nothing at all until I abort it. What I think is important to know is that it is then:
"E:Unable to mout '/internal_sd'
E:Unable to mount storage.", which I think is the problem.

Flash Stock recovery And perform "factory Reset + clear storage" that will fix your storage. Then flash twrp Version 2.7 again and do what I suggested to flash the Rom
Sent from my beloved HTC One S using (most time buggy) Tapatalk

Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.

Akkordinator said:
Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.
Click to expand...
Click to collapse
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
You're facing sdcard bug.
This is how to solve:
1. Flash stock recovery
2. reboot to bootloader and perform "factory reset + clear storage" (While in bootloader NOT in recovery)
3. Flash custom recovery again
4. Reboot recovery - mount usb storage - copy ROM.zip to sdcard // adb sideload rom
7. NOW boot android (Not at any time before! Even there is no system installed)
Please just repeat it.

LS.xD said:
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
Click to expand...
Click to collapse
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!

Akkordinator said:
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!
Click to expand...
Click to collapse
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?

LS.xD said:
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?
Click to expand...
Click to collapse
It was windows! Tried it on the other computer with win7 instead of 8.1 and I finally got a connection!
Thanks so much!!!

[Q] M4 soft-bricked! Cannot restore backup! Need help!!!

Hey guys,
I seriously need help with my M4. I think I might have soft-bricked it :crying:
Here's what I have done:
I unlocked it and installed TWRP 2.7.1.1 to install a custom ROM. The thing is, I didn't know it was branded (as I found out too late, the CID is VODAP102), so the ROM wouldn't install. Now, I tried to change the CID to a SuperCID (11111111) but ran out of luck. So I thought I'd simply revert to Stock. So far, so good. Yesterday I got an update notification for a Sense 6.0 update but it wouldn't install. So I successfully flashed the stock recovery but the installation of the update halted (red exclamation mark). I then went back to flashing the boot.img too (from an UL rom, unfortunately) and relocked the bootloader. Still the same error. Then I read I should factory reset in the bootloader. So I did and the result was I got stuck on the bootscreen!! So I unlocked it again, re-installed the TWRP recovery to at least get back to the backup I made before, but the thing is: My storage got wiped and TWRP won't mount OTG-USB!!! I guess it's that some partitions/files are now messed up. Now I cannot do anything anymore. I don't have the stock ROM as a flashable zip, only the TWRP backup.
Here's what still works:
Fastboot & Recovery
What doesn't work:
ADB (because phone won't boot), ExtSDcard (naturally!) and flashing ROMs via fastboot because I need one that matches that damn Vodafone CID
I think if someone could upload their Vodafone Germany M4 ROM as a zip or exe, I could manage it. If someone has it, PLEASE give it to me!
If someone has any other idea how to get this phone to work, or at least get TWRP to mount the USB-stick, please HELP!!! I'm totally at a loss :crying:

You can ADP from TWRP so all is not lost

apjashley said:
You can ADP from TWRP so all is not lost
Click to expand...
Click to collapse
Well, if I start ADB sideload in TWRP, it says it is starting but then nothing happens. Or does it take more than 5 minutes? Because cmd says no devices found :/

It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.

apjashley said:
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
Click to expand...
Click to collapse
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...

kumpelfred said:
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
Click to expand...
Click to collapse
What does your Windows device manager show when you're in TWRP but not sideload mode?
I've been wrong before but I believe from sideload mode "adb push firmware.zip /sdcard/" should work as normal.

Hi, thanks for your reply.
The device manager lists it as HTC One Mini but with a yellow question mark. When I plug it in, it recognizes it and installs all the drivers with the exception of the MTP driver, and it won't let me manually install it. In fastboot, it is listed as "MyHTC".
When I go into adb sideload mode in TWRP it gets stuck on telling me it starts the service but nothing happens. "adb devices" remains empty in the cmd console.
As I said, I DO have a backup, only I cannot restore it as TWRP is unable to mount the USB-OTG. I simply cannot check the box (all other partitions data, system etc. work)! I tried 3 different sticks and TWRP versions 2.6.3, 2.7.1.0 & 2.7.1.1. On a friend's M7 TWRP loads that stick in a few seconds. ADB is not working as I said, otherwise I could simply push the file to the internal SD and see if I can restore it from there :/ I think it may have something to do with TWRP not being able to fix permissions, too (it tells me to boot the system once after factory reset, which I cannot do of course!) but I'm not sure....
What I have also tried is setting back the phone (relocked, stock recovery, cache erased) via rebootRUU and a Vodafone DE firmware zip but it tells me "read zipped android info fail" and aborts. Probably because I'm on a higher hboot version than the one in the firmware zip and I cannot go S-OFF without ADB working -.-
I'm struggling with this for 3 days now... Is there nothing I can do to get it booted into anything???

Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:

kumpelfred said:
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
Click to expand...
Click to collapse
could u share that drivers pls. i have same problem ((

[email protected] said:
could u share that drivers pls. i have same problem ((
Click to expand...
Click to collapse
Hey, I was wrong about the HTC drivers, this was not the issue. The issue was that the latest TWRP recovery (2.7.1.1) did not work in adb mode for whatever reasons. The solution was not older drivers (as they update anyway) but to install an older TWRP version (2.6.3.0 worked for me).
This is only when you cannot boot into your system and have to adb push something to your sdcard. If the phone is not recognized when connected with a booted system running, the only fix is to remove drivers and programs that could interfere (Samsung Kies, HTC Sync, e.g.), reboot, reinstall the drivers, plug your phone into a different USB port and just hope 'adb devices' gets a result, otherwise try all over again.