I have a G2 that was running a cyongenmod based rom of some sort or another (can't remember) and over the past few days it started freezing and hanging on boot and acting generally weird. Well, now it will not fully boot up. If the red cynogenmod animation goes away at all I am presented with a powered up yet black screen. Anyway, because this seems like a straight up software issue I thought that perhaps installing a new rom would solve my problem. The problem is that in its current state I can't figure our how to move the new rom I downloaded from my PC to the phone.
I had hoped to use adb and just code in the proper command but I can't seem to get the command right.
Any help?
A few details:
When connected to my PC via USB it is recognized by adb
I have the new .zip file in a few places on the PC, both the desktop and the platform-tools folder
I guess I could buy a microSD card adapter and just do things that way but I would rather save the trip and the money and learn something new.
Never mind, I was able to execute the command, but now I have a different question.
Related
Hi
Apologies for the longwinded explaination of my problem but I wanted to be thorough and to let you have as much info as poss to know what I have tried and I think I have it mostly down here..
I recently sucessfully (I think) rooted my i9100 with Neat Rom 4.4.2, which seems very nice
I also have two ZTE Kis phones (via Virgin) which I thought I would try to revive.
I managed to flash one with Firefox OS and it seems fine for the most part although it flickers occasionally
The other one that I had rooted ages ago I eventually managed to reset my recovery via a terminal emulator and flashed a Rom back to its original state except with an unbranded rom courtesy of http://blog.podtwo.com/android/rom/de-branded ROM for ZTE Roamer2 [gingerbread].html THANK YOU SEBASTIAN
As this was not ideal as the storage space quickly disappears I though I would try to flash it with something else... and after some looking around I went here http://www.youtube.com/watch?v=n_DJhaNH14o and downloaded the miscellaneous files attached (first dumb move)
I then tried to flash each of these Roms in no particular order and finally got one of the Xperia Roms to take me to the install stage (2nd dumb move) I was working on some other stuff and yessed away in my own smugness only to find that the rebooting phone showed a green android that gradually faded to a blueish whiteout...
It also would not boot to recovery! power + volume = same android fading away...
It also would not boot to FTM
My main OS - OSX could not recognise the phone via adb/fastboot etc so I decided to try Win 7 (3rd or possibly a lot more by now dumb move)
so I booted to windows and low and behold... adb/fastboot could not see the device upon opening my Browser to try to find a solution I discovered that my Browser had been taken over by Conduit... (I am certain it was not before attaching the Kis and the suspect rom) and I was bombarded by a number of options to remove malware threats and virus' etc.. figuring something was wrong (first smart move) I switched operating systems back to OSX and ran Clam scan and Sophos scan of Windows drive (infected with something in the region of 40 nasties) I quarantined and deleted all the nasty infected files. I booted into Linux and ran ClamTK scan of the windows drive which found something in the order of 1200 threats.. some of which were standard methods used by programs but I spotted a few trojans I think amongst the readout.
I have deleted the Rom files and formatted the SD card that it was on.
Neither ADB nor Fastboot sees the infected/soft bricked Kis device from any OS
I have discovered too that the infected Kis does actually do different things when volume buttons are held down in conjunction with the power button (I am guessing that although the rom was corrupt - or perhaps not meant for my device) the phone is still trying to enter FTM mode as it just boots to a red light on.
From Linux in terminal (lsusb, usb-devices and dmesg | tail) all identify the device - attached file which has a different device id depending on the "mode" it is in when I attach it - Vendor ID is always 19d2, but Device ID is either 1353 or 0112 (the latter is when it is in FTM? mode - Vol down, power on , red light constant)
OS X also see the device: when the device ID is 1353 it identifies it as ZTE HSUSB Device, serial no ROAMER2, version 2.29, ZTE Incorporated. Whne device ID is 0112 it identifies it as ZTE WCDMA Handset Diagnostic Port
Win 7 sees it in "FTM" mode as ZTE Handset Diagnostic Interface (DSU)
Now I have... (mainly from OSX and more recently unbuntu 12.04) with my limited intellect and even more limited knowledge of programming and restricted understanding of terminal commands tried to have tried to cp files directly to the device, I have looked to try to boot from an sd card, I have tried to go into the recovery mode even though I can't see the screen and navigate blindly to the update.zip or recovery.img etc --- I have put them all on the card. I tried to do this http://linux-sunxi.org/Boot_Android_from_SdCard - but got a failure around "awutils, make" I have looked at Odin, Heimdall options, I have tried to adapt other solutions for different phones to mine (which was how I somehow or other managed to recover my CWM through terminal emulator in the first place). I have tried through ZTE to get thir automatic update program/instructions.zip (which despite being on broadband was proposing to take something in the region of 2 to 3 hours to download 136MB....! made me think that that might be how long it might take to copy my 4 and a half ish Terabytes of data... (paranoid now? MAYBE) so I cancelled the download and rebooted to Linux where I feel comparatively safe!?
BUT NOW I AM STUCK
I have the Unbranded rom and CWM recovery I can see the device but I don't know how to force the two together... can anybody help me (I have just tried very hard to resist an Obi-Wan-Kenobi joke)
I hope someone can help
Good Evening,
I have a Motorola G.
I was running a rooted version for a while, although I am admittedly not an expert. however, i did follow the steps and it was working fine, for about a year.
Well today i was low on internal memory space available, and tried transferring some more data onto it. I didn't realize the size of the data. I got a message from the computer saying there was no more space, and unplugged and went to work.
Phone was not really responsive, but I figured I would delete a couple things once I got to work until I could clear it out.
I took phone out, and it's on a black screen. I tried to restart it, it's freezing at the blue M .
Nothing seems to work, I think the memory is just so full the phone can't even boot, so I decided to do a hard reset. Unfortunately, I'm having some difficulty. I've downloaded and installed the updated Composite ADB Driver from Google, and it DOES show in the Device Manager when I plug in the phone.
I've also downloaded the SDK manager and updated it. I plug the phone in and administratively launch a command prompt. I direct the Command Prompt to the folder containing a recovery.img file, and from that point I am lost. The computer doesn't seem to identify the phone , i'm getting either or error: Device not found.
I'm not sure what I've done wrong, I am sure i'm using the newest ADB Drivers......
I tried the "adb devices" within the command prompt, and in that case it comes up blank....
Can someone please help me?
Thank you....
Hello all,
So I have a Kindle Fire HDX and I decided to try play around with safestrap on it. It was going well but me being stupid didn't realise that when I was wiping everything, I was not just wiping the contents of the rom slot but the entire device! So I am in a soft-brick state at the moment, which is OK because I have been here with lots of devices before, just not any quite as restricted and complicated as the HDX. So my only option is to push the zip file or sideload it through ADB, which seemed to be a fairly easy task. My first challenge was installing the necessary drivers for windows 8.1 to recognise the device in adb sideload mode. I managed to do this successfully however now I have a problem when trying to sideload or push files to the device. When sideloading, the server starts successfully but I get a *failed to write data 'protocol fault (no status)' * error. When trying to push files I get an error:closed, the same by running the usb command (I am not sure what this one does but I seen it as a possible solution so have tried it). When I run the devices command I see my device connected and it is shown to be in sideload mode. I have tried the following in order to resolve this error, all have been unsuccessful:
New USB cable
Different versions of ADB (minimal and android studio)
Different computers and operating systems (each again with minimal adb and android studio)
Updating the packages in android studio, including installing the official kindle fire driver from amazon
Killing the server and starting again
None of these steps have helped and I am finding this to be incredibly frustrating as in every thread I have read online one of these solutions has managed to fix the problem for the person asking the question. I figured there isn't a place on the internet with a better knowledge and understanding of adb than here so there would be no better place to ask. Any help you guys could offer would be much appreciated. Also I am relatively new (and dumb) when it comes to adb and using the command line so if you guys could dumb it down as much as possible that would be brilliant.
Thanks in advance
EDIT: I have also noticed that when trying to format the device from the TWRP menu I get an 'unable to locate device to partition' error. I'm guessing this has something to do with it
Just thought I'd update this thread with the fix I found in case anyone else in future has this problem and googles around. I am not sure if I specified but the issue was with a kindle fire hdx 7". Safestrap would not let me change the active rom slot to the default OS and it was stuck in rom slot 1. So I contacted amazon and asked them if there was anything they could do to help me. They started off by giving me the usual reset by holding the power button. I thought there is no way that could fix it because I wiped the system files and that is the problem (I could see from TWRP that the system files were empty). So just in case I done as he said and after holding for a full 40 seconds, the previously soft bricked kindle booted back into the stock os and whilst it was completely wiped, it was now fully functional! I am sure this will only work for a very small percentage of people with a soft brick but definitely try it none the less. I would be interested to hear anyone who actually knows the technical aspects of this chime in with what happened here. Did it just look like I wiped the entire system in TWRP because it was hiding the system files? (even though I could see the folder and it appeared empty). Or does the kindle have a built in recovery drive through which it will replace these files when the power button is held for 40 seconds?
Hi,
Thanks for using XDA Assist if you are getting partition error then possibly your partition table is wrong rectify it and see
Good luck!
No Response .. Thread Closed .. Thanks
Recently I was playing around with my Samsung GT-P3110, having just rooted it.
I transferred a file using adb push, it appeared to work, the problem is now I can't get it off, nothing I do using root and command line on the tablet or root explorer makes it budge!
I did the transfer after an aborted rom install which left my tablet going straight to CWM recovery, I was trying to transfer a backup onto the tablet. Trouble is that I am now running low on space and this folder is about 2Gb.
I can't see an adb command to delete from the tablet, plus adb is no longer seeing the tablet either!
Any ideas?
Cheers,
Katoiam
I followed you on your little quest for an answer, and was saddened by the response. Not one helpful word, just a bunch of people telling you to go somewhere.
I don't own a Tab myself, but encountered the exact same problem on my G3. There was no way to edit the permissions, so Android considered it untouchable.
The solution is an easy one and I can't believe no one could spare the time to say "Delete it in Recovery" but that's what it'll take.
Hello! I have decided to turn in this pixel 2 I have to google finally but I'd really like to make a nandroid backup of it before I send it in as it has some very interesting apks on it (I made previous threads on this), pictures here https://photos.google.com/share/AF1...?key=dDc2UjVBQWpmUk5KUEpmNVJ6WWZYZ0RQUkprZm13 . Problem is that the phone isn't exactly running the stock pixel 2 os, it came directly from google running AOSP with android version 8.0.1. I'm not sure if the kernal and everything else are the same either, I do have a picture of the system information in the above album.
So I tried following this https://www.the***********.com/install-twrp-recovery-on-google-pixel-2-pixel-2-xl/ exactly to boot into twrp, but after following the steps to entering "fastboot boot twrp-3.2.1-2-walleye.img" in windows power shell, powershell says Downloading boot.img OKAY and booting OKAY, but the pixel 2 screen just goes black instead of loading TWRP. I am still able to get back to android and get back to the bootloader, but I can't seem to load or install TWRP.
^not sure why the url gets ***** out. the ***** out portion is "custom droid" with no space
I'm not sure of any other way to pull data off this phone without TWRP installed. The phone won't accept any sim card I've tried, and turning on wifi allows me to connect to my local wifi network, showing the correct IP, DNS, and default gateway, but still refuses to connect to the internet. Usb debugging is enabled, and adb lists the phones serial number when prompted with fastboot devices.
The phone itself shows 24gb/32gb all used by the system. When I plug it in to my PC and view the files, it shows as "AOSP on walleye" with 6.73gb free of 15.6gb rather than the 32gb the phone shows. The files shown on the pc are all most empty as well, I can't seem to find what files are taking up that 10gb or so that my PC does manage to see.
If anyone has any ideas, I'd be happy to hear them. It'd be a shame to let all these tools go. Otherwise this phone should be heading back to google soon.
ravensfan8448 said:
Hello! I have decided to turn in this pixel 2 I have to google finally but I'd really like to make a nandroid backup of it before I send it in as it has some very interesting apks on it (I made previous threads on this), pictures here https://photos.google.com/share/AF1...?key=dDc2UjVBQWpmUk5KUEpmNVJ6WWZYZ0RQUkprZm13 . Problem is that the phone isn't exactly running the stock pixel 2 os, it came directly from google running AOSP with android version 8.0.1. I'm not sure if the kernal and everything else are the same either, I do have a picture of the system information in the above album.
So I tried following this https://www.the***********.com/install-twrp-recovery-on-google-pixel-2-pixel-2-xl/ exactly to boot into twrp, but after following the steps to entering "fastboot boot twrp-3.2.1-2-walleye.img" in windows power shell, powershell says Downloading boot.img OKAY and booting OKAY, but the pixel 2 screen just goes black instead of loading TWRP. I am still able to get back to android and get back to the bootloader, but I can't seem to load or install TWRP.
^not sure why the url gets ***** out. the ***** out portion is "custom droid" with no space
I'm not sure of any other way to pull data off this phone without TWRP installed. The phone won't accept any sim card I've tried, and turning on wifi allows me to connect to my local wifi network, showing the correct IP, DNS, and default gateway, but still refuses to connect to the internet. Usb debugging is enabled, and adb lists the phones serial number when prompted with fastboot devices.
The phone itself shows 24gb/32gb all used by the system. When I plug it in to my PC and view the files, it shows as "AOSP on walleye" with 6.73gb free of 15.6gb rather than the 32gb the phone shows. The files shown on the pc are all most empty as well, I can't seem to find what files are taking up that 10gb or so that my PC does manage to see.
If anyone has any ideas, I'd be happy to hear them. It'd be a shame to let all these tools go. Otherwise this phone should be heading back to google soon.
Click to expand...
Click to collapse
So you're sending the phone back to Google....why? Because it came without the stock OS? It's hard to believe that the phone came with AOSP already installed...that's awesome if it did since AOSP is usually something that you have to load yourself.
So I'm sure you understand that your bootloader has to be unlocked in order to boot TWRP yes? Because typically when the bootloader is not unlocked the phone will reject the recover and shut down. So make sure your bootloader is unlocked in developer settings since you have a Google verison.
Sounds like your partitions are being weird when plugged in to the PC and its only seeing some of the partition. I would try to reinstall the driver and see where that gets you.
If you're concerned about your APKs, I would just use Titanium Backup and backup all the APKs to storage and then pull that from the phone using PC.
Hope this helps.