Database Users

Help Needed... Think I Bricked my Nexus S

Greetings,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I rebooted the phone. This morning, I tried to restore the superuser permissions by following the steps I found here on xda but after running the terminal script I rebooted my phone and when my phone wouldn't boot beyond the Google screen.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
I can't access clockwork recovery from the bootloader.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamaratee
__________________
Phone: Nexus
Rooted with problems

This post might help:
http://forum.xda-developers.com/showthread.php?p=9866675
It has the adb commands on how to replace the existing boot loader with cwm and all.
Hope it helps.
EDIT: If all else fails, you can try flashing a nandroid backup (2.3.3). This post would guide you:
http://forum.xda-developers.com/showthread.php?t=979851

Greetings Cygnum,
Thanks for the suggestion. I have a question: will these commands work on a Mac?

Thank you to AllGamer for suggesting that I post this question here and for the following suggestion:
AllGamer said:
please post the same question in QA or General, then we can all help you
PM is not the best place to ask for help.
The first thing to do is to download the full set of Android SDK 2.3+ for MAC
then we'll continue from there.
Click to expand...
Click to collapse
How do I proceed AllGamer? I downloaded the mac SDK from here (http://developer.android.com/sdk/index.html).

Follow steps 1-7 from here to get back Clockwork Recovery.
http://forum.xda-developers.com/showthread.php?t=878446
If your bootloader is already unlocked, you can skip those steps.
Do steps 8-9 to copy this file over to your USB drive.
http://devsforandroid.com/ip.board/index.php?/files/file/94-stock-deodexed-233-voodoo-rooted/
This rom is Master's Stock 2.3.3 ROM that is already rooted which should get you up and running.
Unmount, go back. Wipe system data, wipe cache. Go to advanced, Wipe Dalvik-cache.
Go back, choose to install zip from SD card. Locate Master's stock ROM. Flash that.
In the end, you'll have a stock deodexed rom that is rooted. Keep in mind that you will lose all your data, but that at least puts you back on track.

Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.

peeturr said:
Also wanted to mention if you didn't already know, mac scripts are run with a "./" in front of them. So to use the adb command you would do something like, "./adb reboot bootloader" after you have changed your directory to the folder that contains the sdk files.
Click to expand...
Click to collapse
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.

krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Yeah my bad. Just whatever had worked for me. Pretty new to mac myself.
Sent from my Nexus S using XDA App

krohnjw said:
I feel bad for being a stickler here, but this is only true if he has not added the location of the binaries to the PATH. ./ just specifies to start in the local directory rather than look to the PATH to search for the file, it's not a requirement for running a script.
Click to expand...
Click to collapse
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.

kenvan19 said:
Doesn't ~/ do the same as well?
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
Click to expand...
Click to collapse
No. ~/ specifies your home directory

Thanks Everyone
Thanks for all the suggestions and help I received. I PM'd KenVan and he provided me with the script and my Nexus S is up and running.

I just had this problem on the weekend I could not get past the lockscreen so I flashed cyanogen nightly and bam booted fine
Sent from my Nexus S using XDA App

Problem Solved Over the Weekend
Thanks for the help everyone. I posted this in a couple places, so I forgot to update this thread.
I fixed the problem with detailed steps from KenVan. Thanks again though to all of you for your suggestions.

Moving a file with terminal emulator

I really need some help with moving a file to system/app
Not good at this kind of stuff.
Its in the root of my SD card
Sent from my SGH-T959 using XDA App

Code:
su
mv /Removeable/MicroSD/file.whatever /system/app/
Easy peezy
sassafras

Hahah thanks. Another easy question, any way to turn wifi off when you put in sleep mode? Big battery saver. Thanks
Sent from my SGH-T959 using XDA App

gobluewolverines4 said:
Hahah thanks. Another easy question, any way to turn wifi off when you put in sleep mode? Big battery saver. Thanks
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Go to settings -> wireless and networks -> wifi sleep policy
sassafras

Ok...noob here..what is the purpose of making at app a "system app"?
And then another question comes to mind; can you go back and make one of those system apps just a regular old app?

rpavich said:
Ok...noob here..what is the purpose of making at app a "system app"?
And then another question comes to mind; can you go back and make one of those system apps just a regular old app?
Click to expand...
Click to collapse
System apps are essentially going to be 'firmware' because unless you're rooted (which is not by design) they cannot be modified. If you make an app a system app, it theoretically can run better, though that is debatable, it will survive factory wipes and cannot be accidentally deleted. What you lose though is the ability to upgrade it in the market.
In all, it's not really necessary 90% of the time. The easiest way to make an app a system app, if you're interested, is to use Titanium Backup Pro. Not only will it copy the .apk over, but it will reassign the permissions of its /data folder as well.
sassafras

Thank you very much Sassafrass....that was informative.

sassafras_ said:
Code:
su
mv /Removeable/MicroSD/file.whatever /system/app/
Easy peezy
sassafras
Click to expand...
Click to collapse
Ive attempted this from the /sdcard/ and /Removable/MicroSD/
both attemps fail with a msg of "cross device link"
And suggestions???

Drukan said:
Ive attempted this from the /sdcard/ and /Removable/MicroSD/
both attemps fail with a msg of "cross device link"
And suggestions???
Click to expand...
Click to collapse
Cross device link occurs when you're attempting to move a file across storage devices due to the way mv works (it only rereferences the inode, not moving the actual data). Instead, use cp to copy it to the sd.

LightI3ulb said:
Cross device link occurs when you're attempting to move a file across storage devices due to the way mv works (it only rereferences the inode, not moving the actual data). Instead, use cp to copy it to the sd.
Click to expand...
Click to collapse
Exactly.
More specifically though, the mv binary included with android. The GNU mv tool included in any modern linux can tell if the data needs to be moved to different mounted devices and will do it if need be.
sassafras

Deactivate the screenshot button

Hello dear Samsung Tab Lovers ;-)
I have a question for the touchwhiz firmware of the Samsung Galaxy Tab 10.1.
Can someone tell me how to deactivate the screenshot button in the task bar?
I just hate this button cause I always accidently press it.
Is there a way to get ride of it??

