[Q] heavily bricked xt910 - Android Q&A, Help & Troubleshooting

So, I was messing some things up in safestrap and I decided I want to do a fresh start on my phone. So I went to the wipe section and wiped everything.. Now as I can tell, I have no /system folder, no OS, nothing. I can access bootloader. After intense reading and searching, I managed to connect my phone via adb, adb devices command shows the ID of my phone in a sideload state. Sideloading a rom never worked, tried many of them, at best I got an error about getprop file missing - tried to modify the updater-script using an editor after instructions but still nothing. My main issue is that while adb works fine, drivers are 100% fine, upon entering phone into fastboot mode, it disconnects and there is nowhere to be found under device manager. If I could get it to work in fastboot I could then use RSD lite to flash a stock rom. Also, the only command that works from adb is the # adb sideload filename, anything else returns error:closed. Even tried #adb usb #adb remount and so on. Is my phone a garbage at this point?

forgot to say also, tried to connect via fastboot under windows 7 sp1 / xp sp3 / ubuntu 14.04 .

bump

bump..

Related

[Q] phone wont boot after build.prop change

My phone will refuse to boot after I added a line in the build.prop (Yes i am rooted) to try to make the touchscreen more responsive. Now I get stuck on the boot animation. I have tried recovery mode but one of my hardware keys will not work and I need that one to enter the choice. I have adb and I tried using that (I am no expert with adb), I tried
Code:
adb root
and it gave me an error saying that it doesn't work on production. Then I tried searching around and found
Code:
adb shell
Code:
su
tried that and still only showed the $ and not #. I tried using the push and pull commands, I retrieved the file and removed the line I entered and pushed it to my sdcard. I wasn't able to push it to the /system do to it being read-only. I also tried fastboot but my phone wasn't detected. Any Ideas on how I can fix my phone? At this point I don't care if I lose all my files. I forgot to mention that I'm on windows 7 and while adb detects the device a driver fails to install (i believe it is the MTP driver)

[Q] Corrupted android system desperately needs help

Okay, so my android system which is found in system/framework/framework-res.apk has been replaced and corrupted, and now my phone is on boot loop. I don't have any custom recovery or anything. So I'm using a default recovery, connected my phone on my computer and it says unauthorized on adb devices, now I selected apply update from ADB, checked adb devices and it went to sideload state. Now when I try to use adb push with all the parameteres, it says error:closed. I tried all other commands but it doesn't work (error:closed) except for one command which is adb sideload <file> but the thing is, I just need to replace that single file with the right one but I cannot use adb push. Is there any way how to do it? I desperately need help. I'm using an MTK device

How to fix adb (error:closed) and fastboot (waiting for device) in cmd

Hi there!
Please help me...
My Infocus M210 is rooted and I've edited the build.prop from a build prop editor to speed up internet data connection but the editor goes wild and changes everything written on the build.prop then forced my phone to shut down and when I start my phone, it stuck at boot loop.
I've already wipe data/factory reset on its built-in Android system recovery <3e>.
but I think its the worst thing that I've done.
Coz I thougt it disabled debugging and removed root permission from my device.
I've used Apply update from ADB.
I tried to sideload stockrom.zip but when its completed sending on my phone, then says "installation aborted" I've tried different ROMs but same result.
I have also tried shell commands:
adb pull /system/build.prop
adb -d -e -s <serialNumber> shell am start options -D
but all shell commands doesn't work and says "error:closed"
So then I've tried Fastboot mode
but my devices wasn't found
so I have followed some threads and watched youtube tutorials:
So I removed drivers via "usbdeview"
Then installed Fastboot device/ Fastboot interface drivers manually.
but I almost tried all drivers from official to many google drivers
but still my device wasn't found in cmd
says "waiting for device"
Now I'm thinking if there are some tricks to fix adb "error:closed"
or try different computers for fastboot
I already used my Windows 7 64-bit from my friend
and Windows XP 32-bit from my friend
Please Help me...

Stuck in bootloader/fastboot and can't get ADB to recognize, but fastboot does..

So I have had my Droid DNA for a few months and I've been messing around with it and doing fine. Since I installed TWRP it allows me to delete internal storage...
Oops, there goes my ROM I had saved. Now I'm stuck in either bootloader or recovery. I can't get ADB to recognize my DNA to save my life. It's really really irritating.
I've tried flashing a zip with fastboot since fastboot can recognize my device but ADB can't and it didn't work.
I have Minimal ADB installed and HTC sync manager, but i installed sync after i messed it up so idk if it installed the drivers.
I need a step by step instruction guide to get this to work. I can't find it anywhere. I keep getting no ADB devices and it saying server out of date and what not. I've been searching for hours and hours.
I can't get this to work. I even bought a new phone in the meantime to get me by and that's not exactly what I wanted to do... Any help would be appreciated. Thank you very much!!
No one?
Pretty quite.. I recently had this happen as well.. No fear tho.. If you have twrp already installed your golden.. Download a rom 2 your computer and on twrp goto advanced and sideload.. Command prompt on your computer.. Easiest if found is running xp. Get to your folder of adb hit control and right click poem command prompt here.. adb devices, then adb sideload rom(name). zip.. Your computer will find your device then , and if it didn't send it will allow you to file Explorer.. Throw a rom on your internal reboot into twrp and flash
Æaa..\../
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
dyllysoilly said:
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
Click to expand...
Click to collapse
You can restrt the phone. Hold down power and volume down together. Then you can reaccess the bootloader from there. If you have twrp you can just go through the file manager instead of messing with sideload.

Cannot see my device under ADB devices

Hey guys,
I have been looking for solutions for 3days now and can't find it.
My phone is showing under device manager both when its on, and when in adb mode without exclamation mark.
I had SDK 24.4.1 installed, installed everything needed (I think) (Platforms, usb drivers,..)
Flashtool drivers installed, it shows device in fastboot devices but not in adb devices..
When I open CMD in admin mode, I cd to the platform tools folder and do 'Adb devices' It does not show.
I tried Adb kill-server not working, daemon starts succesfull but nothing shows under adb devices.
Also tried a different pc, same outcome.
Running windows 10
I hope its something really stupid I'm forgetting..
UPDATE: Solved! After installing the good SDK, I just had to shut down computer, pull out the plug, take out the battery and wait a while.. Restart and now its showing! Thanks anyway guys Root here I come
You power on device with unlocked screen?
Your phone should just be on with screen unlocked like normal if trying to use adb.
Installed android Studios and it appeared I had sdk for android 6.1 and 6.0 but not for 5.1 wich I am running? I deleted both and installed the 5.1 one.. reinstalled sdk with usb drivers etc.. now I am getting this;
server version (32) doesn't match this client (36); killing...
Error; could not instal 'smartsocket' listener: Cannot bind to 127.0.0.1;5037
could not read ok from ADB server
*failed to start daemon*
error: cannot connect to daemon
I tried starting adb while device not connected, gives me the same ****.
Tried with mobile on, screen unlocked stays the same.
read that step 2a http://forum.xda-developers.com/z5-compact/general/flashtool-how-to-flash-sony-xperia-z5-t3425367
and try this http://forum.xda-developers.com/showthread.php?t=2588979
Rooted. Can I update the phone to latest android now? or only trough flashing costum roms?
Yes, you can.
You can read this forum not only ask

Categories

Resources