yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] arinsms:
There is a new function to hide app in TW drawer using leak jelly bean xxls7 but after hiding, cant find any function to unhide back the app. Uninstall and reinstall seem doesnt solve the problem. Anybody can advice?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] msedek:
Just scroll all the way down the menu and select the show hidden application and select what you want lol

Tapatalking on my n7000
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] arinsms:
Hahaha u save the day mate...
[Samsung Infuse 4G] jacobgus:
i have been attempting to update my Samsung Infuse 4g to JB but to get there i had to go to GB then to ICS then to JB. i got GB and was on the last steps of ICS when i was told to go into the menu where you hold the power button and the volume button at the same time until the logo then let go of the power button and install the rom. i did that and it finished then i took the battery out and restarted it like the video says but all im getting is what looks like it should be the correct screen but the top and bottom are just static and it kinda looks like the cyanogenmod symbol of the circle with the top hat on should be there but isn't.I think it still works though, like if i click enter it will attempt to reload because the first button on the menu is "Restart". When i try to turn on the phone it gets stuck at the Samsung logo and does not load. PLEASE HELP ASAP.
[Samsung Infuse 4G] andros11:
You need to flash the GB bootloaders. Be careful doing that. A bad flash will brick your phone.

Look for my how to flash JB guide if you have not seen it yet.

Sent from my LiquidSmooth Infuse
[Samsung Infuse 4G] jacobgus:
link?

do u happen to have a link to that GB bootlaoder? im in a super rush to get this working, im a college kid on a very tight budget and i am getting so close to asking this girl out but its gona be hard if after i ask her out i cant text or talk to her on the phone at all. plus if my parents find out, oh god it will be hell. they call once every 2 or 3 days.
[Samsung Infuse 4G] andros11:
http://xdaforums.com/showthread.php?p=31342159

There's the guide I was talking about.

Put your phone into download mode and use either the odin or heimdall one.

In a sense the heimdall one click is a bit safer since it makes you test wether it can flash correctly before attempting to flash the bootloaders.

Sent from my LiquidSmooth Infuse
[Samsung Infuse 4G] csandman1977:
You may want to rethink doing things like this 'in a rush'. Mistakes happen when rushing and you really really don't want to mess up flashing bootloaders.
[T-Mobile, Samsung Galaxy SIII] BaconStep:
Bacon-JB

UVDLJA 4.1.1

Features

Touchwiz 4.1.1 Official JB

CIQ is gone

Debloated

Boot sounds disabled

Zipaligned

Deodexed

Busybox

Root

BACON!

Download here!

Install Steps

1.Boot into recovery

2.Wipe Data/Factory reset

3.Wipe cache

4.Go into advanced and wipe dalvik cache

5.Go into mounts and storage and then format /system

6.install zip

7.reboot

​
[T-Mobile, Samsung Galaxy SIII] BaconStep:
Screenshots

​

Thanks to:

M0D1441

gmillz

mindmajick

ieatkittys

boobah204

nrm5110

armyvet

Killahurtz

UncleIrish
[T-Mobile, Samsung Galaxy SIII] misael06:
Nice downloading now!!

U have any screenshots?
[T-Mobile, Samsung Galaxy SIII] BaconStep:
not really. I mean its just stock touchwiz. I'll upload some tomorrow.
[T-Mobile, Samsung Galaxy SIII] Warren87:
Looks great! I'm about to try. Thank you!
[T-Mobile, Samsung Galaxy SIII] KillaHurtz:
Congrats dude !
[T-Mobile, Samsung Galaxy SIII] bps119:
Was there an unofficial leak I missed? What did you build this from?
[T-Mobile, Samsung Galaxy SIII] Kelevro:
Hey, guys, he doesn't know! HAHAHAHAHAHA

No, but the official Jellybean OTA was released yesterday (today?) for T-Mobile.
[T-Mobile, Samsung Galaxy SIII] bps119:
Derp, followed a link Bacon posted in the off topic section of the gs2 skyrocket forum and didn't realize it took me to the t-mo gs3 forums.

