yashsingh1/xdaforums huggingface dataset:
[Android] paultje162:
I would also really like a build. The stock rom has some crashes and is not that stable.

Verstuurd vanaf mijn SM-N9005 met Tapatalk
[Android] joniee:
i realy need help with 3G or wcdma, beacuse phone is set to wcdma prefered but it always work on 2G and if i scan for networks he can find me only 2G network.

i have try with all custom roms and stock roms but is all the same problem
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] linuxpeppermint:
I installed CyanogenMod 7.2 on my Samsung Galaxy Y GT-S5360 (this one: http://xdaforums.com/showthread.php?t=2537457).

When I first installed it, I also installed Gapps. However, as I do not want to use Gapps anymore (like Gmail, GMaps, Googlesearch etc.), I want to get rid of them - but I am unable to do so.

I did a complete wipe in the Clockwork Recovery, meaning: wiped cache, wiped, wiped batt stats, formated sytem, data and cache and did factory reset. After that, I reinstalled CyanogenMod 7.2 again, this time without installing Gapps.... BUT: Gapps are nevertheless included.

What did I do wrong? How can I can a Cynanogenmod now on my Galaxy Y GT-S5360 without Gapps?

(Forgive me if I used wrong terminology etc., as I a new to this. I did, however, spent a lot of time searching this forum and others to find a solution before I came bothering you with my question. Thanks in advance!)
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
if you look at the features of that rom it says gapps are included so I dont know why you flashed it seperatly

anyway

if you want to remove any system apps install link2sd from the playstore then you can use it to uninstall any system app you want
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] linuxpeppermint:
Thanks for your answer. I just realized that Gapps are already included. As I am new, I used another, more detailled, step-by-step guide, which used the Percy Rom (with the above link), in that guide, I was told to separately install Gapps... :silly: Thanks for the other hint, too. :good:
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] GSculerlor:
Try to uninstall it after you flash CM 7.2 :o
[Sony Xperia T, TL, TX, V] loolser:
Recently when I try install flash player on my xperia t 4.4.2 omni rom I had problem cuz I coudnt play videos, streams, so I had to explore xda n tada, found thread http://xdaforums.com/showthread.php?t=2548001 unfortunately this wont work on stock browser, but on delphin works really good, didnt try in firefox n others reply here if u try n confirm that works thanks:good:
[About XDA developers] gavapps:
Hello everybody,

I want to present a labyrinth game.

You are a mouse and you have to find the cheese in these complicated mazes which are filled with all kinds of traps.

I offer you an ingenious riddle to aid you in your quest to navigate the harsh mistress that is the Internet, in order to find our Facebook page; any information you need about this game can be found there.

x = https://

website = facebook

suffix = /pages/The-Mouse-Labyrinth/459901347388323

result = x + "www" + "." + website + "." + "com" + suffix

Hint: "+" represents a string concatenation operation
[Xperia SP General] samarth05:
PLEASE NOTE THAT I HAVEN'T CREATED THIS SOFTWARE. I AM JUST SHARING IT.

I REQUEST YOU DON'T CLOSE THE THREAD PLEASE.

Hello Everybody,

I am just sharing this app for rooting any Android...

It works for my Sony Xperia SP even without flashing with DoomLord's Method.

But The Only Problem of this Application is that it's in chinese:(

The Superuser which comes after rooting is also in Chinese but it will 100% root your phone

Please make a backup of your nandroid before using it..

I will not be responsible for any bricking, I have tested the software myself and currently using it. If your device is bricked and you pointed on me, I will laugh at you.

READ THE STEPS CAREFULLY..

Steps :

1. Extract the .rar file and install the software (I know it's chinese but please try to Understand:mad:)

2. Make sure your Internet Connection is ON and star the Software.

3. Turn on USB Debugging and Unknown Resources from your phone.

4. Connect your phone to your PC and If the PC Companion is troubling you, then close it.

5. Then it will take some time to install drivers automatically and when the bottom right button of the software turns grey to Green, click on it.

6. It will take some time so be patient.

7. Then after some time your phone will restart. (It may take some time to start, dont worry)

8. Then check the superuser app (Blue Shield Icon) and grant the permissions (if asked).

9. Your Phone is Successfully ROOTED!! :):D

Steps for Unrooting your phone:

