yashsingh1/xdaforums huggingface dataset:
[Nexus 5 General] jaj473:
This is a step by step guide to root Nexus 5

PLEASE MAKE A BACKUP of your files on your internal storage.

Unlocking bootloader will ERASE EVERYTHING.

Download the file below

http://d-h.st/YGm

Step1: go to Settings->About Phone > hit the “Build Number” until you get “You are now a developer”.

Step2: go to Settings->“Developer options and turn ON “USB debugging” .

Step3: Connect the device to computer.

Step4: For Windows,we need to install drivers.

Right click on My computer and select Manage and select Device Manager

you should see something like nexus 5,

now double click on that and select update drivers..

choose Browse my computer for device software > let me pick from a list > select install from disk >set path to usb_driver file in

extracted folder.

Now you should see something like Android ADB Interface..(do it again if you dont see this)

Step5: Next, open command prompt(win+r > cmd) and type: cd downloads ( or wherever you have downloaded the file to )

cd Nexus5

adb devices

you should get : 'list of devices attached'

some code and " device"

if you don't get this and instead get offline,then check USB debugging is enabled or not and reconnect the device and install drivers again

in device manager(step4)

Step6: Turn off your Nexus 5.Then hold down Volume Down and Power buttons together for 3 seconds until you see the bootloader menu.

Step7: Connect the cable again and open Device Manager and install drivers again( step 4)

This is because you connected the device in another mode and hence pc recognizes it as a new device

Step8: . Go to command prompt and type: fastboot oem unlock

Step9: Go to your Nexus 5 screen and use Volume buttons to select “Yes” and hit the Power button. This WILL ERASE EVERYTHING

and unlock the bootloader.

Step10: Your phone reboots and you get the welcome screen like the day you unboxed it..

Step11: Now log in with a account and connect it to computer and copy the UPDATE-SuperSU-v1.65.zip file to internal storage.

Step12: Power off your Nexus 5. Then hold Volume Down and Power buttons together until you see the bootloader menu then connect

USB cable from Nexus 5 to your computer.

Step13: Go to command prompt and type: fastboot flash recovery openrecovery-twrp-2.6.3.1-hammerhead.img (for TWRP)

OR

fastboot flash recovery recovery-clockwork-6.0.4.4-hammerhead.img (for CWM)

Step14: Next, use Volume buttons on your Nexus 5 and choose “Recovery mode” and hit the Power button.

Step15: Once in CWM or TWRP recovery, choose “Install zip from sdcard” or “Install”. (choose “choose zip from sdcard” for CWM.)

Step16: Browse your internal storage and find the file UPDATE-SuperSU-v1.65.zip. Install this file to root your Nexus 5.

Now your Nexus 5 is ROOTED.

Step17: Next, choose “reboot” from main menu of CWM or TWRP recovery.

:good:Your NEXUS 5 is now ROOTED:good:

PLEASE hit the THANKS:good: button if my post is useful
[Nexus 5 General] MisterEff:
I think this already exists. Also you don't need to turn your phone off you can just use the command "adb reboot bootloader"
[Nexus 5 General] AvRS:
This info is already in the sticky post by Chromium, please read first and post second as saves repeat posts: http://xdaforums.com/showthread.php?t=2507905
[Nexus 5 General] jaj473:
This method is a bit easy than those already existing..

And this for those who are new to android with all downloads in one file....
[Nexus 5 General] jaj473:
Ive added all required files into one zip including drivers and hence no need to download android sdk..

This method is easy to follow for beginners.
[Nexus 5 General] gerardoeliazz:
help

i need some help. i can't go pass step 13 because it won't let me install TWRP. help :crying:
[Nexus 5 General] jaj473:
for the command to work, you should first be in the directory...

paste the downloaded Nexus 5.zip on desktop , extract it on desktop, then do the following..

> windows key + r

or

go to start and find "run" and type "cmd"

in command prompt, type

> cd Desktop

> cd Nexus 5

> now type fastboot flash recovery openrecovery-twrp-2.6.3.1-hammerhead.img
[Xperia Z Q&A, Help & Troubleshooting] kcannonball:
I don't know what happened i have a rooted phone and it does not screen off neither automatically nor with the battery save modes ( stamina and low battery mod).. please help..!
[Xperia Z Q&A, Help & Troubleshooting] Dsteppa:
But can you turn it off with your power button?

