yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] Ingenium13:
Is there a zip we can flash in TWRP or CWM to go back to stock? I'm stock rooted with a couple tweaks (like hotshot mod) and I want to revert to full stock to take the MJA OTA. I'd of course need to manually flash the stock recovery afterwards via odin for the OTA to work.

I know I can odin back to stock, but that wipes data (and possibly the internal sd card as well, the thread isn't clear). I want keep data, since there shouldn't be anything incompatible with full stock.

I suppose I could backup the internal sd card, backup data with TWRP, odin to MF9, take the OTA, use cf to get root, odin TWRP back on, restore the internal sd from backup, and restore data from TWRP. But it would certainly be a lot easier and faster if there was a way to just go to stock without wiping data...
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ROMANTiC KiD:
If you had research. Restoring data on 4.3 messes up your phone. You should stick with mf9 for now really. The only good thing about 4.3 is gear support but come with knox security which is being a pain in the a** for people now. But thats my opinion
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] jj14:
4.3 should have the TRIM support (the main reason that I was interested in it)
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] Ingenium13:
I did research, the concensus was that titanium backup restoring wasn't working, and that was only when restoring the app itself (installing from the Play Store then restoring data only works). But restoring the actual data partition should be fine.

Or if that's an issue, and I had to wipe data, then I would just restore data right after odining to stock MF9 before taking the OTA.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] cruise350:
If you use the stock mf9 tar to return to stock, all of your data will still be there, it does not wipe your data. Your system partition will be overwritten along with recovery, bootloader, and modem. But it will not touch your data. Download the one from sammobile and you should be fine.
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] reverepats:
Yeah trust me, there's a lot more good to 4.3 than just gear support. Trim support was my most anticipated feature i was looking forward to as well, but I can tell a huge difference In the clarity of the screen, and colors as well. Battery life on stock kernel has been ridiculously good.
[RAZR HD Q&A, Help & Troubleshooting] T0ked:
I have a stock factory ROM, ROOTED, MAXX HD. It's on the latest firmware pushed by VZW. After rooting, I had removed a bunch of apk's I knew I wouldn't need. The problem happened when I did a factory reset due to some minor GPS issues. I had forgotten that I removed the Setup.apk. (Yes I'm kicking myself regarding backups... but too late now).

Now my MAXX HD has no launcher. It states the Setup Wizard has stopped working. I have no access to files or applications. I can access the notification bar and the systems menu and such and can see the standard programs running under APPS. Wifi works, etc. I even signed into my gmail accounts, but I don't have access to any apps. Pressing the home button does nothing except bring up the error message again.

I've been trying to use ADB to push the missing files into the /system/app folder and that is described below. If anyone has any other ideas on what I can do, I'm all ears.

This part is for those that know a thing or two about ADB. I'm a noob at this so please correct away!

So, my ADB exploits... I've tried to push the setup files to /system/app via adb but have had no luck. I keep coming across access denied or this action is not allowed in production phone, etc.

The commands I've used are:

adb push setup.apk /system/app/setup.apk (This just gives the copy protected blah blah)

remount and root don't work.

in shell, when I type "su" the "$" does change to "#"

I've remounted the system as rw but pushing the file still gives me a not allowed value.

I'm just going to list the commands I've used now. If anyone has any suggestions or if I'm doing it wrong, please correct away. Thanks!

adb shell (this gives me a [MENTION=520438]Vanquish[/MENTION]:/ $)