1. Turn on USB Debugging and Unknown Resources from your phone.

2. Connect your phone to your PC.

3. Start The VRoot Software.

4. It will detect the phone a another window will come.

5. Click on the Green Tab Button located at the bottom right of the window.

6. Then Your Phone will restart.

7. You have successfully Unrooted your phone.;)

CHECK WITH ROOT CHECKER IF YOU HAVE ROOTED OR UNROOTED.

DOWNLOAD LINK :- MOD EDIT: link removed

IT ALSO WORKS FOR MANY TABLETS AND PHONES..

ALL THE BEST!!..

PLEASE MODERATORS I BEG YOU DON'T CLOSE THIS THREAD..
[Xperia SP General] mrjraider:
The other thread have been closed due to security issues and XDA want to do some research about these apps to root our and many others.

However this was a month ago? And we have no answer what so ever.

I kindly ask you to remove the OP because it will be closed by one of the mods.
[Xperia SP General] samarth05:
OK Please [MENTION=4715675]mrjraider[/MENTION] you by yourself close the thread. Cause I can't do it myself...

THE THREAD IS CLOSED...
[Xperia SP General] noahvt:
The fact that this is an executable application is making me think it's fake most root creators like [MENTION=2784807]DooMLoRD[/MENTION] use a batch file for rooting this executable is perfect for hiding malicious apk's
[Xperia SP General] Cloud1989:
I rooted my device via this option, but my phone decided to randomly reboot every now and then, so had to go back to stock and root via doomlords method, No problems for me now

But yea this thread/links need to be removed as its not 100% safe to use this method
[Xperia SP General] Toledo_JAB:
If you don't know what the software does then please do not share it.

This software has been shown to record imei numbers and send them to a remote server.

As of receiving this from Kingo

Kingo is now allowed.

You can try that.

We have had no contact form vroot.

Thread closed
[Sony Xperia P, U, Sola, Go] bharathbondfire:
Here i Presnt u Guys the modded UI For

XNovathor Project 4.1.2 rom

Works only with this rom

Just replace the file in system/app

1.UI with White status bar

View attachment 2541994

View attachment 2542005

2.UI with Dark edition

View attachment 2541993

View attachment 2541995

View attachment 2542004
[HTC Sensation] zodi79:
installed newest

(date 27.1.2014 with GAPPS modular mini from: http://xdaforums.com/showthread.php?t=2530073)

did full wipe (factory reset, system, cache) as in info

have some major problems with stability, looks like system degrades quickly after leaving screen off mode

After restart I can set up everything fine, can use network, launch apps, change system settings etc

but after first turning off and turning on lock screen starts to show first problems, dots (I'm using pattern unlock) sometimes start to activate on their own, not always but sometimes this happens, but I'm still able to logon...

after second 'screen off' and 'screen on' I'm having big problems trying to unlock screen - sometime dot's don't react to touches, sometimes they do not end connecting after taking away finger from screen...

after third off/on I'm unable to pass unlock screen - it becomes unresponsive, dots start to connect randomly, sometime even 'emergency calls' gets activated...

what can cause this? full phone restart appears to fix problems for short time, but after few off/on have problems agains...

this did not happen in builds from few months ago

tried to set higher min cpu frequency to 384MHz but that doesn't help

other things that I chaged are:

- cpu governor -> badass

- i/o -> noop

- active 'allow purging of assets'

anyone got ideas what could cause this? and how to fix

phone:

htc sensation xe, unlocked

hboot 1.29, radio 11.24a.3504.31_m

can provide other info if needed
[HTC Sensation] nlooooo:
It's easy to be fixed, install stock rom.
[HTC Sensation] zodi79:
thank you, very helpful
[HTC Sensation] Sajito:
What firmware are you on? Did you experience any of these problems on any other rom?

You say the dots connect themselves. As if the touchscreen is used? Sounds somehow like a broken digitizer.
[HTC Sensation] nlooooo:
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?

When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.
[HTC Sensation] Sajito:
I must have missed all of these threads. There were some threads about cm11 but they had other issues.
[HTC Sensation] Sultanxda:
This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
[HTC Sensation] zodi79:
ok, will try

atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before

and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.
[HTC Sensation] Sultanxda:
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.
[HTC Sensation] zodi79:
first of all - sorry for misinformation but I found cause of my problems with interface... looks like minimal amount of water must have got under the cover when I few days ago applied new screen protection, yesterday I got this idea of what could cause this sudden problems... few hours phone stayed on the room heater (not too hot ofc) and touch screen problems are gone! yeah, tbh I love this phone and was very angry thinking I'd have to replace it, now I don't have to ;)

back to rom - atm back to your (sultan) rom based on CM 11 with update from 29.1.2014, it has some small problems but I like to test new features

problems I've found so far:

- less responsive and smooth

- launcher3 doesn't allow to create new home screens on the left, had to create new to the right then make some rearangments before I got things right

- some widget resize problems under launcher3

- other small problems all I can live with ;)

