Database Develop

N1's stock internal memory?

My stock internal memory only reads 196mb.is this correct?
Sent from my Sexy Nexy One using XDA App.

Yes it is correct, Nexus One doesn't have much space on internal storage, so if you plan to install lots of apps, you shall consider to use App2SD.

I thought it was 512 internal memory on stock n1?
Yes I do have half my app collections to sd card and still only have 30 internal memory left.
This Really sucks
Sent from my Sexy Nexy One using XDA App.

The entire OS is on that internal storage as well. A lot of apps also store their data on the internal memory, even if they're installed to the SD card. Going through and deleting data on your apps can help for some of the larger apps, but it will erase everything that app knows about you. Definitely a problem.

Try data, dalvik, or cache to SD...
Sent from my Nexus One using XDA App

danger-rat said:
Try data, dalvik, or cache to SD...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
im assuming thats for root users only?my N1 is stock but unless u know of a tool or app to push all data and cache to SD.thanks

Root it and use DarkTremor's Apps2SD.

GHOST99K said:
im assuming thats for root users only?my N1 is stock but unless u know of a tool or app to push all data and cache to SD.thanks
Click to expand...
Click to collapse
I assume you haven't rooted your phone because you don't want to install a custom recovery ROM and lose OTA updates? At least, that was my original line of thinking until the guys here set me straight. You can root your stock without losing OTA updates (I was stock rooted before the FRG83D OTA update that unrooted me .... now I'm rooted again .
Courtesy of pulser_g2's very level headed response to Shivammcool's 7TH thread about the same damn stoopid question, this will root you without needing a custom recovery ROM.
http://jaxov.com/2010/10/root-androi...gle-nexus-one/
Rageagainstthecage FTW!

zuberio said:
I assume you haven't rooted your phone because you don't want to install a custom recovery ROM and lose OTA updates? At least, that was my original line of thinking until the guys here set me straight. You can root your stock without losing OTA updates (I was stock rooted before the FRG83D OTA update that unrooted me .... now I'm rooted again .
Courtesy of pulser_g2's very level headed response to Shivammcool's 7TH thread about the same damn stoopid question, this will root you without needing a custom recovery ROM.
http://jaxov.com/2010/10/root-androi...gle-nexus-one/
Rageagainstthecage FTW!
Click to expand...
Click to collapse
Hey
Sent from my Nexus One using XDA App

I really wanna root but don't wanna get into command or know much Of command.i actually prefer custom roms specially AOSP(only).always love CM6 but full root on n1 is a lil pain for me unless there is a dummy guide.
Sent from my Sexy Nexy One using XDA App.

GHOST99K said:
I really wanna root but don't wanna get into command or know much Of command.i actually prefer custom roms specially AOSP(only).always love CM6 but full root on n1 is a lil pain for me unless there is a dummy guide.
Sent from my Sexy Nexy One using XDA App.
Click to expand...
Click to collapse
I with you
Sent from my Nexus One using XDA App

Shivammcool said:
Hey
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
HAHAHAHAHAHAHA, you made me laugh with your response. Lol, I'm still laughing just thinking about it.
GHOST99K said:
I really wanna root but don't wanna get into command or know much Of command.i actually prefer custom roms specially AOSP(only).always love CM6 but full root on n1 is a lil pain for me unless there is a dummy guide.
Sent from my Sexy Nexy One using XDA App.
Click to expand...
Click to collapse
I like you, you've been around for a while (longer than me ), you're polite, and I like your signature (Long Live Sexy Nexy!).
Sorry, I don't know why the link in my previous post doesn't work (I must have copied the text instead of the link).
http://jaxov.com/2010/10/root-android-2-2-1-frg83-google-nexus-one/
The above link leads to a one-click type root method - no command line work necessary
And as for a dummy-proof guide .. I made myself a cheat-sheet for what I did to root my phone (before and after FRG83D update).
**This is a sketch of what to do only** I'm not providing any user support for the following and you use it at your own risk! (and you'll need ADB setup use it)
Code:
F:\ADB>adb push rageagainstthecage /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb push Superuser.apk /data/local/tmp/Superuser.apk
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb push busybox /data/local/tmp/busybox
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb push su /data/local/tmp/su
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell chmod 700 /data/local/tmp/busybox
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#
#mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,rw /dev/block/mtdblock3 /system
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
#mount -o remount,ro /dev/block/mtdblock3 /system
mount -o remount,ro /dev/block/mtdblock3 /system
# exit
exit
F:\ADB>adb shell
# su
su
# exit
exit

Zuberio thank you so much.i will follow the full root(bookmaked the page) instead of the one click since I love flashing roms.thanks to all for your effort to help.
Sent from my Sexy Nexy One using XDA App.

Just and FYI

I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Code:
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
When I try to do the SU because I get the $ I get Permissions denied.
I know that this method does not work but I wanted to see where it fails. It appears that they may have fixed the glitch that allowed the rage exploit to work.
I also tried cubes other way and it failed as well.
Code:
Open ADB shell
Your command prompt should be "$"
Run
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Just thought I would toss this out there in case someone wanted to know...

Thanks for the heads up on this good info to know when I get my rev on Saturday
Sent from my SHIFTAO5P using XDA Premium App

Haxcid said:
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Just thought I would toss this out there in case someone wanted to know...
Click to expand...
Click to collapse
Mm, I went through that last night, then downgraded to the V4 software as shown by the other post - still, none of it worked for me.

Pull your SDcard out when trying to root after the downgrade. Or format the SD card. It should work then.

Quick question

Quick noob question everyone, if I have an unlocked bootloader and custom recovery, am I rooted? Because busybox and superuser still aren't giving me command prompts. I'm on stock ics
Sent from my HTC PH39100 using XDA

Long story short no your not rooted but you did the hard part already just follow this guide you'll be rooted in under 2 minutes http://forum.xda-developers.com/showthread.php?t=1498003

THANKS!
Sent from my HTC PH39100 using XDA

I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .

MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Adb isn't set up properly or may need to ne run as administrator
Sent from my HTC PH39100 using xda premium

MMVXIII said:
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.
I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.
I've been up and down the Android and Vivid forums on different websites, but can't find the answer.
I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.
Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.
FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.

If you could get back to stick gb, Google zergrush root. Its a tempt root for users who still have their boot loader locked. But in your case, it should be locked.
Sent from my HTC PH39100 using XDA

jigajay said:
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
Click to expand...
Click to collapse
All In One automatically reboots into recovery, runs the batch then responds with "device not found" after each command.
I did try what you said. I booted into bootloader, then ran the perm root from AIO, but got the same "device not found" result.
---------- Post added at 05:46 PM ---------- Previous post was at 05:10 PM ----------
After much reading, booting and rebooting, I managed to get this response from All In One:
C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
* server not running *
C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
349 KB/s (22364 bytes in 0.062s)
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
4800 KB/s (843503 bytes in 0.171s)
C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
However, no still no root. I've kept up to date with the AIO forum. Read the "under construction SuperGuide cover to cover. I have done exactly what many others have, except no joy for me. It appears I may have the only AT&T Vivid in the world that will not root.

http://forum.xda-developers.com/showthread.php?t=1529669
Flash that in boot loader. If it says update presses yes then you're back to gingerbread.
Sent from my HTC PH39100 using XDA

http://forum.xda-developers.com/showthread.php?t=1341162
Use that to root your phone. Follow instructions carefully.
Sent from my HTC PH39100 using XDA

Rooting/unlocking Nexus One with broken power button using Linux terminal tools

I am attempting to get Cyanogenmod onto my Nexus One, but am running into far more problems than expected. The information on rooting Android devices seems heavily fragmented across the web and the tools unreliable. At least in my case, SuperOneClick has proven a complete misnomer. So I'd like to go back to basics - executing as many of the commands as possible from a Linux terminal to get the phone rooted/unlocked/whatever else has to happen to get Cyanogenmod installed. The two constraints I'm working with here are as follows:
1. The device is running Android 2.2.1 (I downgraded from 2.3.x using the PASSIMG method).
2. The power button on the device is broken, so any method which requires pressing/holding it is ruled out.
The problem I am having is that even after following Linux-centric guides, I get to the point of installing the SuperUser app followed by the ROM Manager app, but I'm never prompted to give ROM Manager superuser permissions and so can't flash the ClockworkMod recovery.
Below I describe the steps I've been taking so far, based on the "How To Root Nexus One Running Android 2.2.1 From Ubuntu Linux" guide (Google it, I can't post hyperlinks).
- Download/extract/move Nexus One Softroot files to same directory as adb
- From adb directory, execute the following commands:
sudo ./adb push psneuter /data/local/tmp/psneuter
sudo ./adb push busybox /data/local/tmp/busybox
sudo ./adb push su /data/local/tmp/su
sudo ./adb shell chmod 755 /data/local/tmp/psneuter
sudo ./adb shell chmod 755 /data/local/tmp/busybox
sudo ./adb shell chmod 755 /data/local/tmp/su
sudo ./adb shell cd /data/local/tmp ./psneuter
sudo ./adb shell
After executing sudo ./adb shell as above, I get the # prompt, which is purported to indicate that rooting was successful.
- Still following the guide, I then execute the commands which purportedly make root permanent:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /data/local/tmp
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp su /system/bin
chmod 4755 /system/bin/su
exit
exit
- Again, still following the guide, I execute the commands which purportedly set the /system partition back to read-only:
sudo ./adb shell
su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
- Now, I download the SuperUser app from the Android Market and open it to make sure it's running.
- Next, I download the ROM Manager app from Google Play (looks like it pulled a sneaky and upgraded from Android Market to Google Play here).
- I run ROM Manager and choose Flash ClockworkMod Recovery. I'm prompted to confirm the phone is a Google Nexus One and then ROM Manager runs for about 30 seconds (yellow program bar goes all the way) before spitting out An error occurred while attempting to run privileged commands!. And this is the point I am stuck at.
I should note that at no point am I prompted by the SuperUser app to give the ROM Manager app super user permissions. I don't restart the phone or do anything else throughout all of the steps I've described above, so I can't see any reason for root to have been lost at any point. In fact, if I execute the command sudo ./adb shell after all this, I still get the # prompt indicating root. And when I execute id afterwards, I get uid=0(root) gid=0(root) -- further confirmation of root. I really am stuck on this one. I've spent a lot of time digging through forum posts and online articles, but the signal to noise ratio is poor and I haven't been able to find anything that actually works. Can someone suggest where I am going wrong?

