yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] imbmiller:
Try wiping dalvik and cache after restoring your backup.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] mikeprius:
Tried everything. The only thing that seemed to work is jimmy rigging in with a 3rd party 4.3 JB Kernel. I checked the original nandroid and everything backs up fine except that original ROM I made. The boot file is inside the made nandroid. I downloaded a modded JB 4.3 and the developer specifically stated that you needed to use Philz as the other custom recoveries will bootloop. Again I can sorta access my original ROM, but its somewhat messed up due to the kernel transfer.

I am going to try and mess around with PhilZ recovery and if it seems to work better with restoring everything then I'll use it. I like TWRP and the interface is nice, but if it cannot install any Touchwiz nandroids and only can restore 3rd party, then I'll have to stop using it.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] mikeprius:
Update: Tried to nandroid touch wiz RIM 4.3 with both TWRP and PhilZ. Twrp bootlooped but PhilZ worked fine. TWRP was 6.3.2.0 I believe. Also TWRP itself sometimes stalls on the blue splash screen so I have to enter recovery again and will not load the touchwiz nandroids i have made. PhilZ interface is not as nice but it's reliable and works so I'm just going to have to get used to it.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] mikeprius:
Update: I am pretty familiar with the ins and outs at this point. I'm sure I'm going to have to re-learn the process if I get another brand of phone in the future (HTG/LG/etc)...as I assume the process is different than Samsung, but for the most part, I have been creating a lot of nandroids, flashing custom ROMs, and playing with the recovery. I've tried all 3, and have found PhilZ to be the best.

I also have tried the various ROMs, however, I noticed that google maps is not present when I flash gapps with Cyanogen or any other ROM.

Right now I have a heavily modded TW 4.3 JB so I keep all the features of the Galaxy S4. Thanks again for the help, I was able to pick it up pretty quick.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] cruise350:
Google made Google maps a separate download a long time ago so it is not included in the gapps package files. Just download it from the play store.
[Galaxy S II Q&A, Help & Troubleshooting] mossywell:
Hi all, I've tried both CM and AOSP based ROM: Pound (with is what I'm currently on), Beanstalk (which hit my battery hard but was otherwise very good) and Omni (which was no better than Pound for me), and none of them appear to have a separate lockscreen wallpaper. Apart from Play apps and xposed / gravity, is anyone aware of any 4.4.2 ROMs that natively have a separate lockscreen wallpaper?

TIA

m
[Galaxy S II Q&A, Help & Troubleshooting] Vivek_Neel:
Nope

SENT USING VIVELROM_OMNI
[Android Q&A, Help & Troubleshooting] typos1:
I ve got my Oppo Find5 into a boot loop by doing something stupid (modding the dpi).

I can get it into recovery and using adb (on ubuntu) and I can connect to the device (shows device id and that its in recovery), but I cant find any instructions on how to push the original build.prop to the device (without loosing any data, obviously).

Could anyone help ?

Can I edit the build.prop using adb ?

Thanks
[Android Q&A, Help & Troubleshooting] demkantor:
You can pull the old one, edit it, then push it back

adb pull /system/build.prop /location/on/PC

Then edit

adb push /location/on/PC/build.prop /system/build.prop

You may then need to change permissions too
[Android Q&A, Help & Troubleshooting] typos1:
Thanks "location/on/PC " is the path to my device ?

That should be shown in the terminal ?

And just noticed that the device id I got from the command "lsusb" is different to the one that abd reports after I connect my phone (seems its a Nexus 4 : ID 18d1:d001is what lsusb reports)
[Android Q&A, Help & Troubleshooting] demkantor:
No, that's just me saying you need to tell it where to pull it to, like if you wanted to pull it to SD card command would be

adb pull /system/build.prop /sdcard

This would save it to your SD

You want it on desktop

adb pull /system/build.prop /home/yourubuntunamehere/Desktop

In this case change yourubuntunamehere to whatever this is for you
[Android Q&A, Help & Troubleshooting] typos1:
Yes, that what I thought you meant, just checking.

Tried to pull it to my desktop and it says that build.prop does not exist.

Could this be because I m getting the code for a Nexus 4 if I type lsusb ? :

When I type *~/Android/sdk/platform-tools$ List of devices attached" it reports "604c7129".

Or could it be because the screen density app has deleted my build.prop ?