but I like more available memory and better battery life, going to test ART soon

and it is good that messanging is back, hangouts is just... not for me
[HTC Sensation] almedin85:
Why cant i find my phone contacts on SIM ??? Its say no contacts found? When i import some numbers from vCard from SD why cant i move them to SIM???
[HTC Sensation] romadd:
cm10.2 - cm11

funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...

Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.
[HTC Sensation] Sultanxda:
I tested it for 3 hours and it was working well :confused:
[HTC Sensation] romadd:
I had fresh install, but configured cpu clock speed 1674 mhz (maybe the problem ?)

And i had the same symptom describe by Firehawk989 http://xdaforums.com/showpost.php?p=49938883&postcount=3341

Any way i run already with your CM11 and it seem more stable for me except a little problem

http://xdaforums.com/showpost.php?p=49353701&postcount=1

This is another story
[Galaxy Note 3 Q&A, Help & Troubleshooting] natious:
Long story shot.

Flashed KK Bootloader, success, flashed x-note 8, phone was in a boot loop.

Waited over 10mins, so definately boot loop and not a slow boot.

tried everything, so decided to flash the stock KK via odin to see where that gets me.

Everything in Odin is setup correct, though when I added all the files to flash the stock rom I get.

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Set PIT file..

<ID:0/005> DO NOT TURN OFF TARGET!!

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

????

However I can flash the bootloader on its on and CWM, now when I try and flash a KK rom (Sweet, xnote etc...) I am now stuck at the Note 3 screen before the boot animation.

Any ideas on what I can try?

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] natious:
Everything is working now via the method found in this thread

http://xdaforums.com/showthread.php?t=2616103

