I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent
Related
It's been a while since I have updated my recovery and rom so I downloaded latest CWM and CM. I formatted all the options inlusing sdcard and system. That turned out to be a big mistake because now I can not push any files to the phone to flash a rom. I can get to CWM inlcuding the option to adb sideload but my computer does not have the fastboot or adb drivers installed. Is there a way for me to push a rom to the device to get back up and running? I have tried to install the fastboot drivers but the mahine is not recognizing the device.
***Update**
I ended up using the universal toolkit in linux so I wouldn;t have to set up the drivers and was able to get back to a stock image and work from there.
So I formatted my sdcard thinking I would be able to install a new rom easily, that was not the case. The problem is that I have not found a way to transfer files to my phone.
I have TWRP 2.7.0.0 recovery installed, but mount USB does not work. I get the sound from my pc that a device has been connected but nothing happens. I tried uninstalling the drivers and reinstalling htc sync + drivers but no difference.
Fastboot commands work, but adb commands do not. So i cannot adb push. Adb doen't work in fastboot as I understand it but should work in recovery?
I was thinking of installing stock rom, because I can appearently do that via fastboot. But after extracting rom.zip from ruu install file, I find out that I have to decrypt the zip-file. And the only decryption tool available is for linux, which is a bit of a hassle as I am running windows.
So do anyone have any suggestions to how I can transfer files to my phone? The easiest would be to get mount usb to work, or adb push to work. I have not managed to get adb sideload to work either. I have struggled with this for the past two days, so any help would be greatly appreciated.
Flash this one, mount the sdcard and wait some minutes
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
I was looking to do a full wipe from TWRP and wanted to wipe data as well. Knowing that that would erase everything from the internal storage and not having an SD card available to me now I decided to wipe everything and then transfer the new ROM with adb commands.
Before wiping, I wanted to make sure that adb was working first. So I downloaded the Android SDK and booted to TWRP. Went to Advanced--->ADB Sideload and started the command prompt on my PC. From the folder were adb.exe was I typed "adb usb" and got error:device not found.
I don't know why but after 30 minutes trying to fix that I pressed the "Fix permissions" option in TWRP and now my phone is stuck at the boot logo every time I try to turn it on. I also noticed in Device Manager on my PC that every time I connect the phone to the PC that there is a yellow exclamation mark next to the phone which suggests that I don't have the needed drivers. However I tried to install versions 3.10 and the newest 3.12 and the exclamation mark is still there.
So my question is how do I reach the phone with ADB and transfer the flashable ROM zipfile so I can get the phone past the boot logo?
Well I'll answer myself if anybody has the same problem in the future. It was obviously the USB driver's fault and since none of the LG's drivers worked, I used Google's USB drivers and was able to adb sideload the ROM zip and now it's booting into the OS.
So always check your drivers people! In case LG's don't work, then use Google's!
I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.
I hope all of you would be fine.
I was trying to install a custom ROM in my HTC one X via CWM recovery. I formatted the system partition (ROM) and tried to flash the new ROM. I ended up soft bricking my phone as the ROM file was corrupt. I tried to push another ROM.zip file into the phone memory via adb. My phone shows up in fastboot devices when it's turned on but it's not detected as adb device. When I turn it off then it shows up in the attached adb devices list. I used the adb push command to transfer the ROM file into the phone memory and cmd tells me it's done as it shows the transfer speed and the size of ROM file. Now the issue is that when I try to search for that ROM file in CMW recovery, it's not there in the memory.
It's been three days since I have been trying to make my phone alive but nothing seems to work.
Any help from you guys would really be appreciated
*My phone shows up in abd devices only when it's turned off.
*The adb pushed ROM.zip file is not present in the phone memory.
*All the drivers are correctly installed and my phone is listed as 'My HTC' in device manager.
Hey there, sorry for a late answer, but right now I have some town-wide internet problems, so...
Back to your problem then, if you cant have any result with adb push, try to use another method:
1. Complete steps at this link https://twrp.me/htc/htconexinternational.html to install twrp
2. Reboot to your twrp recovery
3. Choose "Mount" option and mount any partition you need(depending on your layout), after this step, you can access you phone storage with you pc.
4. Now you can wipe everything you want, do not reboot, and go to "install" option.
5. Just copy/paste you ROM, install it, reboot to fastboot, flash boot.img
Done.
Have a nice day.