Sorry guys, have fun with your official release:(
[T-Mobile, Samsung Galaxy SIII] BaconStep:
hes from skyrocket forums :p
[T-Mobile, Samsung Galaxy SIII] BaconStep:
screen shots added
[T-Mobile, Samsung Galaxy SIII] Kelevro:
Quick question:

Does this function IDENTICALLY to the OTA Stock? You just removed some bloatware. (Yes, I read the OP, just making sure). I've had some really bad experiences with someone's leaked JB ROM (I won't name whose); screen flickering, hot boots, etc. I really just want a perfectly stable build, but I also don't want to go through all the trouble of using ODIN.
[T-Mobile, Samsung Galaxy SIII] BaconStep:
Its straight up stock. No mods or anything. Since the official release I havent experienced any screen flickering or hot reboots at all. Definitely give the official jb a shot before using odin.
[T-Mobile, Samsung Galaxy SIII] Kelevro:
That's good news. I couldn't stand all of the glitchy aftertaste the leaked Jellybean ROMs were leaving in my mouth. I'll try this out later tonight, when I'm not constantly on the phone with people.

Thanks, Bacon!
[T-Mobile, Samsung Galaxy SIII] deeoh1084:
i guess u missed the news for T-Mobile Samsung Galaxy S III, T-Mobile released the official JB firmware as of yesterday called UVDLJA
[T-Mobile, Samsung Galaxy SIII] darren.wlsn1:
priceless, made my day.
[T-Mobile, Samsung Galaxy SIII] BaconStep:
new link is up
[T-Mobile, Samsung Galaxy SIII] cdshepherd:
Bacon coming up in this big ol brony world. :p:p:p

Bacon, its whats for dinner
[T-Mobile, Samsung Galaxy SIII] KillaHurtz:
Am I in the thanks for selling you the phone ? :D
[T-Mobile, Samsung Galaxy SIII] BaconStep:
Yeahhh
[Nexus 4 Android Development] Stryder5:
Yep, worked like a charm. Got Titanium running and restored all my apps :)

Btw, check your PM.
[Nexus 4 Android Development] HQRaja:
Checked...thanks. =) Added the links.
[Nexus 4 Android Development] StickyEyez:
stem/bin/sh: su: can't execute: Permission denied

that is what i always get when i put in the "su"--permision denied
[Nexus 4 Android Development] Stryder5:
You need to boot the unsecure boot.img first.
[Nexus 4 Android Development] HQRaja:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
[Nexus 4 Android Development] Stryder5:
I'm pretty sure I used the one Harry GT-S5830 provided.
[Nexus 4 Android Development] StickyEyez:
I used the one in the OP of that thread.. is there a different one I'm supposed yo use?

---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------

It works :)
[Nexus 4 Android Development] Stryder5:
Glad to hear :)

Did you install the OTA before doing this? I gained root before installing the OTA.
[Nexus 4 Android Development] apzalo:
No issues with installing the OTA after root?

Edit: Just noticed in your sig that you did not install the update.
[Nexus 4 Android Development] StickyEyez:
I installed after ota
[Nexus 4 Android Development] Stryder5:
You mean you gained root after you installed the OTA?

---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------

I gained root, but haven't installed the OTA yet.
[Nexus 4 Android Development] Elemenopee:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
[Nexus 4 Android Development] StickyEyez:
Yes sorry gained root after OTA
[Nexus 4 Android Development] HQRaja:
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.
[Nexus 4 Android Development] resynx:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
[Nexus 4 Android Development] 0.0:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
[Nexus 4 Android Development] HQRaja:
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)
[Nexus 4 Android Development] HQRaja:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/

The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
[Nexus 4 Android Development] 0.0:
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?
[Nexus 4 Android Development] fkrone:
You can download stock recovery here: http://www.mediafire.com/?57zmq7yw089gcr8
[Nexus 4 Android Development] grayson73:
I see that there are two methods in the OP. Which method should I use?
[Nexus 4 Android Development] mcnob:
Use the first but don't try to permanently install CWM yet cos it obviously has issues.
[Nexus 4 Android Development] ziggy34:
From a Google+ post

https://plus.google.com/115049428938715274412/posts/hCFx1H1u5HN

