yashsingh1/xdaforums huggingface dataset:
[Sony Xperia ZL] sturmtruppler:
I'm using Illumination Bar Notification from playstore. You can adjust colours and brightness, but I don't think you can make the light brighter with this app.
[Sony Xperia ZL] rick196600:
Hi yes Im also using Illumination Bar Notification and yes your correct in saying there's no option to adjust the led brightness.
[Verizon Samsung Galaxy S 4] mindlogiczero:
i just flashed a stock rom/unrooted my phone, but now im unable to update latest update from verizon. ive tried threw my phone which says error while installing, and threw my computer using verizon upgrade assistant without any luck
[Verizon Samsung Galaxy S 4] matt1733:
try using odin and flashing back to stock with the tar file from there you should be able to download the update.
[Verizon Samsung Galaxy S 4] mindlogiczero:
that is how i unrooted, was by flashing the stock tar in odin, everythings back to 100% stock besides the phone letting me update it
[Verizon Samsung Galaxy S 4] camden07:
i wouldnt

i wouldn't update because unfortunately like myself and others update causes you to loose your root,and rooting capabilities and locks the boot-loader. If you want the new baseband there is a link in development forum to flash via odin just baseband not the hole firmware. just my opinion tho.
[Verizon Samsung Galaxy S 4] mindlogiczero:
i dont want to be rooted, i just want to be 100% stock again.
[Verizon Samsung Galaxy S 4] nuttsp:
I am trying to do the same thing. I flashed back to stock using "VRUAMDK_NoWipe.tar.md5",it successfully flashed and it was unrooted. I then factory reset the phone. When I try to do the update (over the air) it says update failed.

My phone has a broken proximity sensor and I have to return it. I want it back to stock before I do. My thought is that it is not stock if it won't take the update.
[General Questions and Answers] j2000:
I have a Socblue A860, problem can not connect to any Android, except to the Samsung Galaxy Note 2, but the Note 2 sold.

I have checked into few website the info about socblue still very little.

Socblue that already pairing and connect with socblue program can not connect to another Android, we must UNBIND it first from 1st phone, before rePairing to other one

After unbind, Socblue can pairing to another Android or iPhone, because the MAC address binding Socblue bluetooth device connected to the previous.

I see the link on socbue forum, then I see unbind "link software".

Unbind programs in http://apt.fise.com.cn/db

http://en.socblue.com/_d275413864.htm?c=999

But the link above is dead...

I am confused with Socblue website, why they don't put the program publicly, eg posted on Support page or Download page.

Why Web Manufacturing Socblue so carelessly?

i also post on youtube http://www.youtube.com/watch?v=gC2bjcnXFoc

-----------

Question:

Did anybody have Unbind program ?

I need you share it...

Regards

Joel
[Galaxy S III Q&A, Help & Troubleshooting] morganflame:
Hello guys, Sorry for posting a new thread, I understand it's unwelcome, but I've been looking around for a bit now and can't seem to find a solution to my problem.

So what's happening is that a while ago I rooted my device and installed Jellybam 7.2 something... Recently, I wanted to update Jelly Bam to the latest version and so I downloaded it using ROM manager and lauched the install from the recovery mod.

Problem is that now, my phone doesn't start anymore, it turn's on, the Samsung Galaxy stuff appears on the screen and stays there, nothing else is coming. Been like that for hours.

So if anyone can direct me to a solution to recover my phone in a working state, that would be awesome.

I tried to recover backups but didn't work

I tried to swipe all data and cache and to do a factory reset, nothing worked, I'm running out of ideas. Please someone.

Peace to you all

Morgan
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
Common solution is to flash the stock rom via odin on your pc, plenty on guides how to do in the stickies.

Also, questions should be posted in q&a forum, you can request a moderator move it for you.
[Galaxy S III Q&A, Help & Troubleshooting] Simonna:
If you can't get into recovery or download mode it can probably be Sudden death syndrome.
[Galaxy S III Q&A, Help & Troubleshooting] laura almeida:
I think u have flashed a wrong version.

I have heard multiple people saying that they have stuck at Samsung logo after flashing a wrong file.

Are you sure that you have flashed a I9300 version ?
[Galaxy S III Q&A, Help & Troubleshooting] morganflame:
Thanks to all