The same question
Thanks!

uninstall screencaptureservice.apk via root explorer (system/app) or titanium backup

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

Can this be done using adb commands?

paradoxni said:
Can this be done using adb commands?
Click to expand...
Click to collapse
Just do it via root explorer. Its on sale for.99 cents today from amazon. Its a one day sale, so get in on it, its a must have app...
Sent from my Galaxy Tab!

task650 said:
uninstall screencaptureservice.apk via root explorer (system/app) or titanium backup
Click to expand...
Click to collapse
When we delete iit, will the menu icon slide over or will there be a gap?
Sent from my Galaxy Tab!

mroneeyedboh said:
When we delete iit, will the menu icon slide over or will there be a gap?
Sent from my Galaxy Tab!
Click to expand...
Click to collapse
The button will still be there, just won't take the screenshots
Sent from my GT-P7510 using xda premium

paradoxni said:
Can this be done using adb commands?
Click to expand...
Click to collapse
You can get titanium backup free in the market. It will allow you to uninstall screencapture. You need root for it as well as for root explorer.
Sent from my GT-P7510 using xda premium

Thanks for the suggestion and I can stop those stupid screen capture !

You don't need to uninstall it with Titanium Backup, just freeze it. I have no idea what mad scientist at Samsung thought there was the dying need to make screenshotting an ever-present feature button.

