yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] teachmeluv:
Did i explain my problem not good enough?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Q&A, Help & Troubleshooting] mhrlive:
Hello man, I have a similar problem its very annoying and turn me crazy during last days, after many searches I found the cause and I want to help readers here, ths might fix your problem just try it, in my i9300 sound problem, I managed to just turn off the sound detection by google now widget, and stop it, if you dont know what I mean check this page where I found the solution : http://www.guruht.com/2014/01/fix-cutting-sound-issues-on-cm1011.html

wish this helps.
[Windows Mobile Development and Hacking General] netters:
Can anyone help???

I'm trying to locate a facility to call the volume option from the task bar on my XDAIIi, I'm using mobi control to issue lockdown screens however my users want to change the volume.

any way of calling it from a shortcut or is there a seperate application I can use..

many thanks in advance. :(
[Android] JustArchi:
ArchiKitchen - Brand new Android Kitchen

Commits/Changes -> https://github.com/JustArchi/ArchiKitchen/commits/master

Source -> https://github.com/JustArchi/ArchiKitchen

TODO list -> https://github.com/JustArchi/ArchiKitchen/issues?state=open

Download. Of course you can also clone my repository to stay up to date.
[Android] JustArchi:
[SIZE="+1"]Features:[/SIZE]

Compatible with every Linux, which provides bash shell (every available distro nowadays)

Full ARM/X86 support for all included android binaries (Root, Busybox)

Dynamic permissions - A generic list of all available permissions, with proper filter for your local build and device

Dynamic symlinks - A generic list of all available symlinks, with proper filter for your local build and device. Additionaly if you're building from stock image, support for including symlinks from image itself, which results in best 1:1 copy

FS-friendly method of flashing - ROMs created with ArchiKitchen are fully compatible with every available partition, which means that they don't reformat /system partition during flashing. This is extremely important for dual-FS support for example for EXT4 and F2FS on SGS3.

Kernel repacking - Powered by mkbootimg, repacking a kernel never was easier. With one click you're extracting the kernel along with ramdisk to the proper folder, and with the second you repack it back

Deodexing - With one click you can easily deodex your whole ROM. With multi-threaded process and automatic API detection, this never was easier as well.

ArchiDroid Init.d - Forget about relying on kernel's ramdisk. Implement init.d in your ROM, not the kernel!

Latest [Bak]smali

Latest SuperSU

Latest Busybox

Latest Zipalign

And many more in the unique shell ktichen

[SIZE="+1"]Credits:[/SIZE]

[MENTION=4544860]osm0sis[/MENTION] - For mkbootimg

[MENTION=631273]Chainfire[/MENTION] - For SuperSU

[MENTION=1335872]Stericson[/MENTION] - For BusyBox

[MENTION=1299419]JesusFreke[/MENTION] - For [Bak]smali

[MENTION=455439]bgcngm[/MENTION] - For MTK-Tools

AOSP - For Zipalign
[Android] JustArchi:
[SIZE="+1"]ArchiDroid Init.d[/SIZE]

ArchiDroid Init.d is an innovative method for including init.d support in the ROM itself, and not in the kernel. ArchiKitchen supports adding ArchiDroid Init.d to any Android ROM.

ArchiDroid Init.d is based on two files. A core - debuggerd hook, and a check part - simple init.d script.

Init.d script is named 00ARCHIDROID_INITD, and it only creates a special file to notify the core that init.d has been already executed, therefore it can't conflict with anything and it's completely safe.

The core is a hook for special /system/bin/debuggerd binary, which is normally called once during initial boot. Therefore, when it's called, ArchiDroid Init.d firstly waits a specified amount of time (default: 5 seconds), in case if user has already a kernel with init.d support. This is required because otherwise all init.d scripts would be executed twice - by kernel and our init.d. After specified time, if init.d is still not executed, our hook executes all scripts in alfabetical order. Lastly, when we're done, hook is executing original debuggerd binary (default: debuggerd.real) and shares the environment, arguments and everything. This is a perfect method for implementing init.d in the ROM itself, because we don't need to trust the kernel that it supports and executes init.d properly. We give it a 5 seconds to execute it, and eventually we do the job if kernel is not interested in that. This way we can support both custom kernels with native init.d support (we wait initial delay, if kernel executes init.d, all is fine and we don't have to do so), and also pure stock kernels without init.d support (we wait initial delay, kernel doesn't care about init.d, so we're executing it).

