Database Info

Bricked phone build.prop missing

Hi to all here. i just want to ask anyone what to do with my phone. well first of all, my phone is a sky pantech vega racer im-a760s, not really a match for samsungs popularity but budget wise this is the model for me. it has a dual core. now my problem starts when i started editing the build.prop in its system (tweaked for some texting problem of limited character sending). of course i know what im doing on that part, but the only thing i didn't think that would happen was, i copied it in my computer, i edited it there, then i saved it as "all" in file type so it wont become a ".txt" format. but when i placed it in my phone. the file instantly disappeared, i think it was only hidden and the phone just cant identify it nor read it like something. now i restarted the phone, it booted up to its logo then it just went blank and it just stops there. i tried pushing recovery with adb in my pc cmd. but it cannot detect my device(no problem with my adb installation to eliminate this from the question), i also tried putting an sd card with a recovery file but there was no option for sd card path. but the phone can still function well, i know because it can still be loaded under flashboot, download screen and S / W upgrade menu and it can still perform wipes for all partition and caches and can reset for factory settings etc. but whenever i will reboot, its not going to complete. anyone please help me how to make my phone be detected by my pc. The usb drivers are just fine, updated it many times, read all procedure for making the driver connect perfectly. i reformatted the sd so it wont be a problem when i put it in. but in the recovery menu i just cant see my sd card, theres just the option for "update from external storage" but it doesn't have anything inside. what a mess. i cant make my phone reflashed cause its not responding with the connection with my pc. but when i am opening an odin (just used for connection monitoring) there are two yellow boxes with com port like these: 0:[com7] and 0:[com9], so i know it is still somehow communicating with my pc. please help any advice, i dont want to resort to jtag for im not sure if it will support my phone and it's already avialable for the model but definitely not going to send my phone for repair cause it will be costly. thanks to all who will respond. Please help thank you. additionally: OS was ics version 4.0.4 and rooted. already gone through rooting several times with no problem. just the editing part.

to edit Android files on Windows use only Notepad++ anyway do not use Windows notepad this is for Windows files formatting only
well, you have to get build.prop from your phone edit on PC then copy back
so enter recovery connect phone to PC create a folder say C:\tmp
to get build.prop from phone
Code:
adb devices
adb shell
mount system
exit
that's to mount system partition then
Code:
adb pull /system/build.prop C:\tmp\build.prop
edit it and copy back to phone
Code:
adb push C:\tmp\build.prop /system/build.prop
maybe is not your case ? but I wanted to give you an idea

@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot

cruelink said:
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
Click to expand...
Click to collapse
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again

ruscan.calin said:
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
Click to expand...
Click to collapse
Hi, cant still afford to make the adb component in my device manager to appear, but it's good to inform you that it helped me a bit because i was able to see the storage of my phone and i was also able to put some files in there without any hassle that alone was satisfying me that my phone is not really dead. sad to say i did everything i could to have my pc detect my phone via recovery menu, but still no devices found. it's really weird that some links are saying that i should make my phone's "usb debugging" enabled, wherein fact i cant even go beyond my original problem(bricked phone), i can't even see the inside of my phones directory, only the storage one that was activated just recently. i even did a reinstallation of my usb, uninstalled every other phone related usb installation to avoid conflicts reinstalled my phones proper usb installer then restart. no progress still to be called. it makes me feel that the phone was just trap in the state of booting and not knowing what to do because it cant see any command inside its system. i cant go into the systems directory as well. and that's the only way i think i could revive my phone in replacing a new build.prop, as you advised to be edited in a notepad++ which i recently acquired and installed. by the way how do i save the build.prop to its original file format, and what is the extension. thanks alot for helping out. im getting a little brighter each step of the way, im not loosing it to come to smashing my phone to pieces instead of keeping a very expensive paper weight.

usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail

isa. rgiespea
ruscan.calin said:
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
Click to expand...
Click to collapse
that's great news, you actually come to emailing the phones manufacturer? wow, im flattered. well you're a very nice guy to help me out on this. and i have good news too. i found out that i have a little conflicting usb drivers, as i have installed samsung for my previous phone(samsung galaxy 1) i had it liquidated for this new one. but a little hard on the support. you gave me a new idea about the usb. so i uninstalled all the related usb drivers and have it reinstalled. now i am able to communicate with OTA firmware server, and i got a reading that was not happening before(stucked in just detecting the phone) now i have a percentage reading of downloading or so. but i still have to wait if it will complete and have it repaired. so by now you can give me a little more help cause im still not at it in pushing through the use of adb programming. and the link you mentioned, i'll wait for the progress about it and see what really was it. and thanks a lot. really appreciate it.