Look at the screen timeout settings, maybe there is something there that you can change.
[Xperia Z Q&A, Help & Troubleshooting] kcannonball:
screen timeout is set to 15s and the screen continues to remain open until i press the power button to close it.!
[Xperia Z Q&A, Help & Troubleshooting] Ewors:
you should try to reflash thst latest rom, or just do the factory reset. if nothing works then just download any other stable rom and then try to flash again (ofc wipe cache and dalvik cache). its very recommended do the backup before you flash any ROM, so if something happens you could restore your pre-flashed rom/backup
[General Questions and Answers] komjin:
Hello,

I have the following issue:

I have a galaxy s3 (GT-I9300) running [MENTION=3690986]_Sale_[/MENTION]s neatrom lite 5.4 (XXUMJ9, Android 4.3) where I'm really happy with.

Only issue I have is I can't open MP3-files out of solid explorer. It says there is no program to open this files. With video files there is no problem, only mp3.

With the samsung music player app everything is working. I can also open them out of the stock file explorer (crap).

Perhaps anybody have or had the same problem.

I will be very helpfull with every piece of help :)

Thanks in advance

komjin
[General Accessories] winnie1314:
all sold out.
[General Accessories] defroster:
prices please.
[General Accessories] winnie1314:
Please delete my post that we no longer sell in this way.

Please delete my post that we no longer sell in this way.
[Android Software/Hacking General [Developers Only]] daniel_hk:
Before we can take a bite on the new KitKat, some of us may encounter the set_metadata.. error at flashing.

Problem:

The new updater-scritpt use set_metadata and set_metadata_recursive to assign the permissions to the newly copied files.

Most of the existing /system partition doesn't support the "capabilities" option. Script in android/build would assign 0x00 to "capabilities".

However, assigning a "capabilities" with 0x00 to the unsuported partition also cause error!

If you are lucky, you might find an updated custom recovery to solve that.

For those who don't have a workable recovey or don't want to update the recovery yet. Here is a solution

Solution:

I patched the script when building my 4.4 rom for GT-7.7. The included "update-binary" would solve that problem at flashing.

Open the zip of the ROM or gapps. Replace the file in /META-INF/com/google/android with this one.

Now you can flash the 4.4 rom and gapps without an recovery update..

It works for cm11 & aosp based ROMs and gapps.

Cheers!

Edit:

Silly me, how can it be hardware independent... This one is compiled for armv7. Different cpu surely need a recompile.:p

Here is the change in the source: http://xdaforums.com/showpost.php?p=47692333&postcount=15
[Android Software/Hacking General [Developers Only]] nomancoolboy:
Thanks dude
[Android Software/Hacking General [Developers Only]] phil_greg2001:
Thanks daniel_hk

It works fine on my SGS :good:

:cowboy:
[Android Software/Hacking General [Developers Only]] ibub:
[MENTION=4948627]daniel_hk[/MENTION]

Thanks for this. But it does not work for my armv6 device (lg p500). Could you please tell us what you changed, so that it can be "ported" to older devices. I have read that some recoveries have merged changes to source, but these devices do not yet have a ported version. So if you have time, this would be much appreciated by my device community. :)
[Android Software/Hacking General [Developers Only]] daniel_hk:
The theory of what I have done is already mentioned in the thread.

In details, I changed the file in the source of the recovery. The update-binary is generated there.

In the function ApplyParsedPerms, when encounter a 0x0 for "capabilities", I drop the flag .

The attached file was from the rom I built.

For ROMs using the CyanogenMod cm-11 or AOSP 4.4 source, it should work.

Send me the link of your ROM which fail. Let me take a look. ;)
[Android Software/Hacking General [Developers Only]] ibub:
Thank you so much. But I may have spoken too soon. I found an updated recovery (4.3), and new update binary for my phone. I will try it later to see if it works, before asking you to waste your time. :)
[Android Software/Hacking General [Developers Only]] ibub:
Ok, I tried but had no success. So here is a link to the rom:

http://jenkins.androidarmv6.org/job/submission-test/755/

Again, thanks. :)
[Android Software/Hacking General [Developers Only]] daniel_hk:
Is your error "set_metadata_recursive"... "fail"? Can you list the exact messages at flash. Take a photo to avoid typing.

I think you might get an assert error not set_metadata related
[Android Software/Hacking General [Developers Only]] ibub:
Yeah, it's set_metadata_recursive error or fail. I think my recovery will copy messages to SD. Will record soon. The devs for this device are now trying to add set_metadata tags in boardconfig.mk, and then use set metadata =false. But I'm not really sure if that would be an actual fix, or just a temporary work around to get it to flash. So I'd rather try to do it your way. Just wish my 32-bit system would compile newer Android. :rolleyes:;)