Programs might expect su to be in /system/xbin rather than /system/bin, which is probably your case.
Also, use SuperSU instead of Superuser.
Also, make sure the su you're using is matching the relevant control program - which means, downloading Superuser from the Play Store won't help, if it can't work with the binary you have. So download a complete ZIP from XDA with SuperSU.apk and su binary, and use those. The last version I used was 0.89 and it was on XDA just like I described above.

interesting problem with ez fix, get new phone. n1's are $100 on ebay, thats how i got mine.

[Q] Terminal Command to enable permissions system RW?

I'm having trouble with enabling system permissions after install a new rom. I've tried several command with no luck.
I'm rooted and have busybox installed.
Can someone point me in the right direction on this...

In ADB or a terminal emulator on the device? If your on your computer using adb, make sure you have root enabled for adb and apps not just apps only.
Code:
$ su
# mount -o rw,remount /system
Sent from my SM-N910T using XDA Free mobile app

DieHappy said:
In ADB or a terminal emulator on the device? If your on your computer using adb, make sure you have root enabled for adb and apps not just apps only.
Code:
$ su
# mount -o rw,remount /system
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
That happens to be what i remembered and it didn't work. I tried it just now and didn't work. I also did a reboot to no avail.

This seemed to do the trick
Internal sdcard not writable? Fix..