Search results

I don't really understand the purpose of this script. Does it allow notifications on the gear S with CM12.1 installed? Please add directions on what I need to install on my samsung phone to utilize my gear s after running this script.

Here is the stock odin firmware for the SM-R750T: R750TUVU1APC1 https://drive.google.com/open?id=0B0a0KxS2Q3gUNndJM3NnSXpHeXM To root the above firmware, flash this rootfs with odin which enables root access: https://drive.google.com/open?id=0B0a0KxS2Q3gUcGNoOGdDOWhhbGM

Added root access to the newest update for my own Gear S, so decided to share: (flash using Odin) https://drive.google.com/file/d/0B0a0KxS2Q3gUcGNoOGdDOWhhbGM/view?usp=sharing Also I have the stock odin firmware for the newest release. Oops, this is for the T-Mobile version.

Yes, I have already rooted mine running the newest update. I'll post my rootfs later today. Update: here you go: https://drive.google.com/file/d/0B0a0KxS2Q3gUcGNoOGdDOWhhbGM/view?usp=sharing Actually this is for the T-Mobile Gear S. Do not flash if you have R750A.

NOTE: This is probably a good place to start for finding someone with a Developer Edition Note 3: http://forum.xda-developers.com/showthread.php?t=2525208 I'm running JasmineROM_V6.1-LRX21V.N900VVRUEOF (Installed from rooted stock using Flashfire) Hardware version: N900V.07 busybox - installed...

I have a production N900V, and I'm willing to help with whatever I'm able to do. I definitely want to convert my N900V to the developer edition :)

According to the link below, pushbullet allows you to sync notifications between two or more android devices, so this should have the desired feature of receiving notifications from the phone that the Gear S is paired with. http://www.androidauthority.com/pushbullet-notifications-update-384910/

After flashing and running the above Android Wear alpha release for the Samsung Gear S, here is some initial feedback: What works: - Bluetooth pairing - Setup / syncing with the Android Wear application with an Android device - adb over usb/bluetooth working - Displaying WIFI access points -...

There is already an existing Android Wear port for the Samsung Galaxy Gear S which it seems has been overlooked. Basically it looks like DeejayBaca from xda started an alpha port of Android Wear running on the Galaxy Gear Live, and didn't seem to follow through on the project. I Would like to...

Great! I can't wait until I can root my N900V. I'm counting down the days in anticipation. What's your percentage of completion on the N900V?

Has this been tested with N900V 5.0, and what version of kingroot? Or does this just with with N9005? Also was it done with the android or PC version of kingroot? Actually I'm a bit confused by your post. So did you flash CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 with odin, then...