Hey guys, thanks so much for your answers. I'm pretty sure I've downloaded the version for my I9300 as I got careful with that detail while rooting, flashing etc... Though, my version of Jelly BAM was the 7.2 something and the new one 9.something... maybe the upgrade was not possible from mine to the new one... Flashing the stock version seems to me to be the way to go. I'm gonna try that and let you know if it worked.

Sorry for misplacing the question, how do I request a moderator to move it ?

Peace y'all! ;)
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
FIFY ;)
[Galaxy S III Q&A, Help & Troubleshooting] morganflame:
Stuck in the process.

Hey everybody, so I've started to work on flashing the stock rom on my s3 i9300 and I'm following the tutorial located here

androidrootz.com/2013/06/how-to-unroot-galaxy-s3-on-mac-osx.html

I have a problem now, the step 10 of the tutorial tells me to locate aboot in Heimdall's flash tab after locating the pit file from my phone that I saved in step 5.

10. Click on "Add" and select "ABOOT". Then click on "Browse" and locate "aboot.mbn". It is the folder that was renamed and untarred. Then click "Add" and do the process again for the all files in the folder (watch the video above for detailed instructions).

aboot.mbn --- ABOOT

boot.img --- BOOT

cache.img.ext4 --- CACHE

NON-HLOS.bin --- MODEM

recovery.img --- RECOVERY

rpm.mbn --- RPM

sbl2.mbn --- SLB2

sbl3.mbn --- SLB3

system.img.ext4 --- SYSTEM

tz.mbn --- TZ

Problem is that I can't see anything called ABOOT in the scroller it should be in. Even weirder, the tar file I got from the stock rom I downloaded doesn't contain that "aboot.mdn" the tutorial is talking about.

Anyone knows about that ?

Thanks a lot
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Not sure. You may need to add "Heimdall aboot?" to your thread title to get a more targeted response now as the scope of your original issue has changed. Now you need heimdall support.

Or maybe create a new thread with this new issue?
[Galaxy S III Q&A, Help & Troubleshooting] morganflame:
Ok

Ok, I will do that. Thanks
[Galaxy S III Q&A, Help & Troubleshooting] morganflame:
No answer

Hey guys,

I posted a new Thread with a better title here http://xdaforums.com/showthread.php?t=2379894 but I got no answer whatsoever. When I make a google search about my problem, the first result is actually my own thread so I don't know if anybody got the same problem before. Can any of you tell me where I should look for help conscerning Heimdall and my particular problem.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
where I should look for help conscerning Heimdall

Google >>> heimdall xda

or just search XDA .

jje
[Galaxy S III Q&A, Help & Troubleshooting] boldface123:
Hi. Maybe you can try to flash IT with oder in a win PC. Maybe one of your friends does own one. Since there is obviously no one Who can help you Witherspoon flashing with heimdall.

Gesendet von meinem GT-I9300 mit Tapatalk HD

---------- Post added at 01:16 PM ---------- Previous post was at 01:11 PM ----------

Gesendet von meinem GT-I9300 mit Tapatalk HD
[Galaxy S III Q&A, Help & Troubleshooting] smohanv:
Hi

I use to mod SystemUI.apk and Framework-res.apk to hide notification bar it worked on 4.1.2. After flashed I9300XXUFME7 I could not mod these files. Using apktool I am able to decompile but after the changes when i am trying to compile it shows error.

I am using deodexed ROM (omega 46.1).

Can anyone please help how to fix this.

Thanks in advance.
[JAM, MDA Compact, S100 General] gentelman:
hello,

has anyone some infos about the maximum bitrate that's possible with the magician over bluetooth?