su (this changes the $ to a #)

mount | gret system (this gives me a long device-system name. it indicates it is now rw. it was originally ro)

mount -o rw, remount <device name from the previous command> /system

exit

exit (back to C:/adb)

adb push setup.apk /system/app/setup.apk (still says not allowed) (the root and remount commands still don't work)

I read that I need to type in "adb shell su push..." but I cannot get that command line to work at all.

Any help is extremely appreciated. Thanks!
[RAZR HD Q&A, Help & Troubleshooting] T0ked:
Solved it myself

I guess I need to brush up on my ADB.

I got it to work by pushing the files to /sdcard/, then in shell, used # cp /sdcard/<file> /system/app/<file>

To all the ADB guys out there, how could I have done this in 1 step? I definitely don't have the syntax down.
[T-Mobile HTC One (M7)] jaws197:
All,

I have a T-mobile HTC One that is locked to T-mobile and was wondering if it would be worth my time and effort to get it Sim unlocked and stay with T-mobile for the purpose of maybe getting the Android 4.4 Kit-Kat update sooner? I read that HTC USA is bringing it out "within 90 days" for all HTC Ones, but the Google Play edition within two weeks and the "unlocked" and developer editions within 30 days. I know I'm being impatient but I am looking forward to the new functions and am hoping that it fixes the horrible battery drain that I have noticed since the 4.3 update.

The phone is paid for and I have already called and am eligible to get the unlock code....

One of my questions is how to unlock it without a "foreign" sim? Can I just by a net talk or other phone company sim and unlock it then just pop the T-mobile sim back in? And if so would that qualify the phone as "unlocked" to get the update that much sooner? Also, would that cause me any issues with T-mobile's network? I know I could use one of the many fine roms here but my hacking skills are nil and I would prefer the factory update, I would rather not put my non existent skills to the test.

Please any and all help would be greatly appreciated! :highfive:

Thanks for looking!
[T-Mobile HTC One (M7)] onlineunlocks:
Getting your phone sim unlocked will not help you get the htc update faster,so if that's the only reason you need it unlocked do not waste your money on that.Probably will be a custom firmware available for your phone and can use that if can not wait for the official release from your carrier,but that may damage your waranty
[T-Mobile HTC One (M7)] jaws197:
So that wouldn't qualify it as an "unlocked version"?
[T-Mobile HTC One (M7)] onlineunlocks:
even if you unlock it by an unlock code when updating using the built in update feature,will update to the tmobile rom,the "unlocked version" is the never locked version,that came unlocked with unbranded rom
[T-Mobile HTC One (M7)] malushko:
not really bro, ur confusing what is the factory unlocked version international, to a sim unlocked tmo version, two diferent things lol hapened to me with the note2 i had, i recomnd being patient im sure our devs wont let us down:D:good:
[T-Mobile HTC One (M7)] jaws197:
Thanks to all!:D

That was exactly what I was wanting to know!

I really appreciate the info!

Love this site!:cool:
[T-Mobile, Samsung Galaxy SIII] mrbackdoor:
SuperSU on TW ROMs running 4.3 (regardless of version, source of version and how you got it) is frustrating. Apps that need root do sometimes able to get root access, and most often than not wont' be able to.

YES !!! I have done more of my share of reading. And please do NOT treat users with less than 10 posts like idiots.

*** The only solution is to change between Default Access modes. Going from grant, to prompt. Doing so for some strange reasons wakes up SuperSU***

The following solutions DO NOT WORK (meaning the problem resists)

1. Flash Antenna (regardless of which, even with the one provided by OP on their threads)

2. Flash insecure kernel zip

3. Download the version form Play and Update

Hope this help any of you that are experiencing some crazy frustrations like me.

*** Not to offend anyone, but the rule of 10 post or less = No reply/post on dev. forum is beyond me ***

*** I have tried to report my experience with certain ROMs, but Nooooooooooo.... <10 amigo ***

--- One more, since I think I am going be booted because of offending Seniors Party Members. ---

Can anyone tell me the logic of formatting a partition 3 times ??? I found this ridiculously offending being an engineer myself.

I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible.
[T-Mobile, Samsung Galaxy SIII] Perseus:
[MENTION=4062020]mrbackdoor[/MENTION]

Whoa Cool down Bro. Take a deep breath. Now tell me what precise are your problems ? I got the part with SuperSU making you go Ape. But what's with Roms and 10 Wipes ? I have no Idea what you are getting at.

So about SuperSU. If that app is making you go nuts, why don't you try SuperUser by [MENTION=1562806]ChainsDD[/MENTION] ? There's also a great Superuser app from CM team. But without knowing your Rom, I won't recommend it.

Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.

P.S. - Your Current Post Count is 1. I did respond right ?
[T-Mobile, Samsung Galaxy SIII] mrbackdoor:
LOL... thanks man. I am positively NOT HOT

what's with Roms

>>> TW 4.3 ATT leak on Tmobile LTElessS3

>>> I was just venting the fact that a member CAN NOT post on Development Forums because he/she has less than 10 posts.

>>> That's like filling 10 forms before you are able to download a file. Similar to registration process that just drive you nut.

>>> One engineering note is wiping a partition 3 times. The wipe process before installing a new ROM.

>>> I just don't get it... Why 3 ??? "insanity according to Albert Einstein"

Superuser..But without knowing your Rom, I won't recommend it.

>>>Superuser - NOT an option, not even working

Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.

>>> YES sir. Fully understood

P.S. - Your Current Post Count is 1. I did respond right ?

>>> call me up when you want a beer... or couple shots of the good sh****
[T-Mobile, Samsung Galaxy SIII] Perseus:
[MENTION=4062020]mrbackdoor[/MENTION]

I don't have the ATT S3 Let alone the leaked Rom so can't comment. I hate TouchWiz anyway. I don't want to comment on the rules. They are there for a reason. Yes they may be an irritant but they keep Noobs away. You my dear friend is a Newb. There's a difference.

Whoever asked you to wipe the same partition 3 times needs to get their head examined. But then I am jumping ahead without knowing full circumstances. So if you don't mind, show me the thread link.

Are you trying to get the Leaked ATT Rom with a working Root ?

Now you too sir, have been guilty as well. I need to have full problem statement, which I am sorry I have not got as yet. So can you kindly explain what precisely are you trying to do and where does SuperSU come into play ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ok, first, please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.

Yes, we want you to do as much on your own as you can. No, most of us do not consider a low post count an indicator of idiocy. We might, however, judge how much we want to help depending on the quality of your post, or any other OP by anyone. If you do your best to find your own answers, and post clearly and respectfully, it'll show.

And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!

So if you'd care to try starting over on a better note, here are my points regarding your issues.

There is no real benefit to formatting something more than once. This is something that apparently began with some old device where the recovery wouldn't always format correctly. So people got in the habit of wiping several times rather than the king after each time. They then spread out across xda and push this practice like gospel sometimes, even though it gives no benefit and imo shortens the life of the device. I have tried to point out to folks this is not necessary, but gave up long ago! To each his own.

Enewman found a bit of a workaround for the su issues. It's not perfect but does seem to help a little.

Find these files

/etc/install-recovery.sh

/etc/init.d/dameonsu (or similar named script)

Find this line

/system/xbin/daemonsu --auto-daemon &

Delete --auto

Reboot

Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.

But also keep in mind that it's a combo of things, you do also need the insecure kernel. And Knox is still gonna screw with it if it's not been removed.

Also, try to remember, all of this stuff is brand new to all of us. Do not expect miracles, it takes time to relearn everything for everyone. But if it's really that bad, then consider going back to an older Rom for now.

These are after all leaked builds and should not be expected to be fully functional and bug free.
[T-Mobile, Samsung Galaxy SIII] mrbackdoor:
Dr. and Perseus

To you both, thank you, thank you and thank you. It would have been more appropriate on the General thread. Anyhow:

Perseus

If needed, I can point you to the threads. You are kind. I do appreciate that.

Dr.

I think you know exactly what I was talking about. So to you I do apology if my post is offended. In fact, to anyone who do feel the same. My bad.

please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.

>>>No Sir, no way in any shapes or forms I do assume people are jerks. Like I stated before, I was just venting on the fact that the rule cripples members ability to contribute and alienates them as well.

And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!

>>> Understood. Complain is absolutely not my thing. If there is a way to monitor users' footprints, you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.

So if you'd care to try starting over on a better note, here are my points regarding your issues.

>>> Of course.

There is no real benefit to formatting something more than once.

>>> Got it. Now's that is at the core. That's exactly what I was looking for. Instead banging my head trying to understand how partitions are being formatted and the file system that is basically associated to the NIX for a long time . Basically what I posted is the workaround that I use for now.

Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.

>>> Correct.

But also keep in mind that it's a combo of things, you do also need the insecure kernel.

>>> Appreciate your time Dr.

Statement below is my initial love your developers. That has not changed. Just "kang" members that I do find .... well.... you got my drift.

"I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible."

Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.

Again, thanks.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Actually your join date of May '11 is the first thing I noticed. Pretty big time Reading on your part if you didn't ask before.

I am afraid we are still missing the problem you posted for aren't we ? Or what steps Doc suggested about the leak solved your problem ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I'm on the app most of the time, so I can't readily see post counts, join dates, junior/senior member status, etc. But anyway, thanks for the reply op. I lurked around the forums for about a year before my first post, reading and learning all I could, so I can appreciate that you seem to have done so as well!

I was slightly off earlier, when you find those files, change this:

/system/xbin/daemonsu --auto-daemon &

To this:

/system/xbin/daemonsu --daemon &

Had to go look it up again. Sorry bout that!

[MENTION=3639717]Perseus71[/MENTION]

I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.

If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.

Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.

The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.

And then there's Knox. If it's not removed it can also cause problems with root access.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Oh I see. Honestly on my 4.3.1 rom that I had, I never experienced this problem. Possible its related to the leaked Rom's implementation of SELINUX?
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers. The developers do they developing, and we do modifications to make things how we want them and hopefully others enjoy it too, that's all.

To OP, we're aware this SuperSU problem was annoying, we were one of the first few dealing with non-stop before bringing the leak from AT&T and debloating it over here.

enewman17 and his infinite knowledge did some poking around in the files and found a way to make root more persistent, albeit this is a leak, and we have Samsung KNOXing at our door. Things are bound to be broken, and especially because myself and others working on the leak are not professional Android developers nor do we ever claim to be, more like hobbyists who try to learn on their own by reading, or their own personal knowledge of NIX' and shell scripting.

Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder.
[T-Mobile, Samsung Galaxy SIII] mrbackdoor:
All

Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.

I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.

>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.

nor do we ever claim to be

>>> Nor did I

Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder

>>> I wouldn't doubt you. I've seen your work.

>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Glad to know we could be of assistance. Glad to clear that up with you. Feel free to post more, don't be such a lurker! :P
[JASJAR, XDA Exec, MDA Pro General] NullMind:
I received a letter nto logn ago, with some O2 info (my first bill) one of them was a number to cal and get special voices for your voicemail

I misplaced it ... anybdy knows what that number (or others) are ?
[Galaxy Note 3 Accessories] sweeney_uk:
I've recently bought these items for the car:

Suction Mount

http://www.ebay.co.uk/itm/231075692419

Car Charger

http://www.ebay.co.uk/itm/221275878538

USB 3.0 Cable

http://www.ebay.co.uk/itm/271214509031

Bluetooth Music Receiver

http://www.ebay.co.uk/itm/231013811746

I used them during my working day and was very pleased, the charger charged at about 4-5% per hour on sat nav using google maps and bluetooth streaming using deezer.

The cable is good quality and the bluetooth receiver sound quality is spot on, no breaks or anything.

All in all excellent results from £20 worth of kit :D
[Nexus 5 Q&A, Help & Troubleshooting] Johmama:
Hey guys, I searched multiple times and couldn't find anything on this. Do we know what the internal codenames for the Nexus 5 and the respective factory image are? For example, the Nexus 4 is 'mako,' with an image called 'occam,' the Nexus 7 2013 Wifi is 'flo,' with an image called 'razor,' etc.

It's kind of confusing because on the factory images page, they call the image 'hammerhead,' but when I look on the AOSP site, they seem to call the Nexus 5 'hammerhead.' Anyone know what's up? Sorry if it's a stupid question, the Google-box on my Internet-machine isn't telling me what I want it to tell me. :laugh:
[Nexus 5 Q&A, Help & Troubleshooting] tulongest:
Just found out about it now.

The image name is called 'hammerhead' 'hammerhead' as for the internal device name, it's probably somewhere there in the web but I can't find it yet. I'll edit this post again when I do.
[Nexus 5 Q&A, Help & Troubleshooting] .ax:
Hey, I was just looking for this and came across the Google Dev Listing.

Hope this helps : https://developers.google.com/android/nexus/images

:victory:
[Galaxy S 4 General] alferret:
Guess I just have been sleeping....

Downloading now, will post details when finished.

Sent from my Nexus 7
[Galaxy S 4 General] oxfordmark:
Old news!
[Galaxy S 4 General] alferret:
Must have missed the news flash!

Sent from my Nexus 7
[Sprint HTC One (M7)] ChaOtixForce:
I've wiped my filesystem but I have absolutely no idea what to do now. I need to use my phone again ASAP, so any help would be appreciated.
[Sprint HTC One (M7)] tonyrance:
Have you gotten any help yet?
[Sprint HTC One (M7)] flomexico:
Reflash recovery, sideload ROM.
[Sony Xperia P, U, Sola, Go] shtresatu:
Check this out. I am just sharing what I've found. Works on xperia p jb

http://repo.xposed.info/module/com.wedy.semcphone2