fixed bricked phone via OTA by fixing link to pc.
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.

cruelink said:
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
Click to expand...
Click to collapse
that's good news ! and thanks for feedback
feedback is an invaluable resource ! (some just forget about that from my experience :laugh: NOT your case ! )

[Q] Can't access phone becouse of pin

Hey
I have to use TimePin app, but today something went wrong (i dont know what), but i cant use my default pin, TimePin pins cant be used too... actually I cant access my phone in any way. Cant reset password thru Aroma file manager, cant reset it via adfb, cos usb debug mode is disabled..
is there any solution? Anyone can help me?

why don't you try to contact the developer of this app maybe he can help you

Mile_zdr said:
why don't you try to contact the developer of this app maybe he can help you
Click to expand...
Click to collapse
already sent email, but I need my phone ASAP ;(

My solution
hexen88 said:
Hey
I have to use TimePin app, but today something went wrong (i dont know what), but i cant use my default pin, TimePin pins cant be used too... actually I cant access my phone in any way. Cant reset password thru Aroma file manager, cant reset it via adfb, cos usb debug mode is disabled..
is there any solution? Anyone can help me?
Click to expand...
Click to collapse
This worked for me:
1. Enter to recovery
2. Plug your phone to a computer and start adb
3. Type the following commands:
adb devices
adb shell
cd data/system
su
rm *.key
And then reboot your system and you will not be asked for the pattern or password (my case)
I used a Moto G with Stock 4.4.2

[Completed] [Q] rm "not recognized as a command' Help please

When I try to use adb.exe to remove entries in my dhcp folder the rm command is not recognized.
Alcatel fierce 2 --roooted via kingroot ..thank you
platform tools installed..I think everything need
device is shown using "adb devices " as unauthorized?
Help please

Artofkicking said:
When I try to use adb.exe to remove entries in my dhcp folder the rm command is not recognized.
Alcatel fierce 2 --roooted via kingroot ..thank you
platform tools installed..I think everything need
device is shown using "adb devices " as unauthorized?
Help please
Click to expand...
Click to collapse
Update okay finally after hours of searching and trying a few commands I got adb to accept all commands however phone still says "obtaining ip address" forever. Any ideas?

Hi, thank you for using XDA Assist. What are you trying to do? Messing with system folders and files can lead to your device not working properly.

jd1639 said:
Hi, thank you for using XDA Assist. What are you trying to do? Messing with system folders and files can lead to your device not working properly.
Click to expand...
Click to collapse
At the moment I am just trying to get my phone to connect to my wifi at home.
It is an Alcatel one touch Fierce 2 using Android 4. 4. 2
when I enter my wifi password it continually says obtaining IP address. I was trying something that I read on this site and was not having a lot of luck.
so hopefully we can figure out what's going on

Artofkicking said:
At the moment I am just trying to get my phone to connect to my wifi at home.
It is an Alcatel one touch Fierce 2 using Android 4. 4. 2
when I enter my wifi password it continually says obtaining IP address. I was trying something that I read on this site and was not having a lot of luck.
so hopefully we can figure out what's going on
Click to expand...
Click to collapse
I figured i out...wasn't the phone, it was my wifi
now on o better things.

Glad you got it fixed. I'll close this thread.

[Completed] How can i access the data on a phone that has a broken screen and is pattern locked?

Im trying to access the data on a Galaxy S4 on which the screen is not working at all(no backlight and doesn't respond to touch). the data I mainly require is the contacts.db file. what I have tried sofar:
1. tried to access the data via USB but cant access the content due to the lock on the phone.
2. tried to access the data with KIES but once again failed to do so due to the lock on the phone.
3. Downloaded the ADB shell and installed the required USB drivers but cant access the phone, when running the command "adb devices" it says no devices found which I think is because the USB Debugging setting on the phone is not enabled.
4. Also tried to sync with the Google account but unfortunately it was not setup to sync contacts with the Google account.
Some other suggestions were to get another S4 and connect its screen to the the one in question which im sure will work but is there no other way to access the data or to somehow remove the pattern lock from the phone? maybe using another platform to gain full access to the phone or anything?

Hello, and welcome to XDA Assist! You may want to try this tool: [Tool][Windows] Control a device with a broken screen, or possibly use a programme such as Droid Explorer to view your files. If all fails, try and ask here: General discussion Questions and Answers. You will need to register to post.
Good luck!

[Completed] CUBOT X6 dead screen, no USB debug enabled, Stock ROM, no root

Hi there.
I got my hands on this CUBOT X6 with broken screen. I can see the screen just fine BUT can't operate it from its bottom half approximately.
I would like to use this Android phone as a security camera to watch my garage, but without control, I'm stuck
What I'm trying to achieve here is to:
a) start up the phone and load a security app to it
b) control the phone via some "Android Control"-like app (without using the phone's broken screen)
c) set it up as a security camera and let it take pictures for me
Can anyone pls point me to some links here on the forum to solve my below listed problems ? ( and YES I've spend searching and reading this and few other forums for the last few hours and found just what is listed below)
So....
1. The phone was locked with swipe password with the posibility to control only the top three dots, the other ones are dead, NO USB Debugging available, Phone was set to CHARGE ONLY mode when connected to PC via USB - I managed to download stock ROM and Flashed it but....
2. It asks for a few details and requires you to click NEXT which is in the botom of the screen which is touch-dead. So i have searched and found this tread: http://forum.xda-developers.com/show....php?t=2786395 But....
3. The phone is STOCK rom with absolutely no settings = no USB Debugging enabled and I do not know how to "modify the default.prop" http://forum.xda-developers.com/show...9&postcount=17 when the screen is dead and no usb debuging is enabled = Can't access the file system (or can I ? )
4. The phone is not detected by the Android Control app at all.
5. The recovery is in Chineese ! I tried translating it via Google Translate via pictures, but that did not shows/offers me the option for entering the command prompt (as advised in tread mentioned in point 3)
I'm too lame in this Android/Linux based sea, so if anyone is willing to help me here (if you think its possible to achive my goals a-c) please give me some step by step guide how to do that. (links to treads would be enough)
Thanks a lot !

SparrowCZ said:
Hi there.
I got my hands on this CUBOT X6 with broken screen. I can see the screen just fine BUT can't operate it from its bottom half approximately.
I would like to use this Android phone as a security camera to watch my garage, but without control, I'm stuck
What I'm trying to achieve here is to:
a) start up the phone and load a security app to it
b) control the phone via some "Android Control"-like app (without using the phone's broken screen)
c) set it up as a security camera and let it take pictures for me
Can anyone pls point me to some links here on the forum to solve my below listed problems ? ( and YES I've spend searching and reading this and few other forums for the last few hours and found just what is listed below)
So....
1. The phone was locked with swipe password with the posibility to control only the top three dots, the other ones are dead, NO USB Debugging available, Phone was set to CHARGE ONLY mode when connected to PC via USB - I managed to download stock ROM and Flashed it but....
2. It asks for a few details and requires you to click NEXT which is in the botom of the screen which is touch-dead. So i have searched and found this tread: http://forum.xda-developers.com/show....php?t=2786395 But....
3. The phone is STOCK rom with absolutely no settings = no USB Debugging enabled and I do not know how to "modify the default.prop" http://forum.xda-developers.com/show...9&postcount=17 when the screen is dead and no usb debuging is enabled = Can't access the file system (or can I ? )
4. The phone is not detected by the Android Control app at all.
5. The recovery is in Chineese ! I tried translating it via Google Translate via pictures, but that did not shows/offers me the option for entering the command prompt (as advised in tread mentioned in point 3)
I'm too lame in this Android/Linux based sea, so if anyone is willing to help me here (if you think its possible to achive my goals a-c) please give me some step by step guide how to do that. (links to treads would be enough)
Thanks a lot !
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist and there is no forum specifically for the Cubot devices at this time but I see that you have already posted an identical message in the General Forum at http://forum.xda-developers.com/showthread.php?t=2728355 which is a reasonable place to start where members familiar with your device might be able to advise you. I also see a number of references to your model from a site search at http://forum.xda-developers.com/sitesearch.php?q=cubot x6 which might be worth reviewing. Since your device is relatively uncommon, please be patient and give the experts there plenty of time to respond.
Good luck!
This thread is closed.