---------- Post added at 06:37 AM ---------- Previous post was at 06:06 AM ----------

Ok, here's my recovery log. :)

---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------

http://www.mediafire.com/view/?dddwi6vtbo3a1fg
[Android Software/Hacking General [Developers Only]] daniel_hk:
in line 1260:

-> ApplyParsedPerms: removexattr of /system/xbin/su to 0 failed: Operation not supported on transport endpoint

seems the file system doesn't support XATTR, remove a non exsist attr probably cause error.

Did the log come from my update-binary?

If so, you need to tell the rom developer to check the kernel source:

if the kernel support selinux and file system is EXT, you need the following

CONFIG_EXT4_FS_XATTR=y

or

CONFIG_EXT3_FS_XATTR=y

Either one must be enabled dependent on the file system.

If kernel doesn't support selinux, disable it.

For YAFFS, there might be similar config for kernel need to enable or disable

Good luck!;)
[Android Software/Hacking General [Developers Only]] ibub:
No, that was the original update binary, built with the rom. I don't know for certain, but have read that the binary is specific to the chipset. Anyway, I'm gonna search through the commits to see if the xattr has been used. Remember seeing it... somewhere. :confused: Again thanks. :)
[Android Software/Hacking General [Developers Only]] daniel_hk:
I think you haven't try my update-binary. I don't know why you said it fail? :eek:

You better try my update-binary again. "capacities" is one of the xattr. update-binary is just a set of functions calling the kernel's routine to do

things. I don't know who told you its hardware related. I already point you out where in the source creating it. Take a look at that part of the source is what you needed...

It would not waste our time if you have tried.I don't know how to help if you don't try it.

Good luck!
[Android Software/Hacking General [Developers Only]] ibub:
Thank you. I did try with your binary previously. But I will try again with an updated recovery and your binary. And then copy the recovery log again. Sorry for misunderstanding.

---------- Post added at 09:56 PM ---------- Previous post was at 09:08 PM ----------

Ok, I tried again with no luck. And here is the log:

http://www.mediafire.com/view/?hcibdddd1vxtcr3

Again... thanks.
[Android Software/Hacking General [Developers Only]] ibub:
Ok, I don't see any indication in the log as to what caused the error with binary. But I opened it in hex viewer. On line 044f21 the platform is listed as arm v7. I think my arm v6 device cannot use this. Anyway, thanks for helping. I guess I have MORE research to do. :)
[Android Software/Hacking General [Developers Only]] daniel_hk:
Just returned and studied your log. It is not set_metadata fail issue. The update-binary can not run on the devices

I found that p500 use Qualcomm MSM7227 (ARM11) on the web. I can't find the cm11 device tree for p500 nor the kernel source. However, I think the update-binary is not work on the kernel and/or cpu.

The easiest way would be including the following commit and rebuild again: (I simplify it for you, just change one line)

Change the file in (cm11 source):

<cm11 source dir>/bootable/recovery/updater/install.c

in line 694 (under the function ParsePermArgs(int argc, char** args):

694:- parsed.has_capabilities = true;

694:+ parsed.has_capabilities = false;

That is the simpliest way I can think of to fix the set_metadata fail in your device.

Good luck!;)
[Android Software/Hacking General [Developers Only]] ibub:
Thank you so much. I would have never found it. Now I just need to fork the repo, make the change, init repo, build/envsetup sh, sync, add to local manifest, and try to compile. :) ... Or just submit a pull request. That code is interesting. I think I'm gonna learn some more soon. :):):)
[Android Software/Hacking General [Developers Only]] chrisc60:
I have a galaxy SIII (at&t). I have gotten this error instantly when trying to flash a 4.4 rom. Once I replace the aforementioned file with the contents of your zip, won't I need to re-zip the rom and somehow sign it? And if so, do you have a zip "signer"?
[Android Software/Hacking General [Developers Only]] antutu:
thanks :good: working on my tab with CM11
[Android Software/Hacking General [Developers Only]] ADM818:
Thanks bro.
[Android Software/Hacking General [Developers Only]] srelyt:
Ahah too bad I saw the thread only today.

I had this error yesterday and had to waste a lot of time finding a solution. I finally had to flash a stock recovery , a stock system partition and adb sideload the update to resolve it without losing any data.