I think that such hook works far better than relying on the kernel and modyfing stock ramdisks. Also we're sure that even if user changes kernel to any custom one, we still have reliable init.d support, regardless if custom kernel supports init.d or not.
[Android] JustArchi:
Reserved.
[Android] Harris_xx:
Me too! ;)

THX for your work!!!

If i get my new Laptop next few days i will dl and test it!

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Android] JustArchi:
Looking forward.
[Android] SavanTorian:
i really appreciate your work, like every time :)
[Android] JustArchi:
In general whole kitchen needs a magic touch more or less but firstly I'll want to make it fully usable (and modern!) then eventually rework it.

As for now it's more or less up-to-date. Also added Note3 variant.
[Android] Darkman:
Thanks for your work and projekt!

I will download and test it with the new Galaxy Note 10.1 2014 :good: (Android 4.3)
[Android] JustArchi:
Feel free to test it, but keep in mind that it's still work in progress :).

Today I've added new experimental method for *better* handling setting up rom directory. As for now it supports only system.img in sgs format, however it automatically extracts it (if needed) from any tar/zip package, also with properly detecting cache.img. This is the main feature I was missing in original kitchen.

https://github.com/JustArchi/Android-Kitchen/commit/cf025ebf6573d23e5d2b7cfde258d9b7c36abd29

Just please don't track "wip" branch, as it's rebased often and merged into master when ready :).
[Android] romuloxiii:
This is great, as I love the kitchen it is awesome that you've updated it. I'll be trying it out tonight. Thanks for your work.
[Android] pendroz:
Great work :good:

Tested New device LG G2 ;)
[Android] Perka:
Looks very good, thanks for updating the kitchen.
[Android] Perka:
Got an error when using the kitchen:

-----------------------------------------------------------------

BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.

-----------------------------------------------------------------

Add BusyBox (y/n)? (default: y):

Found ./system/xbin/su

Found /system/xbin

Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):

Replacing /system/xbin/busybox
Adding /system/xbin/busybox

Error: No update-script found!

Press Enter to continue

Due to that I converted the update-script to edify.
[Android] JustArchi:
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.

This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.

As for now I suggest avoiding conversion before final build.
[Android] Perka:
Thanks.

Also

1. with koush rooting theres no deamonsu in xbin, is this right?

2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?

3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)

Again thanks :)
[Android] JustArchi:
1. That's right, koush doesn't have direct support for su daemon.

2. User should be able to modify this, on todo with many other things...

3. I think we can do it, soon :).
[Android] Perka:
Sounds good :)

---------- Post added at 03:50 PM ---------- Previous post was at 03:44 PM ----------

Donation made :)

4T106212CC7164407
[Android] theresident:
i worked with planty firmwareswith the latest kitchen for my devices but anytime the SuperSu after installation was saying something like "there is a SuperSu, but not Supersu binary installed". that thing was gone after i flash the SuperSu update binary. Does your kitchen gonna give me SuperSu from the start (instalation)?
[General Questions and Answers] randev4:
hello, i have a starmobile engage 8 tablet from Philippines that I was able to root. i guess the bootloader is LOCKED, there is NO RECOVERY, and I can't install one. usb debug mode is unfortunately DISABLED without thinking that my tablet will have problems. when i restarted the phone, it showed me splash screen/starmobile logo then followed by a blank screen. after around 5 minutes, it restarts and then same thing happens.

what can be done in this case? please help!:crying:
[General Questions and Answers] Albraxes PH:
keep trying to fix it!

I feel your pain, I have the same unit with a different issue but my temporary fix might help you.

Rooted my phone and installed a game(was in the middle of copying a file to the obb ), forgot to activate modded play store and restarted the tablet trying to do a quick modded play store install. after the stupid move My tablet now keeps restarting and stops after the star mobile logo and restarts again and it just keeps restarting.

What I did is I randomly press the following keys to attempt finding the safe mode: home+volup, home+voldown, pow+volup and etc... I finally found the safe mode and did a factory reset which did nothing to fix the restarts. Try not doing this!

