yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S II SGH-T989] Bluntified:
I set mine to 50-75% when I'm indoors, when I'm in the sun I have to bump it up to 100%. I don't notice much battery drain from normal usage, only with games and video, they normally drain batteries really fast. I don't play any games only some YouTube or videos I took.
[T-Mobile Samsung Galaxy S II SGH-T989] c5vette211:
If you go to settings then power saving, you will see custom power saving settings you can then adjust how to same battery including the option for brightness.
[T-Mobile Samsung Galaxy S II SGH-T989] RushAOZ:
I always keep mine at full brightness and I've gotten killer battery life. My phone averages 3-4 hours screen on time. Of course I can make that stretch 5 hours or one whole day. Depends on how much you use your phone of course.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Beremat:
Thanks, worked like a charm on my SII. And I finally have ADB set up for any future hiccups!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lyrictenor1:
I'm having the same issue; I did the above procedures (using a Mac) but every time I type "adb shell", I get this:

"-bash: adb: command not found"

Help, please....

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lyrictenor1:
Nevermind, I figured it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] countrylife:
good write up, thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erstad:
Seems to be only when you use a gnex as build prop.

HTC jewel works great

I had two softbricks worked great
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Riggzo:
very helpful. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mknlb50:
This doesn't do anything for me. It still shows rw-rw-rw after running that command in adb. Any other ideas?

It also seems like it doesn't modify any of the files at all. I even tried renaming because i have a build.prop.bak file that i want to use and it doesn't seem to rename it.

[update] I am using the Odin method just to reflash it to the stock rom. I have moved on from this useless method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballot:
Hi i just edited the /system/build.prop

for able to play gameloft games

now my tablet cant boot

i use this room : http://xdaforums.com/show....php?t=1816795

i tried your method

i got this error

>adb shell

error: device not found

what can i do i don't want lose data

i tried to recovery mode and normal booted mode no lucks :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rattouille:
please help. ican't find my device in device manager
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SU-noobe:
Thank You !!!!!!!

Thank You, Thank You, Thank You, Thank You, Thank You, Thank You - I was hours away from taking my phone back ... I found my build.prop file with 0 bytes but fortunately I already had a build.prop.bak in there. I'm fairly certain I softbricked my phone by not following the instructions closely on rahpyqui utube Google Wallet process. Thanks SO MUCH!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eortizr:
isn't just easier to re-install the ROM you are running? You don't loose any settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cleit0n:
unable to chmod build.prop

Help me!!

Error: unable to chmod build.prop: Operation not permitted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CharkeyBeckles:
I'm having the same problem, how did you solve it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dimikon:
IMEI unknown - invalid

I have problem with IMEI ,no sim cards work in lenovo A660.I have done some factory resets and tried all possible solutions referred in xda forums but none worked.DOu think that build.prop could cuz problem to the IMEI somehow? i had to overwrite a build.prop file from a friendly site because i couldnt use 160 characters in sms and they said that this would help.BUt now , no IMEI.Can anyone help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
Thank you for the info:highfive::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cobby2004:
Help!!!

How do I boot my Xperia S into Recovery Mode? Do I have to press the power button + VOL UP Button so that the LED gets blue?

Anyways I did it that way, expecting it to be in Recovery Mode, but when I run the adb shell it says "Device not found." Can somebody help?:crying::crying::crying:

I guess its because I didnt install the naked drivers but I cant do it because I wont find my device in the device manager... Why not?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krosa:
Very nice guide, thanks!!!:victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kocane:
THANK YOU!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Daveybeer:
permission denied

I am getting this when starting adb shell

- exec '/system/bin/sh' failed: Permission denied (13)

