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] NOOB ROM FLASHER, 5 OS's, 3 phones and a SOFT BRICKED ZTE KIS

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

[Q] how to install motto g drivers onto pc with no internet access

I have an older pc with no internet access that I want to root my moto g on. I plugged the phone in and the pc pooped up stuff saying it needed top install drivers. I couldn't get the phone to show up as a usb drive to get the drivers I had dled on the phone onto the pc. How can I get the drivers from the phone to the pc without the drivers being already installed? Can I dl an app that turns the phone into a generic usb drive or what? I was thinking of getting an usb otg and flash drive and copying the files to that then plugging into pc but I would hope for a free alternative if possible. I'm pretty broke. Also does anyone have any tips or advice on how to root/unlock broader of motto g x1034? I have the wind mobile Canadian version.
I'm using a windows xp pc with no internet.
So how do I get drivers onto pc with no internet
How do I root xt1034 moto g
What's the best/fastest rom to run on this phone
Where do I read to learn how to develop my own room?
What's a modified recovery? Can that help me root my phone without pc?
What have I missed?

tmw93 said:
I have an older pc with no internet access that I want to root my moto g on. I plugged the phone in and the pc pooped up stuff saying it needed top install drivers. I couldn't get the phone to show up as a usb drive to get the drivers I had dled on the phone onto the pc. How can I get the drivers from the phone to the pc without the drivers being already installed? Can I dl an app that turns the phone into a generic usb drive or what? I was thinking of getting an usb otg and flash drive and copying the files to that then plugging into pc but I would hope for a free alternative if possible. I'm pretty broke. Also does anyone have any tips or advice on how to root/unlock broader of motto g x1034? I have the wind mobile Canadian version.
I'm using a windows xp pc with no internet.
So how do I get drivers onto pc with no internet
How do I root xt1034 moto g
What's the best/fastest rom to run on this phone
Where do I read to learn how to develop my own room?
What's a modified recovery? Can that help me root my phone without pc?
What have I missed?
Click to expand...
Click to collapse
Have you tried connecting the phone in mass storage mode?
Now, to responds your answers in order:
So how do I get drivers onto pc with no interne
A: when you plug your phone it asks you the mode, instead of MTP switch to USB Mass Storage in the notification bar or in Settings>Storing (?)>USB Connection>USB Mass Storage.
How do I root xt1034 moto g
A: Look here ithe Q8.
What's the best/fastest rom to run on this phone
A: Look here. Sorry.
Where do I read to learn how to develop my own room?
It depends, first you need to own a room, is not enough to have a room with your name on it, you need to OWN it, make it a extension of you, decorate it with pictures of YOU... owning things with your picture on it, very empowering thing, right there. Then you develope it with good taste and decorations.
If you took a picture of it and want to develope it, you can do that in a red light or a very dark room.
You can join in a architect or a design school to start developing rooms, not only your own.
If you are referring to a ROM, you need a little background in programming and compiling source code, preferably in linux. If you'd like to experiment the basics, you can try to compile Cyanogenmod,following the guide in the wiki.
What's a modified recovery? Can that help me root my phone without pc?
a modified recovery is a recovery that's been altered from its original form.
nothing can help you to root your phone without a pc, adb and the drivers.
for a better understanding of what is a recovery, a custom recovery or other strange, make-up words and technobabble, read this.
Also, depending on the method used, you don't need to touch the recovery for rooting. But the easiest (according to me) is
see here.
What have I missed?
What have you hit?

[Completed] Srrange ADB sideload error, shows device but can't push or sideload files.

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

[Completed] accessing files and/or wipe data on a phone with broken touchscreen

hey there,
I am trying to access my files / wipe data from my Xperia Z3. The device has an unresponsive screen after I dropped it. I want to do a factory reset / wipe my data before selling it on. I do not need to save any further data.
A couple of weeks ago, I saved my files from the external phone SD card via USB on my computer (so USB debugging must be enabled I guess). However, I since updated my computer from Windows 7 to Windows 10 and now the Z3 somehow doesn't show up any more.
I tried to use ADB, but it does not connect to the device (ADB drivers and tools installed). The Z3 still shows up on my girlfriends computer runnnig Win7, although it is only shown as an "empty" device (no folder/file system visible in windows explorer).
I can not wipe the data via an app since I do not have any such app installed/configured with this phone. I also can not do it on the phone, because the screen doesn't show anything.
does anyone have an idea on how to wipe my data from the device or why it won't show up via ADB any more?
thanks a lot!

XDA Visitor said:
hey there,
I am trying to access my files / wipe data from my Xperia Z3. The device has an unresponsive screen after I dropped it. I want to do a factory reset / wipe my data before selling it on. I do not need to save any further data.
A couple of weeks ago, I saved my files from the external phone SD card via USB on my computer (so USB debugging must be enabled I guess). However, I since updated my computer from Windows 7 to Windows 10 and now the Z3 somehow doesn't show up any more.
I tried to use ADB, but it does not connect to the device (ADB drivers and tools installed). The Z3 still shows up on my girlfriends computer runnnig Win7, although it is only shown as an "empty" device (no folder/file system visible in windows explorer).
I can not wipe the data via an app since I do not have any such app installed/configured with this phone. I also can not do it on the phone, because the screen doesn't show anything.
does anyone have an idea on how to wipe my data from the device or why it won't show up via ADB any more?
thanks a lot!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. First, have a look at your device's homepage here:
Sony Xperia Z3
You can find a lot of useful information in the General Forum located there. If you create an XDA account, you can ask your question in the Q&A forum, also located there. Good luck and welcome to XDA!

hey,
that actually was me, I was not logged in for some reason.
I did look through the forums before, but I can not find any solution to my problem so far.
Since this is a problem with ADB, I thought it belonged to the general section rather than to a device-specific forum...
thanks and cheers