I have a copy of the original build prop, can I just push it to the device (overwriting any existing one if there is one) ?
[Android Q&A, Help & Troubleshooting] typos1:
I have tried to edit it on the device in Team Win Recovery, but there is no build.prop in system (or anywhere that I can find) to edit, so maybe adb is right and there is no build.pop ?
[Android Q&A, Help & Troubleshooting] demkantor:
Yes you can pull the existing, but there should be one there unless deleted, try

adb shell

cd /system

ls -l

And look for the build.prop

But you're fine just pushing another one if you have it
[Android Q&A, Help & Troubleshooting] typos1:
On seperate lines ? Nothing happens and now I get this message

(gedit:5398): IBUS-WARNING **: The owner of /home/******/.config/ibus/bus is not root!
[Android Q&A, Help & Troubleshooting] demkantor:
Yeah separate lines, this time try

adb shell

su

cd /system

ls -l

And for future reference paste full input/output from terminal session (either in code wraps or if real long pastebin link)
[Android Q&A, Help & Troubleshooting] typos1:
OK thanks.

Could you tell me how to push a new build.prop it to the device ?

I am trying to sort out the issues I have with the device id being wrong. Once I have I ll try pushing it to the device, once I know how to do it.

Does it matter if the device id is wrong ? I mean is it ok as long as it connects ?

Thanks
[Android Q&A, Help & Troubleshooting] demkantor:
Directions to push in first post from me, adb devices is only picking up your one device correct? If so yes feel free to push
[Android Q&A, Help & Troubleshooting] typos1:
Sorry, very stressed ATM.

For location on pc do I just put Desktop, (thats where it is) or home/username/desktop/build.prop ?

And putting buid.prop at the end will overwrite the one on the device at the moment ?

Thanks
[Android Q&A, Help & Troubleshooting] demkantor:
Forgot the space