is this just a driver issue as I installed the naked driver and rebooted after.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Android_Brick'A'Holic:
Alcatel One Touch Fierce NOT booting up :(

It's been about 2 months, and i've searched everywhere... I was messing with my build.prop to try and use the Milk app for Samsung. After I did what was needed; I rebooted my phone and it wouldn't boot up. I got really disappointed and I thought my phone was forever broken. So, I recently today, came across trying to fix my buld.prop. and wondered across these instructions. TWO QUESTIONS. Does the work for Alcatel One Touch Fierce? If it does, can I stll fix it with these instructions even though my USB debugging may not be activated?

-Please Help Me, I just got this phone, and it was rooted when I got it. Also, I obviously don't know what I am doing with android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chamaria17e:
Please Help....

I followed your instructions but it got an error in updating drivers....

what should i do ?????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
This is actually rather out dated at this point. It is good to learn about adb though, so im not saying its not helpful, but there is an easier way now.

Get a good copy of your build.prop from your rom, copy to sd, boot into recovery and use the built in file manager to copy to /system and set permissions.

Thats it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chamaria17e:
please tell me more about it...

My phone is in the same problem that is discussed here...

I'm new to all these things.

I first had copied the build.prop of nexus 5 to my gionee g3, after that many of its apps stopped working. Then I edited it again to its original build.prop and restarted my phone, now it just sticks to company logo screen.

I'm able to start it in recovery mode.

I had tried the above discussed process, but got an error in updating drivers. After applying adb shell command it shows the message - device not found.

But I don't have any further knowledge. Please Help.

Any help will be greatly appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Unzip the rom you are currently using and copy the build.prop to your sdcard using the computer.

Then in recovery find the file manager and copy it over the existing one.

Then set permissions on it to rw-r--r-- (0644).

Reboot.

No need for adb or specific drivers doing it this way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chamaria17e:
thanks. but...

Thanks. But can you also tell me how to unzip the ROM?

After unzipping it, will I be able to access it from computer?

And please also guide me how to zip it back to its original state.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Any file manager should be able to do it. I use Root Explorer, just long press on build.prop file and select Extract. Then copy it over. If doing this on a computer, install 7zip, right click the file and either extract or copy/paste it out.

No need to unzip/rezip the entire rom. All you need is that one file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chamaria17e:
:(

Ohh... I'm unable to understand.

I think root explorer is an android app, and I had already told you that my phone just hangs on company logo screen.

If I use computer... What to do?... Where to extract?....where to paste?... How to copy that in my phone?...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joel32137:
HELP!!!

I get "Error: Unauthorized Device..."

Does this mean I have the wrong drivers?

When I bricked my phone, USB Debugging was turned off... could this be the problem? Any way around this?

Any help is appreciated...

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justinflorendo:
my device usb is boken and cannot connect to pc

what would i do if my gt-p1000 (galaxy tab) cannot connect to pc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Thanks a lot bro.

:victory::laugh:

Worked like a charm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eWay:
have no root access

When starting the adb shell I am not able to execute the "su" succesfully. Instead of getting the root prompt # it seems to hang. Have to kill it with Ctrl C ...

So my problem is how to get root again. The phone was rooted before my experiments with Root Genius. Now it seems not to be rooted :(

Any idea how to get root # ? Root Genius is not able to root it in this "soft bricked" state.

Need root, to write to the file system because it is READ ONLY ( $ ). Would like to make it RW with "# mount -o rw,remount /system" to rename my original build.prop.orig to build.prop ...

thnks

eWay
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chamaria17e:
done..

I had changed my phone's build.prop file.

And my phone had just stopped..

I had tried many things after that... But nothing was helpful.

Then I had taken it to service centre. And they had solved the problem in 10 minutes, in front of my eyes.

So I recommend you to take it to service centre.

** but do not tell them anything.. That your phone is rooted or not.. And what have you done with it....​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eWay:
I am located in Munich, Germany and don´t know of any service center, that would look at a chinese phone like my Newman K1S ... Where exactly is "your" service center ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TreadOnMeNot:
I can't see my device in device manager so I can't install the driver. (unless I go to the side load)

Which I need to open a shell on the phone.

Anything I need to see my device from the recovery menu?

Can someone please be kind enough to help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 11_SHOOTER_11:
Maybe u didnt installed the adb drivers correctly, just follow the link above to install the adb driver
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 11_SHOOTER_11:
I had the same Problem as you have. The bad thing is that i didnt find a solution for this problem without wiping all data :/. I tried this method: But its only for google Nexus devices

1. Download the Nexus Root Toolkit from WugFresh.

2. Install it and follow all instructions.

3. Choose your Device in the Toolkit

4. Click on the option 'unlock bootloader' Make sure you follow all instructions

5. If your boot loader is unlocked, turn your device off

6. Now click on flash+unroot (WILL WIPE ALL DATA)

7. Follow all instructions that are displayed !!!

8. If everything was successful: your device should reboot now

9. Done :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 11_SHOOTER_11:
Install the right driver for your device. Just search the specific device drivers on Google and install them on your PC. After that restart your PC.

Hope it worked :good:

---------- Post added at 12:56 PM ---------- Previous post was at 12:31 PM ----------

Try a hard reset: (

WILL WIPE ALL DATA

)

1. Turn your device off.

2. Push the power button and instantly, while pressing the power button, press the volume down button, until the boot loader menu popped up.

3. Now navigate with the volume down/up button to ''recovery mode'' Now click the power button to apply the recovery mode.

Wait Until your device show 'No command'

.

4. Now press the power button, while pushing the volume up button only 1 time.

5. You will see now the reset menu of your device. Just click on wipe all data.

6. Now try to reflash your recently installed android version with a program like Nexus Root Toolkit(not compatible with your device).

---------- Post added at 01:12 PM ---------- Previous post was at 12:56 PM ----------

Try this to solve the problem: cd <path of adb.exe> (write the correct path in there like: C:\Users\Hello\Downloads\adb Now you must see something like this in cmd

C:\Users\Hello\Downloads\adb>

Now type adb shell again:

C:\Users\Hello\Downloads\adb>adb shell

Hope it worked :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eWay:
build.prop edit boot loop solved !!

I have solved my boot loop issue with the edited build.prop by the help of honzikd :) Honza - thanks ! I have re-flashed my MTK-device with SP flash tools with a ROM from www.needrom.com . That has succesfully overwritten all existing data including my badly edited build.prop.

Adb shell experiments makes no sense, if you don´t have superuser access (root # ). If yes, it´s pretty easy after mounting the file system as r/w. e.g.

# mount -o remount,rw -t rfs /dev/block/st19 /system

Good luck !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tb4jc:
You safed my life!

Thanks a lot, you saved my life! ;)

After tweaking my build.prop file, it had bad permissions on my new Elephone P3000S and thank God I had USB debugging enabled and could access the device with adb and correct the permission!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpit141:
I have the same issue, but i am not able to boot into recovery mode
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tolol:
i managed to fix build.prop, here are the steps:

enter twrp

advance

file manager

goto system

copy build.prop to sd card

now goto windows

browse to Micro SD Card

open build.prop with notepad

edit build.prop (in my case, i delete a few lines, causing bootloop)

save it (filenames should be build.prop without any extension)

put build.prop back to sd card

back to TWRP

file manager, copy build.prop from sd card to system

then click on build.prop, chmod 755

the reboot, voila.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gloftking:
Urgent

I have just screwed up my Samsung p3110 by replacing the build.Prop file however I did backup the original build.Prop file although stupidly it's in the root folder of the tablet and that can not turn on. I only have access to Odin mode and at the moment this tablet won't even switch off

Any help will be really appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yaksh123:
method compatibility

Will this method work with my nexus 6?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] genterminl:
I don't know if it is due to a different device or different version of some app or os, but none of this has helped me. I added a line to the end of build.prop, and got the dreaded bootloop. In that state, adb works, but without root, I can't edit, copy, or chmod build.prop, nor can I remount /system rw. I can type "su" but it does not do anything. When the tablet was working, invoking su would pop up a window requesting approval of the su, but that can't happen stuck in the bootloop. In recovery mode, neither adb nor fastboot sees the device. In bootloader mode, fastboot seems to succeed in flashing a new (original) copy of build.prop to /system, but I suspect /system is not really mounted, because the old version is still there when I reboot. I've tried creating an update.zip to replace build.prop, but get the signature failure error. The tablet is an Acer A1-830, and I rooted with FBRL and SuperSU, running the stock (after official OTA upgrade) 4.4.2 (I think - with the phone in bootloop, I don't know how to confirm the current android version)

Thanks for any other suggestions?.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
..

---------- Post added at 08:07 AM ---------- Previous post was at 07:56 AM ----------

You could flash AROMA file manager from recovery and use it to replace your build.prop. If you're using TWRP recovery it has a file manager built in that you could probably use to fix your build.prop problem.

Or you could try signing your update.zip to get it to flash. The link is a pretty good step by step.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] genterminl:
Thanks for the suggestions.

I'd love to give Aroma a try, but as delivered, it's only for ARM, and my Acer A1-830 is Intel Atom. At some point, I'll get set up to compile it myself, but that's a longer term project for me. I'll also see if I can hunt down a TWRP for Atom.

I have signed it, using the keys that came with testsign.jar. I suppose the problem is I am using the stock recovery? I suppose I could try to remember how I rooted the tablet (FBRL) and see if I can use the update.zip within that recovery.

I probably won't be able to try much more until much later today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Sorry. I never noticed AROMA fm was ARM only. I've never had any Intel mobile devices, but I have been thinking about picking one up lately.

I don't know what the custom recovery options are for your tablet, but looking into those might be your best shot to fix it yourself if fastboot is not working for you and there are no other flash tools along the lines of Samsung's Odin or LG flash tool but specific to your tablet. TWRP recovery has the file tools you need if it is available for your tablet and you can get fastboot to flash it.

Good luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] genterminl:
I got mine by cashing frequent flyer miles, so I'm still really happy with it. The issue of multiple possible processor types wasn't much of an issue until the larger variety has become more popular. However, I've run into it before looking at open source Router software. Android mostly avoids it by using Java, but that doesn't help with the OS itself, or other low level utilities that need to run when Android itself isn't.

I'm sure I can get something to work, since I did root the tablet. I've just got to find the right combination of pieces to use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I think [MENTION=4880021]genterminl[/MENTION] has only one custom recovery option, that is the tethered recovery by social-design-concepts. or the Linux version by vampirefo. By his reply I see he is familiar with the work by them. That recovery is CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] genterminl:
Well, I finally got INTEL_TRIAL2_TETHERED_CWM_PKGKIT (found on another thread here) to work, and finally managed to produce an update.zip that fixed the permissions of build.prop back to 644 (including my edit). The only problem is that when the tablet (Acer Iconia A1-830) rebooted, it was in Demo Mode. I was able to disable the demo video app, but apparently the only way to actually get out of Demo Mode is a factory reset. Since everything else seems to be working as before, I'm going to wait a while, and do a full backup before I resort to that. In fact, I might just use this opportunity to go hunting for a custom ROM or newer version of the OS, since I'm already out of warranty.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If you find a custom ROM for the A1-830 please let me know. I haven't found one yet on XDA, but I don't expect to considering the locked bootloader on the device. (I did see a link to a site that looked very untrustworthy.)

