One click root - Nexus S General

So I can't root my nexus s I don't know why I have had all the great androids since day one but this baby wont budge. Will any of those one.click apps work never tried one?
Sent from my Nexus S using XDA App

dskyers said:
So I can't root my nexus s I don't know why I have had all the great androids since day one but this baby wont budge. Will any of those one.click apps work never tried one?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There's no one click method I know of for the Nexus S.
What do you mean you can't root & it won't budge? This phone is about as easy they come (without some one click app): http://forum.xda-developers.com/showthread.php?t=931865
Install the android sdk on your computer.
Put the su.zip file on your sdcard partition of the phone.
Put the phone in fastboot mode.
Fastboot flash the recovery.
Select recovery.
Select install zip from sdcard.
Flash it.
Reboot.
You're done.

If your computer doesn't recognize the phone while it's in the bootloader, you gotta install the google Nexus S drivers or the one from PDAnet. That was where I got stuck at 1st when I tried rooting. Fastboot couldn't find my phone because I had the generic windows drivers.

Also if you have PDANet on, turn it off before putting your phone in fastboot mode.

Actually there is a one click method...brb with it
http://www.theandroidsoul.com/easy-one-click-root-for-nexus-s-full-guide/
Or search superboot nexus s
Here on xda
Either will work PC or mac.
Sent from my Nexus S using XDA App

vapor311 said:
Actually there is a one click method...brb with it
http://www.theandroidsoul.com/easy-one-click-root-for-nexus-s-full-guide/
Or search superboot nexus s
Here on xda
Either will work PC or mac.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Interesting. So the steps on the referenced one-click method you posted are:
1) put your phone in fastboot
2) do the fastboot oem unlock command manually.
3) run a batch file that contains two lines (fastboot-windows.exe flash boot boot.superboot.img & fastboot-windows.exe reboot).
I guess that's easier than putting your phone in fastboot directly and typing in a command to flash clockwork, then selecting a zip file to install from clockwork, but not much.
The drawbacks here are of course that it's superboot, and that it requires you to unlock the bootloader. I guess it's useful if you're really noob, but it only saves you typing one command.

The noob part is very true. However I prefer my bootloader unlocked anyhow.
Sent from my Nexus S using XDA App

vapor311 said:
The noob part is very true. However I prefer my bootloader unlocked anyhow.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Why do you prefer it unlocked?

I like the unlocked lock! No seriously custom roms etc.
Sent from my Nexus S using XDA App

main reason i think there is no one click root is because its so simple to do on this phone

vapor311 said:
I like the unlocked lock! No seriously custom roms etc.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You do not need an unlocked bootloader (currently) to use custom roms, or to root, or to flash clockwork recovery, etc...

On day one that wasn't a known entity.
Sent from my Nexus S using XDA App

vapor311 said:
On day one that wasn't a known entity.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Of course, but since you contradicted my statement earlier that one disadvantage to the posted method here was that it had you unlock the bootloader by replying that you like having yours unlocked, I was trying to pin down if there was an advantage to unlocking the bootloader that had been discovered that I hadn't heard yet.
There's indication on git for our phone that the next update includes a change to the bootloader being able to use the fastboot boot command while locked. Unknown what that will actually do in terms of just fastboot flashing clockwork to apply root and custom roms.

I c wut u did there. I'm not sure how the update is going to affect things ATM. I keep it unlocked for "in case sh*t" happens. Never know what an update will bring in changes to rom management.
Sent from my Nexus S using XDA App

Related

Strange Root Issue