Then I pressed and hold both volume keys when the star mobile logo shows up and the red star mobile logo turns blue completing the boot process for some reason starting the tablet.

As of today my engage 8 still does the infinite restart if I restart it but I can bypass it with the method. Hope it helps you.

Planning to do a cache/dalvik cache wipe when my research is done to try and fix this tab, good luck to me...
[General Questions and Answers] randev4:
thanks for your reply...:) what i thought was that starmobile technicians do not want to share the key combinations. and im glad that you figured it out. can you remember that specific combinations you used? :confused:so that i can try then...
[General Questions and Answers] randev4:
just so you know, i sent the unit to star mobile for repair and they managed to fix it. unfortunately i made the same mistake so i just dumped it.
[General Questions and Answers] Ciprum:
There are only a few buttons on the phone. I mean, if you have 3 buttons, there are 3 combinations.

Assuming your phone has 3 buttons try:

Power + Volume Up

Power + Volume Down

Power + Volume Up + Volume down

If your phone has 4 buttons also try:

Power + Vol Up + Home

Power + Vol Down + Home

Power + Vol Up + Vol Down + Home

NOTE: Press ALL the buttons and hold in the same time.

NOTE2: Try the combinations in the order from top to bottom
[Nexus 4 Q&A, Help & Troubleshooting] Wassupdog:
Hello.

Since I can't load color profile in the FKU for some reason, I guess I need to check it manually.

I saw that the phoneix gamma profile are really good but I can't find it anywhere.

Help please?
[G2 Q&A, Help & Troubleshooting] vPro97:
Does it get hot?
[G2 Q&A, Help & Troubleshooting] revan17:
Not really, no. Only time it gets hot is during games, but I hardly ever play games and it never rebooted during games. I doubt it's temperature related.
[G2 Q&A, Help & Troubleshooting] revan17:
Any other ideas?
[Galaxy Note GT-N7000 General] NoteboyTech:
Hey guys, so as my warranty was about to get over, I thought of taking my note to them and get a service, I needed to get an update! they actually downgraded my phone, which happened for good, I always complaint about subway surfers hanging and frame drops, but after they flashed it (not via Odin) the problem was gone, it is not like I haven't done it my self, I have flashed almost each and every firmware from 2.3.5 to 4.1.2 via Odin and that problem arose always,

they gave my device back to me in 25 minutes due to lot of S4's in the line! btw I am really happy with the samsung support service, I live in Faridabad, Delhi, India the service center was good, they told me to calm for 15 minutes, I even checked my IMEI and I did not have any change in the IMEI No.

I am happy!

Thanks!

-

P.S. you can all post your service center experiences here!
[HTC One SV] hydraprime:
Hi all,

Can anyone provide a step by step guide on how to root the phone after the 4.2.2 OTA update?

I need root so that I can shift apps to the external SD. Right now I can only shift apps from the phone memory to the phone internal SD card, which is full already..and i can't even load whatsapp images now

I am using LTE version of the phone in Asia (Singapore)

Kernel 3.4.10-g47d5073root@abm016 #1 SMP PREEMPT

Baseband 1.1840a.00.05_10.81a.40.23L

Build 3.12.707.2 CL274701 release-keys

Thanks
[HTC One SV] old.splatterhand:
If your phone is still S-On/locked, unlock it at htcdev.com (follow the steps there).

Then flash TWRP Recovery 2.6.3 from here with fastboot.

Now you can boot to recovery and flash Superuser.zip from here.

Reboot, and check if SuperSu is in appdrawer and if root could be granted.
[HTC One SV] hydraprime:
Thanks a lot.

Now there is root on my phone. I tried to use link2sd but it only detects the phone sd card and not my external sd card. I have partitioned my external sd card for apps.