adb push /home****/Desktop/build.prop /system/build.prop
[Android Q&A, Help & Troubleshooting] typos1:
Thanks, it said it was successful, but phone still in same state and still cant find build.prop in system using the file explorer in TeamWinRecovery :(
[Android Q&A, Help & Troubleshooting] typos1:
Tried to pull it again and it doesnt exist, apparently, pushed it again and it said it was successful. Cant find it using the file explorer though, still in boot loop. Found out more info and the app sets permissions to 777 and they should be 644, got to chmod it, but unsure how to do that and if teh build.prop does not exist, well, I cant change permissions on it. Really stuck here.
[Android Q&A, Help & Troubleshooting] demkantor:
Try either fixing permissions in recovery or chmod with adb, something like

adb shell

su

chmod 0755 /system/build.prop
[Android Q&A, Help & Troubleshooting] typos1:
Thanks. So I just open adb make sure its connected then type:

"adb shell

su

chmod 0755 /system/build.prop"

Why 0755 not 644 or 00 644 ?

How do I fix permissions ? Do I mount the system in recovery ?

Shouldnt I do something in adb to get root ?

I have CM10.1 so recovery mode is TeamWinRecovery which has loads of features, including a file browser, but as I said I cant find build.prop, maybe I need to get root but nothing asks me for it.

It has a terminal emulator as well, but it asks me what folder I want to start from and thats stumped me as I was expecting a terminal just to open.

Sorry for all the questions !
[Android Q&A, Help & Troubleshooting] demkantor:
No worries, questions are how you learn

In truth I can't recall what /system should be, I'm on mobile so this is off the top of my head, it may be 777 or 644 but I think it should be rw-r--r-- if I remember right, also been drinking, friends bday

You may need to mount system first too, fix permissions should be in advanced settings in twrp

When you type su that gives you root

Also dirty flashing your current ROM ontop of this one should fix your issue, shouldn't wipe anything
[Android Q&A, Help & Troubleshooting] typos1:
I didnt have root permissions and the system wasnt mounted, I mounted the system with TeamWinRecovery, re-pushed the build.prop to the phone and theres a chmod755 option in TWR so I did that and rebooted and the phone is back alive !!

Thanks for all your help !! !!

Really, really grateful.
[Android Q&A, Help & Troubleshooting] Arrowblue:
hi,

I have similiar problem,

i was tweaking my build.prop using Android_A10_Falsher and when i rebooted it i got bootloop.

but in my case no supported recovery at all the device is Medion p4501 rom based on cm10 jb 4.1.2 i managed to root it and now thats it.

I check your method and i still have build.prop file in my system folder but permissions are 9071 -rwxrwxrwx so i think my permissions are wrong thats why i got bootloop.

Then i tried to change those permission like you told in this thread chmod 0755 /system/build.prop

unable to chmod / system/build.prop: Read-only file

so i think unable to chmod is that my system is not mounted ( writeable ) so i tried then to adb remount

Remount failed: Opreation not permitted .

Then i googled this one i tried adb root and every thing that i can find out still my system is not mounted and permissions wont change and bootloop wont go away. plz help me with this thing.

Edit : i found some thing that i need insecure boot or something to mount my system partition to reset permissions of build prop.

but there is not custom kernel no custom recovery nothing what i got was root i hope you can help me you are really my last hope.there is no system partition img so i cant flash it to restore my system.

Edit2:This is a newly released mobile in europe wow i spent alot of time here on xda and never had those problem with samsung or Sony.I even talked with Medion they dont want to give signed system .img that i can flash it with Stock recovery, This rom is based on cm 10 open source but Medion is making it closed source !!!!!

EDIT : Finally i solved it Mobile working again :D

What i did was :

in adb shell :

To mount system partition.

Then

That fixed my build.prop permission to rwrr and it worked.

Special Thanks to Demkantor i followed your adb commands on this thread to write permission and other thing. at first i even didnt knew that permission was the caused to boot loop because of you i manage to solve it out thnx alot
[Galaxy S 4 Q&A, Help & Troubleshooting] noobiewei:
I flashed my S4 with the latest Omega Rom. While flashing the modem using odin, I accidentally flash it on "phone" instead of "pda". Its like nothing happened so I reflash using "pda".

Everything is good except now everytime I make a call or accept a call, my whole screen become black and the phone freeze for few minutes.

Can anyone please help me on the problem?
[Galaxy S 4 Q&A, Help & Troubleshooting] Repulsa:
Reflash the modem via odin by selecting Phone/cp. Make sure to turn off your phone manually. Have a nice day

Sent from Hell ?
[T-Mobile Samsung Galaxy Note 3] Naturesretard:
My Jump! just came up yesterday but was too busy to go swap my device. The only real decent phone that catches my eye and criteria, being it must have an sd slot, is the Note3.

Now I have a few questions regarding this. I currently have the s3 and it's rooted; will I need to unroot and triangleaway before taking it in? I've read some reports that tmo wont care if it's rooted and I don't remember where to find the t999L unroot method.

Furthermore, should I be worried about this KNOX thing? I love flashing and trying new things, because over time I get bored with the same setup. I dont plan to ever go through samsung for replacements as that's why I have tmo insurance and warranties.

from what I've seen, this KNOX thing is just a new problem attracting attention to samsung as most US based phones deal with carriers as far as returns and exchanges, not the actual company. Not to mention android itself is open source.
[T-Mobile Samsung Galaxy Note 3] atlzonly89:
there are other methods to root. id suggust look through the forum if you can only b.c i cant rmr the name, i think its la something vega or vegas. i came from the htc one so the roms here are so much different.

---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------

there are other methods to root. id suggust look through the forum if you can only b.c i cant rmr the name, i think its la something vega or vegas. i came from the htc one so the roms here are so much different.

id recommend you get the note three
[T-Mobile Samsung Galaxy Note 3] corwest:
Short answer. Yes. Best phone I've ever owned.
[T-Mobile Samsung Galaxy Note 3] Naturesretard:
ty for the replies guys. Should I just wait a month or two before rooting? I played with the handset instore for a little and it doesn't feel like it needs rooting right away.

I'm concerned about KNOX. I don't think I'll have to do any warranty exchanges, but it's better to be safe than sorry.

I'm far too lazy to unroot my s3, so I'm just gonna try and swap it while it's still rooted. if they give me problems I'll just unroot it then take it to another store
[T-Mobile Samsung Galaxy Note 3] pandacookie:
I'd wait to root. The phone is so much fun, as it is. And the whole Knox thing is a bother worth avoiding, for now. I could see it being worth rooting if there were reliable KitKat roms with TouchWiz. But there aren't. So why bother, for now?
[T-Mobile Samsung Galaxy Note 3] Eric214:
For me rooting is about debloating the phone. Either by removing bloat or (as i have done with the Note 3) just freeze them for now. This gets a very noticeable increase in battery life. Also some mods can be nice. I like a very clean ROM with optimizations to battery and UI. The Kernel can be optimized too but like a stock kernel usually.

I'm coming from the VZW S4 running CleanROM and Bonestock but right now on the Note 3 I'm Rooted on Stock, with Bloat frozen and getting 7-10% battery drain per hour of screen on time (at 35% brightness) depending on what I'm doing.
[T-Mobile Samsung Galaxy Note 3] YrrchSebor:
i am curious how people like this phone, especially compared to the Note 2 and Galaxy S4. i thought the Note 2 was probably my favorite ever, the stock UI was smooth and battery life was excellent. i used the S4 briefly and found it a bit clunky and laggy with all those fancy features(although battery life seemed excellent).

so, how would you say the Note 3 is in these regards?
[T-Mobile Samsung Galaxy Note 3] nighthawk626:
Phones awesome. Get it. No downsides whatsoever on this phone, sexy build, power, speed, removeable battery and SD card, great stock battery. Big ass sexy 1080 screen, what more do you really want or need from a phone?
[T-Mobile Samsung Galaxy Note 3] Eric214:
My S4 was fine with the slightest of lag stock out of the box. I have the VZW variant from launch day (May 23rd) and i never took an OTA. With that said the 2 ROMs i used 100% wiped out any remaining lag. My S4 was pretty much perfect for me. The reason I am now on a Note 3 is i took advantage of Tmo paying off ETF. So why not upgrade to the Note 3 instead of making a lateral move?

That said, the Note 3 is AMAZING. It's much snappier and faster. I am Rooted with TWRP but stock ROM with just bloat frozen. It has better battery life and the spen functionality is really good. If you haven't you should really watch some YouTube vids to really see it in action. A 5 inch screen is most ideal but I have large hands so 5.7 is nicer for me as i do consume a lot of content (Youtube, SlingBox, Netflix). This wile still on the stock ROM too. I think anyone coming from the S4 or Note 2 will be very happy and would think of it as a worthy upgrade not a marginal one.
[T-Mobile Samsung Galaxy Note 3] rosedog:
To the op question ~ I'm still torn between my Note 2 and this. The volume on this is so low that Samsung is practically begging you to root this phone just for that.

Tough call imo both are good. I believe you can still get the N2 pre 4.3 and not have to worry about Knox.

Software side its the small things that bug the hell out of me like having a white dialer and not being able to open internet pages in the background. Things like this that are enough to piss off the Pope!
[T-Mobile Samsung Galaxy Note 3] Naturesretard:
I ended up getting it. I had to go back 3 times because my IMEI didn't reflect my account thru my warranty exchange. Went back today and handed in my s3 still rooted. The first 2 they actually checked if it booted, the 3rd just went ahead and did it. But to be fair he was there the other 2 times and was helping me then too. But they didn't go through any menus or anything to verify if modified or not. Just a 3 point inspection: No water damage, Boots, No cracks in the glass.

playing with it for a while..... Holy **** this thing is fast. I though I had stable quick roms on my s3... this thing just ZOOMS. I managed to lock it up once learning an spen feature, but only a mild hiccup. Aside from that I absolutely LOVE this phone. SO worth the minor 9$ bill increase. I can't wait to see what sammy drops for this. I'm surprised kitkat isn't an ota right now. I see no reason why it can't handle it.

Booted into download mode to see what was up. knox hasn't been tripped. I really want to try rooting just to see if I can debloat a little bit, but I'm a little worried to even mess with it. Do we know for sure if it's an eFuse or just software?
[T-Mobile Samsung Galaxy Note 3] Eric214:
If all my reading is correct Root De La Vega will root without tripping Knox counter to 0x1.... it will stay 0x0 but the CF-auto root i think may trip Knox just with rooting. BUT... if you put any custom recovery on it like TWRP or CWM that will trip the Knox counter to 0x1. Knox is an eFuse, its hardware i believe the eFuse is in the Snapdragon 800 chip.
[T-Mobile Samsung Galaxy Note 3] Naturesretard:
But do we know for sure? I've done a bit of reading too. And from what I've seen it's truly unknown. Even if so, would Sammy actually tear down that far to validate warranty claims?

Is this root method easily undone? Cuz all I really want to root for is my tibu and ad blockers. I'm content with stock atm
[T-Mobile Samsung Galaxy Note 3] krelvinaz:
There is talk that it can be reset by Samsung, but nothing specific, I rooted via de la Vega and stayed stock to get some basic access without any issues. Very happy with the phone like it is and have no urge to try other roms.
[T-Mobile Samsung Galaxy Note 3] Eric214:
I think Root De La Vega you're safe but not if you put a custom recovery on. just going to have to read through the post. and others can chime in if they did it that way. I put custom recovery on my phone right away so i just used CF-Auto root so i can't confirm from my experiences.
[T-Mobile Samsung Galaxy Note 3] d12unk13astard:
Everything about the note 3 is superior to the note 2(except audio lol), screen is crisp and brighter, more storage for games and apps, apps2sd is back!!, snapdragon800 soc is friggin insane even tho i do give props to sammys exynos soc, better build quality, better battery life.
[T-Mobile Samsung Galaxy Note 3] tyhill:
Note 3

YES! I had my Sprint S3 stolen.... so glad I spent my hard earned money to switch to T-Mobile and to get the Note 3. Best choice I made in years!!!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] marcematt:
Hi,