i want to stream mp3 songs from my mdac to an bluetoothmp3-module. but i have no luck, in my tests it looks like the magician provide only <=115200bit/s on OUTGOING connections (it's the same for obex-profile and serial-port-profile) and that's not enough for a "normal" 128kbit mp3-song.

but when i send a message TO the mdac i get a bitrate that's about 230400bit/s . can anybody explain me that?

has anybody an idea how to push the performance for the upstreams like that of the downstreams?

thank's
[General Questions and Answers] Raghavendra Karanth:
I get an error "The device has either stopped responding or has been disconnected" when I try to transfer files from my PC to phone. I use MIUI v5 on Micromax A110. can i get mass storage option activated instead of MTP? or is there an alternative.

I am sorry i don't know to which for i should post this and hence have posted in general

Thanks for the help.
[General Questions and Answers] niravjadatiya:
you should download usb swithcer from play store

download this and restart your phone:good:

play. google .com /store / apps /details ?id= in.zatta.USB_switch&hl=en

remove space from this link and dwnld
[General Questions and Answers] guiller711:
not found why not tell the name of the app instead
[One (M7) Q&A, Help & Troubleshooting] pipehippy:
Is there a setting somewhere that allows you to use the green illuminated call (button?) that is in the same place as the end call button which does work? I find the thumb stretch it takes to initiate the call by pressing the photo a nuisance.
[Asus Transformer TF700] bark00000:
i have a rooted/unlocked TF700t

TWRP 2.2.2.1 installed

alright, so i wanted to do a factory reset (through android, not twrp) but every time i tried it would boot me into TWRP and not actually do anything.

at some point i did all the wipe options in TWRP and even did the wipe option in recovery menu (pwr+voldown)

now i have no idea what happened.

I cannot boot up my pad at all. it immediately goes from the asus splash into TWRP every single time.

recovery mode (power+voldown) does not work at all. nothing comes up. just straight to TWRP.

I cannot install anything. an error with /cache and kills the install every time

I can only mount /system. the rest do not check for me (sdcard,data,cache are my only other options to mount)

I cannot even adb/fastboot. just says "waiting for device" and the list of connected devices is empty (however my pc does detect an adb device under the device manager when i plug in)

I have ZERO access to anything other than TWRP.

I am really on my last legs here
[Asus Transformer TF700] _that:
You bricked your tablet - TWRP 2.2 is ancient and not compatible with current bootloaders.

There is hope - if you can get access to TWRP via adb shell, it should be possible to recover.

Edit: Read this thread: http://xdaforums.com/showthread.php?t=2291974

I hope you didn't successfully wipe your Android system, otherwise it may be hard or impossible to fix this. The first step is to determine if you even have access to your storage from the recovery. If not, read post #14 in that thread (the related instructions are in post #10) and see if you can get to the bootloader menu and use fastboot or cold boot Android.
[Asus Transformer TF700] sbdags:
As said due to you being on a very old version of twrp there's a possibility you have bricked it. :( Try _that's suggestion and let us know.
[Asus Transformer TF700] graphdarnell:
[/COLOR]

I'm in the same boat as the OP. Did try bootit.ko and the tab did boot to Android. Ran into the same problem as the person in the thread referred to above with the CWM recovery. Mine reported

loop1

loop2

loop3

loop4

loop5

loop6

loop7

mmcblk0

Did try hex dump as instructed in the thread but returned nothing. What should I do, if anything? Help, please.

Note: As there was _that's question about access to internal storage from TWRP recovery, I've enclosed a thumb for perusal.
[Asus Transformer TF700] _that:
If your Android is rooted, this can be fixed:

Boot Android, and in Terminal or via adb shell, run the following commands:

su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1

This should break the forced reboot to recovery, and it will enable the boot menu and normal booting to Android again.

Your picture only shows the contents of the recovery's ramdisk but not anything from the internal storage - you'd have to navigate to /dev/block and see if mmcblk0p1 to mmcblk0p8 appear there.
[Asus Transformer TF700] graphdarnell:
Su command returns "not found" though superuser was installed before. Su binaries are not found in /system/bin/sh, and I can't find a way to root it now since twrp doesn't see the zip from where it is. Is there a way to copy the zip anywhere in internal storage to permit twrp to access it, or a rooting method from inside android? I tried chainfire su with the same result - no su binaries installed.

/dev/block shows mmc0blck0p3. That's it. However, running ls /dev/block shows as captured in the enclosed thumb.
[Asus Transformer TF700] _that:
OK, that means it is not rooted. Which Android version is that? Stock? If it's build 10.6.1.14.8 or earlier, it can be rooted with Motochopper.
[Asus Transformer TF700] graphdarnell:
Thanks a million, it resurrected my tab. You're the devil!
[Asus Transformer TF700] graphdarnell:
A question of purely academic (or un-academic) at this point. So if you have custom recoveries installed, you'd have access to ADB on the intial screen, but not when the tab's on official recovery? Even if you have custom recoveries installed and you cannot access it - as when volume down + power or any other jump-start method would still take you to the booting process that wouldn't complete - you'd still have access to ADB or fastboot or not?
[Asus Transformer TF700] _that:
The fastboot protocol is implemented by the bootloader and is available while the bootloader menu is shown (or after selecting "USB" in old bootloaders that had that icon).

The adb protocol is implemented by the adbd program (adb daemon), which requires at least a running Linux kernel, a running Android init, and a configuration that starts adbd. The stock recovery doesn't start adbd, but both known custom recoveries (TWRP and CWM) do. Android starts adbd if "USB debugging" is enabled in Settings.
[Asus Transformer TF700] graphdarnell:
If I strike you as an ignoramus, that's because I'm one when it comes to this type of software setup. I know a bit more about hardware than soft. But to clarify, when you have a tab that's stuck in the initial screen (Asus logo with "device unlocked") without more - commonly referred to as being "bricked" - like so many with a TF300 who effected OTA updates that never finished, the bootloader was then gone and there was absolutely no way to rewrite it unless you have NVflash files generated prior?

The difference in our case at hand is what? Here we still have the bootloader that doesn't show because of that glitch that triggered booting straight into the custom recovery instead? And your instructions break the cycle?

Last but not least, thank you again for taking the time to respond. If this involves too much technical stuff for someone like me, please ignore. :D
[Asus Transformer TF700] _that:
I don't know the situation on the TF300 and why they have 3 different and incompatible bootloader/recovery combinations. I also don't know what "Unrecoverable bootloader error" means (other than "you're screwed").

Correct. The bootloader has a nasty "feature" that if the misc partition (mmcblk0p3) contains the command to boot to recovery, there is no way to activate fastboot. With some version of the bootloader they changed something so that older kernels - like those in older recoveries - can no longer access the internal eMMC storage (error -110), so there is no way to clear that command in the misc partition from the recovery.

In this situation there are only 2 possible ways to recover: NVflash (with wheelie and the matching blob for your device), or a rooted Android system and some way to boot it. Not aware of "adb reboot bootloader" at that time I wrote a loadable kernel module for someone else a while ago, but today it was confirmed that apparently the module works better than adb reboot bootloader: http://xdaforums.com/showthread.php?t=2528313

Don't hesistate to ask if you want to know more.

Recommended precautions on Asus tablets with a custom recovery:

* Know your bootloader version.

* Read XDA and always use a recovery compatible with your bootloader version.

* Make blobs for nvflash and the recommended backups *before* you brick your device.

Avoiding writing the "reboot to recovery" command to misc:

* Don't use "reboot to recovery" features a custom ROM or recovery installer might offer, especially after flashing a new version of the recovery - always always start it the via power/volume button combination at least for the first time to test if it works.

* Avoid "Wipe data" in the bootloader menu and "Factory reset" in Android settings.
[Asus Transformer TF700] graphdarnell:
I don't know if I'm gyrating sur place,or pushing the envelope here, but with the acer A500 (which of course uses the same Tegra T20 as the TF101), the released NVFlash Code allows for erasure of the partitions, and then while in APX mode, enables rewriting of the partition table, which in turn allows reloading of a bootloader in place of that which has been corrupted. This, I've done: the apx command returns the particular SBK of the tab, which opens the door for reflashing of whatever.

Apparently, a bricked TF101 can be similarly unbricked with the help of a comparable software tool, though I've never had to resort to it. The situation with Tegra 3 is that Asus encrypted the code, which makes it impossible to rewrite the bootloader. Am I assuming correctly so far? If yes, then 2 questions:

(1) Nvflash for JB is now possible,which indicates some “inadvertent” leak somewhere to someone. If the code is now available for an Nvflash exploit, why can't the same thing be done as with the Tegra T20 chip? Therein, one doesn't need Nvflash files generated beforehand to extricate from a “brick”;

(2) Asus must have a decrypt tool to unlock that impasse (to us) embedded in Tegra chips they installed on their tabs. I assume the same code is used for all Tegra chips, or at least a batch of them, because Flatline.img works across the board regardless of individual SBKs.

If they do have this tool (they must have it), theoretically, there's no need to replace the motherboard where the tab “bricks” as a result of an OTA gone awry. Asus can just reflash the bootloader. Am I off the mark?

I realize this is a lot to ask of a member who participates gratuitously. You've done more than your share of giving and helping. I evidently would prefer a response from you, since that way, I can benefit from your insights. However, I'd equally appreciate a referral for further readings. Thanks again.
[Asus Transformer TF700] JoinTheRealms:
Yes your correct with the tf101 and other tegra 2 devices, NvFlash is available without having to generate blobs etc. This is because the SBK or secure boot key which encrypts nvflash communication is known so generic nvflash binary's can be used.

However from the Transformer Prime and onwards, The SBK is not known so work arounds are required to access NvFlash communication. Im a bit fuzzy with the details here on im sure _that will correct me if im wrong :).

