Database Develop

build.prop deleted

Ok so here's the newb in me. I was trying to get Netflix working on my rooted NC. I made a backup of build.prop by making a copy and renaming it build.prop.bak. I went into build.prop to change the product model and manufacturer. I did that, saved and rebooted but Netflix still did not work...whatever.
I decided to give up for the night, so I went back into /system and renamed build.prop.bak back to build.prop. At this point I had 2 build.prop files. I deleted the modified one to find out that both had been deleted.
i thought a reboot (again newb mistake) would magically restore the build.prop file (hind-sight says obviously it wasn't going to). It reaches the "n" screen and then the screen flashes black.
Is there a way to fix this without reflashing? I know there this thread:http://forum.xda-developers.com/showthread.php?t=949699
I did use Titanium Backup to back up all my "stuff" on the SD card if that means anything. Again, sorry for the dumb questions.
Any help would be appreciated!

Easy method - re-flash your ROM without clearing data. Will also overwrite any other tweaks.
More difficult method. Extract the build.prop from the ROM you are using. Boot into CWM and push the build.prop using ADB.
Sent from my NookColor using XDA App

martian21 said:
Easy method - re-flash your ROM without clearing data. Will also overwrite any other tweaks.
More difficult method. Extract the build.prop from the ROM you are using. Boot into CWM and push the build.prop using ADB.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
so for easy method, are you referring to setting up a bootable SD card with Clockwork Mod and reflashing ManualNooter?

NookyLov3r said:
so for easy method, are you referring to setting up a bootable SD card with Clockwork Mod and reflashing ManualNooter?
Click to expand...
Click to collapse
My bad. I assumed you were on CM7.
Since you are on stock B&N, your options now are pretty much flash one of the stock images (and lose everything - ie. return to stock) or extract the build.prop from the stock image, boot into CWM, and ADB push the build.prop.
Sent from my NookColor using XDA App

Yeah. This is what I ended up doing...such a PITA. Oh well, at least it can be done this way. Thanks for the help!

[Q] Anyone Know Where Texts & Calendar Data is Stored?

I've somehow busted my phone. I was trying to get rid of Motorola Setup so deleted Setup, and now it starts to boot, I get the spinning globe, but then the screen goes black.
I haven't done a backup for three months and I have some pretty important data in this thing. I'm thinking about using fastboot to flash the system.img, but am concerned that this will overwrite texts and calendar.
Has anyone figured out how/where these are stored?

Well in TWRP there seems to be a file manager and adb sideload. Could these save me?

Flashing the system.img only should not wipe your data. But there is always risk of something not going well. I am sure I don't need to remind you to make a nano back up in recovery before making changes to your system.

I can't believe this is still a mystery, after all this time.

Thanks, but a nano backup wants to go into /, which is likely to be wiped when I flash system.
Alright then, I'll use the TWRP file manager to set aside my /data dir to flash and hope that's where everything is.
Now I need a fastboot-flashable version of system.img v4.4.3. Where can I get this? I have 4.4.2 but my current system is 4.4.3.
Anyone know where a fastboot-flashable 4.4.3 image is?

Quantumstate said:
Thanks, but a nano backup wants to go into /, which is likely to be wiped when I flash system.
Alright then, I'll use the TWRP file manager to set aside my /data dir to flash and hope that's where everything is.
Now I need a fastboot-flashable version of system.img v4.4.3. Where can I get this? I have 4.4.2 but my current system is 4.4.3.
Anyone know where a fastboot-flashable 4.4.3 image is?
Click to expand...
Click to collapse
Try here. http://sbf.droid-developers.org/download.php?device=0&file=919 Assuming you have the T-Mobile version

Thanks, this helped. But now when I boot everything just crash-crash1ty-crash-crashes. Is there something else I can restore to reduce these crashes so I can at least run SuperBackup and get my texts and calendar saved? (I do not trust G**gle and their sync)

[SOLVED] Deleted bloatware but came back after reboot

Hi!
I have rooted my phone, and deleted bloatware using uninstall.
After reboot, the apps returned, so I deleted /system/apps/*.apk (relevant) files (I'd also like to know what are the *.odex files if someone can kindly tell me )
Then, I rebooted again, and again they were... I have read in previous threads that flashing the kernel is needed. Is that so? And if so, how can it be done?
Thanks!

barashe said:
Hi!
I have rooted my phone, and deleted bloatware using uninstall.
After reboot, the apps returned, so I deleted /system/apps/*.apk (relevant) files (Id also like to know what are the *.odex files if someone can kindly tell me )
Then, I rebooted again, and again they were... I have read in previous threads that flashing the kernel is needed. Is that so? And if so, how can it be done?
Thanks!
Click to expand...
Click to collapse
You need a custom kernel with /system write permission (unsecured kernel) .
You will not be able to install ota updates if you mess with /system files.

Thanks!
alray said:
You need a custom kernel with /system write permission (unsecured kernel) .
You will not be able to install ota updates if you mess with /system files.
Click to expand...
Click to collapse
Downloaded and installed ElementalX-m7 kernel and now they are all gone!

barashe said:
Downloaded and installed ElementalX-m7 kernel and now they are all gone!
Click to expand...
Click to collapse
for future reference, you can also stay on stock kernel (dont really know why ) and do the changes in custom recovery (eg TWRP)
if you want a relatively easy file manager for custom recovery, check out Aroma File Manager... that would save you the hassle of using an adb shell
oh, and if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title

Bootloop after copying a file to /system using TWRP with no root

Hello
I've got the Note 5 SM-N9208 and I am trying not to root (tripped Knox tho as I but Phillippines system.img on it) it as the annoying Barclays App doesn't work.
I am however, trying to add my custom CA certificate into the /system/etc/security/cacerts folder. This is what I used to do in my rooted devices before and worked fine.
I have flashed TWRP and taken a full backup (thank God!) and then mounted the system as RW, copied the file, rebooted and voila, boot loop on the Samsung Note 5 screen.
The only fix is to reflash the system partition from the original TAR file which makes me wonder - is there a mechanism that prevents system from being modified if the device is unrooted? Something like Samsung's system protection or something.
Could anyone try to reproduce the issue on an unrooted phone just to see if it's just me being unlucky? Or is is simply not possible to modify system without root? If so, how come TWRP allows me to do so?
Let me know what you think guys
Looking forward to hear someone else's opinion.

mateuszd said:
Hello
Let me know what you think guys
Looking forward to hear someone else's opinion.
Click to expand...
Click to collapse
You must be rooted to make system changes.

You need to make some changes in ramdisk : remove support_scfs,verify from the fstab files for system partition

bootloop after messing with build.prop

hello, please help me recover my phone, it's stuck on bootloop after i tried to change brand and model by editing build prop
my phone has lots of important notes , and many open tabs on chrome i don't want to lose track of.
i ve been trying with adb, but i am desperate now, will flashing system.sin delete my data ?

Did you try to fix the permissions with adb? Do u have a backup

masterofnocrack said:
Did you try to fix the permissions with adb? Do u have a backup
Click to expand...
Click to collapse
i have a copy of my build prop, after messing arround and experimenting how to use adb, i think i manage to remove the old file, and pushed the backup, but still my phone keep rebooting after sony logo, i don't get the blue waves

Gamer4Life said:
i have a copy of my build prop, after messing arround and experimenting how to use adb, i think i manage to remove the old file, and pushed the backup, but still my phone keep rebooting after sony logo, i don't get the blue waves
Click to expand...
Click to collapse
I don't know how to do it but it must work, you should create a zip file that would inject build.prop. Maybe somebody can help you to do it.

U need to set the proper permissions.
After pushing ur backup build.prop to /system
Do this in adb shell: chmod 644 /system/build.prop

if you have TWRP recovery go to mount option and mount system partition.
then go to file manager and find build.prop file in /system then chmod that file.
reboot system.!!!!!
on the other side of the coin you can flash your phone using FLASHTOOL

Gamer4Life said:
hello, please help me recover my phone, it's stuck on bootloop after i tried to change brand and model by editing build prop
my phone has lots of important notes , and many open tabs on chrome i don't want to lose track of.
i ve been trying with adb, but i am desperate now, will flashing system.sin delete my data ?
Click to expand...
Click to collapse
flash system.sin using flashtool and exclude userdata from wipe box
if you are on stock try to flash the same build cause as i think every version is do resize partitions so that will make your internal memory not accessible and you will must flash userdata if that happened
and best of all if you have TWRP is to build prerooted firmware and copy to your Internal memory or sdcard and flash it
this will don't do anything with userdata partition

Thanks everyone, i flashed sin system with flashtool, lost my mods and root, but not big deal my notes are saved.
All this hassle was because i wanted to spoof my phone into galaxy s2 to get old gameloft games to work on my phone. I changed manufacturer ftom sony to Samsung and model number.
Dont know what i did wrong.