I need some help please:? I have bought my V1640 in Spain and the windows version is only is Spanish without any other language option. My Pc is all in English (XP Prof & Office 2003). When installing Active sync, it gave me the message of incompatibility error. Hence can synchronised properly (lost haft of data, and the synchronisation "options" for update address book & other items are not available).

I have spoken to Vodafone and 4uphones in Spain and they have not come with the solution.

Any suggestions what to do..... I will more than grateful.

Marce
[Galaxy S III Mini Q&A, Help & Troubleshooting] rclebalez:
Hi everybody,

first of all sorry for my bad level in english. I will try to be clear.

I would like to know if it s possible to add to the s3mini i8190 the security assistant that we found on the s4 or s4mini originally.

Why ? because my company is working in Caracas(Venezuela) and it s very dangerous. and we have only s3mini.

So the interest for me and my company is having this function actives, like this in case of attack, pushing at same time vol up and down, the mobile send automatically short alert message at a frecuency predeterminated to a list of contact determinated too with alert message and GPS position.

Many thanks in advance for your help to solve this case.
[Galaxy S III Mini Q&A, Help & Troubleshooting] rclebalez:
So, nobody to help me with my problem or that could be telling more about ?

Is it technically possible to have a similar program on the SIII mini like on S4 o S4mini ?