It requires a patched bootloader, it seems this patched bootloader can manipulate the devices AES encryption engine (This engine is the only thing that can read the SBK directly, its used to encrypt the boot partition after an OTA update) to encrypt wheelie blobs (wheelie is a pre-loader for NvFlash aka it opens the door for nvflash communication) Now you have signed wheelie blobs (with a unique signature to your device) you can use them to authenticate NvFlash and gain access. And we didnt need to know the SBK! And once this process has been done, you can swap back the official non patched bootloader, in fact you could completely wipe nand, with NvFlash be able to re-write these partitions.

But this method requires an unbricked and unlocked device, since we need to flash the patched bootloader, and use a modified recovery to generate those wheelie blobs. The good thing about this is once you've done it thats it. Asus cant do anything about it. Since the SBK is embedded deep in one-time programmable memory they cant change your devices SBK meaning those wheelie blobs will always be vaild.

If you send a bricked device back to Asus for repair AFAIK know they will have to replace the motherboard to repair it. Otherwise they would have had to leave a writable bus somewhere on the motherboard to let you re-write nand. Some kind of JTAG exploit might be possible, but thats far out of my league :)
[Asus Transformer TF700] graphdarnell:
Thanks for the very instructive information, if only relatively so to me (lol). In any case, let's see how low-IQ I can get here: the SBK is particular to every motherboard, but the tool that encrypts and conversely decrypts and read it is not; it can be manipulated to retrieve the SBK of any MB, if available. Am I right? If there's a way out, there must be a way in, eh?