Sent from my A500
[Nexus 4 Android Development] Stryder5:
Don't flash the recovery. It isn't ready. I would follow this thread for flashing the recovery after CWM has been updated: http://xdaforums.com/showthread.php?t=1995440
[Nexus 4 Android Development] mastaworm:
This didn't work for me. I booted the unsecured boot.img and booted the CWM recovery to make sure they worked and they did. I then applied the disable recovery revert, flashed both boot and recovery, and now my phone bootloops at the google screen. I can still get into the bootloader, fastboot boot recovery.img will bring up the CWM and fastboot boot boot.img will make the phone boot properly but it will always bootloop if it ever turns back off. What happened?
[Nexus 4 Android Development] thatguyitsme:
Not sure what happened but I had problems, bricked for a few hours yesterday. The only thing that worked for me was flashing factory image. I followed a tutorial for a bricked nexus 7 and it finally booted.
[Nexus 4 Android Development] mastaworm:
Yeah I'm already downloading it and about to do that.
[Nexus 4 Android Development] Stryder5:
Don't flash anything at this point through fastboot.

You will boot loop if you try to flash the unsecured boot.img. The instructions do not mention to flash the boot.img so I don't understand why anyone would try. Read before you flash!

CWM isn't working properly yet so it won't work if you try to flash the recovery. I'll PM HQRaja to remove that part from the instructions for now.
[Nexus 4 Android Development] mastaworm:
I've seen instructions saying it's fine to flash the boot but that is clearly a bad idea. For anyone else in my position, downloading the factory image and running flash_all.bat within the extracted folder will completely wipe your phone and make it work again. I tried flashing the stock boot.img out of that archive and that did end the bootloop but it appeared to be looping on the boot animation after that so I just went ahead and wiped since I hadn't really done anything since the wipe from the bootloader unlock.

Everyone, just do fastboot boot recovery.img then use that to flash a root.zip, it's so much simpler for now.
[Nexus 4 Android Development] Stryder5:
The instructions don't say to flash the boot.img file. I'm not sure where you saw it, but don't flash anything from fastboot.
[Nexus 4 Android Development] evaradar:
So I take it the CWM team's recovery for this phone is not yet stable? Buggy? How long will it take them for them to update it?
[Nexus 4 Android Development] nibrwr:
Someone working on the issue said later today.

The recovery works well enough (for me anyway), but of course doesn't stick on reboot
[Nexus 4 Android Development] mcnob:
There's no need to revert to factory image. Just go back to bootloader (power and volume down), boot unsecured recovery using the CWM zip and when you get in, clear cache (and flash SU zip if required), reboot to bootloader, reflash stock recovery and reboot. Reboot again to complete rooting.