This is successfully exploiting a vulnerability and is rebooting my note 3 (not installing su yet, haven't had time to fully research how this root exploit works: https://github.com/retme7/CVE-2014-7911_poc/ I've attached the prebuilt apk for this vulnerability. I'm getting activity on logcat...

UPDATE: I have some really good news which I came across which applies to N900V NJ6 (build KTU84P): http://www.androidpolice.com/2014/06/19/google-rolling-out-android-4-4-4-update-ktu84p-with-a-security-fix-factory-imagesbinaries-up-for-nexus-devices/ According to the above, the vulnerability...

I have serious doubts about the so called "proof of root" youtube video for 4.4.4 N900V, so I've decided to start a research related thread so we don't have to rely on someone who will probably give everyones hopes up. Since N900V NJ4 4.4.4 is the oldest flashable version on those of us stuck on...

I'm attempting to patiently wait for this exploit. It seems like someone who actually achieved root access would want to publish their finding immediately. I think the case here is they "think" they found a root exploit, and are possibly scrambling to release it to the public on the 15th, either...

Does anyone have a rooted Verizon SM-N900V DE with stock rom? Please post partition dumps to help all of the rest of us with locked BL stuck on 4.4.4 or 5.0. Please post at least the following partitions: aboot.mbn boot.img recovery.img sbl1.bin And also if you get a change, please post a dump...

After doing some further research, found out that these are the variations of the LG G Vista: VS880, LG-D631, and LG GX2 (F430L) Here is a utility which flashes the Philz CWM recovery for the LG GX2 F430L (LG G Vista)...

Since I own this phone and feel like is one of the best bang for your buck large screen phones for Verizon, I really hope my discovery will lead to ROM development. To answer your question, all of your data will remain in tact. The only thing that changes is that you will now have full fastboot...

Hello all, I have an AT&T Galaxy Note 8.0 (SGH-I467) which had stock firmware version 4.4.2 (NI2). I attempted to flash the pre-rooted I467UCAMF1 image, ended up wiping out the SYSTEM partition since flashing the system partition fails from both stock and pre-rooted I467UCAMF1 system.img...

This is a guide on how to boot your Verizon LG G Vista (vs880) into fastboot mode, unlock the bootloader, and flash CWM recovery. This device will now be open to flashing custom roms based on this discovery! I've verified this on my Verizon LG G Vista running 4.4.2: This guide requires that you...

Anyone still interested in this? I might have some free time coming up to have everything working. Hmm looks like the link was taken down. The current version on my phone is completely different at this point.

Sorry everyone I've been a bit busy. More info to come and I'll put out a new release. The next release will have wifi working and possibly sound. UPDATE: Wifi is working 100%, finishing up custom keymap for epic 4g which is taking forever, and after that audio v0.2 is coming soon, just been busy

It should work but isn't, configuration just needs to be tweaked. Thats why I wanted to put out this beta version so all feedback welcome. I'll play around with it when I find some extra time. UPDATE: looks like wireless is actually working (at least on my phone). If anyone wants to test let me...

Which site is typically used for large files?

Concept based on thread started by gTan64: http://forum.xda-developers.com/showthread.php?t=1584659 This is an Ubuntu build which runs natively without any Android code. I made the build pretty minimalistic but still functional to keep the filesystem file small. Here is the first public release...

Posted full ubuntu build in this thread: http://forum.xda-developers.com/showthread.php?t=1660736 UPDATE: I'm still working on it just busy, version 0.2 to come soon.

Thanks for the feedback gTan64, it was quite helpful. I will soon be putting out an ubuntu build.

That would be great actually, I need a place to host. By the way I found a huge oversight in the kernel which most definitely prevents wifi from working. Fixing that now. Things I've found wrong: - wifi is being compiled as a module, so I changed to built-in at least for now - wifi firmware...

kernel.zip for kexec boot I had to pull info from multiple sources as information on this project is scarce, but I put together a kernel to boot ubuntu from CWM. So here you go the file is epic4g-kexec-ubuntu-kernel.zip, and to boot from CWM5 you just do an update, and select this zip file...

Is there a precompiled kernel available? EDIT: Nevermind for some victory_defconfig was missing. I compiled it and here's a link: http://www.2shared.com/file/PivhoUuJ/zImage_ubuntu_victorytar.html

Confirmed! I got rid of the aweful 2.3.5 electrify bootloader. Just did this: [email protected]:~/Desktop/SMG_BP011UP$ fastboot flash boot CG59_0x00000130.smg sending 'boot' (3294 KB)... OKAY [ 0.206s] writing 'boot'... OKAY [ 0.734s] finished. total time: 0.940s

Holy crap I think I did it, I'm now getting a completely different productID (has anyone else seen this one)? Bus 001 Device 044: ID 22b8:7090 Motorola PCS According to my quick google search, 7090 is the Atrix 4g product ID :)

From what I've found so far, I've been able to get the full range of error codes, so I'm pretty sure I'm actually flashing CG39/CG42 and CG47, its just this CG3.bin which I believe is cdl.bin. I've received the following errors on different instances: 1) Failed to boot 1 2) Failed to boot 2...

# cat /sys/firmware/fuse/ReservedOdm 30000000000030003000100004000 Photon with an unlocked radio stuck on bootloader. If only I had flashed derpunlock.sbf beforehand :/ everyone stay away from 235pudding.sbf if you have a motorola photon, it's bad news. Has anyone successfully flashed the...

Looks like now I'm in the same boat, grrr.

I pulled RDL3_unlocked_electrify.smg from 235pudding.sbf. What SBF file do you usually flash to unlock the electrify? Maybe I don't exactly understand what you're trying to do.

The reason is because when you flash a new SBF, it will overwrite the rdl.bin with the RDL3.smg from the SBF file.

I'm pretty sure the reason you're receiving this error is because this RDL is from derpunlock.sbf from photon_pudding.rar. I'll post the unlocked pudding electrify ramloader. Attached is the unlocked pudding electrify ramloader, run: fastboot flash rdl.bin RDL3_unlocked_electrify.smg

At what point did you receive the error?

I already can. just do the following: fastboot flash rdl.bin RDL3_unlocked.smg fastboot erase system fastboot flash system your_system_file.smg fastboot erase boot fastboot flash boot your_boot.smg fastboot reboot EDIT: file extension doesn't really matter, can be smg or img Theres also...

Not yet, you can flash it but it is not yet bootable since I haven't figured out yet how to jump to recovery from the ramloader (you'll probably get an error 2 if you flash CWM then boot to recovery). After you reset your phone, rdl.bin gets cleared out so the same protection mechanisms are...

The process of loading the unlocked ramloader is the same regardless of your firmware, even if the bootloader is 'locked'. The ramloader is just that, its written to ram, and so when the phone is reset the code is cleared out of memory. This means to unlock your radio, you don't have to flash...

I have something great I discovered while investigating this issue: run unlocked bootloader without flashing http://forum.xda-developers.com/showthread.php?p=24250470 Basically I discovered how to load the ramloader from derpunlock.sbf, so now you can have unlimited flashboot access without...

You can actually unlock the radio with the stock locked bootloader still in place (derpunlock.sbf flashing no longer needed): [email protected]:~/Desktop/SMG_derpunlock$ fastboot flash rdl.bin RDL3_unlocked.smg sending 'rdl.bin' (3072 KB)... OKAY [ 0.193s] writing 'rdl.bin'... OKAY [...

I recently discovered this, and I thought it would be of some benefit to those who are wanting to unlock, modify partitions, etc without the need to flash derpunlock.sbf or modify your photon in any way. What you need to do this: 1) fastboot for Windows or Linux 2) unlocked RDL3 (ramloader)...

OK it seems that the reason my network settings were wiped out is because I did an 'erase', go figure. So I did another radio flash as follows without the erase and it worked fine when the phone came back up: fastboot flash radio CG5.smg Here was the output on the screen: Flashing partition...

I didn't mess up the radio, just basically reset the radio settings for the Motorola, which caused my phone not to work. I'm so glad I made a backup with QPST lol, did a restore and I'm back on Sprint. I've verified that CG05.smg is in fact the radio image for the Motorola Photon. NOTE do not do...

I've been a bit busy this week, but I should have time this weekend. I'm extremely close to having a fix for this issue. UPDATE: I figured out how to flash the radio on the Motorola Photon! Bad news at the moment is I have no service, lol

I've narrowed it down to being an EAP authentication bug somewhere. The good news is the bug is most likely in one of the modules or wimaxd, so this should be very fixable.

I'm most definitely onto something. Using the wimaxc tool, I discovered that the radio is in fact connecting to a 4g base station. The odd thing though is after that the server dies, the wimax daemon wimaxd just crashes. It is grabbing a list of base stations, and is connecting to sprint towers...