Search results

Make sure you are already rooted with busybox installed. Download the eMMC brick bug check app on the Play Store to verify your CID starts with 15. If it does, you are good. If not, it will not work. Read this Post First. Download the unlocker manual install zip and unzip the two files...

So first try went better than it had been, before it kept repeating "Y", this is where I assume it was failing last time Followed the steps from page 8, set permission ran the first time and it did its thing and shut off. Pulled battery and rebooted, 2nd time it was a blank screen. Waited and...

Are you going to make this available to those of us who followed the advice to stay on NC2 in the sticky thread? As I said earlier this week, Id rather just unlock 4.4.2 than have to nuke and odin NC4/OF1 and use the yemen thing ..but if thats what I have to do would be nice to know

Did you ever make a 4.4.2 version apk or did you end up upgrading to unlock? Don't really want to nuke my phone either if something is still in the works

OK, so apparently I'm behind the times and this isnt working for me on 4.4.2. Whats the easiest way to get on 4.4.4 to get this installed without bricking or should I just wait for a modded apk. Have safestrap installed but haven't done anything with it for ages Still working on this?

Have you activated it in the Google App under Settings>Now Cards? I have attached an SS of where it is.

I used wugfresh toolkit to unroot, return to stock and flash factory image. I usually just pull boot and system.img and flash them thru fastboot but looks like they changed the bootloader from 04.04 to 04.05 so to not risk anything I just wiped everything and had the toolkit do it after it...

Virgin Mobile XT1526 , still waiting on 5.1 here as well

Might have been an issue with fstrim not running on your device, apparently this was tweaked in 5.0.2 http://www.androidpolice.com/2014/12/20/developer-changelog-posted-for-android-5-0-1_r1-lrx22c-to-5-0-2_r1-lrx22g/ I've been so far so good since I flashed factory image ... don't get me...

If you've never seen this , give it a read, explains why the OTA may have not reached your device yet. http://www.reddit.com/r/Android/comments/1r1dz4/44_kitkat_has_started_rolling_out_on_the_n4/cdiwt6f

Doubtful anythings coming tonight but I could eat my words, still no images up

As long as its not NC4 taken from OTA you can downgrade with odin

What is the kitkat build you are on- go to settings>about phone>build number If you took the OTA you would be on NC4, in this case there is no way to go back to 4.3, the bootloader is incremented to prevent downgrade. If you flashed the NC2 leak then you can just odin back to MJE use this...

Our bootloader is locked. That just appears once you have root, some ppl have gotten rid of it with wanam and xposed if that doesnt work you can use triangle away "Reset Flash Counter" to get rid of the icon If you are going to upgrade to kitkat DONT take the OTA follow a link on here and get NC2

Nothing you can do on NC4 but wait

Fwiw I used 3.65 on MJE to install then flashed the firmware with Odin then switched over to 3.72 once I was booted up on NC2 didn't run into any issues

This may help http://forum.xda-developers.com/showthread.php?t=2749463

This is not true. The bootloader is still locked on NC2. What you mean, is that it wasn't incremented to prevent downgrade to MJE, and the big thing was kernel modules enabled, which may lead to kexec in the future (for ppl who DIDNT take the OTA). Would have definitely been a much bigger...

Retail Note 3 is locked to the stock kernel, aosp uses a diff one. I think others like Bionic can use kexec to boot which was what they were looking into on NC2 since kernel modules are enabled (and why they told everyone not to take the ota)

Yeah it is normal now to stay if you are on kitkat rom. If you use xposed, you can download the module "Samsung Data Connection Icon fix" and that will get it to go away but it will make the verizon specific 4g icon turn into the normal tw icon as well

I used the program Root Explorer to paste the files into /system/media/audio/ui After they are pasted I changed the permissions to rw- r– r– Reboot and its working here.. I used this link...

I got the files and followed the instructions from this link using Root Explorer http://www.droiddog.com/android-blog/2013/01/root-lightsaber-sounds-on-s-pen-attachdetach-on-the-galaxy-note-ii/ worked fine here

Go to Settings>About Phone, what is your build number. If you are on the NC2 kitkat leak, then yes, you can go back to MJE build with odin. If you are on NC4 by taking the OTA, there is no way to go back to 4.3. You're stuck, the bootloader is incremented preventing downgrade.

http://forum.xda-developers.com/showpost.php?p=52603311&postcount=12 http://forum.xda-developers.com/showpost.php?p=52609797&postcount=42 I would not get your hopes up anytime soon, this is why I stayed on NC2 and disabled OTA's after reading the psa by hashcode.