Phone rooted and unlocked and usable again.
[Nexus 4 Android Development] fenixjr:
Touch worked for me, maybe try it again? normal recovery i couldnt interact with power button either though.
[Nexus 4 Android Development] 0.0:
a new recovery update is suppose to release today, according to clockworkmod's twitter
[Nexus 4 Android Development] evaradar:
Any progress/status on it?
[Nexus 4 Android Development] Stryder5:
You're probably better off following the CWM thread: http://xdaforums.com/showthread.php?t=1995440
[Nexus 4 Android Development] evaradar:
Thanks! Its a shame that even though they did a great job, there are bugs with this version :(

Kudos to them still.
[Nexus 4 Android Development] iomartin:
Hello,

I'm trying to do this for the first time. After I issued

fastboot oem unlock

my Terminal has been displaying a < waiting for device > message. Secure boot is enabled and lock state is locked. I don't know if anything is happening, but I'm afraid of cancelling the process in the middle (noob question: what are the chances of bricking?). Is it supposed to take very long? It's been over 5 mins.
[Nexus 4 Android Development] Stryder5:
Not at all. It was a very quick process. If your device didn't change at all, then chances are fastboot doesn't detect your phone. Did you install the drivers yet? If not, check my signature for the drivers if you have Windows.

When your phone is in bootloader, run "fastboot devices" from command prompt (without the quotes). If the proper fastboot drivers are installed, you should see a serial number listed in command prompt under devices.
[Nexus 4 Android Development] iomartin:
Thanks for the quick reply. I was trying to unlock in Linux, so I shouldn't need drivers. I'm not sure why it didn't work, but I moved to Windows and I got all the way to step 9. I'm in CWM Recovery and I'm trying to perform a backup. I can go up and down to choose an option, but I can't select any. I assumed the power button would select, but it doesn't work. Am I missing something? What should I do?

CWM Recovery says it couldn't mount a few folder (/cache/recovery/command, /cache/recovery/log and /cache/recovery/last_log)

I forced a reboot, but then the phone is staying forever at the Nexus logo.
[Nexus 4 Android Development] Stryder5:
I haven't checked, but it should be a touch-based recovery. (just tap with your finger on what you want)
[Nexus 4 Android Development] ZappiestOyster:
FWIW, I used the second method. I had issues with adb (no devices found). It turned out that I had to uninstall and reinstall my drivers. Also, I used the drivers from the Android SDK. Once my device showed up after running "adb devices" I was able to root without any issues. Titanium Backup up and running!

Thanks OP!
[Nexus 4 Android Development] PoloB12:
New released recovery works like a charm when flashed ! :D

Finally a permanent recovery ! Thanks koush !
[Nexus 4 Android Development] dadennis:
I can confirm that. Flashed the latest CWM-Touch Recovery and it works perfectly. The non-Touch still doesnt work due to the not-working power-button.
[Nexus 4 Android Development] sr-ha:
Where can i get the latest CWM-Touch? Is it the one linked in the first post?

And can i flash it without changing any rewrite script on the phone?

thanks
[Nexus 4 Android Development] ziggy34:
Latest CWM - Touch (Current version is 6.0.1.8)

http://www.clockworkmod.com/rommanager

Sent from my A500
[Nexus 4 Android Development] sr-ha:
I flashed this one. But it isnt working. :crying:

EDIT: oh i flashed the non touch version.

Edit: nope, not working for me. Andy with red triangle :(

Edit: Now it works :D
[Nexus 4 Android Development] kaiowas82:
how it did works? I cant access into recovery, always android with red triangle
[Nexus 4 Android Development] mistersixt:
I always get this red triangle thing with "No Command" or something, I flashed the latest CWM touch via fastboot... what am I doing wrong?

Thanks, mistersixt.
[Nexus 4 Android Development] jimmyz:
Did you rename the script that reflashes the stock recovery on reboot?

http://xdaforums.com/showthread.php?t=1995440
[Nexus 4 Android Development] PoloB12:
Did you succesfully obtain root privileges before flashing the recovery image ?

Not sure if necessary but was the case here and worked straight away with the new version of last night.
[Nexus 4 Android Development] evaradar:
New version of ClockWork?

http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.9-mako.img
[Nexus 4 Android Development] satbir7:
Just flashed the latest touch recovery, and it worked like a charm!!!

Thanks to Koush!!
[Nexus 4 Android Development] adidas007:
Thanks !
[Nexus 4 Android Development] HQRaja:
Hi guys,

I was away from XDA over the weekend. The official CWM had just been released when I left, so I added the flashing instructions, provided a link to it, and then left without any seeing any testing response, so my apologies for any inconvenience it might have caused. (I myself don't have a Nexus 4, so couldn't possibly test.) Though now we have a fully working CWM available and the latest response here in the last few posts confirms that it flashes and boots perfectly fine, so there should be no problem with flashing it anymore.

I have also messaged fkrone for his permission to use his recovery revert disabler in my rooting script, so that CWM recovery sticks after being flashed. Till I can get his permission, you guys can flash his script directly from his thread.

Happy rooting. =)
[Nexus 4 Android Development] irishrally:
The latest cwm recovery stops the stock recovery re-flash.
[Nexus 4 Android Development] HQRaja:
Ah I see. Again, the pain of not having the device itself and posting only based on my experience with other Nexus devices and my limited knowledge of how things have been working on those so far. I'll update the OP again. Thanks. =)
[Nexus 4 Android Development] CloudTown3:
How do you bit straight to cwm recovery? Mine boots into bootloader first
[Nexus 4 Android Development] irishrally:
I tried volume up and the power button and it didn't work.

If you are already rooted I recommend the Quickboot app. I prefer it even over custom ROMs extended power menus.

Booting into the bootloader first though isn't really that big a deal, and might even be safer.
[Nexus 4 Android Development] bline007:
Worked like a charm.

---------- Post added at 06:36 AM ---------- Previous post was at 06:34 AM ----------

I prefer goo manager its as simple as a click of a button no fancy stuff. Load the app and select reboot recovery.
[Nexus 4 Android Development] resynx:
Cave wait to try out the CWM method tomorrow =)
[Nexus 4 Android Development] jimmyz:
Could someone comment on how it stops the stock reflash?
[Nexus 4 Android Development] evaradar:
Apparently after you flash the latest CWM version 6.0.1.9, you boot into recovery from the bootloader. Then it will prompt you if you would like to stop the re flash into stock.