I do have a HK note.
[Galaxy Note 3 Developer Discussion [Developers Onl] Da_G:
Hi guys!

I've been a bit busy in life for my first two months or so of owning the Galaxy Note 3 SM-900A. But finally I've run into a bit of a block of time, so I'm hoping to get some bootloader work done. I've already been studying it for a day or two, and am ready to begin some modifications in attempt to disable Knox/Signature verification/etc. But unfortunately I was broken into a few months back, and all my specialty hardware related to brick recovery is stolen (JTAG, etc.) - so I need some help from anyone who has a nice cozy return policy/warranty/replacement system available to them, who can risk rendering the device into a total brick (perhaps not bootable by any known method other than JTAG)

If you can help me out, please PM, I will get back to you soon regarding contact methods etc. - I am used to using an IRC channel on irc.freenode.net where #xda-devs lives, but perhaps we could use a more up-to-date collaboration method also.

Again, we will make every effort to do incremental testing that runs as much a minimal risk of brick as possible, but with such things there are no guarantees. Be ready and absolutely willing for a brick if you want to help. Thanks :)
[Galaxy Note 3 Developer Discussion [Developers Onl] TheDriller:
Done and done. I'm ready to crack this thing :thumbup: let's do this.

Sent from my SM-N900A
[Galaxy Note 3 Developer Discussion [Developers Onl] Da_G:
Has anyone attempted patching of the SBL? Simple one-byte patches of code there or to the Kernel? Does the signature verification catch these, obviously full image verification is only done at flash-time on the various open partitions as they are modifiable freely without tripping Knox/etc. Hard to find any public-facing info on if anyone has done work on it yet, trying to get a feel before I start so I don't duplicate work.

Also, in poking around, Carrier IQ seems active on the AT&T Build. Surprised more people aren't up in arms over this given it's previous reception :)
[Galaxy Note 3 Developer Discussion [Developers Onl] Walter.White:
I think you should talk to [MENTION=766721]ryanbg[/MENTION] and [MENTION=4939386]Surge1223[/MENTION] They have done lots of research regarding this Knox/BL and have made some pretty good progress.

I personally think that doing that will make sig check fail and the Knox flag would trip 0x0 and it won't boot.

P.S. No matter what you do don't flash over RPM because that will definitely hard brick your device. (No SD Odin mode either).

http://xdaforums.com/showthread.php?t=2476353

Also please keep this thread clean because most of this kinda threads get closed down before because of flame wars.
[Galaxy Note 3 Developer Discussion [Developers Onl] gordec:
DA_G is pretty reliable with good reputation. He can play dirty and get away with it just a little more.
[Galaxy Note 3 Developer Discussion [Developers Onl] ryanbg:
Message me
[Galaxy Note 3 Developer Discussion [Developers Onl] Da_G:
Hi Ryan, I surely am interested in looking at the SBL source also. Is it a generic platform source or specific to the AT&T variant?

PM sent. :)
[Galaxy Note 3 Developer Discussion [Developers Onl] tazman171:
Hey Da_G! Just got the AT&T Note III myself, dropped my G-Note and broke it, but don't have any of the hardware needed to do what you are doing. Will be following this thread though and great hearing from you again. :cool:
[Galaxy Note 3 Developer Discussion [Developers Onl] Da_G:
I don't have any of the hardare needed anymore either. Flying blind :)

And I just missed a byte flashing to aboot, bam, hard brick. Lets see if i can recover :)
[Galaxy Note 3 Developer Discussion [Developers Onl] Da_G:
SD Card restore worked wonderfully. http://xdaforums.com/showthread.php?t=2476353

Had made a 500mb image beforehand, wrote it to SD, booted from it, then flashed previously-dumped aboot back, fixed right up.
[Galaxy Note 3 Developer Discussion [Developers Onl] radicalisto:
Nice, I managed to hard brick testing N900w8 bootloader on my N9005, Reason I was playing around is the N900w8 has the capability of downgrading from 4.4.2 NA2 to 4.3 and rooting via CF-Autoroot without tripping KNOX and upgrading/downgrading again with zero issues. - I flatlined straight out :(
[Galaxy Note 3 Developer Discussion [Developers Onl] xclub_101:
For the research involved here it might be interesting to test IF the boot restrictions applied when booting from internal flash are still applied when booting from the external microSD - so for instance if you are on MJ7 bootloader now and you brick it you might want to first test is you can unbrick with a recovery image made from the older MI7 bootloader! (those are versions on N9005 but you should get the idea since most Note3 versions have gone through at least 2 bootloaders so far).

A few other things that I would like to contribute:

- the check on the very, very first bootloader is apparently weaker than any other security check after that - as far as I remember that one might be "fooled" by updating a 32-bit hash, which could be brute-force attacked in a decent time; everything after that initial step is on the same level as a brute-force attack on RSA (128 or 256, I do not remember);

- it might be interesting to also take a look at the trusted zone code (everything secure is pretty much done from there) and eventually find a way to dump the content of the qfuses (that might be needed in order to brute-force things later)

- it might be interesting to also look at the bootloader differences in the N9005W8 version - we already know that some of the keys involved in that case are controlled by somebody else than Samsung (Telcel)

- regarding debricking by booting from external SD - I now see that some/most Qualcomm models seem to NOT need any extra hardware signal, but Exynos models almost certainly do - search after 13-58_SM-N900_Boot_Recovery_Guide_rev1.0.pdf and you will see the official internal Samsung document on that (there is a similar one on the i9300)

- another interesting interesting document that might be worth reading in the context of knox and all SWREVs is called (13-74) Galaxy Note3 Unlocking for Reactivation Lock Guide Rev 5 0.pdf - but IMHO this is of less interest right now.
[Galaxy Note 3 Developer Discussion [Developers Onl] KennyG123:
Thread cleaned

Reminder this is a Developers Only Discussion section

Take questions to your device Q&A section
[Galaxy Note 3 Developer Discussion [Developers Onl] Cobaltikus:
KNOX WARRANTY VOID: 0x0

Referencing ODIN files here: http://xdaforums.com/note-3-att/general/n900aucucnc2-odin-files-t2838117

In BL_N900AUCUCNC2

aboot.mbn (mmcblk0p6)

Address 0005F6E4 = "KNOX WARRANTY VOID: 0x%x"

So my question is: What if I just change that string to "KNOX WARRANTY VOID: 0x0"?

I know it's probably not going to work, but why not?

I would just go ahead and try it but I'm not ready to brick my device just yet.

....

Ok so I tried that and see that the auth failed in Odin 3.09 because the altered aboot.mdn within the BL tar causes a different md5 / different SHA1 hash, which is encrypted with RSA using the a public key which I believe is in the boot image, and I guess whatever is validating this has the private key so it can decrypt the encrypted md5 and compare it to the real md5. So if I want to edit aboot, I need to then encrypt the new md5 using the same public key... but then what would I do with that. I'm missing something. I'll get it. More reading...

On a good note, this did not flip the knox flag, nor did it brick my phone, so all is ok for now.
[Galaxy Note 3 Developer Discussion [Developers Onl] benwaffle:
I think the files are signed with Samsung's private key (which we obviously don't have) and verified with their public key (likely in boot.img). So, no, you can't sign the modified boot image since you don't have the private key.
[Galaxy Note 3 Developer Discussion [Developers Onl] Cobaltikus:
From what I know about rsa, the public key can only encrypt, and the private key can encrypt and decrypt. I don't know if that is the case here, but I'm guessing it is for now. Either way, "can't" is too strong a word for me. All encryption is crackable. I'm reversing the boot image and will figure it out eventually. The only two things that could possibly stop me are death, and someone else beating me to it.
[Galaxy Note 3 Developer Discussion [Developers Onl] ryanbg:
It's not encryption (well, sort of), but a signature. It's a 256 byte chunk of an 'encrypted' PKCS#1.5 padding and the SHA256 of the image (like aboot, or boot.img.) The private key does this 'encryption' and signing of the image hash, and the public key can simply verify/decrypt this signature to compare it with what it derives. If it matches, it returns 0 and continues to flash/boot/etc... If return =1 it will fail and boot/flash will be denied (like your Auth: fail in Odin.)
[Galaxy Note 3 Developer Discussion [Developers Onl] Cobaltikus:
Thank you ryanbg! This information is truly helpful!
[Galaxy Note 3 Developer Discussion [Developers Onl] Cobaltikus:
Does anyone know the address of the function which validates the signature? I've been looking at the NC2 binaries, but a more recent version would be just as helpful.
[Galaxy Note 3 Developer Discussion [Developers Onl] Cobaltikus:
Consider the following assembly in aboot.mbn

If you were to run the aboot.mbn file, executing each instruction, following each branch, you would end up here

0x0F810A5C 00 50 93 E5 LDR R5, [R3] (Loading value 0x0 from memory at 0xFC4CF808)
0x0F810A60 00 00 55 E3 CMP R5, #0x0 (0x0)
0x0F810A64 FC FF FF 0A BEQ loc_F810A5C

This is an infinite loop, continually loading 4 bytes from the address 0xFC4CF808, and looping for as long as these bytes are all zeros.

What is it waiting for?

Once the value is not zero, it checks to see if it is 1. If it is not 1, it references the string "SPMI write command failure: cmd_id = %u, error = %u"

So what is SPMI? Apparently it is something that writes a 1 to the address FC4CF808 upon success.

Digging deeper. Feel free to help if you can if you want.

Ah ha! https://android.googlesource.com/kernel/lk/+/qcom-dima-8x74-fixes/platform/msm_shared/spmi.c
[8125, K-JAM, P4300, MDA Vario General] Fork:
Unlike some, I actually LIKE the battery icon that's displayed at the top-right of the screen in the new ROM's. Unfortunately, after running the Registry Wizard it's removed it and left an empty space.

What egistry key will actually RESTORE the battery icon? I've tried searching the forum but the Search engine is producing errors at the moment.

Thanks,
[8125, K-JAM, P4300, MDA Vario General] meschle:
With registry wizard - by default under the Taskbar date/time settings it is none - try setting it to clock and the battery should reappear ;)

More info in nicodekker's orginal post below

below

below
[8125, K-JAM, P4300, MDA Vario General] Fork:
No, unfortunately unticking the box just leaves an empty space still.

Any other suggestions?