Now it seems that there was not much point in rooting my phone...zz
[Verizon HTC One (M7)] aaronpw0621:
So somehow my HTC One m7vzw was wiped completely of everything from the ROM, system and data to recovery image, etc. Now I cant access the developers options to turn USB Debugging on. Is there anyway to recover from such an ordeal?? HELP PLEASE !!!!!!:(:(:(
[Verizon HTC One (M7)] mmuzzy:
There is an ADB push option in TWRP which should let you put a ROM on the phone using:

adb push PUTROMENAMEHERE.zip /sdcard/.

or

You should be able to RUU something back onto the phone. Try to get to fastboot by rebooting to the bootloader from TWRP. Then you can use something like:

http://xdaforums.com/showthread.php?t=2485319 Firmware update if needed

http://xdaforums.com/showthread.php?t=2437436 RUU image

or

Alternatively, if you have an OTG cable you should be able to select a flash drive as a source media in TWRP.
[Verizon HTC One (M7)] thatsonlyme:
I had a similar issue a few days ago when I wiped everything including my internal storage without even thinking how am I going to get the rom.zip back on the card (all my previous phones had SD cards).

In order to avoid flashing RUU I used sideload in TWRP to load rom directly through ADB. the only issue I had was with the drivers because for some reason my PC wouldn't recognize the phone (even though I used the same PC to root it) so I downloaded universal drivers that I found somewhere on the XDA.

unfortunately I don't have the links saved but if you search sideload and universal drivers I'm sure you'll find it.
[Verizon HTC One (M7)] jpradley:
To activate Developer Options, go into Stettings, then About Phone, then find Build Number. Press Build Number seven times.
[Verizon HTC One (M7)] brholt6:
You must have misread his post. Everything was wiped. There is no way to go to settings, etc. There is no rom.
[Verizon HTC One (M7)] selayan:
Your options are to boot it to the bootloader manually by holding power and volume down, then go to fastboot and push a recovery to it, from there you can also push a Rom to your storage and then use recovery to install your Rom.
[Verizon HTC One (M7)] aaronpw0621:
I tried installing a couple recoveries. A new TWRP and also CWM Recovery(hoped that worked since was the most recent recovery I used.
[Verizon HTC One (M7)] selayan:
Once you have a recovery on there now just push a Rom using fastboot. Then boot into recovery and install Rom or if you already have a Rom on the internal storage just boot recovery and go from there.
[Verizon HTC One (M7)] aaronpw0621:
When I try using adb sideload in twrp the progress bar just keeps spinning.
[Verizon HTC One (M7)] selayan:
Instead of side load can't you push a rom through the pc in fastboot? Drivers on your pc may not be working properly with sideload.
[Verizon HTC One (M7)] aaronpw0621:
I have nothing on internal. Like I said all is wiped
[Verizon HTC One (M7)] bregga:
you can try

You will need to reboot to recovery and enter fastboot

not sure if this is exact so research it lower case and caps are needed the way they are done in tuts i used copy and paste then edited

enter command prompt window change to where your adb stuff is

fastoot devices if you get a response with sn great

fastboot oemRUU

fastboot flash zip imagename.zip where imagename is the rom you want to put on

for recovery it is like

fastboot flash recovery imagename.zip where imagename is your custom recovery
[Verizon HTC One (M7)] aaronpw0621:
Well I got it to get into recovery. I ended up using a HTC ONE all in one kit. So I got a stock like ROM and radio and firmware to get me going. Thing is now is when I try to sideload any ROM I keep getting stuck in either a bootloop or at the Boot Image. I still have SuperCid. I tried using the how-to on changing "mid" so that way I can use any variant ROM. But apparently I dont have a way to re-zip files :( So now going trying to sideload CM10.2 with GAPPS. Thing is is what I do sideload I cant find in storage. I just cant figure out why a few ROMS I had before now wont boot past the boot animation or just wont flash. PLEASE HELP
[Verizon HTC One (M7)] bregga:
how did u make out with cm 10?

just checking in
[TouchPad Q&A, Help & Troubleshooting] Gil1957:
I tried to install TWRP from Goo Manager. After when the Touchpad rebooted, I had lost my ClockworkMod and there was no TWRP item. The only recovery left was WebOS recovery. Any suggestions?

Thanks
[TouchPad Q&A, Help & Troubleshooting] Moody66:
Extract the zip and place the uImage.TWRP into the boot folder. Delete uImage.Clockworkmod if it's there. Then reboot.
[TouchPad Q&A, Help & Troubleshooting] vishnumrao:
Is there any instructions on how to install CWM or TWRP recovery? I installed milaq's build using instructions in this thread: http://xdaforums.com/showthread.php?t=2542353

But someone I don't have the CWM or TWRP installed. As a result, in the moboot menu, I can't see a reboot into recovery and can't install any updates either.
[TouchPad Q&A, Help & Troubleshooting] Moody66:
I just answered that in the above post. Unzip the install zip. Name the image file.... In your case uImage.TWRP copy it into boot folder.
[TouchPad Q&A, Help & Troubleshooting] woodytrain:
/boot is possibly too full

Either choose CWM or TWRP and remove one or the other (be sure to employ the recovery specific to the ROM... see the specific ROM thread for more info)

You can use 'Root Browser' in ROM Toolbox Lite app (to copy, paste, move, delete uImage files from the recovery zips to or from /boot)
[TouchPad Q&A, Help & Troubleshooting] zoser42:
If /boot has adequate then you may want to to copy the TWRP installer zip file into the /cminstall folder in WebOS and use ACMEInstaller on your PC to reinstall it.
[Nexus 5 Q&A, Help & Troubleshooting] Pain-N-Panic:
So I've read the tutorials by Chainfire and Chronium. I really don't have any need to flash a custom ROM at the moment but root access is pretty much a necessity for me with any device. I plan on using Chainfire's auto-root to root my phone. However, is it alright to have my phone rooted on stock ROM and later down the road when I'm ready for a custom ROM to unlock the bootloader and load TWRP? Or will I run into trouble? The only reason I ask this is because after reading Chronium's tutorial in the stickies, he first goes through the process of unlocking the boot loader and loading a custom recovery and THEN goes into the option of rooting. Does it matter if I root before unlocking boot loader? Coming from the g2x, I never had to mess with the boot loader unlocking so I'm a little nervous about this. Thanks for the help.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
You cannot root without unlocking the bootloader

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Nexus 5 Q&A, Help & Troubleshooting] Pain-N-Panic:
So chanfire's auto root won't work unless I unlock the boot loader first?

Or will cf-auto-root also unlock my boot loader?
[Nexus 5 Q&A, Help & Troubleshooting] mistahseller:
I recommend this way http://xdaforums.com/showthread.php?t=2507905

Better just to get it over with now incase you want to load different ROMS later

When you unlock the bootloader it wipes everything!

---------- Post added at 10:27 AM ---------- Previous post was at 10:27 AM ----------

I don't know will it? use link above
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
It will unlock the bootloader...

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

-----------------------

Sent via tapatalk.

I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
[Nexus 5 Q&A, Help & Troubleshooting] Pain-N-Panic:
Sweet, appreciate your input rootSU. I read this from the auto-root thread, "CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root." If I feel like flashing a custom ROM....will this rooting method be sufficient?
[Nexus 5 Q&A, Help & Troubleshooting] wantabe:
Need a custom recovery to install/flash any roms.
[Nexus 5 Q&A, Help & Troubleshooting] Pain-N-Panic:
Yeah I'm aware of that. I was just wondering if this root tool-kit will provide me with problems down the road. Either way I decided to go ahead and just root,unlock and install TWRP all manually through ADB and fastboot.
[Nexus 5 Q&A, Help & Troubleshooting] cmstlist:
If you ever want to root or ROM later, unlock the bootloader now. All root methods require this. If you relock, then in the future you'll have to wipe your phone.

But it's OK to leave your phone with stock rooted and stock recovery as long as the bootloader is still unlocked. If later you ever lose root or need to install custom recovery from outside the OS, you can do it in fastboot.
[Nexus 5 Q&A, Help & Troubleshooting] Pain-N-Panic:
This is exactly what I plan on doing. In the process now actually. Just unlocked boot loader now I'm installing custom recovery and then rooting the device...I figured since I got the phone 2 days ago I might as well do this now and wipe the device since I barely have anything on it at the moment.
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
any root toolkit can/will provide issues at some point. the biggest issue will come because you dont learn anything from it. many newbies that use root tool kits later cant/dont know how to preform basic maintenance and later think they bricked their device. in reality, for any nexus device, its easiest to do things the proper way instead of a root toolkit. for any nexus this is the procedure..

1. fastboot oem unlock via fastboot. this unlocks the bootloader.

2. fastboot flash a custom recovery.

3. flash the su binaries(supersu) with your new custom recovery.

4. reboot and enjoy.

this is it for ANY nexus device.