So I have just taken my One X from stock, unrooted, and am attempting to put CM on it.
I had no problems using adb or fastboot until I flashed CWM, I am still able to see the device using fastboot (when in fastboot) but in recovery on CWM 'adb devices' comes up blank.
I have tried doing kill-server/start-server, restarting my phone and laptop, updated all my drivers and followed the advice given in every other thread I could find to no avail, what should I try next?
Thanks in advance.
Resolved
I ended up resolving this by placing the phone in mass storage mode, moving the zip file like you would on a flash drive and installing it from there with no ADB interface. If you intend to do this DO NOT put the zip in any sub-folder, just save it to /sdcard/. I made the mistake of saving it to .android-secure which CWM can not see, to install I had to reflash to twrp to move the .zip and then go back to CWM to install, much more hassle than was necessary!
Related
Guys need some help here.
I was previously on 1.28 with ARHD 4.1.
Recently tried to flash to ARHD 5.1 but during flashing, phone was bricked. It's currently stucks at the htc logo homescreen.
I can enter CWM into recovery mode but I do not have any existing ROMS in my SDcard. I believe we can write into the SD card by using the ADB commands in terminal. But my ADB devices list is being shown as empty
I have installed the latest htc drivers. I suspect this could be because one have to manually select the USB debugging mode on the phone upon plugging in. But since my phone is bricked, how do I go about enabling this option? Kind of lost now
Any help would be greatly appreciated!
Cheers!
If you can enter in recovery then it is not bricked. Try to mount storage in recovery and put zip file and reflash. Sorry cant help much myself but dont worry someone will tell you exactly what to do. I can reassure you, your phone is not bricked.
Cheers
If you can enter recovery, under mounts and storage or something there's an option called Mount USB Storage. Use that to connect your phone like a thumbdrive to your computer and you can flash any zip file from there. Also, did you flash the boot.img for ARHD via fastboot?
tlkh said:
If you can enter recovery, under mounts and storage or something there's an option called Mount USB Storage. Use that to connect your phone like a thumbdrive to your computer and you can flash any zip file from there. Also, did you flash the boot.img for ARHD via fastboot?
Click to expand...
Click to collapse
yes. i had flashed the boot.img file prior to it. i had tried the mount usb storage option but my computer ( have tried both mac & pc) , doesn't seem to pick up the device.
http://forum.xda-developers.com/showthread.php?t=1609190
Don't worry you can push files thru adb on to the sdcard, i did it few days back to recover from a similar situation.
The way to get adb working is by booting the phone directly from the recovery image rather than using the recovery on your phone.
Firstly, in case you aren't already using it, get the latest CWM recovery so that you may charge your phone in case its low on battery.
Secondly, get into fastboot mode and boot directly into recovery. (Not very sure about the syntax right now so not writing it here, search the forum.. its there somewhere)
Next, make sure sdcard & data are mounted in the recovery under "mounts & storage".
Now you can check if adb is working thru devices (most probably it should). Once that is confirmed, you are ready to push files thru adb & flash them.
Hope this helps...
problem solved. +)
cheers to all!
have a great day ahead!
I didn't to a NANDROID backup before trying to flash a new ROM (fail I know). I had factory reset my phone before flashing the new ROM, but the ROM that was flashed hasn't installed correctly and the phone no longer powers completely on. I would like to just throw a different ROM/gapps on the SD card, but I can no longer access it on my computer since the phone will not completely boot up.
Someone suggested somewhere that I mount the USB Storage from recovery, but in the mount + storage recovery section all I see is mount /data, mount /system, and mount /cache, none of which make the GNEX storage available on my computer.
Any suggestions for fixing this problem, or for simply accessing the SD card on my computer without the phone turning completely on?
Thank you.
You can adb push a ROM while booted in a custom recovery. You should check out the stickies in this forum & the general forum.
Download the factory image from google for your phone. Extract it and get system.img from it (you have to extract it a few times). Get adb/fastboot setup by installing the correct drivers and the android sdk (there may be files posted here at xda with just the files needed for adb/fastboot). Then put system.img in the same folder as fastboot.exe (assuming you use windows).
Connect your phone while in bootloader (both volume keys + power) and from a command prompt in that directory, type:
1) fastboot flash system system.img
2) fastboot reboot
It won't wipe anything other than /system.
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
I have the same problem. Going to take a look at what mwalt suggested tomorrow. Paybacks, if you find a solution, can you please post it here? Thanks.
mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
I was finally able to flash the system.img from Google, but see no change. What is expected to happen once this .img has been pushed?
EDIT: Ended up flashing the entire .zip installation instead of just the system.img file and I have a stock install atm. Thank you for the help!
To Man_Utd, I ended up just re-executing the superboot r5 while in bootloader and it seemed to help recognize the phone..-shrug-.
So I wanted to flash CarbonRom on my phone, but wanted to do a complete wipe of everything (pictures, music, etc) and then push the rom via adb but I ran into a problem.
So I booted into cwm (v6.0.3.1) did wipe data/factory reset, wipe cache partition, in mounts and storage I did format sdcard, format system, format cache, format data and /data/media (/sdcard), then wipe dalvik cache, and fix permissions. After that I opened up the GNex Toolkit v11.1.0 and entered push files to device, then it said “the toolkit will check for insecure boot.img” It asked am I using a custom rom or insecure boot.img I said no, it booted into fastboot and loaded boot.img then loaded back into cwm and then asked me to select file, I entered carbon* set the location, then about 20 seconds later said “An Error Occurred. You are not using an Insecure Boot Image”
I also tried this, unzipped CarbonRom and copy/pasted boot.img into sdk/platform-tools, then held down shift opened command prompt typed in fastboot devices, my device showed up, then typed in fastboot flash boot boot.img then booted into cwm, and tried to push files again through the GNex toolkit and the same thing happened “An Error Occurred. You are not using an Insecure Boot Image” I also tried this with another Rom (Vanilla RootBox) but got the same error.
I finally tried this, went to My Computer, Local Disk (C: Drive) Galaxy Nexus Toolkit, root, copy/pasted boot-insecure-jdq39-toro.img to sdk/platform-tools, typed in fastboot flash boot boot-insecure-jdq39-toro.img, then went into gnex toolkit and tried the push file and got the same error. I realize I could do adb push in sdk/platform-tools but I’m new to command lines and felt more comfortable using the toolkit.
I think there must be an easier way to do this. Before thinking of adb push to load the rom I was hoping that maybe there was someway that I could wipe everything and then mount my phone as a storage device and just drag and drop the rom and gapps onto my device and then install the zip from sdcard, but then I got this whole boot.img thing (I don’t know what it is) so my plan of dragging and dropping probably wouldn’t have worked. or maybe it would have? is it possible to do that CWM or TWRP? If so what would happen to the boot.img step?
I’m all out of ideas as to what to do next. Any help/advice is greatly appreciated! Thank you
why are you using a toolkit? it did nothing for you
1) you will never be able to mount your phone, so dont even bother.
2) adb push a rom to your phone or adb sideload it.
3) STOP USING A TOOLKIT
Zepius said:
why are you using a toolkit? it did nothing for you
1) you will never be able to mount your phone, so dont even bother.
2) adb push a rom to your phone or adb sideload it.
3) STOP USING A TOOLKIT
Click to expand...
Click to collapse
Thank you so much! I stopped using the toolkit and just pushed it via adb with command prompt in sdk/platform-tools and it worked!
However next time if I want to flash a rom and do a full wipe of my phone will I have to flash the boot.img via fastboot (taken from the rom) & then push the rom via adb? (sdk/platform-tools) or just push via adb and do nothing to the boot.img ? I'm assuming do nothing wtth boot.img and that it was just the toolkit that was giving me that strange error, is this correct?
Thanks, again
Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.
adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery
Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!
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.