If there is a way for them to do it you're going to be waiting a while for it http://forum.xda-developers.com/showpost.php?p=52609797&postcount=42

No root method for NC4 and no way to downgrade either Only way to go back to MJE is if you are on NC2 leak

http://forum.xda-developers.com/showpost.php?p=52633373&postcount=391

Wont work with NC4, hes stuck with no root til a new exploit Might help, I havent seen any stutter on NC2 with mine. Phone has been the fastest its been since I got it at launch, it used to lag on me sometimes turning the screen on even thats gone now

Saw John Hammond getting food the other day lmao

Whatever you do, dont use RDLV on it , cause youll end up with a brick

You mean some people rush to have the newest things, that they dont realize what they are giving up for it. http://forum.xda-developers.com/showthread.php?t=2750875 This thread already exists in Q&A and was simply trying to save some headaches now as well as down the road for those who don't...

I haven't had any issues yet running NC4 baseband over NC2 leaked build everythings been good

Theres nothing wrong with taking it if you guys have no issue with not being able to change kernels in the future or downgrade with Odin. If you screw up the survival process though and lose root, beans has already said it will probably be a very long time til there will be an exploit...

I know some people just want root, but really what other point is there to doing this?? This sounds just like what happened over in the S3 forum when people who wanted 4.3 ota so desperately they ended up getting hard bricks and relocked bootloaders. Taking the OTA, you are giving up kernel...

If you take the OTA there is no going back If you just odin the modem and stay on NC2 should be fine to go back if you want

Well looks like I ran into this situation as well, gave my wife my S3 after moving to the Note and shes on a d2vzw cm11 build 2/8 and texts apparently stopped working after the first text is sent in stock sms app. Following the method in this thread I: Flashed MB1 firmware ( was on ML1) Backed...

Nexus 10 has never shown 2gb available, I've had it since launch and I believe the most I've ever seen was back on 4.2 was about 1400MB or so, and it has gone down from there on each update. You never get what they advertise on the box, every single one of my devices has less than whats...

Can't speak for anyone else, but haven't had a single issue with GPS on my Note 3 from launch on MJE Locks quicker than a few of my other devices

It's probably the nightly he's using, I use bluetooth daily between my S3 and 2013 Si Navi and haven't encountered an issue yet on 2-8 , no skipping audio, info shows, steering controls work, phone calls and texts come thru.. You can keep your Ford or Chevy lol

Not an issue yet here on 2-8 coming from 1-20 Deep sleeps fine with Bluetooth on and all my stuff works like it should (** I have MF1 firmware / ML1 radio/ stock kernel)

I think this is the commit masta is talking about. Great work tracking it down and getting it worked out guys. :good:

It's failing on cache because you cant use the older files to root a newer update! As others have said its Kingo on MJE, if it failed just try it again until it pushes the supersu then flash a good one thru safestrap after

In the header of the post to the right of the Facebook share logo is the thread post # Apparently post 16 was from me so I'll quote it for you http://forum.xda-developers.com/showpost.php?p=47288273&postcount=16

fwiw my Galaxy Nexus Toro on CM11 same day nightly before bluetooth was "fixed" exhibited the same behavior trying to connect to my car, com.android.bluetooth or whatever it was would crash on pair and connect , reconnect then crash again over and over- nothing worked with my unit until 1-18 /19...

That just means your /system was detected to not be stock and was flagged "Custom" and is no longer "Official" (you can see this status in settings>about phone>Status) If you took the OTA, your bootloader is locked. No going back

Battery is fine on 1-20 with the working bluetooth just turn it off when not in use, its the wakelock that keeps it from deepsleeping and drains it. Cpuspy is great for making sure the phone is getting deep sleep. Haven't had any problem making it a full day here and using it in the car on my...

Hopefully you backed up your EFS.. dont know what you searched but theres plenty of search results for "lost imei" http://forum.xda-developers.com/search.php?searchid=251362212 http://forum.xda-developers.com/showthread.php?t=1852255 this might help never used personally though...

Bluesleep wakelock is what drains it when the Bluetooth is turned on. Rudedog posted this earlier and I can confirm with cpuspy I've got no issues on 1-20 deep sleeping with BT turned off, however once its turned on no longer deep sleeps. Goes back to normal once I turn it back off with the...

Exactly the same here phone is running good on 1-20 and bluetooth works with the Navi in my car, just while BT is on the phone will not deep sleep its fine with it off though

Same thing here.. my headset works fine but the Navi in my Si causes it to crash on connect, then it tries to reconnect and does, then crashes again and repeats. unpairing , rebooting doesnt matter it isn't individual to my S3 however, my GNex on CM11 it does the same thing too , works perfect...