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)
Related
I'm trying to fix my tablet. It doesn't start in bootloader or recovery mode. I already tried powering it up pressing as many combinations as imaginable, it doesn't work. I think this modes are disabled.
Then, I started trying to fix it using adb. Some commands like recovery in adb shell throw a Segmentation Fault and no other explanations.
fastboot devices returns nothing.
flash_image returns
error scanning partitions: No such file or directory
I already tried a myriad of scripts and other programs, nothing seems to work, I'm stuck with android robot dancing in loop.
That's my tablet genesis gt7200 [I can't post a link...] (probably only sold on Latin America and Asia) and it's produced by SKMtek
How can I reinstall a rom? Or atleast make it start normally again.
Have you tried "adb reboot-bootloader", "adb reboot recovery" or "adb reboot bootloader" commands?
I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls
Really no one can help???
bamp
cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk
If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:
CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up
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..
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
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...