When I saw the port for ICS come out I got really excited and flashed it right away. Then I realized for whatever reason I didnt have SU permissions so I couldn't tether to my computer. I was disappointed but I thought, "no biggie, I'll just restore from my back up." When I flashed my back up the SU app was in my app drawer but I still couldn't tether. As a matter of fact I can't do anything that requires SU but the bootloader still reads unlocked. WTF?
I can't flash a new recovery either. I tried installing from ROM manager, I tried pushing it from my computer but I can't get to the recovery any more. ROM manager says that I have CWM 5.0.2.0 currently installed but I can't get to it at all. Again, WTF?
Sent from my Nexus S 4G using XDA App
^clearly the phone is working perfectly fine with the stock ROM from the back up but obviously I want my SU back.
Root your phone and read the development thread versus making blog posts.
Sent from my Nexus S 4G using xda premium
Flash this http://www.tylerwatt12.com/XDA/ics/root_and_theme.zip and please post in right section
Sent from my Nexus S 4G using xda premium
Thanks for not answering my questions. The bootloader is unlocked but I don't have root and I don't have access to recovery mode even tho ROM Manager says I have Clockwork Mod 5.0.2.0 currently installed. I cannot access the recovery mode AT ALL. I cannot flash or push a new recovery but it fully boots into Gingerbread w/o any issues. What is wrong with my phone and how do I fix it.
Sent from my Nexus S 4G using XDA App
Try from rom manager to reinstall a previous recovery version.
Sent from my LG-P920 using XDA App
That doesn't work either. It goes through the prompts but it doesn't actually reboot do the installation.
I just tried unrooting and then re - rooting but that didn't work and I think that actually wiped my phone completely. I don't even know where an SD card would get into this thing.
Sent from my Nexus S 4G using XDA App
Use adb on your computer and push a clockworkmod recovery.img. And we are trying to help u no need for the sarcasm
Sent from my Xoom using xda premium
I'm sorry but I'm just really frustrated right now. Nothing I have tried has worked. Maybe its my commands? To push that recovery image what would I type?
Sent from my Nexus S 4G using XDA App
I also I can't download that zip you linked to. Every time I try it just says failed.
Sent from my Nexus S 4G using XDA App
obsydian2k7 said:
I'm sorry but I'm just really frustrated right now. Nothing I have tried has worked. Maybe its my commands? To push that recovery image what would I type?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I get it
Fastboot flash recovery recovery-xxxxxxxxx.img and hit enter
Sent from my Xoom using xda premium
Esteway.619 said:
I get it
Fastboot flash recovery recovery-xxxxxxxxx.img and hit enter
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Get cwm image from here CWM Recovery
Sent from my Xoom using xda premium
relock the phone then unlock it again i had the same problem
I tried relocking and unlocking again then pushed the recovery I just (finally) downloaded but it didn't work. Terminal says error cannot load 'recovery-clockwork-5.0.2.0-crespo4g.img'
Sent from my Nexus S 4G using XDA App
obsydian2k7 said:
I tried relocking and unlocking again then pushed the recovery I just (finally) downloaded but it didn't work. Terminal says error cannot load 'recovery-clockwork-5.0.2.0-crespo4g.img'
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Is that the right name of the recovery img? Try renaming it to just recovery and see if that works.
Edit: make sure your phone is in debugging mode. And uninstall then reinstall the drivers on your computer
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
Is that the right name of the recovery img? Try renaming it to just recovery and see if that works.
Edit: make sure your phone is in debugging mode. And uninstall then reinstall the drivers on your computer
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
manually go into recovery with volume down and power flash the su.zip and u should be good to go that wat I did
Sent from my Nexus S 4G using xda premium
No suggestions have worked so far. It does not matter what the recovery image name is, whenever I try the flash it Terminal says that it cannot load "***.img" or if I try an install command it says that it cannot find "***.zip" I'm on a snow leopard iMac so I don't need drivers n such.
Let me pose the question like this, what would I do to completely restore the phone to factory condition and try to root it again? Like I said before, the bootloader says that it is unlocked but I do not have any root privileges, could not access the recovery I had before nor install a new recovery after having locked the unlocked the phone's bootloader again.
Sent from my Nexus S 4G using XDA App
http://forum.xda-developers.com/showpost.php?p=13773677&postcount=1
go to the link above and follow the directions for returning to stock.
find yourself a one-click root method on XDA that includes superuser, busybox, and CWM.
EDIT: Also, double check the md5 sum for the CWM .zip. use
Code:
md5 recovery-aaaaaa.img
in the terminal and make sure the output matches whatever is given on the CWM site. if they dont have one up, ask for it
NS4g one-click root app:
http://www.mediafire.com/?2jx8xtx2602hi23
this will:
unlock the bootloader
install cwm 5.0.2.0
root
No commands, no messing with pushing files manually, etc. This thing has already saved me from major headaches while restoring my phone once and I've only had it for 3 weeks lol
hp420 said:
NS4g one-click root app:
http://www.mediafire.com/?2jx8xtx2602hi23
this will:
unlock the bootloader
install cwm 5.0.2.0
root
No commands, no messing with pushing files manually, etc. This thing has already saved me from major headaches while restoring my phone once and I've only had it for 3 weeks lol
Click to expand...
Click to collapse
im assuming this is for windows. he said he has a mac so that wouldnt work for him. here this is for mac http://forum.xda-developers.com/showthread.php?t=1129759 just copy and past everything thats there in terminal
Esteway.619 said:
im assuming this is for windows. he said he has a mac so that wouldnt work for him. here this is for mac http://forum.xda-developers.com/showthread.php?t=1129759 just copy and past everything thats there in terminal
Click to expand...
Click to collapse
I missed that...my mistake

[Q] Which rooting method?

I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Nate2 said:
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash cmm recovery, flash the su binaries, reboot and profit.
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
frozenspark said:
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
AndDiSa said:
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
frozenspark said:
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
then you should br helping out all the people that mess up their devices afyer using toolkits and dont know how to fix it. i havent seen you help out, yet you are still recommending toolkits. why is that?
I used the steps outlined at http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/ to guide me.
I must say it might not be trivial for the non-software-developer types.
I was a Java developer for many years, so I didn't have much problems setting up Java,
Android-sdk, etc.
My N7 was recognized by adb when booted normally, but after I flashed cwm, I could not do 'adb shell' to mount the /system partition and rename the recovery-from-boot.p file to prevent the recovery from getting reset to stock each time.
I ended up installing the ROM Manager app to enable me to boot into cwm recovery.
I have done the obligatory cwm backup. I believe this is the nandroid backup?
Edit:
I used my Linux box to re-flash the bootloader and cwm recovery images to the Nexus 7, and I could 'adb shell' and rename the recovery-from-boot.p file. So I'm all set now.
I just needed to run 'adb start-server' and 'fastboot' using sudo, so it might have been a permissions issue on my Windows box.
Sent from my unrooted DroidX using Tapatalk
I used Wug's Root Toolkit. Both of the toolkits seem good, but that was just the first one I saw. The Wug's Toolkit is an application and the other one is in a CMD.
Sent from my SGH-T989 using xda premium
Linexus said:
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
Click to expand...
Click to collapse
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Use the fastboot commands
Good to see you alright!
This is like asking "Should I get an automatic or manual car?"
veeman said:
This is like asking "Should I get an automatic or manual car?"
Click to expand...
Click to collapse
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Look at these lazy people..
Beamed from my Grouper.
Nate2 said:
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes there was a bootloader bug on the nexus 7 and most people could not boot into CWM recovery without plugging it into their computer.
I however used TWRP back then [have since switched back to CWM touch, now that the bug is fixed] and had no issues. Now I have no issues with CWM touch, I can boot it directly from fastboot menu, or "reboot -> recovery" when booted.
Nate2 said:
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Click to expand...
Click to collapse
exactly what I would have done! sounds like you're getting the hang of it. and yes, I definitely recommend manual rooting/fastbooting to a toolkit.
Wilks3y said:
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Click to expand...
Click to collapse
Yes that's my favorite too. It does it all and more. It slices, it dices, it'll even cut a can!
Nate2 said:
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Click to expand...
Click to collapse
Yeah, that's what I'm saying. They both have their ups and downs. If you're willing to learn a little about how Android works and learn some adb and fast boot commands then you should definitely do it manually.
If you just want to be a "1337 Haxorz" and aren't willing to learn then just use a toolkit.
OK, just one sub-question on rooting. I see no real reason to root except maybe to get more tablet interface than nexus has. Kinda like when the wifi indicator is at the bottom, since there are those !$#$$ back/home buttons already and a lot of wasted space Anyways, the question.
I bougth N7 16Gb and upgraded via forced OTA to 4.1.2. Do all these root methods work with 4.1.2?
Thanx,
D.

Is it possible for me to lock my bootloader?

Is it possible for me to lock my bootloader so I can go send my nexus 4 in for a replacement? My earpiece stopped working! When i dial I can't hear anything the other party can't hear me either! I'm freaking out
Sent from my Nexus 4 using xda app-developers app
yes its possible to lock your bootloader.
use search on how to do so (factory stock images nexus 4)
let me guess.... you used a toolkit?
I didn't I used fastboot method I don't trust toolkits
Sent from my Nexus 4 using xda app-developers app
Raphael17 said:
I didn't I used fastboot method I don't trust toolkits
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you didn't use fastboot then how did you have your bootloader unlocked in the first place?
I'm running stock rom with Franco kernel I want to go stock everything so I can send it in for a replacement
Sent from my Nexus 4 using xda app-developers app
Raphael17 said:
I'm running stock rom with Franco kernel I want to go stock everything so I can send it in for a replacement
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You're not answering my question. If you didn't use the fastboot method OR toolkit, then how did you unlock your bootloader in the first place? I'm asking this to know where you stand (e.g. drivers installed, fastboot environment set up).
It's either or. I already answered your question,
use search on how to do so (factory stock images nexus 4)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
That thread should help you return to stock.
zephiK said:
You're not answering my question. If you didn't use the fastboot method OR toolkit, then how did you unlock your bootloader in the first place? I'm asking this to know where you stand (e.g. drivers installed, fastboot environment set up).
It's either or. I already answered your question,
Click to expand...
Click to collapse
I think he didn't use punctuation/correct grammar, likely a non-native English speaker. It should have read: "I didn't use a toolkit because I don't trust them, I used the fastboot method."
zephiK said:
If you didn't use fastboot then how did you have your bootloader unlocked in the first place?
Click to expand...
Click to collapse
Raphael17 said:
I didn't I used fastboot method I don't trust toolkits
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I believe he missed a comma or 2, should read: I didn't (use a toolkit), I used fastboot method, I don't trust toolkits.
To answer the OP,
Code:
fastboot oem lock
Actually if you run the lock command, then unlock then lock again, the unlock code will wipe everything (internal mSD too) so you will be back at factory settings, assuming you had previously flashed a factory image.
smacksa said:
http://forum.xda-developers.com/showthread.php?t=2010312
That thread should help you return to stock.
I think he didn't use punctuation/correct grammar, likely a non-native English speaker. It should have read: "I didn't use a toolkit because I don't trust them, I used the fastboot method."
Click to expand...
Click to collapse
Or he was educated in the U.S. He is probably a college graduate. I'm from the U.S., by the way.
jakejm79 said:
I believe he missed a comma or 2, should read: I didn't (use a toolkit), I used fastboot method, I don't trust toolkits.
To answer the OP,
Code:
fastboot oem lock
Actually if you run the lock command, then unlock then lock again, the unlock code will wipe everything (internal mSD too) so you will be back at factory settings, assuming you had previously flashed a factory image.
Click to expand...
Click to collapse
Oh you're right on that. I was just checking on which "position" he was in. That makes more sense. Tiredness starting to kick in. Totally missed the "I" between didn't and used.
That forum post is the exact one I was referring to (just wanted him to google it out ) follow that guide and it will lead you to the right place. Don't just lock it and think your phone's good. You have to revert back to stock kernel as well which that forum thread will tell you how to do so.

[Q] [HELP] Can't re lock nexus 4 bootloader!

I have my first android device, the nexus 4, and I rooted it. I used the Nexus toolkit, being new to android and rooting and all. I now need to send my phone back to Google and I can't relock the bootloader! I managed to unroot it but now I just need to relock it and get rid of the padlock. I have tried everything that I have found online and nothing has worked!
I am really becoming annoyed with this! Can anyone help please?!
Thanks, LJ.
It should be an easy thing to do from fastboot. I think the command is something like fastboot oem lock. The toolkit should be able to do this action also. Once that command is complete then reboot fastboot and it should be completed.
Sent from my Nexus 4 using Tapatalk 4 Beta
That is exactly the command.
fastboot oem lock
Sent from my Nexus 4 using xda app-developers app
Being "new to android and rooting and all" is the biggest reason not to use a toolkit. You just press a button, have no to little idea what exactly happens to your phone and then go "pls my phone doesnt work and is eating my cat pls help" when something goes wrong...
Sure, everything seems easier when you use a toolkit, but you end up having no idea what to do when the toolkit fails
Just sayin'.
vanmarek said:
Being "new to android and rooting and all" is the biggest reason not to use a toolkit. You just press a button, have no to little idea what exactly happens to your phone and then go "pls my phone doesnt work and is eating my cat pls help" when something goes wrong...
Sure, everything seems easier when you use a toolkit, but you end up having no idea what to do when the toolkit fails
Just sayin'.
Click to expand...
Click to collapse
this.
and for any nexus device, rooting the right way is just as easy if not easier than a toolkit. the only difference is that youll need to read up a little, get familiar. im mean how easy is this to root..
1. fastboot oem unlock
2. fastboot flash a custom recovery
3. flash either the su binaries or a custom rom
4. reboot and profit.
then to lock the bootloader just fastboot oem lock.
thats all that is needed for any nexus.
I have been using a nexus as well. Download nexus toolkit v2.0 it does it all. I flashed half a dozen ROMs and unrooted and relocked bootloader and re rooted it
Download it and enjoy
Sent from my Nexus 4 using xda app-developers app
abhijitsohoni said:
I have been using a nexus as well. Download nexus toolkit v2.0 it does it all. I flashed half a dozen ROMs and unrooted and relocked bootloader and re rooted it
Download it and enjoy
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have tried using the toolkit v2.0 but still no success I am really becoming annoyed about this!
LJGDY said:
I have tried using the toolkit v2.0 but still no success I am really becoming annoyed about this!
Click to expand...
Click to collapse
Are you getting any commands to work when you are in fastboot? Like fastboot reboot or flashing a recovery img? I'm just wondering if you have fastboot setup correctly. If you can do those other commands, relocking shouldn't be an issue.
Sent from my Nexus 4 using Tapatalk 4 Beta
eqjunkie829 said:
Are you getting any commands to work when you are in fastboot? Like fastboot reboot or flashing a recovery img? I'm just wondering if you have fastboot setup correctly. If you can do those other commands, relocking shouldn't be an issue.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I have also followed efrans guide, step by step, and was typing all commands into the command prompt. The phone was responding too. When I booted it up, I was stock rom again but the boot loader would not lock. Strange! :/
LJGDY said:
I have also followed efrans guide, step by step, and was typing all commands into the command prompt. The phone was responding too. When I booted it up, I was stock rom again but the boot loader would not lock. Strange! :/
Click to expand...
Click to collapse
Follow that guide but instead of entering the first command for returning to stock now just type in "fastboot oem lock"
Sent from my Nexus 4 using xda app-developers app
LJGDY said:
I have my first android device, the nexus 4, and I rooted it. I used the Nexus toolkit, being new to android and rooting and all. I now need to send my phone back to Google and I can't relock the bootloader! I managed to unroot it but now I just need to relock it and get rid of the padlock. I have tried everything that I have found online and nothing has worked!
I am really becoming annoyed with this! Can anyone help please?!
Thanks, LJ.
Click to expand...
Click to collapse
Trickster Mod has an option to Lock/UnLock your Bootloader as long as you are rooted and you use a kernel which supports such extravagances. (i.e.Franco-r210, for example)
I'd recommend getting familiar to fastboot would be the best option, too. If it's not working, what is the exact error or is there none?
You could try this app to lock it, too, if the phone is still rooted

[q] nexus 4 backup

Hi
i stupidly dropped my nexus 4 on the floor and the screen completely smashed, the buttons work fine, but my phone is locked so whenever i connect to my laptop it wont backup my files.
Is there anyway i can backup my pictures and videos?
Any help or suggestions will be greatly appreciated, as i have some memoroable pictures stored on there?
Thanks
mr cazorla
Do you have USB debugging enabled? If so you can pull your picture folder via adb.
Sent from my Nexus 4 using xda app-developers app
NEXUS 4
morbe said:
do you have usb debugging enabled? If so you can pull your picture folder via adb.
Sent from my nexus 4 using xda app-developers app
Click to expand...
Click to collapse
hi
no its not enabled as my phone has not been rooted
phone doesn't need to be rooted to enable usb debugging.
CAZORLA said:
hi
no its not enabled as my phone has not been rooted
Click to expand...
Click to collapse
As goofball2k said, you don't need to root your device to enable USB debugging. In your case though, you can't enable it due to the broken screen.
When your screen is locked and you connect your phone to the pc, does it show the phone? If it does it will probably show no folders inside. Right?
What you need to do is unlock the bootloader, flash a custom recovery and then in the recovery you will be able to use adb pull command.
To do all that you can read efrant's guide (unlock bootloader, flash custom recovery) in this forum, or you can use a toolkit like this guy in your same situation: http://forum.xda-developers.com/showthread.php?t=2177440
I would recommend efrant's guide as it teaches you the basics on how to use adb and fastboot to flash anything you like.
Cheers
Sent from my Nexus 4 using xda app-developers app
Unlocking his bootloader will wipe the device though. He's SOL unless it's already unlocked.
DrFredPhD said:
Unlocking his bootloader will wipe the device though. He's SOL unless it's already unlocked.
Click to expand...
Click to collapse
True, but I think that with "boot unlocker" you can unlock the bootloader without wipe
Sent from my Nexus 4 using xda app-developers app
Another solution would be to make a backup image of the entire phone memory (see the bootloader unlock sticky thread), but he needs to set a password for the desktop backup first.
Morbe said:
True, but I think that with "boot unlocker" you can unlock the bootloader without wipe
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It needs root to work and he can't unlock his device to use an app even if he had root.

Categories

Resources