paradoxni said:
Can this be done using adb commands?
Click to expand...
Click to collapse
It can be done using adb.
I'm assuming that the system apps are located in /system/app/ like my phone (I don't have a tab yet, though hopefully I will soon).
If that is true then a
Code:
adb rm /system/app/screencaptureservice.apk
should remove it. I have an inkling that there might be some capital letters in there (Like I said, I dont have the tab so I cant check), if the above code gives you an error about the file not being found type
Code:
adb ls /system/app/
which will show you the list of all files in /system/app/ and change part of the first code to reflect any capital letters.
I would suggest not deleting the file but renaming it or moving it somewhere (so it can be restored afterwards. Both are done with the same command mv (short for move)
The following code would rename the file and add renamed to the beginning:
Code:
adb mv /system/app/screencaptureservice.apk /system/app/renamedscreencaptureservice.apk
Or alternatively:
Code:
adb shell
cd /system/app/
mv screencaptureservice.apk renamedscreencaptureservice.apk
Whether renaming/moving or deleting I suggest rebooting after completing the task.

This will be great for my not-so-tech parents Tab, they would be so confused by the false "screenshot" screen if they would be pressing this endlessly.

Worked great thanks, don't know why this button exists.

Overly complicated since there's a setting in (ICS) it to change it: Settings -> Display -> Quick launch.
Sent from my Nexus S using xda premium

On my ICS rom which is based on the stock touchwiz, in settings>display>quick launch. You should be able to change what the button does or to remove it completely. Hope this helps if you have the same options.

scoffyburito said:
Overly complicated since there's a setting in (ICS) it to change it: Settings -> Display -> Quick launch.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Turned out to be pretty simple. Thanks a bunch!

New to NC; Whats the hot setup?

Hey all!
I am new to the NC community, but have quite a bit of experience working with my Samsung Fascinate. I have some minor themeing experience.
Just ordered a NC from ebay for 119 and was curious what sort of setup (ROM, KERNEL) etc are stable and working well?
What OC is stable?
Is Honeycomb worked out as fully functional?
I have done some sticky reading, and I would like to just make a bootable sdcard, and leave the Emmc alone for now.
What are the recommendations?
Thanks!

CM7 is definitely the best for this. Honeycomb did not have access to the sources and so was more of a demo.
We hope that ICS may make it onto the NC one day but for now CM7 gives a really good stable experience.
You can choose to use the latest stable CM 7.1 or choose to use one of the late nightly builds. There has been an issue with what is called SOD (Sleep of death) where the device occasionally doesn't wake up from sleep and needs a reboot. This was an issue even with 7.1 on some devices. It now appears to have been solved but requires an extra patch which should make it into a nightly soon.
Installing onto a boot SD or emmc is both easy tasks and there are plenty of guide material on this. If you are going to boot from SD make sure you use a Sandisk card (e.g. a class 4 16 or 32GB). These give much better performance when used in this role over other brands.
If you end up primarily using CM7 and not reverting to stock then I would say it is worth going full emmc. It is easy to revert to stock if you ever need to. Running from emmc gives more overall memory and makes management and back up more straightforward.
Most Nooks OC fine up to 1300 and remain stable. The boost in performance is fairly dramatic. For some reason some graphics benchmarks peak at 1200MHz and get worse if the OC is pushed higher. I guess the GPU may end up clocking lower if the main clock is pushed too far.

Thanks BOB!
I had used CM7.1 on my fascinate, but it was a short stay as it wouldn't play nice with wifi at my house. Hopefully that's not the case with the NC.
How is MIUI on the NC? From what I see it has done pretty good. Do you have any particular experience with it?
As far as kernels, what are the stable ones by name?
I have plenty of experience of writing ROMS to the internal memory with CWM so I shouldn't be too far off if I need to do that, or choose to go that route.

If you use cm7 can you still use the stock Nook Reader? or what is the reader of choice?

I believe you can only use the Stock reader in the Stock ROM. There is a standard Nook App for Android but it is not the same. Works OK for your standard reading etc but not as nice as the stock reader.
If you want to use the Stock Reader and CM& then I think your choices are ...
1) Run CM7 on the SD card and boot into Stock whenever you want to use the Stock reader.
2) Make a Stock ROM set up on a SD card, Install CM7 on emmc and reverse the procedure of 1.
3) Install a dual boot Stock and CM7 off the emmc. At start up you then choose whether to boot into Stock or CM7 and the SD card remains fully usable as data.
I did use method 3 for a while when I first started with Nook but I so rarely went into stock and I don't really need to access the stock reader that I gave up and redid the emmc as full CM7.
I did try MIUI out but I ended up reverting to standard CM7 really just to keep compatibility with other CM7s I use.

Advantages of Internal Dual boot over SDcard boot?
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles

charles_w said:
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
Click to expand...
Click to collapse
I personally would stay away from dual booting on emmc. It plays with your internal partitions which is not a good idea. I would keep stock on emmc and the newly released 7.2-RC1 on SD. By making one simple change to stock you can have both systems share the 32GB card and not have to take the card out ever. The boot menu of CM7 makes it very easy to boot between the two.
Sent from my Nook Color running ICS and Tapatalk

Thanks for the reply.
leapinlar said:
By making one simple change to stock you can have both systems share the 32GB card
Click to expand...
Click to collapse
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles

charles_w said:
Thanks for the reply.
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
Click to expand...
Click to collapse
It does have advantages, you don't have to worry about SD card switches, etc. I was just saying it is non-standard and risky to your partitions. One of the partitions, (2) is vital to your system (it has your serial #, etc in it) and since you have to write to the partition table to accomplish dual boot, you risk the possibility of corrupting it as you are setting up dual boot. But a lot of people have done it with no problem.
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file. But there are plenty of rooting threads that tell you how. You can even unroot after you have fixed the file if you want. The other way is to change the file on your PC using adb. Both methods take a little extra effort, but it is worth it to not have to swap SD cards all the time. Both systems then share the SD card storage area. By making this change, I know of no advantage to dual boot and it is much safer (and you already have the SD set up).
And you use the boot menu to select which operating system you want to boot to. That comes with CM7. (But you know that having run CM7 for a year).
Sent from my Nook Color running ICS and Tapatalk

found the link for sharing sdcard
leapinlar said:
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file.
Click to expand...
Click to collapse
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles

charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmx to be rooted.
Charles
Click to expand...
Click to collapse
good job!
Sent from my Nook Color running ICS and Tapatalk

charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
Click to expand...
Click to collapse
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
The free version of ES Explorer allows mounting system as r/w.

Little update....
I have found that the best setup I have found so far is CM 7.2 RC1 (03042012) with V6 (Update 9 RC6.9) supercharger set to option 9 (super 1000HP) supercharge (link for the V6 is on Mr666's page). The ICS transitions included in RC1 are swift and with the supercharger everything is super smooth. I can say I have noticed a small increase in my battery life as well. I toyed around with the UV/OC settings and returned to the sleep of death's I was getting on 7.1. So I re-flashed and just have left everything set to default in the peformance settings that comes with 7.2. So far, no SOD"s and I have a very capable tablet.

leapinlar said:
The free version of ES Explorer allows mounting system as r/w.
Click to expand...
Click to collapse
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
You don't need to mount it where racks said. You can mount it in /data, which you should be able to make r/w. Where it says /mnt/nooksys, substitute /data/nooksys. First go to /data with es explorer and manually create the nooksys folder (you need to set your home directory to / in es explorer before you can see /data). Then follow his steps except don't do the mkdir command since you did it manually. And wherever it says /mnt substitute /data.
Edit: you need to modify the mount command, it now needs to have appended to the end, -t ext4. - Scratch that. It's only necessary if you are trying to do it from CM9. CM7 works OK as written.

I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
What is the -o in the line for? And you manually created the folder first? And you did check the root button in settings?

All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"

Sherip said:
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Click to expand...
Click to collapse
After you created the folder, did you check it. By that I mean open it? It should be an empty folder. Exit out of the folder, but leave Es explorer open. Use the home key to get back to home screen so you can open terminal. I don't know much about es, maybe it has to stay open to keep root access.
Edit: the :not found error is saying it cannot understand the mount command. Are you using all lower case? Very important. Terminal does not like upper case.

Need to get CWM Nandroid off of my phone. Can't find in mnt, data, backups... WTF!?

I've read all of the similar threads, can't find it in mtn/shell, data/ only has starbucks and titanium, backups folder. Between Storage, SD, 0/, emulated, and legacy folders, something's gotta be hiding.
When I boot into recovery I'll find it in the restore options, but I need it off of the phone to flash to a replacement device. Any help?

I'm going through the exact situation /;
Sent from my Nexus 4 using xda app-developers app

theedon323 said:
I'm going through the exact situation /;
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can use Root Explorer to go to /data/media or use adb shell and then run "su" to get root privileges and then the directory will be visible.
The directory is not visible as a normal user and need superuser permissions.

I LOVE THIS MAN/WOMAN. I'd like to give you a present. A hard written card. A bumper. A piece of chocolate.
gauravsri said:
You can use Root Explorer to go to /data/media or use adb shell and then run "su" to get root privileges and then the directory will be visible.
The directory is not visible as a normal user and need superuser permissions.
Click to expand...
Click to collapse

Do I need the blobs? Never seen em before...
FishFan319 said:
I LOVE THIS MAN/WOMAN. I'd like to give you a present. A hard written card. A bumper. A piece of chocolate.
Click to expand...
Click to collapse

FishFan319 said:
Do I need the blobs? Never seen em before...
Click to expand...
Click to collapse
Yes, you need to copy the blobs as well as backup directory.
From what I understand, Backup directory is now very small in size and backups are done incrementally by pointing to blobs (which are the actual data).