Sounds like your solution would have been a lot easier, I hope people can see it before attempting more complicated things like me ;)
[Android Software/Hacking General [Developers Only]] daniel_hk:
You don't need to extract the ROM zip file.

Use application like 7z,

1. navigate to the above mentioned folder in 7z

2. drag the attched file (this one need to extract;)) to replace the file inside the zip

That's all and you can flash the rom now.

Good luck!
[Android Software/Hacking General [Developers Only]] xxLeoxx93:
Is this working with armv6?
[Android Software/Hacking General [Developers Only]] dredremon:
i got a bootloop on 4.4

problem solve by this:

go to recovery flash a any kernel that based on stock rom for your phone ( kernel with cwm )

after done flashing go to advance reboot recovery

now you can flash a new rom again

sorry in my english
[Android Software/Hacking General [Developers Only]] feiplane:
hello sir,

is it necessary for a kernel to support selinux in order to make 4.4 based roms work?

or is there any other method to make older/selinux unsupported kernels to work with 4.4 roms?

thx
[Android Software/Hacking General [Developers Only]] sukhjit_bhullar:
Hey its good. I was also finding meta error while updating my nexus 7.i then flashed stock recovery and system then applied ota update to upgrade from 4.3 to 4.4
[Android Software/Hacking General [Developers Only]] daniel_hk:
No. kernel with no selinux support can live with 4.4. In some rom (eg. cm11), The bottom of about would show the status of SElinux.

I have try both enabled and disabled version of my kernel to the same ROM (testing the speed for my own interest). Both perform the same in my 4.4 ROMs.
[Android Software/Hacking General [Developers Only]] feiplane:
err, I mean for kernels totally without selinux, not kernels with selinux disabled or enabled

is this possible?
[Android Software/Hacking General [Developers Only]] daniel_hk:
The answer is yes too. The nexus one 2.6.xx kernel can also implement 4.3 roms and I believe 4.4 too.
[Android Software/Hacking General [Developers Only]] feiplane:
but the 4.4 is selinux enforced isn't it? 4.3 is still permissive if I'm not mistaken
[Android Software/Hacking General [Developers Only]] mukulsoni:
Could you please help to make update binary for armv6 compatible devices especially LG P500... :p

Thanks
[Android Software/Hacking General [Developers Only]] ibub:
Daniel has already told us everything that we need to know to make it work for the p500. Let me get home from work tonight, and we will discuss this via pm. Sorry Daniel. Looks like a feeding frenzy. :)
[Android Software/Hacking General [Developers Only]] daniel_hk:
I'm using a kernel with no SELinux support for my rom now. This is a fact.
[Android Software/Hacking General [Developers Only]] daniel_hk:
To be honest, it is not practical for me to build. I don't have a similar device to test and I can't find any source of cm11 kernel & device tree for p500 on github. Your rom builder have everything ready. He or she can have this done in minutes. Why don't you ask him or her?
[Android Software/Hacking General [Developers Only]] feiplane:
good to hear that:victory:
[Android Software/Hacking General [Developers Only]] Tinchoska:
Downloading let's see if it works

Enviado desde mi Droid RAZR HD mediante Tapatalk
[Android Software/Hacking General [Developers Only]] DaBrinz:
ty ty ty

didnt really want to mess with bootloader. solution worked great. ty :good::good:
[Android Software/Hacking General [Developers Only]] FLY_EAGLES_FLY:
flawless!!

thanks a ton man! finally got 4.4 on my xt926! :D
[Android Software/Hacking General [Developers Only]] KikoLyne:
working on my samsung tab 2 :D

Thank you so mutch bro.

You rock!
[Android Software/Hacking General [Developers Only]] caspboy:
[MENTION=4948627]daniel_hk[/MENTION]

Sorry to blaze you thread, but I got a problem. See I just compiled cm11, which is working fine. But I wanted to add some tweaks to it before I release it. Unfortunately, the updater-script turns out to be in "set_metadata" instead of "set_perm", which I know nothing about. I need to set some permissions for the extra files and folders I've added, and the permissions are:

