I have a LG nexus 5 and started playing around with software, Installed cyanogenmod to see what it had to offer.
Now I want to go back and I have succeeded in that but when I type fastboot oem device-info in cmd it says that the device has been tampered with.
I have access to Android toolkit PRO for nexus 5 so if anyone can give me a short guide step by step I would be very thankful.
For your information I have tried alot of different solutions none seem to work.
1.1 unlock fastboot
1.2 fastboot flash a recovery
1.3 flash the tamper fix zip
1.4 fastboot flash back to stock
1.5 check status
1.6 lock fastboot
Sent from my Nexus 5 using Tapatalk
nevermind
rootSU said:
1.1 unlock fastboot
1.2 fastboot flash a recovery
1.3 flash the tamper fix zip
1.4 fastboot flash back to stock
1.5 check status
1.6 lock fastboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quickest answer I've gotten ever.
Where can I D/L the recovery and tamper fix?
Rest I will manage. Ty
senseiblaze said:
Thanks for the quickest answer I've gotten ever.
Where can I D/L the recovery and tamper fix?
Rest I will manage. Ty
Click to expand...
Click to collapse
It's all in HERE for you, steps you need to take plus how to reset the tamper flag.
radicalisto said:
It's all in HERE for you, steps you need to take plus how to reset the tamper flag.
Click to expand...
Click to collapse
Thank you guys!
radicalisto said:
It's all in HERE for you, steps you need to take plus how to reset the tamper flag.
Click to expand...
Click to collapse
So still the same problem. It says in CMD That there's no such file or directory and it cant find twrp.img
senseiblaze said:
So still the same problem. It says in CMD That there's no such file or directory and it cant find twrp.img
Click to expand...
Click to collapse
Then you're doing it wrong. You need to type the path to the recovery. So if it's in c drive
fastboot flash recovery c:\twrp.img
Or if it's on your desktop
fastboot flash recovery c:\users\senseiblaze\desktop\twrp.img
Also note, the file must be called twrp.img. if it's called recovery.img, adjust your commands accordingly. It's also Case sensitive.
All basic stuff that every rooted user should know
Sent from my Nexus 5 using Tapatalk
Instead of flashing the twrp recovery boot from it.
Fastboot boot recovery recovery.img
Because as far as I can remember flashing that zip will also lock the bootloader.
rootSU said:
Then you're doing it wrong. You need to type the path to the recovery. So if it's in c drive
fastboot flash recovery c:\twrp.img
Or if it's on your desktop
fastboot flash recovery c:\users\senseiblaze\desktop\twrp.img
Also note, the file must be called twrp.img. if it's called recovery.img, adjust your commands accordingly. It's also Case sensitive.
All basic stuff that every rooted user should know
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Bro, it says cannot open file or cannot determine image filename
No such file or directory :S
senseiblaze said:
Bro, it says cannot open file or cannot determine image filename
No such file or directory :S
Click to expand...
Click to collapse
Screenshots please
Screenshot 1... Cmd prompt, the error and what you typed
Screenshot 2... Windows explorer open to the directory where you saved your recovery please
Sent from my Nexus 5 using Tapatalk
rootSU said:
Screenshots please
Screenshot 1... Cmd prompt, the error and what you typed
Screenshot 2... Windows explorer open to the directory where you saved your recovery please
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Here's a Pic with both of them in one, lol.
Better resolution and u can zoom in I believe : http://postimg.org/image/f7srtnc05/
senseiblaze said:
Here's a Pic with both of them in one, lol.
Better resolution and u can zoom in I believe : http://postimg.org/image/f7srtnc05/
Click to expand...
Click to collapse
Your phone is booted into fastboot, right?
What is output of "fastboot devices"
Sent from my Nexus 5 using Tapatalk
rootSU said:
Your phone is booted into fastboot, right?
What is output of "fastboot devices"
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It is booted into fastboot yes. What do you mean by output of fastboot devices?
I'm from Sweden so I rly didn't understand what you meant by that last sentence
Also I noticed your file is called "TWRP.img" but the file directly above it is called "setup". Usually I would expect it to be "setup.exe" which means that you probably have the "hide extensions for known file types" set in windows explorer > organize > folder options...
If you turn this off, I'm hoping you'll see that you actually have TWRP.img.img which is of course, incorrect
Sent from my Nexus 5 using Tapatalk
rootSU said:
Also I noticed your file is called "TWRP.img" but the file directly above it is called "setup". Usually I would expect it to be "setup.exe" which means that you probably have the "hide extensions for known file types" set in windows explorer > organize > folder options...
If you turn this off, I'm hoping you'll see that you actually have TWRP.img.img which is of course, incorrect
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hahahahahaha! You sure are special. I've been sitting here trying to solve this all day long. gives my soul peace to know that I can do this now.
Last but not least. THANK YOU!!! :victory:
rootSU said:
Also I noticed your file is called "TWRP.img" but the file directly above it is called "setup". Usually I would expect it to be "setup.exe" which means that you probably have the "hide extensions for known file types" set in windows explorer > organize > folder options...
If you turn this off, I'm hoping you'll see that you actually have TWRP.img.img which is of course, incorrect
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Seems like a lot of novice users make this same mistake. Perhaps a note of caution should be added to the guides?
Related
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
mrnexus said:
I Having a problem when everytime I go into fastboot mode and click on recovery the /!\ comes up and would have to take the battery out and reflash the custom recovery image thru adb. Then it will work but can someone help make the recovery image stick
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There is a .sh file that needs to be removed, totally forgot the location of it :/
/etc/install-recovery.sh needs to be deleted or renamed.
It's a "safety" feature in 3.3.1 and above to restore the stock recovery if it doesn't pass a check on boot each time.
This is pointed out in numerous threads...search a little for more details if you need them.
Ok thanks
Sent from my Nexus S using XDA App
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
mrnexus said:
It wont let me rename so I guess I going to delete it
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
distortedloop said:
Are you mounting the /system partition as read/write?
Use root explorer or similar or issue the remount command from the command line before trying to rename it.
Click to expand...
Click to collapse
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
EDIT: Nevermind, I used root explorer and was able to find "mount r/w" and rename it finally. Thanks.
godzigga said:
I am having problems renaming it as well. I'm not sure what you mean by "use root explorer or similar or issue the remount command from the command line before trying to rename it.
I have tried using Astro and Android Mate to rename the file and both will not let me.
Click to expand...
Click to collapse
Because those won't allow you to modify system files. Get Root Explorer, like he said, and use that.
AllGamer said:
that's the trick just rename the image, and the CW recovery will stick
that's the way it's written in the step by step guide,
Click to expand...
Click to collapse
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
sarge363 said:
Cause u probably used ADB to get it to stop reflashing the stock recovery. Using root explorer is the same thing only less technical.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
True, I used adb, spent like 2 hour trying to get the pc drivers to recognize the nexus. I used the PDAnet drivers eventually.
vaust said:
weird, i don't remember renaming anything besides the clockwork image to recovery.img . Still able to boot into clock after each reboot.
Click to expand...
Click to collapse
Are you on a custom ROM like CM or Bionix? They remove the script that rewrites stock recovery.
If you're on stock, what version of it are you on? 2.3.1 and higher have a file called /etc/install-recovery.sh on them, and if that's there it should be reflashing stock on every boot, whether you renamed the image you flashed to recovery or not...
unlocked my bootloader running official stock
would like to lock it so i can upgrade and flash a rom.
i saw this thread : http://forum.xda-developers.com/showthread.php?t=1675312
but the only problem is that i didnt save my original files
so the question is, how can i relock my bootloader ?
I believe the command for it was fastboot oem lock but please check the q and a section the answer is there
Sent from my HTC One X using Tapatalk 2
The_Zodiac said:
unlocked my bootloader running official stock
would like to lock it so i can upgrade and flash a rom.
i saw this thread : http://forum.xda-developers.com/showthread.php?t=1675312
but the only problem is that i didnt save my original files
so the question is, how can i relock my bootloader ?
Click to expand...
Click to collapse
The only original file you need is the Unlock_code.bin. They emailed this to you, that's the only way you can get the file. So if you did not delete the email, you can just go and download it again from your email. If you did delete it, it's most likely still in your email's trash bin.
BTW you do not need any original files to relock. Just boot back into fastboot usb mode and do as they said in the thread "fastboot oem lock"
I still have the file that htc emailed me. But in the instructions it list needing to move 2 other files to the android folder you create.
So basically just move the unlock.bin to that folder and follow the instructions as normal?
Sent from my HTC One X using xda premium
Are you talking about these 3 files adb.exe, AdbWinApi.dll, fastboot.exe? Really he shouldnt have said to move them. You can leave them where they are at. On your PC navigate to C:\Android\platform-tools and they should all be there still. Look and see if they are. If they are not, then I can send them to you.
If they are still there, then you just navigate to that directory in CMD prompt and follow his instructions. Where he says to navigate to C:\Android you instead navigate directly to C:\Android\platform-tools in cmd. Does that make sense?
NguyenHuu said:
Are you talking about these 3 files adb.exe, AdbWinApi.dll, fastboot.exe? Really he shouldnt have said to move them. You can leave them where they are at. On your PC navigate to C:\Android\platform-tools and they should all be there still.
Click to expand...
Click to collapse
I never had a directory called C:\android\platform-tools. I could not get any fastboot commands to work without having those 3 other files in the same directory as the Unlock_code.bin I was trying to push. Which is why I told them to put them together, to avoid the same issue I was having.
freshleysnipes said:
I never had a directory called C:\android\platform-tools. I could not get any fastboot commands to work without having those 3 other files in the same directory as the Unlock_code.bin I was trying to push. Which is why I told them to put them together, to avoid the same issue I was having.
Click to expand...
Click to collapse
if you update your SDK to the latest you will see. Everyone should update their sdk once every month or so. you put your unlock file in that folder too, it's same instructions they tell you, but instead of moving those files out, you keep them there and you move your unlock file in. so you don't break the SDK for future stuff.
NguyenHuu said:
Are you talking about these 3 files adb.exe, AdbWinApi.dll, fastboot.exe? Really he shouldnt have said to move them. You can leave them where they are at. On your PC navigate to C:\Android\platform-tools and they should all be there still. Look and see if they are. If they are not, then I can send them to you.
If they are still there, then you just navigate to that directory in CMD prompt and follow his instructions. Where he says to navigate to C:\Android you instead navigate directly to C:\Android\platform-tools in cmd. Does that make sense?
Click to expand...
Click to collapse
I never had that folder created if you could send them to me that would be awesome
Sent from my HTC One X using xda premium
The_Zodiac said:
I never had that folder created if you could send them to me that would be awesome
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
sure you can download it here http://www.mediafire.com/?dn8py7ww4rsbi5e
Just extract it to the same folder in that other thread then to keep it simple.
NguyenHuu said:
sure you can download it here http://www.mediafire.com/?dn8py7ww4rsbi5e
Just extract it to the same folder in that other thread then to keep it simple.
Click to expand...
Click to collapse
Thanks for the help I'll give it a shot when I get home from work
Sent from my HTC One X using xda premium
I have followed everything to a 't' and took the jb image 'renamed it' to (basically took out jb and kept 'recovery' and '.img') IS THAT CORRECT?
and when I ran the command for the image recovery it says image not found.
I even tried TWRP image and renamed... Same problem-
I know I posted some stupid stuff and I apologize - i have read a lot more into rooting and figured a lot out, but this is am @ a loss... Not sure what else to...
I plead for help
ganggreen777 said:
I have followed everything to a 't' and took the jb image 'renamed it' to (basically took out jb and kept 'recovery' and '.img') IS THAT CORRECT?
and when I ran the command for the image recovery it says image not found.
I even tried TWRP image and renamed... Same problem-
I know I posted some stupid stuff and I apologize - i have read a lot more into rooting and figured a lot out, but this is am @ a loss... Not sure what else to...
I plead for help
Click to expand...
Click to collapse
the image file needs to be in the same place that you are running fastboot from. for example i have C:/andriod abd where all my adb/fastboot drivers and .exe and such are and to flash a blob/img file i must put the file in that same folder because thats where fastboot looks for the blob/img.
ide bet money that this is your problem. and what fastboot command are you using? It would be helpful if you could be more descriptive of the steps you have tried
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
the image file needs to be in the same place that you are running fastboot from. for example i have C:/andriod abd where all my adb/fastboot drivers and .exe and such are and to flash a blob/img file i must put the file in that same folder because thats where fastboot looks for the blob/img.
ide bet money that this is your problem. and what fastboot command are you using? It would be helpful if you could be more descriptive of the steps you have tried
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
BTW-THANKYOU soo much for hekping
I will put more information up and pics to help-people see what I see and are doing
I actually made a file folder (I saw it on a YouTube video) and put all of the files needed for the recovery;for example
"rocovery1"=file folder (in c drive) and that folder includes the two(2) adb(.dll) files / the fastboot file (but my 'fastboot' file doesn't have an exe after it) does that matter-/and then of course the image file... ALL OF THAT IS IN A folder I named... should I have not done that? If not where would I find my adb files? Better yet how are they supposed to be listed?
Sent from my Galaxy Nexus using Tapatalk 2
ganggreen777 said:
BTW-THANKYOU soo much for hekping
I will put more information up and pics to help-people see what I see and are doing
I actually made a file folder (I saw it on a YouTube video) and put all of the files needed for the recovery;for example
"rocovery1"=file folder (in c drive) and that folder includes the two(2) adb(.dll) files / the fastboot file (but my 'fastboot' file doesn't have an exe after it) does that matter-/and then of course the image file... ALL OF THAT IS IN A folder I named... should I have not done that? If not where would I find my adb files? Better yet how are they supposed to be listed?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
FYI
Asus uses .blob NOT .img
Even if it's CWM or TWRP (either one would be '.blob') NOT '.img' - either one?
Sent from my Galaxy Nexus using Tapatalk 2
ganggreen777 said:
Even if it's CWM or TWRP (either one would be '.blob') NOT '.img' - either one?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Recovery is through fastboot, and fastboot for asus requires .blob. So yes, its blob irregardless.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
I AM ROOTED!
Sent from my Galaxy Nexus using Tapatalk 2
Hey guys,
I goofed today, and clicked system when wiping without having a backup in my sdcard (whoops). My problem is now, I can't boot the phone (obv) so the phone doesn't show up in windows. I still have access to TWRP, but I need stock zip. I have a stock zip, but I can't transfer it to my phones sdcard.
Other than doing the traditional adt bundle + flashing it the long way, does anybody have any ideas on how I can get the zip file to my phone even though I have no system and it won't show up in Windows 8?
Thanks so much.
Download the Google image from Google and extract the system.IMG
Then go boot loader on phone then type: fastboot flash system system.IMG
That will flash the system back on and you're done.
Sent from my Nexus 5 using XDA Premium 4 mobile app
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
Also you can do adb sidelod to flash a ROM zip file. No need to put it on the SD card.
Sent from my Nexus 5 using XDA Premium 4 mobile app
nxt said:
Download the Google image from Google and extract the system.IMG
Then go boot loader on phone then type: fastboot flash system system.IMG
That will flash the system back on and you're done.
Sent from my Nexus 5 using XDA Premium 4 mobile app
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
Also you can do adb sidelod to flash a ROM zip file. No need to put it on the SD card.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks dude, I ended up fixing this myself. Just used ADB to push a 4.4 stock zip to my phone and flashed through TWRP.
please help
tehdef said:
Thanks dude, I ended up fixing this myself. Just used ADB to push a 4.4 stock zip to my phone and flashed through TWRP.
Click to expand...
Click to collapse
How do you do this please help
I have the same problem (I goofed today, and clicked system when wiping without having a backup in my sdcard (whoops). My problem is now, I can't boot the phone (obv) so the phone doesn't show up in windows. I still have access to TWRP, but I need stock zip. I have a stock zip, but I can't transfer it to my phones sdcard.
Other than doing the traditional adt bundle + flashing it the long way, does anybody have any ideas on how I can get the zip file to my phone even though I have no system and it won't show up in Windows 8?
Thanks so much. ) same with me
sabirchowdhury said:
How do you do this please help
I have the same problem (I goofed today, and clicked system when wiping without having a backup in my sdcard (whoops). My problem is now, I can't boot the phone (obv) so the phone doesn't show up in windows. I still have access to TWRP, but I need stock zip. I have a stock zip, but I can't transfer it to my phones sdcard.
Other than doing the traditional adt bundle + flashing it the long way, does anybody have any ideas on how I can get the zip file to my phone even though I have no system and it won't show up in Windows 8?
Thanks so much. ) same with me
Click to expand...
Click to collapse
Have you phone booted into recovery.
Connect it to your PC
Move the stock zip file into the same folder on your PC as adb.exe
Open the command prompt from that window (shift + right click then "open command window here")
Type the command: adb push nameofzip.zip /sdcard/
(nameofzip being the name of the file you want to push)
It will transfer the file to you internal storage and you can then flash it.
thank you but ...
El Daddy said:
Have you phone booted into recovery.
Connect it to your PC
Move the stock zip file into the same folder on your PC as adb.exe
Open the command prompt from that window (shift + right click then "open command window here")
Type the command: adb push nameofzip.zip /sdcard/
(nameofzip being the name of the file you want to push)
It will transfer the file to you internal storage and you can then flash it.
Click to expand...
Click to collapse
i dont think i even have a sd card it could have gone when i deleted the system
sabirchowdhury said:
i dont think i even have a sd card it could have gone when i deleted the system
Click to expand...
Click to collapse
Trust me, you have an sdcard
Sent from my Nexus 5
sabirchowdhury said:
i dont think i even have a sd card it could have gone when i deleted the system
Click to expand...
Click to collapse
/sdcard is not on /system. Wiping system does not wipe /sdcard
More info here
[ info] Storage: Nexus 5 Data (info / loss / recovery / prevention)
http://forum.xda-developers.com/showthread.php?t=2534010
Sent from my Nexus 5 using Tapatalk
how do you
can someone tell me how to make my device recognized on adb
ive tried installing drivers and the driver which has been installed is a disk drive and i cant install a new driver because i have no system files :crying: :crying: :crying: :crying: :crying: :crying:
sabirchowdhury said:
can someone tell me how to make my device recognized on adb
ive tried installing drivers and the driver which has been installed is a disk drive and i cant install a new driver because i have no system files :crying: :crying: :crying: :crying: :crying: :crying:
Click to expand...
Click to collapse
There is a big sticky thread at the top of q&a about diagnosing USB and ADB.
thread
rootSU said:
There is a big sticky thread at the top of q&a about diagnosing USB and ADB.
Click to expand...
Click to collapse
could you send me a link plz
sabirchowdhury said:
could you send me a link plz
Click to expand...
Click to collapse
No... Its at the top of q&a where you posted this thread. I'm sorry, but if you can't find that...
sabirchowdhury said:
could you send me a link plz
Click to expand...
Click to collapse
Realy dude, use the search buttons in the right corner and Google. This is not a daycare center
rom
thanks i got it to recognize but is it usuall to take so long to push the rom
Hint:
TWRP has USB-OTG- support: you can use a flashdrive ( FAT32 formated (default on 99.9999..%of the devices))
the flashdrive must be mounted (Menu: Mount)
Hi guys
After a few weeks on f2fs i decided to revert back y filesystem to ext4. Everything goes well except sideloading new rom to my device ( as its completely wiped ) Everything is now formated to ext4. Then the problem starts..
When I'm trying to sideload the rom i get error 'cannot read' even though I've put rom in my adb folder and my device is connected in sideload mode.
If someone could help me via team viewer ( free software allowing you to use my PC from yours PC ) it would be super great.
Thanks
When you type adb devices is your phone recognized?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
When you type adb devices is your phone recognized?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
yes
screenshot of my ADB folder and command window
toster jp said:
screenshot of my ADB folder and command window
Click to expand...
Click to collapse
Must give the path to your ROM zip. Your cmd prompt runs from c: \users\koppa but the ROM is not there.
You can't put the ROM in the adb folder. That only works if. You haven't added adb to your environment variable path and you have cd to that location
To get this to work either put the ROM in c: \users\koppa or cd to your adb folder or give the full path in the command
Sent from my Nexus 5 using Tapatalk
trying now
thanks
del.
No, sorry. If you want my help,, you'll have to keep replying in this thread
Sent from my Nexus 5 using Tapatalk
toster jp said:
could you pm me on hangouts? my email is : [email protected]
thanks
Click to expand...
Click to collapse
I don't think rootSU or I are going to pm you. The answers here can help others and it's best to keep them here. Did you put the rom.zip in the folder rootSU suggested?
okay
I just thought that you could help with this via TeamViewer so i could learn how to and you know, not spend another hour or two doing super basic things.
+yes
What directory is your ROM.zip?
Sent from my Nexus 5 using Tapatalk
I'm trying to flash stock 4.4.3
Its placed in a few places... C:/users/kopa/adb C:/users/kopa/desktop C:/users/kopa
toster jp said:
okay
I just thought that you could help with this via TeamViewer so i could learn how to and you know, not spend another hour or two doing super basic things.
+yes
Click to expand...
Click to collapse
A neat little trick with Windows and cmd is to back out of the folder you are in. So, if the path was C:\Users\toster jp\adb, back out to the C:\Users\toster jp folder. Hold shift and right click the adb folder. Select Open command window here. Then, cmd automatically cd to the proper directory. Then your adb sideload rom.zip will work.
toster jp said:
I tried to put my rom everywhere... And still same thing. 'cannot read'
Click to expand...
Click to collapse
Be explicit please
Also don't forget you must enable sideload in recovery
Sent from my Nexus 5 using Tapatalk
Aerowinder said:
A neat little trick with Windows and cmd is to back out of the folder you are in. So, if the path was C:\Users\toster jp\adb, back out to the C:\Users\toster jp folder. Hold shift and right click the adb folder. Select Open command window here. Then, cmd automatically cd to the proper directory. Then your adb sideload rom.zip will work.
Click to expand...
Click to collapse
SOLVED
huge thanks guys
I'm super happy because of that! And finaly I feel like I know how to use adb
THANKS!
toster jp said:
SOLVED
huge thanks guys
I'm super happy because of that! And finaly I feel like I know how to use adb
THANKS!
Click to expand...
Click to collapse
Glad you got it worked out
Sent from my Nexus 5 using XDA Free mobile app