I once activated demo mode just to see what it was, thinking that there would be an easy way to leave it. I had to do as you are thinking is necessary. I reflashed the stock ROM. There is an image on one of the threads by s-d-c.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] undeadrwby911:
does anyone mind to make a video guide? im doing something wrong in the command prompt. thanks. also bump.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nano.nano:
Is this way can be done without using a computer, or there are other ways besides using the pc I have problems with my device bootloop the only stop in the logo when turned on. I thought it might be mistakes in the build prop because before that I was using tweaks to build prop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mursssky:
Unauthorized

I'm stuck at RUN "adb shell".It says device is unauthorized,I'm in a bootloop so I can't access developer options or other stuff.I changed my build.prop permissions and now I'm trying to fix it,got no custom backup but I have a copy of the default build.prop file and I read online that there still is a way to fix my device.I'm not an expert with cmd,adb so please help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpm1590:
My device is unauthorized, for authorized this I need power on and check it, how can I do it, if my device is bricked and dont power on!!!????

someone can helpme please!!! :(((((
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Anand@95:
I have my buil.prop file in my sd card... But i have only default recovery in micromax a311 ,cwm or twrp not installed......so pls guide me how to set permissions
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Will it boot? I'm guessing no since that is why most people end up here. If it will boot, Root Browser is a good app for setting file permissions.

If it won't boot into the system, there's still a chance you can revive it if you are rooted and it is getting far enough into boot and allows an adb connection. Connect it to a computer and if

adb devices

returns something then you can try this:

adb shell
su
chmod 644 /system/build.prop

I'm not at all familiar with that phone. I checked out the forum for it and it looks like TWRP is available, but you have to flash it using a toolkit from a rooted rom according to the directions. :( You might get some better advice in the micromax a311 Q&A if there are any device specific tips or tricks.

This sounds promising if you're still soft bricked. Good luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Anand@95:
fixed.

i done flashing my phone...it works fine.....

since it was it bootloop adb not recognised my device. so i installed adb from "coolpad"sort of and just installed firmware....... anyway thanx friend...........:fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kumarakash938:
Well you can always use TWRP to revert back to the original build.prop file and change its permission via chmod755 option in TWRP file manager.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lyvyoo:
I search one day for solutions, including this advices from the first post. Another hint is to try this complete guide to extract build.prop, edit, and push back. But I make another trick, having a backup of the untouched build.prop file. So, enter in twrp / install and flash the custom ROM. The next window in Aroma instaler will be something like "Install ROM / About / File manager". So click file manager and move or delete build.prop in Downloads for example, edit the file or replace using your computer widows explorer (because you can access the internal memory) and from the phone move the new file back to /system.

So, a push the backup file back, but surprise, my phone wasn't boot :( Maybe you are more lucky.

For me, the solution was to reflash the ROM with TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maticellphone:
I will try this guide right now. But I ignore the commands to rename a file.

I renamed bootanimation.zip into bootanimation.old and now the phone is in a boot loop. I did a factory reset/wipe, etc via recovery mode. Nothing. I'm an ignorant but I managed to change many annoying android things to my liking. Then, I renamed that damn file...

Can I use this guide to simply rename the file again to what the system is looking for? I can't believe how dumb it is to make it mandatory during boot to have that file... Why not just skip it???

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Should work. Boot it into recovery, connect it to a computer and:

adb shell
cp /system/media/bootanimation.old /system/media/bootanimation.zip
chmod 644 /system/media/bootanimation.zip