And some more like that. But I don't want to mess up the updater-script. Can I just add these perms in between or does the updater-script only read "set_metadata" lines?
[Android Software/Hacking General [Developers Only]] ibub:
If I understand correctly, set_perm_recursive statements cause everything within the specified directory to have the same permissions (unless set in an additional statement). That said, I believe that the set_metadata statements do the same thing, and more. Looking at /system/xbin/openvpn in the cm9 rom that I am currently running, the permissions are 755. This is the same as the set_metadata_recursive statement for /system (cm11 on my sdcard). So without another statement, your permission should automatically be 755. Do you really need write access to that binary? Sometimes people give unnecessary access to files. Overkill. Also noticed that kitkat gapps zips do not generally use these metadata statements in their updater scripts. So not everything flashed to /system requires it... I guess. :);):cool:
[Android Software/Hacking General [Developers Only]] ruscook:
Thanks worked great!
[Android Software/Hacking General [Developers Only]] abhi-xiaomi-1s:
i want to install PureKat on my Desire z but isnt installing,

here what i did, (I use ClockWork Recovery 5.0.2.7)

1.backup my current rom (CM 10.1)

2.wipe data/factory reset, cache partition, delvik cache & format system..

4.install zip from sdcard, and select your "pk_vision-2.0-BETA1-20140425.zip"

5.When "Do you want to wipe user data?" comes on Aroma installer, i select both options 2 times, but its not working at all

6.on the "Select Google applications you want to install" step, i click next without change anything

7.same thing i did on Custom Apps step

8.and then its installing...

it shows -

>>>formatting partitions

>>>mounting partitions

>>>cleaning partitions

>>>writing data & system

>>>installing google chrome....etc

>>>Creating toolbox symlinks

>>>Creating additional symlinks

>>>installing busybox

>>>setting permisions

set_metadata_recursive:some changes failed
[Android Software/Hacking General [Developers Only]] KGB1021:
Question

Will this metod work if i have a lg g2 d802, i wanted to flash a rom (cloudyflex) and got this error Set meta data........

You mentioned that

that is because i am asking you! Thanks
[Android Software/Hacking General [Developers Only]] daniel_hk:
It won't flash in different cpu so it's quite safe.

Try to get the lastest recovery first. TWRP normally works and no need to modify.

Don't sent KGB agents if doesn't work... :D

Good luck!
[Android Software/Hacking General [Developers Only]] KGB1021:
Don't worry I won't send no body! :P

Is it enough to update the TWRP 2.6.3.3 to 2.7.0.0?

And one off topic quetion, what would you do if you have a LG G2 D802 with imei nuber 0, but i can make call,connect to mobile internet etc. ??

Running CM 10.2.

Thakns
[Android Software/Hacking General [Developers Only]] ibub:
Edit: Yes twrp 2.7 should work.

That's probably just a bug in the rom. Probably does not know where to read that information to display. Rest assured. If you have network, your imei is intact. :)
[Android Software/Hacking General [Developers Only]] showcheap:
Thanks it's works :good:
[Android Software/Hacking General [Developers Only]] wodeking:
Great Help

Wow..this this is great. I had my S2 semibricked and nothing was working even some professionals said they are not able to flash. I could flash CyanogenMod after changing this file in the zip file. Really a huge help.

Thank you so much.
[Android Software/Hacking General [Developers Only]] Roars21:
THANK YOU! Been wondering why my HTC One X that I have lying around would not flash a new ROM... :) Brilliant!!!
[Android Software/Hacking General [Developers Only]] troll_warhead:
I faced the same error while flashing PAC ROM on Xperia L and after updating the binary, it finally flashed successfully. (even the gapps) But then when I rebooted, nothing happened. No logo or boot animation. The device will not boot up. Any advices? Where am I going wrong?

CWM version used: 6.0.5.0

PAC ROM version: 20141214

Gapps: Kitkat mini latest one

P.S. I tried the whole procedure once again and after flashing the ROM and gapps, I wiped data and dalvik cache..still the same result..
[Android Software/Hacking General [Developers Only]] brilliant_smart:
works great
[Android Software/Hacking General [Developers Only]] Annoyingmouse:
thanks you so much,you saved my phone from a bootloop
[Android Software/Hacking General [Developers Only]] petera703:
For me it made the updater fail with error 4 instead of error 7.

However, this was a ROM I'd flashed before on this phone, so I was already puzzled to think it might need this fix. So I was looking for other causes too.

In case it helps others hitting the error 7 issue and not helped by the update-binary fix: what I found was that removing the SD card allowed me to flash the ROM without any errors. (Unmounting it didn't help--I had to physically remove it.)

Obviously I then had to sideload, but since TWRP can sideload, no problem.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] monkey10120:
So after I flashed the update everything was fine and preformed great until last night when I unplugged. I woke up this morning and had 60% battery. The most battery used was Android os. And I don't know why. Here is the screen shot. Any help would be nice because the battery just plummeted over the last few days.