Database Info

adb and ruu problems

Hi!
First of i got a Htc one S from sweden and have been using utb rom for the last weeks with CWR Touch. After hearing that Cyanigenmod 10 was not as buggy as i thought i decided to use it.
This is what i did:
Downloaded the rom with rom manger - the phone restarted and viped everythig and started to install. It then aborted because of something wrong with the file.
Now i dont have a rom on my phone and i cant acces my SD card where i got other roms waiting for me to install.
When i try to use any ADB commands like "adb devices" nothing shows up under devices.
I tried "adb kill-server" and "adb devices" still nothing. When i use "fastboot devices" my device shows. I have tried both Hboot and Fastboot.
I tried to use one guide i found where someone used "all in one toolkit" to go back to stock recovery, delete space, re-enter recovery but that did not work for me.
I tried to adb push roms to my phone but still, no luck because my phone cant be found.
I tried to use the software "quick adb pusher" and with it i could se my device show and i could acces the storage, but there is a folder named "error device not found".
I tried to use "all in one toolkit" so i atleast could get CWR back on my phone, it flashes and finds my device, but when i try to rebot to recovery nothing happens anymore.
Do anyone have a fix for this? 7h later and im out of ideas.....what ever small ammount of knowledge i have about this ended hours ago and google cant help me anymore.
I even tried to download a ruu to try and install it but keeps telling me its the wrong version and then the installation aborts.
i have htc sync and htc usb drivers.
I also downloaded....well atleast 15 diffrent drivers and tried them still no adb device found.
I tried to download android atk but it complains about me not having java runtime but i installed it.
Im using windows 7 x64 bootcamp and osx

aasterix said:
Now i dont have a rom on my phone and i cant acces my SD card where i got other roms waiting for me to install.
Click to expand...
Click to collapse
In fastboot you can flash boot images and recoveries.
You can only use ADB when booted (which you can't) or when in recovery.
If you are unable to mount /sdcard in recovery, check the sticky on how to fix unmountable sdcard. It's here in Q&A.
Once you can mount /sdcard in recovery, you can adb push roms to it. You have to be in recovery for that, not in fastboot. First flash the boot image for your rom from fastboot, then boot into recovery and push and flash the rom. Wipe your data and cache.
You can do this either on windows or osx but on osx you dont need drivers so you can't have the wrong ones.
Good hunting,
-Jobo

The CWM version shipped with all-in-one doesn't work. CWM doesn't mount the sdcard anyway. I'd suggest TWRP because it can mount the sdcard and also has other features that CWM lacks.
Just boot into bootloader and in fastboot:
fastboot flash recovery twrpfilename.img
Then do as jobo said within the recovery.
Sent from my HTC One S

Pheroh said:
CWM doesn't mount the sdcard anyway.
Click to expand...
Click to collapse
What I meant, and what I think aasterix meant as well, is not mount the sdcard onto your computer over usb, but just mount the sdcard onto the root filesystem in recovery on the device.
If that doesn't work, you have to fix that first using '[HOW-TO] Fix soft brick & error mounting sdcard'. Once you can mount /sdcard in recovery (any custom recovery will do) you're good to push and flash your favorite rom.

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.

Wiped all partitions in twrp, now flashing a rom gives me a bootloop

So I was stupid enough to wipe all partitions (Data, system, internal storage etc) thinking that I'll do a super clean install of the new update.
Now I flash the new file (which I downloaded from the official website), it flashes just fine but gives me a bootloop.
I have (or had) root and can flash TWRP fine.
What else can I do to get back any running rom?

https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Hopefully this will help you like it did with me .

Try flashiing stock boot.img from adb or try to the unbrick tool

Absolutely nothing at all worked, not even in the slightest, everything gave me a boot loop. Except for one thing; I flashed the Open Beta DP3 zip file in twrp and that worked, then I use set it up and used the rollback-to-stable release file to revert to stable release.
I see absolutely no logic behind how and why this worked and not the other traditional methods though, anyone have any clarification on this please?
Thank you for your responses though guys, much appreciated!

If you can still access TWRP recovery, try sideloading a rom via fastboot on a Windows PC. Boot to TWRP > Advanced > Sideload. On your Windows machine - Open fastboot and type "adb sideload *rom name*.zip. See if that works. If sideloading fails for whatever reason but you can still access TWRP try pushing the rom to internal storage by using fastboot again. Boot to TWRP on your phone and do nothing else. On your Windows machine open fastboot and type "adb push *rom name*.zip /data/media/0" this will push the rom to your internal storage.

railpressureflip said:
Absolutely nothing at all worked, not even in the slightest, everything gave me a boot loop. Except for one thing; I flashed the Open Beta DP3 zip file in twrp and that worked, then I use set it up and used the rollback-to-stable release file to revert to stable release.
I see absolutely no logic behind how and why this worked and not the other traditional methods though, anyone have any clarification on this please?
Thank you for your responses though guys, much appreciated!
Click to expand...
Click to collapse
the most important thing you missed mentioning was which ROM were you ON when you wiped everything?
bcz if it was using an August security patch, and if you tried to go back to a july one without formatting data you were bound to get bootloops.
glad that it finally worked though.
but if you wanna try again, be sure to format data and your super clean install will go through.
wipe everything
format data
reboot fastboot
fastboot boot recovery
adb push stock stable ROM
flash via twrp
adb push twrp zip
flash twrp zip
reboot
now you will be fine.

speedyjay said:
If you can still access TWRP recovery, try sideloading a rom via fastboot on a Windows PC. Boot to TWRP > Advanced > Sideload. On your Windows machine - Open fastboot and type "adb sideload *rom name*.zip. See if that works. If sideloading fails for whatever reason but you can still access TWRP try pushing the rom to internal storage by using fastboot again. Boot to TWRP on your phone and do nothing else. On your Windows machine open fastboot and type "adb push *rom name*.zip /data/media/0" this will push the rom to your internal storage.
Click to expand...
Click to collapse
Thank you very much! Sideloading rom worked for me (OP6T).