That i want to know is it a hardware problem or the infactiblity to detect the doble push on volume down and up.

Or it s only a software problem in this case may be is it possible to modifiy the S4 asistance security software.

thanks in advance for your answer.
[Galaxy S III Mini Q&A, Help & Troubleshooting] lexihel:
It might be possible. The problem, I think, is that the feature is part of Touchwiz (Samsung's custom User Interface) and that is propietary software. The option would be that someone who has both phones could extract the code from S4 and then try to port it back. There are a lot of possible problems to consider and it would take time. So it would be tecnically possible in my opinion, the thing is finding someone with the time, knowledge and resources to do that :(
[HTC One V] Curtis1973:
I have noticed the past few days a number of issues with our forums for the One V. Some times when you visit the main forum link,it will show a Samsung device where our One V's photo is usually located. And now clicking on forum topics(none in particular,at random) will take you to another devices forums that are not the One V.
[HTC One V] parkourz:
It shows Galaxy Note 2... today, when I wanted to enter General section, I've landed in one of Note's 2 ROM thread :p
[General Omni Discussion] ThePotatoRage:
Hey guys,

Last month i bought a new Galaxy Note 10.1 2014.

This tablet is great, but have no vanilla rom at all. I love OmniROM (been using it on another devices of my) and i'll be happy if you will develop a version for the Note 10.1 2014.

Thanks for your great work! :D
[General Omni Discussion] XxPixX:
if it's exynos then forget it :D otherwise there may be a glimmer of hope.
[General Omni Discussion] Entropy512:
As always, device support is heavily dependent on a maintainer expressing interest and picking up the device.

Note that after years of Samsung treating the aftermarket firmware development community like crap, quite a few former Samsung device maintainers have moved to greener pastures and have no interest whatsoever in returning to the pain and suffering that is working with a Samsung device.
[General Omni Discussion] ThePotatoRage:
Do you think that one day we'll get a Vanilla ROM?

TouchWiz working fine right now, but i'm sure that not for long.

And i love Vanilla. :(