Taken from Step 7 here:
[Nexus 4 Android Development] irishrally:
Yep, that method certainly works. The new recovery may also prevent stock recovery re-flash automatically if you reboot immediately after flashing recovery, but I can't confirm that because I haven't tried it yet. I'll try it tomorrow, but in the mean time it's a quick extra step to go into recovery and do as you described.

EDIT: I just checked and the latest cwm recovery does stop the stock recovery re-flash without going to recovery first and accepting the prompt. On the off chance you hang on boot, hold the power button down until the phone shuts off, boot back into bootloader by holding volume down and power button, scroll to and enter recovery, factory reset and reboot.

EDIT2: As a double check I flashed the factory image and started over. CWM sticks after flashing.
[Nexus 4 Android Development] smenes:
erase stock recovery first?

Do we need to:

fastboot erase recovery

prior to flashing the new CWM recovery?

fastboot flash recovery recovery.img

If we don't erase the stock recovery when we flash CWM, does it overwrite the stock recovery? or does it install side by side with the stock recovery on the partition? Coming from my old phone, an Atrix 4g, I erased the stock recovery before flashing the new.
[Nexus 4 Android Development] Stryder5:
You don't need to erase. It seems to overwrite stock recovery.
[Nexus 4 Android Development] DaX05:
Thanks! Worked flawlessly!

1. Flashed it via Fastboot

2. Rebooted

3. Powered down again and THEN flashed SUPERSU.

That did the trick. :laugh:

Beamed via Nexus 4
[Nexus 4 Android Development] Nucleotide:
I used the ClockworkMod Recovery Method and it all went well although after flashing recovery, I rebooted the phone and it took a good couple of minutes at the Google logo and after about 10 minutes sitting on the Nexus X logo, I had to hold down the power button to force it to restart. It did this 2-3 times and then finally booted up fine.

Otherwise all good. Rooted, busyboxed, and working great. :)
[Nexus 4 Android Development] DaX05:
That happened to me only because I flashed SuperSu right after flashing the recovery.

SuperSu has to be flashed after an initial reboot.
[Nexus 4 Android Development] kptnk:
Thanks guys for your explanations, unlocked and rooted successfully in few minutes ;)
[Nexus 4 Android Development] Night Galaxy:
I'm a bit of a root noob... how would I go about unlocking the bootloader, rooting/ installing CMW through the use of a Mac (OS X)? What are the different commands, as well as the files needed?

Thanks!
[Nexus 4 Android Development] PoloB12:
At this moment, as far as I know, do yourself a favour and use someone's windows/linux pc for half an hour and you're settled.
[Nexus 4 Android Development] irishrally:
There really isn't much difference getting setup on OSX, you use terminal instead of windows cmd prompt, and you precede commands with "./".

So if you see this command in a Windows guide:

fastboot oem unlock

You would type the following in terminal:

./fastboot oem unlock

This might help: http://xdaforums.com/showthread.php?t=1917237
[Nexus 4 Android Development] apzalo:
That is the guide that I used to set up my mac, it is a good one. Read the whole guide before starting to set it up. It will be super easy and once you add the folder to the bash profile, all commands are the same as the windows guide.
[Nexus 4 Android Development] harpo1:
Should we do the OTA update before or after rooting if we plan on keeping the stock recovery?
[Nexus 4 Android Development] irishrally:
Before.
[Nexus 4 Android Development] amdhunter:
Worked like a charm. Thanks.
[Nexus 4 Android Development] harpo1:
how long does it take when you do the fastboot oem unlock? Mine is sitting at waiting on device.

Edit: NVM I was being a dumb ass. Super easy process thanks.
[Nexus 4 Android Development] bigwhiteegg:
THX! it worked like charm!

:victory:
[Nexus 4 Android Development] drew_grant:
Worked great. Even better, my phone didn't not wipe at all. Don't know how that happened but whatever, I'll take it!
[Nexus 4 Android Development] namartlu:
Works like a charm, thanks a bunch. root in few minutes. Now restoring my apps through Titanium and I will be rocking~ ;)
[Nexus 4 Android Development] kptnk:
Same here, unlocking the bootloader hasn't wiped my phone neither...and it is now obviously well rooted.....:confused: