Database Users

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

Nexus 7 Boot Looping

Hey everyone, I joined xda to see if someone could help me with my problem. So recently I rooted my nexus 7 using wugfresh's root toolkit. I then installed aokp after i tried out paranoidandroid......i flashed gapps each time. I then wanted the old tv style screen off animation and using that toolkit, so i extracted the framework-res.apk ...........and i don't know what went wrong. Now all i can do is boot into the bootloader. When i try to go to recovery, it shows an open android with a caution sign in it. it just keeps bootlooping the aokp animation. I can't find any solution....help! i just want to go completely stock and lock the bootloader. it wont work with wug's toolkit.

Are you plugged in to your PC using the USB cable?

Yeah. Using the OEM cable from Asus. It charges and everything.....what do I do? I'm stuck and stressing about it.
Sent from my SCH-I510 using xda app-developers app

AndroidNinjaReview said:
Yeah. Using the OEM cable from Asus. It charges and everything.....what do I do? I'm stuck and stressing about it.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?

AndroidNinjaReview said:
Hey everyone, I joined xda to see if someone could help me with my problem. So recently I rooted my nexus 7 using wugfresh's root toolkit. I then installed aokp after i tried out paranoidandroid......i flashed gapps each time. I then wanted the old tv style screen off animation and using that toolkit, so i extracted the framework-res.apk ...........and i don't know what went wrong. Now all i can do is boot into the bootloader. When i try to go to recovery, it shows an open android with a caution sign in it. it just keeps bootlooping the aokp animation. I can't find any solution....help! i just want to go completely stock and lock the bootloader. it wont work with wug's toolkit.
Click to expand...
Click to collapse
reflash your recovery via fastboot, not with a toolkit. then reflash your rom/gapps. if its still a no go, wipe then reflash your rom/gapps.

CharliesTheMan said:
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?
Click to expand...
Click to collapse
The message I get is error: device not found when I use the adb reboot recovery. And I'm not familiar with it at all. I was trying to get that TV off animation and I was following a guide. This is my first root. So far....not a good experience.
Sent from my SCH-I510 using xda app-developers app

simms22 said:
reflash your recovery via fastboot, not with a toolkit. then reflash your rom/gapps. if its still a no go, wipe then reflash your rom/gapps.
Click to expand...
Click to collapse
Can you tell me how to do this without the toolkit? I'm lost....
Sent from my SCH-I510 using xda app-developers app

help!
CharliesTheMan said:
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?
Click to expand...
Click to collapse
Please help! I need this fixed asap and it seems like you know exactly what to do! Aghh. Im stressed...this is my first tablet andi just want it to work :crying:

AndroidNinjaReview said:
Please help! I need this fixed asap and it seems like you know exactly what to do! Aghh. Im stressed...this is my first tablet andi just want it to work :crying:
Click to expand...
Click to collapse
So i think all i need to do is flash the factory image. how would i go about doing this?

HELP! I think I bricked my nexus 7. [SOLVED]

After i tryed flashing kaos droid i think ive managed to brick my nexus 7. It just boots into cwm v6.0.1.0. Ive tryed a number of times holding down the power and the volume buttons together and i CANT get into the bootloader ): . No matter what i do it just boots into the recovery even if i flash another rom it goes back to cwm. I dont know what to do please help? I cant even shut the screen off its been in cwm for over 3 hours now \:
And i was rooted and unlocked before this. Tab was working fine till i flashed kaos droid
Sent from my myTouch 4G Slide using Tapatalk 2

Just use recovery to restore your backup.
Sent from my Nexus 7 using xda premium

This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.

The toolkit does everything for you. All in one method and you're done.
I'm sure its his .img
Sent from my Nexus 7 using xda premium

I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
Sent from my Nexus 7 using xda premium

El Daddy said:
I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
I will try using the toolbox but i dont think i have access to fastboot from the recovery? I mean im telling you guys my screen has been on for over 4 hours because it just reboots and wont turn off.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
When i get home. To my computeer im going to try using the toolkit hopefully it works
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem on my og evo. Try seeing if you can flash the recovery from a computer while booted into cwm. Then it'll reboot into new recovery, you flash rom, and you stop sharding your pants

nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader

kieso said:
This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.
Click to expand...
Click to collapse
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2

El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2

On a side note, i had tryed everything i formated the sd in cwm and now it appears on cwm as if theres "No files found" but on my computer everything i had previously is still there.
So there is a connection to the storage part of the device but not adb or fastboot
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Hmmm. You should have a working adb while booted into a custom recovery. Are your drivers installed correctly?
Also, the reason why you computer sees the files is because with mtp it caches the files.
Sent from my Nexus 7 using xda premium

El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
So far i got adb to work finally! Happy im making some progress.
Now im able to boot into the bootloader so i can run fastboot commands. I currently have NO rom whatsoever installed so im waiting to flash the stock rom using the toolkit. Thank you for your help
Also when i booted into twrp it said i had 3% battery left lol so im just hoping it will work now.
Sent from my myTouch 4G Slide using Tapatalk 2

OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?

Mach3.2 said:
OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?
Click to expand...
Click to collapse
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2

nemesis93 said:
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium

El Daddy said:
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yeah i tryed at first because i was lazy and it didnt work so i did it through fastboot.
Thanks again
Sent from my myTouch 4G Slide using Tapatalk 2

Glad you got it working

nemesis93 said:
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Sorry I wasn't trying to bust your stones. I haven't rooted yet because of all of the posts like yours. I've just seen more problems with flashing on this device then any other that I have with my past Droid devices. What we really need is apx (spelling?) Drivers and n7 files for a sure fire recovery from any disaster

Hopefully I don't have to start another thread.
I too think I bricked my Nexus 7.
I was having trouble and I accidentally cleared a file from the System UI app (its a system required app) which caused me to loose the 3 buttons on the bitten of the screen.
So I went to CWM to do a restore which said it failed.
After that it would not boot.
Its just stuck with the Google logo on the screen.
I held down the power up & down volume buttons and I get a screen that gives me that START button on the top right of the screen with the text in small size on the bottom left.
I can use the up and down volume to make the start button change to recovery mode or bootloader but activating them just goes to Google logo.
Can I recover or is it totally lost?
I also don't remember if I left the Nexus 7 in Debug mode which is usually required to perform custom Roms
Thanks
Rob
Sent from my SPH-D710 using Tapatalk 2

[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.

Enable USB Debugging in Recovery Nexus 4

So I managed to break the digitiser on my Nexus 4 last weekend. I have most things off it anyway but there are a couple of apps I need to run to get the data I need. I would like to be able to use android screencast to run the couple of apps or use it to set up my bluetooth mouse so I can use that as the screen itself still views fine. However, I need to enable USB Debugging in regular operation.
My phone is rooted, has CWM as the recovery and I have the ADB platform tools downloaded to my mac. This for a Nexus 7 is the closest I have come to an answer of how to do it. However, I can't find these files so I guess they are somewhere else to change these settings?
Any help would be much appreciated, thanks!

If you have cwm, not into recovery and use adb to pull files you want off your device
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you have cwm, not into recovery and use adb to pull files you want off your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I can't seem to find build.prop to be able to edit it. I can find default.prop but when I do adb pull /system/build.prop it doesn't work just says 'does not exist'.

mike_dangerous said:
I can't seem to find build.prop to be able to edit it. I can find default.prop but when I do adb pull /system/build.prop it doesn't work just says 'does not exist'.
Click to expand...
Click to collapse
In your recovery, I use twrp, mount system. It should work then.
Sent from my Nexus 5 using XDA Free mobile app

Works! Brilliant thanks! Hopefully the rest of this works!

So I have managed to Brick my phone into a boot loop of the cyanogenmod startup symbol. What can I do now?
Can someone confirm what the file permissions should be for settings.db and build.prop?

mike_dangerous said:
So I have managed to Brick my phone into a boot loop of the cyanogenmod startup symbol. What can I do now?
Can someone confirm what the file permissions should be for settings.db and build.prop?
Click to expand...
Click to collapse
Permissions should be rw-r-r. There's always the factory image to flash. You're not bricked!
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Permissions should be rw-r-r. There's always the factory image to flash. You're not bricked!
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
OK so I'm stuck how do I flash a factory image then? And I can't wipe my data or else the exercise is moot. Is there a way I can flash an image with the USB Debugging I require enabled? That would make my life much much simpler!

mike_dangerous said:
OK so I'm stuck how do I flash a factory image then? And I can't wipe my data or else the exercise is moot. Is there a way I can flash an image with the USB Debugging I require enabled? That would make my life much much simpler!
Click to expand...
Click to collapse
This going to get some what experimental but it won't wipe your date. I assume your bootloader is unlocked Just flashing the factory image will wipe your data but.... Download the factory image and extract it using winrar or 7-zip. Inside is a zip file, extract that too. You should find a system.img file in there. Flash that in fastboot
fastboot flash system system.img
Hopefully that'll get you past the boot loop
Edit, I'd forgotten that I made this. It'll get you up and running too. http://forum.xda-developers.com/showthread.php?p=533289
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
This going to get some what experimental but it won't wipe your date. I assume your bootloader is unlocked Just flashing the factory image will wipe your data but.... Download the factory image and extract it using winrar or 7-zip. Inside is a zip file, extract that too. You should find a system.img file in there. Flash that in fastboot
fastboot flash system system.img
Hopefully that'll get you past the boot loop
Edit, I'd forgotten that I made this. It'll get you up and running too. http://forum.xda-developers.com/showthread.php?p=533289
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Your link doesnt seem to work?

mike_dangerous said:
Your link doesnt seem to work?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks a lot, I have now successfully unbricked my phone, enabled usb debugging and through a series of key strokes turned on bluetooth and connected my mouse. However, somewhere in the process I appear to have lost all my app data which was the points of trying to get in there in the first place. What could have done this? All my data e.g. photos is there but my SMS are gone!

mike_dangerous said:
Thanks a lot, I have now successfully unbricked my phone, enabled usb debugging and through a series of key strokes turned on bluetooth and connected my mouse. However, somewhere in the process I appear to have lost all my app data which was the points of trying to get in there in the first place. What could have done this? All my data e.g. photos is there but my SMS are gone!
Click to expand...
Click to collapse
You most likely wiped the data partition while trying to fix the bootloop.

Would the data partition not be where everything else is stored?

Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Is this image modified so that USB debugging is ENabled?
Background: I'm in the same situation as OP. Broken screen/digitizer, USB debugging is DISabled, unlocked, rooted, CWM recovery. I need to ENable USB debugging, otherwise I just keep getting told "error: device offline".

theman5511 said:
Is this image modified so that USB debugging is ENabled?
Background: I'm in the same situation as OP. Broken screen/digitizer, USB debugging is DISabled, unlocked, rooted, CWM recovery. I need to ENable USB debugging, otherwise I just keep getting told "error: device offline".
Click to expand...
Click to collapse
If you boot into recovery and then type adb devices is it still offline? It shouldn't be. You can recovery data while in recovery if that's what you're trying to do
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app

Yes, when I attempt to run adb while in recovery I still get told that the device is offline.
Not sure what the best solution is. I was thinking about trying to flash a modified factory image that is already set up to have USB Debugging Enabled because I can probably flash that without wiping data. However, I don't know if such images exist or, if necessary, how to make my own.
Clearly the OP got around it but I can't seem to be able to and I'm not sure what to do.

theman5511 said:
Yes, when I attempt to run adb while in recovery I still get told that the device is offline.
Not sure what the best solution is. I was thinking about trying to flash a modified factory image that is already set up to have USB Debugging Enabled because I can probably flash that without wiping data. However, I don't know if such images exist or, if necessary, how to make my own.
Clearly the OP got around it but I can't seem to be able to and I'm not sure what to do.
Click to expand...
Click to collapse
I would start by flashing a twrp recovery in your current cwm recovery. I.know you don't need usb debugging checked in trwp.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I would start by flashing a twrp recovery in your current cwm recovery. I.know you don't need usb debugging checked in trwp.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well I'll start there and keep you posted. Thanks!

I was able to get TWRP running as my recovery. When I run adb, my device appears as "recovery", however, I'm not able to access the "build.prop" file to edit it so I can ENable USB Debugging. I think this is because I'm not able to remount "system" as read/write. Not sure what my issue is, but when I run adb root, it claims to be already in root, however when I run su in adb shell, it claims it can't find su. Any ideas?