“... AES encryption engine (This engine is the only thing that can read the SBK directly, its used to encrypt the boot partition after an OTA update...” According to this scenario, we have something that could read the SBK directly, or at least can manipulate AES to do so, right?

If the SBK, whether burned into or not, is known, refashioning the NAND is possible through some software tools, like say Bab Sector? Then why does Asus have to replace the MB? It looks like every time you troll an OTA, a new bootloader is rewritten!

Where the brick is caused by the bootloader being corrupt or effaced, how is rewriting it different from an OTA doing it? I mean, how did they initially program the bootloader onto a virgin mmc anyway?

At any rate, we should wait to see if Merlin would respond and whether it'd shed anymore light onto this before going on, or not.:D:D
[Asus Transformer TF700] _that:
Maybe "read the SBK" is the wrong term here. As far as I understand, the AES engine *uses* the SBK to encrypt or decrypt data, but there is no way to extract the SBK from the engine.

As JoinTheRealms explained, wheelie allows us to use nvflash without knowing the SBK at all, but we need a pre-encrypted blob that was encrypted by our own device with its unique key. Flatline is just another way to work around the bootloader signature so that this blob can be created, there is still no way to read the SBK directly.

Because I assume the service centers that do the repairs don't have the access to the SBKs either. And it's more profitable for them to charge for a new mainboard than just for reflashing the firmware anyway. :p
[Asus Transformer TF700] graphdarnell:
No kidding!! :D:D:D
[Samsung Galaxy Nexus] dorperez:
Hello, I have Samsung Galaxy Nexus but gameloft games aren't working ...

I enter the game and it crash on start no matter where I am download it from..

Can someone help me plz ?
[Samsung Galaxy Nexus] paarthdesai:
what rom?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] runderekrun:
Most (older) Gameloft games do not work past the versions of Android that they were developed for.
[Samsung Galaxy Nexus] dorperez:
In how long they will fix it for the newer versions?
[Samsung Galaxy Nexus] dexviajiboy:
which games? just tested Asphalt 7 & Modern Combat 3 works fine on my stock 4.3, others than gameloft PES2012 & NFSMW.. running much better than custom rom 4.2