[Q] [UPDATED]some question about signal, contacts and app on sd - Nexus One Q&A, Help & Troubleshooting

Hi to all...
I have a big problem
I have a N1 with froyo 2.2.1
radio rom 05.12.00.08
build frg83D
And I cant' recieve OTA because it said that my version is upgraded....
But this is not the main problem...
I've root the mobile with SuperOneClickRoot and everythings goes fine, I have the icon in the launcher and I have the phone rooted...
I've tried to flash the recovery of amon Ra with the terminal app, and it said that flash_image not found...
So I've tried the ROM Manager and I've installed clockwork...when the yellow status bar finisch it gave me and error that some command cannot be executed with high privileges (or without high privileges I didn't remember the error was in italian language)...
What I have to do? I'm stuck with this phone...maybe rooted but it seems that anythings works on it
Please...
Thanks in advance
EDIT:
Please read THIS for the updated questions
Thanks

RealPsygnosis said:
I've tried to flash the recovery of amon Ra with the terminal app, and it said that flash_image not found...
Click to expand...
Click to collapse
Interesting.. It's not found? Did you also where did you put the file and what was the command you did? Also.. what instructions did you follow? I'm assuming you typed in "su" as well right?

Try either fixing permissions via ROM Manager, or installing busybox through the Titanium problems menu...

Maybe it's because I've root the phone without installing the SDK but only the driver for nexus?
when I root I see that all adroid driver for windows was installed except the one of nexus...
Can I install SDK and then root again?

Of course it won't allow you to use flash_image - you don't have the executable on your phone.
Please read the proper manual in Wiki under "Installing Recovery image" (link in my signature), and follow the manual step by step.

Just because you have superuser in the app draw does not mean you're rooted.
Sent from my Nexus One using XDA App

New question
I've found out that the problem was that ROM Manager doesn't have the root privileges -.-
So I've installed amonra and cyanogen...
everything is good but I have a really BIG problem
The phone sometimes goes to "only emergency call" also if there are strong signal, maybe it's the Radio? can I re-install it? or can be the sim-card?
Sometime it happen when the phone is for long time stand-by some time random...it's pretty annoying
I've installed Cyanogen mod, the phone is already rooted?
how can I import windows contact to android?
There is a way to config the app I want that can notify me?
Can I install app directly on SD instead of trasfert it after they are installed on the phone memory?
Thanks in advace

1. It's not a radio.
2. Yes.
3. Google can answer that with 1000 guides.
4. Only in the app itself. There is no external control over notifications.
5. There's an option for that in CM. I don't suggest using it or transferring apps to SD that weren't meant to go to SD - since the next question you'll come with would most probably be "Why are my apps/widgets disappearing".

ahahah LOL
thanks, but I didn't understand well the point 5 about the app to sd (why some peole talk about App2SD???)
And if it is not the radio what is it???

There are several options for moving apps to SD. In CM7 they use the default option, existing since Froyo days. This default option has several limitations that you need to know before using it - I wrote them.
The other way is partitioning the SD card, adding another partition to it, and running a special set of system scripts that moves all the apps by default to that partition.
Please read FAQ, question 13, and the thread that it links to.
If it's not radio - it can be your SIM, it can be your signal, it can be your phone, or anything else. The radio is just a SW build, and it works.

Related

'Recovery Flasher' + 'Backup for Root' Problems.

I have started a new thread from - http://forum.xda-developers.com/showthread.php?t=549622 - as this is a new problem and thought I would separate it out.
I'm having a problem with 'Backup for Root' after using 'Recovery Flasher'. I am now getting very confused about this process of rooting.
OK, so the story goes:
I thought that I could use 'Recovery Flasher' and be rooted there and then. Once I had done that I could use the 'Backup for Root' program, backup all my stuff, then I could boot into the recovery menu, flash, restore, whatever. But, it seems I was wrong?
After applying the Recovery Flasher' I can't seem to use the 'Backup for Root' program. Well, it runs and says complete, but there isn't anything on the SDCARD. Even if I reboot after using 'Recovery Flasher' it doesn't work.
In addition I downloaded 'Terminal Emulator', after applying the 'Recovery Flasher' program, from the market and ran 'su' on it and it said 'Permission Denied'.
Can anyone shed more light onto this? Maybe help me understand more? Am I getting things wrong anywhere?
The fruit of all this effort is that I want to install an Ion Rev.2 ROM, but I want to backup my apps and stuff first.
I would like to say thanks to DirectMatrix for helping out so far. His advice is to give up with the Rooting program and move onto more conventional (and longer) methods. I am this to agreeing and forgetting the rooting app.
you will not be able to use backup for root users until you flash a modded rom. you have to flash a modded rom for su to work check my sig for a guide to using 1 click root easily if you still want to do it that way.
Original question(s) seem to be solved.
Closing thread

Question about a rooted G1

Hi,
i have question, when i root my G1 and flash CyanogenMod or an other custom image/rom, can i also flash the newest official T-Mobile OS Release Rom???
So i have none disadvantages with rooting compare to not rooting, or???
ScorqYoN
No. You cannot. You can't flash two ROMs at the same time.
That said... Everything in the latest official Tmo release is in CyanogenMod, with the exception of the IM app in his latest build (I guess he found out it was proprietary? I dunno why). But you can drop that in from another build easily (pm me if you need help), so you will have no disadvantages.
Honestly, there are no disadvantages to rooting, as long as you do it right. But if you're totally new at it, instead of CyanogenMod, try WesGarner Build. The one without the RAM hack. It's almost exactly like Cyanogen's, but easier to flash, because you don't have to do the HTC image first. It's a good newbie ROM.
No i don't mean second roms on one time...
The possibility to flash the normal T-Mobile img back with root acces?
The IM App I doesn't need because I don't
use google talk.
Can i also delete **** Apps like Web'n Walk or other Commercial of T-Mobile or Google, when i have rooted my phone??
What do you mean with with HTC Image? The recovery.img???
And what with Ram Hack????
But the Cyanogen is the most stable and fastest rom or???
And he have full themes of Hero etc..
I have read many tutorials of rooting so i'm familiar with the most things...
Only one thing: Apps2SD, Radio and SPL do i flash at last or???
And what first APPS2SD or RADIO AND SPL?
Where i became the really "up to datest" RADIO AND SPL???
Last Question: Can I loose root anywhere or not??? Because I don't want to root the phone twice...
If what you want is the official T-Mobile build w/ root access, enomther has a good rom with exactly that, and each time T-Mobile send out an update, the ROM gets updated accoringly and there's also an expansion pack that includes the things that "root" users have come to love like apps2sd & tether and what have you, you can check that out here
Yes you can remove unnecessary apps through the terminal emulator or using ADB
If you've read up on installing Cyangogen as you said you've been reading up on rooting, the HTC image is the Developer image that you flash to your phone first, so the first time you flash Cyanogen it can back up and restore all the proprietary Google apps that Cyanogen no longer Distributes
The RAM hack adds ~10MB of space to your phone, but takes aways from the video, so if you play any 3D games they will be rather laggy or possibly unplayable
Cyanogen being the most stable or fastest - It's my favorite ROM, and it's definately by far one of the more popular. Fastest, Most Stable though will depend on what apps you put on your phone and how you use, so if Cyanogen doesn't work out for you, try another. I doubt you'll be dissapointed after tryin one though
If you're doing the radio & spl, after you get root access and have the custom recovery you can boot into flash radio first, reboot, then spl reboot, apps2sd is automatic in all ROM's that include it
No you can't really loose root, you'd have to downgrade and reflash an official T-Mobile image and go back to stock to loose root
Ok, thanks.
So i think i root my phone, because i think they are almost only advantages.
What is terminal emulator and is it easier then adb for removing unnecessary apps???
Optionally, i want to play 3D games... I don't unterstand why the 10mb from the internal space of the phone. When I have APPS2SD I think I have enough space...
All in all, i think i flash first with CyanogenMod Tutorial and CyanogenRecovery.img+Cyanogen Rom... and after that i can try many other Roms... like http://unslaved.think-android.com/ or one in this list http://db.androidspin.com/android_build_information.asp ...
So, downgrade->root->recovery.img->radio->spl->and then custom rom???
Other question: When is a wipe necessary??? With every update??? Cyanogen has the advantage of a instant Updater...
But what is with other roms... when i have to wipe and how???
ScorqYoN
PS: Sorry for my bad english, I'm german.
Teminal Emulator is just a terminal you can open up from your phone, I prefer using ADB, but you should be able to accomplish the same task either way
One thing I forgot to mention about apps2sd, although moving the apps to the sd is automatic you have to manually setup your ext2/3/4 partition, if you're gonna use the Cyanogen Recovery as you've stated you can follow this guide to do so
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
you would partition your card anytime after you have Cyanogen's recovery and before you flash your rom
Yes the steps you posted are in the right order
Wipe is necessary when switching roms, the first time you go to Cyanogen and anytime you switch to another rom, you don't have to wipe if you're updating to a newer build of the same rom you're using unless the dev specifically says to.
To wipe you'll want to boot into recovery, you'll see an option to wipe from there
Also you'll want to clear everything in your ext partition, so while in recovery choose the option to go to console and use the commands below
Code:
# mount -o rw /dev/block/mmcblk0p2 /system/sd
(enter)
# rm -rf /system/sd/*
(enter)
# rm -rf /system/data/*
(enter)
# reboot recovery
Thank for your support , i'm new in the android scene and get the g1 few days ago...
Ok, with the Wipe and Roms i unterstand.
But with the Partition and so seem to be very complicated...
At the moment i have the in package of g1 SanDisk 2GB SD Card.
So the ram hack isn't necessary or? Because i want the option to play 3D games...
And partitions on SD can i make later or???
But without them i can't use Apps2SD??
Another Questions: How do I backup my contacts,apps,settings... before wipe or flash an other rom???
I've heard from a app called "Backup for root users", but i don't find it on the market... (Many apps read in the internet i don't find in the market, strange...)
When i plug my G1 with USB on my PC, and it detected with ADB Interface, i have a ADB connection or?
So then i have to cmd: "adb shell" and it say:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
-> So then i have a ADB connection???
Partitioning the card is really easy if you give it a read through then go through the steps
Alternatively if you use Amon_RA's Recovery instead of Cyanogen's you can setup you're ext partition automatically, his recovery image can be found here
No the RAM hack isn't necessary, and it's not part of Cyanogen's build
Yes you can make the partition's later, but without an ext partition apps2sd will not be used, the ext partition is necessary for apps2sd
For you last question, contacts will sync automatically with your google account, as for the apps and setting, I've never tried this, so someone else will have to chime in or you could search for it, I've never found terribly painfull to reinstall the handfull of apps I use and change my setting for wireless etc ... back to what I want
So the recovery img hasn't relation to rom???
So whats the most recommendable recovery img???
Can i update or switch recovery img after flashing rom so stay in all except recovery img??
And have i a 100% functional ADB connection???
Last imporant question: How do i get acces on my sd over my g1 for format, downgrading etc., because at the moment i haven't a card reader...
No you can use either Recovery image it has nothing to do with the rom
Amon_RA's has more options than Cyanogen's, which probably makes it a bit more user friendly, especially towards the noobs.
Yes you can switch between recovery images without affecting the rom
THANKS, although i have few questions left...^^
When i plug my G1 with USB on my PC, and it detected with ADB Interface, i have a ADB connection or?
So then i have to cmd: "adb shell" and it say:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
-> So then i have a ADB connection???
Another very imporant question: How do i get acces on my sd over my g1 for format, downgrading etc., because at the moment i haven't a card reader...
The error says it's not finding your device
Make sure on your phone you go to Settings -> Applications -> Development and check the box for USB Debugging
Make sure all the drivers are installed properly, go into the device manager on you computer and make sure there are no "yellow exclamation point"
Then try to use adb shell again, report back if you're still getting an error
Using the guide I linked you to, or using Amon_RA's recovery the card will be partitioned/formatted while in the phone, you won't need a card reader to accomplish this.
For adding your downgrade file you can turn on USB Mass Storage from your stock rom and place your downgrade file & your recovery image on your sdcard
Once you flash your recovery which based on your circumstances you should definately be Amon_RA's recovery because it has an option for USB-MS toggle which will turn on the USB Mass Storage, so you can add all your zip files for your updates to your sdcard after formatting & partitioning straight from recovery. So it sounding more and more like you should go with Amon_RA's recovery
Ok so i think i take Amon Ra's recovery img, because it partitions my sd card for apps2sd and has many other advantages, also for beginners, or???
So i can take this tutorial http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod and when i have to use the cyanogen recovery.img, i use Amon RA's Recovery.img, or???
But how do i do that:
"For adding your downgrade file you can turn on USB Mass Storage from your stock rom and place your downgrade file & your recovery image on your sdcard"
Now i have activate USB Debug and install the driver and its all detected with ADB...
But still no device found..
Do i have to be in a certain mode, because i am in normal home screen...
I also need ADB for login after downgrading with wifi, because i haven't umts/gprs... http://modmygphone.com/forums/showpost.php?p=51891&postcount=12|
So, when i have ADB connection i start downgrading.
Yes when you get to the part of the guide that says
flash_image recovery /sdcard/cm-recovery-1.4.img [enter]
replace with:
flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
When you plug your phone into you computer it will ask if you want to mount, that's what I meant by mass storage device, you can add it like that
Ok now i think all understand!!
Except working ADB... do i have to be in a certain mode like recovery or something else for ADB, because i'm at homescreen...
jackslim said:
The error says it's not finding your device
Make sure on your phone you go to Settings -> Applications -> Development and check the box for USB Debugging
Make sure all the drivers are installed properly, go into the device manager on you computer and make sure there are no "yellow exclamation point"
Then try to use adb shell again, report back if you're still getting an error
Click to expand...
Click to collapse
Did you make sure to check those things for ADB, once everything is installed correctly ADB will work from the home screen
The two things I pointed out are the most common mistakes in setting up ADB if you're still having issues refer to this thread
http://forum.xda-developers.com/showthread.php?t=532719
It should be able to get you up & running with ADB
Ahhh, nice it work!
I completely disinstalled the driver and all and tried then with your posted tutorial and now it work it found a device under adb devices and adb shell work,too!
So ADB i use for login with wifi, delete apps like web'n walk etc. and what else?
Is their a tut for deleting "undeletable apps, or aren't these apps, like web'n walk not in custom roms??
I have a problem with downgrading...
When i put the dreaimg.nbh on my formatted sd card and start the phone in bootloader it said: "Loading...", "Checking...", "not allow"... then the multicoloured screen in the middle "serial 0"
I read that i have to make my sd card to goldcard, so i think i try it...
ScorqYoN said:
I have a problem with downgrading...
When i put the dreaimg.nbh on my formatted sd card and start the phone in bootloader it said: "Loading...", "Checking...", "not allow"... then the multicoloured screen in the middle "serial 0"
I read that i have to make my sd card to goldcard, so i think i try it...
Click to expand...
Click to collapse
Why are you downgrading if you have root?

It is simply ridiculous that HALF of the Nexus One RAM is unusable in stock...

...so I am compelled to root. ALL I care about is unlocking that other 256 (himem, I think it's called) for use and apps2sd would be nice but not necessary. Any other practical enhancements would be welcome. I'm using build ERE27. So which ROM fits that description best and where are the easiest instructions with links to download? I have been all over this and other sites and there are so many tutorials and none seem identical. Try Youtube and you know what you get? The most popular root tutorial (by far) flat out tells you from the start "This is not for beginners". Well, where the **** is the one for the beginners? I've jailbroken Iphones and flashed ROM's on to WM devices but I've never seen a more convoluted method to implementing a ROM replacement for a phone. Step by step (with backup reminders at critical times during process) would be great.
For example (from CyanogenMod):
Before continuing, you should first copy all the necessary files to your SD Card. Doing so will make the entire process much easier and faster.
Files you will need:
Download the latest release of CyanogenMod for the Nexus One and the Google Addon from http://forum.xda-developers.com/showthread.php?t=623496
Download the latest release of Amon_Ra's Nexus One Recovery Image from http://forum.xda-developers.com/showthread.php?t=611829
Rename Amon_Ra's recovery file "Recovery.img", and copy all three files to the root of your SD Card
Click to expand...
Click to collapse
I'm sorry, did you not just provide me with 2 files to download? Where does the third come from? And why does every "Link" lead to a full page with 3700 more links rather than just a freaking file to download??
Even Droiddog uses a Mac during the process because a PC would have been far too convenient for the masses (Plus I don't want the Desire ROM-too borky).
Preparing myself beforehand (going through the motions of the root without rooting) led to me opening 7 windows instead of direct file downloads. 7 Windows. 7. Does it really have to be this arduous?
I'm sorry for the frustration but deciding to root was suppose to be the hard part. Now I'm just overwhelmed with the unnecessary difficulty of it all. In truth, I'll probably be posting "thanks" from a rooted N1 by tomorrow and wondering what was so hard about all of that.......or I'll be crying over a $530 brick in my hands.
I believe Cyanogen mod (latest version in the link) includes the himem by default, just install that and you'll get the more available RAM (unless there is more steps to the process), I do not use Cyanogen.
Please note this is not the iphone OS we are dealing with here, things will not be as simple as a button press.. I honestly do not know what a "noob guide" is when it comes to Android, it all seems so straightforward to me... If I rooted my G1 and I'm only 13, not even being a nerd at that (wouldn't care if I was though..), I would imagine it not being hard for anyone..
At least the ram thing can be fixed with an ota. It looks like the multitouch problem is hardware. I feel like the ram, choppy scrolling, weird picture quality and image issue should really be solved by now by official update. I can see stringing us along for software upgrades like cupcake, new market, etc...but software fixes should be released asap. Any eta on the nexus 2?
DMaverick50 said:
At least the ram thing can be fixed with an ota. It looks like the multitouch problem is hardware. I feel like the ram, choppy scrolling, weird picture quality and image issue should really be solved by now by official update. I can see stringing us along for software upgrades like cupcake, new market, etc...but software fixes should be released asap. Any eta on the nexus 2?
Click to expand...
Click to collapse
Choppy scrolling is just that launcher2, and has nothing to do with the actual phone hardware which is a good thing. I went back to an older 2.0 launcher that is MUCH MUCH faster with continuous scroll.
I will switch if continuous scroll is added to launcher2, but yeah that choppiness stinks
It's a bug the iPhone had its bugs too. One of the great things about rooting your phone is not having to wait for Google to fix bugs the devs here do it nice and quick. I waited a month then rooted my phone and I am happy I did.
Prod1702 said:
I waited a month then rooted my phone and I am happy I did.
Click to expand...
Click to collapse
Does the extra 256 of ram make a noticeable difference in the overall speed and experience of the device (you should know having gone a month with stock on it)?
I didn't know CM rom unlocked the RAM you are talking about. I thought we were still waiting on an update from google for that.
jz9833 said:
I didn't know CM rom unlocked the RAM you are talking about. I thought we were still waiting on an update from google for that.
Click to expand...
Click to collapse
Is this true?
CM mode unlocks a good upgrade portion of the ram, for example with 10 apps Open I used to have 60 or less MBS left of ram, after CM upgrade with Kspec theme, i have 10 similar apps open and have 200+mbs of ram left, dont believe me? I actually made a video while still pretty shocked, check it, might as well rate and sub. I think I had 230+mbs while 10-12 apps running
www.youtube.com/user/exclusivegslick = my only video.
Ok to answer a few of your questions:
Does CyanMod include more ram? YES. This bump up in ram is included in the Kernel, and all of the newest roms have this including the undervolted/overclocked kernel's as well.
You get about 400mbs after the free up.
The Three Files:
Google had to go after Cyanogen so he HAD to seperate "google apps addon" from his mod. OTHER ROMS will include Google apps in most cases. So CYanogenmod = 2 files.
Ok here is a quick summary that will hopefully help the other guides make more sense. USE THE OTHER GUIDES STILL this is a conceptual map.
1) Install Android SDK to your COMPUTER which gives you ADB and the windows drivers. The drivers can also be downloaded via another thread. Search drivers/sdk drivers/adb drivers etc..
2) Download/install Fastboot to your COMPUTER
3) Download Amon Ra Recovery 1.6.3 to your Fastboot FOLDER on computer
4) Download CyanogenMOD 5.0.4.1 to the ROOT(VERY TOP LVL) directory of your SD CARD.
5) In same post, Download Google APPS 36ERE thing to ROOT of your SD CARD.
*This gives you all of the proper stuff. Make sure you get ADB SDK drivers loaded I stumbled here and wasted a couple of hours*
6) Unlock bootloader via fastboot. This is a command given from your Computer in DOS prompt in the folder you created with fastboot stuff. Your phone is connected and you are in the BOOTLoader. READ the guides for exact directions or the androidandme video, or countless other things.
7) Install Amon Ra's Recovery while still in FASTBOOT from a command via your computer. Follow guides or even first post on Amon Ra's Thread.
8) Now that you are unlocked. Go into RECOVERY which is done via the bootloader. Guide will give exact direction.
9) **** MAKE A NANDROID BACKUP **** just get in the habit. It is your FAIL SAFE. This in theory makes a nandroid backup of your "stock but unlocked" setup. I always "RE" nandroid backup before making changes or when I "Like" my setup. Command is in recovery.
10) WIPE data via recovery command.
11) FLASH from ZIP - pick Cyanogenmod5.0.4.1 (file you dl'ed to your sd card)
12) Flash from ZIP - GAPPS(googleapps) (file you dl'ed to your sd card)
REBOOT the phone. VOILA. Your done.
Important notes. If you decide, IFFFF, to update the radio. NEVER EVER EVER EVER pull the battery. MD5CheckSUM the radio download. and Repeat NEVER EVER EVER EVER pull the battery until the radio is entirely installed. It can take awhile. This is how you BRICK your phone.
Anyways. that is a real high lvl overview but maybe puts things in perspective easier.
btw you actually have less than half of the total RAM & ROM usable on a stock n1.
I would love to post a cyanogen guide...but haven't rooted yet. I believe he has a wiki with steps too.
britoso said:
btw you actually have less than half of the total RAM & ROM usable on a stock n1.
I would love to post a cyanogen guide...but haven't rooted yet. I believe he has a wiki with steps too.
Click to expand...
Click to collapse
Same here. I'm temped every day to root and unlock the benefits, but I don't know if it's worth voiding my warranty :\
I know what you mean with the "this is not for beginners", it was annoying because, even cyanogen had to unlock his first android phone some time. I followed that guide anyway, after doing as much research as possible. It didnt work though, i could not go straight from unlocking the bootloader to installing amon_ra's recovery, i had to install superboot first. I was hoping for a 30 minute root job, but it ended up taking about 4 hours all up.
I think the stock android kernel is .29 Which only recognises 256mb ram, cyanogen's mod is on the .32 then the .33 kernel which is a highmem kernel, by flashing cyanogenmod you are automatically unlocking the extra ram, no other work is required.
Also, i would suggest sticking with the ERE27 radio, i personally have no problems with reception with it, also if you don't flash the radio, your chances of bricking your phone are very very very low. If you want to do the radio, you can flash it later, when you are more experienced.
seanowns said:
The Three Files:
Google had to go after Cyanogen so he HAD to seperate "google apps addon" from his mod. OTHER ROMS will include Google apps in most cases. So CYanogenmod = 2 files.
Click to expand...
Click to collapse
I downloaded the Android SDK
2) Download/install Fastboot to your COMPUTER
Click to expand...
Click to collapse
Where is fastboot?
Do I have to do this? : (from Cyanogen's Wiki)
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others) Latest windows version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may have changed. (sorry I don't know how to format this correctly!)
Run C:\AndroidSDK\SDK Setup.exe
If it gives you an error go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
I have Amon RA Recovery Image.
4) Download CyanogenMOD 5.0.4.1 to the ROOT(VERY TOP LVL) directory of your SD CARD.
Click to expand...
Click to collapse
Please go to the Cyanogen Page and tell me where that is. The only link that states CyanogenMOD 5.0.4.1 will lead to another tab opening with the exact same page as the one you just left. Check for yourself: http://forum.xda-developers.com/showthread.php?t=623496
5) In same post, Download Google APPS 36ERE thing to ROOT of your SD CARD.
Click to expand...
Click to collapse
Is this the file underneath the CyanogenMOD that is named Google ION? It does the exact same thing that the CyanogenMOD file does when you click it. Re-opens that same page in another browser.
I have no problem following the instructions once there is a clear link to the files one actually needs to complete this process. I'm not trying to be difficult, the ability to root to Cyanogen on xda developers is, right now, broken.
whodatfever said:
I downloaded the Android SDK
Where is fastboot?
Do I have to do this? : (from Cyanogen's Wiki)
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others) Latest windows version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may have changed. (sorry I don't know how to format this correctly!)
Run C:\AndroidSDK\SDK Setup.exe
If it gives you an error go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
I have Amon RA Recovery Image.
Please go to the Cyanogen Page and tell me where that is. The only link that states CyanogenMOD 5.0.4.1 will lead to another tab opening with the exact same page as the one you just left. Check for yourself: http://forum.xda-developers.com/showthread.php?t=623496
Is this the file underneath the CyanogenMOD that is named Google ION? It does the exact same thing that the CyanogenMOD file does when you click it. Re-opens that same page in another browser.
I have no problem following the instructions once there is a clear link to the files one actually needs to complete this process. I'm not trying to be difficult, the ability to root to Cyanogen on xda developers is, right now, broken.
Click to expand...
Click to collapse
Cyanogen has moved the download to the CyanogenMod web page.
If you have sdk, and fastboot, on you machine and you have already put on amon-ra recovery, then you should be set to go.
Go to Cyanogen Mod.com and click the link to download the latest stable release. If you are in the US. I recommend that you get the new ERE36B radio. You should flash it as well. Just read up on flashing radios and plug in your phone, dont pull the battery during the radio flash and always md5sum a radio image no matter what. The radio is the only area where flashing has the potential to be dangerous.
Good luck and welcome to the Cyanogen World, you will never go back!
Gr8gorilla said:
Cyanogen has moved the download to the CyanogenMod web page.
If you have sdk, and fastboot, on you machine and you have already put on amon-ra recovery, then you should be set to go.
Go to Cyanogen Mod.com and click the link to download the latest stable release. If you are in the US. I recommend that you get the new ERE36B radio. You should flash it as well. Just read up on flashing radios and plug in your phone, dont pull the battery during the radio flash and always md5sum a radio image no matter what. The radio is the only area where flashing has the potential to be dangerous.
Good luck and welcome to the Cyanogen World, you will never go back!
Click to expand...
Click to collapse
What is the difference between the Cyanogen's N1 Addon which I am getting from this tutorial:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
and the ROMS available on this page (and which one do I download. There's a dozen!)
http://www.cyanogenmod.com/downloads/rom
Where do I download the radio and why is ERE36B better in the USA? A poster above said I should stay with the one I have (27).
addon - vs mod
whodatfever said:
What is the difference between the Cyanogen's N1 Addon which I am getting from this tutorial:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
and the ROMS available on this page (and which one do I download. There's a dozen!)
http://www.cyanogenmod.com/downloads/rom
Where do I download the radio and why is ERE36B better in the USA? A poster above said I should stay with the one I have (27).
Click to expand...
Click to collapse
The add-on was what Cyanogen made before google released the source code for android 2.1. It is not a full custom rom.
The ROM's ie. 5.0.4.1 is all the Cyanogen tweaks, highmem etc. 360 degree rotation (left right and upside down if you enable it) and all sorts of stuff.
You really should try both radios and see which one works better for you. Some people have better results with one and some the other. I have the best continuous 3G/HSPDA signal with the ERE36B radio.
On Cyanogen mod forum, go to nexus one and there is a link to get the latest stable ROM 5.0.4.1 that is what you want. You have to also download the Google add-on.
Cyan used to include them but got a nice letter from google telling him he was not allowed to "optimize" their stuff. So he puts it in a separate package as is, and you have to flash it after you flash his rom to get the google apps.
Google apps will be called: gapps-passionERE36B(2) or something very similar.
I am willing to answer any questions you have just send me a pm.
andythefan said:
Same here. I'm temped every day to root and unlock the benefits, but I don't know if it's worth voiding my warranty :\
Click to expand...
Click to collapse
there is a thread here about your warranty and as long as you have a problem that is a legit hardware defect HTC has been replacing them, dust under screen bad battery, and a few other things.
GR8Gorilla. Thank you for all of this. It was a convoluted mess trying to decipher some of the tutorials. I am very grateful and am starting the process in a few minutes. I'll let you know how it goes and thank you again.
whodatfever said:
GR8Gorilla. Thank you for all of this. It was a convoluted mess trying to decipher some of the tutorials. I am very grateful and am starting the process in a few minutes. I'll let you know how it goes and thank you again.
Click to expand...
Click to collapse
Remember if and when you flash the radio, plug in phone, and whatever you do, do not pull the battery while it is doing the radio. That is the biggest NO NO. It can make a nice nexus One paperweight. As long as you dont pull the battery you will be fine. I have flashed mine about 4 or 5 times....and I have flashed roms about 1000 times.
The phone is going to reboot a couple of times during a radio flash, be patient.

help installing apk using terminal

ok i just updated to CM 5. and well none of my apps are there, now im trying
this following :
sh /sdcard/installapk.sh /sdcard/theapp.apk
and no luck i think i can b doing it wrong.
cant DL the app cause i dont have the market app ether
Download DroidExplorer and you can do a bulk install of all your apps straight to the sdcard. Works everytime!!!
Link is in my sig
yea but i have no market on the phone and i dont have adb set up on my pc is it possible trew terminal to install astro so i can go on from there?
If your market is not there then you failed to flash the gapps.
You need to flash those AFTER CM5 or BEFORE. I've heard it works different for some people. First time I flashed it, it was before. Now it's after. Before and after won't hurt.
i figured that but the link on CM page for gapps is not working for me
I'm not really sure what having the market working has to do with anything. Clearly you didn't even take the time to click the link in my sig and go to the DroidExplorer thread.
it seems like that is for computers 64bit and up i have 32
brios86 said:
it seems like that is for computers 64bit and up i have 32
Click to expand...
Click to collapse
Are you talking about DroidExplorer? I have it installed on my 10 year old Dell and it is definitely a 32 bit machine. I'm assuming you are talking about something else.
You can use busybox if you have the latest CM ROM installed which you do. Busybox is included in the ROM so you can run busybox commands from terminal.
Put the apps you want to install on the root of your sdcard just to make them easy to find. Once in terminal, su so you have a # symbol
Then
Code:
busybox install /sdcard/yourapp.apk /sd-ext/app
great now i am F*** i tried installing the debug phone ota file that was required for CM 4.x and now i have no recovery it comes out the phone with exclamation mark
trying the droid explorer now
no luck droidexplorer seems to view the device but nothing else
brios86 said:
no luck droidexplorer seems to view the device but nothing else
Click to expand...
Click to collapse
Well that makes sense considering Droid Explorer requires root...According to your post on the first page, you are seeing an exclamation point when booting into recovery which means you lost root access by flashing whatever it is you flashed. Time to start all over again.
There is an updated rooting post for the Dream over at theunlockr.com
ok now my thing is i cant have the phone on cause it will keep getting FC and after a few it reboots
im trying to set up ADB on my pc now will that help me fix this? the phone boots up and the it reboots on its owne
It seems pretty clear that you don't really know what you are doing when it comes to modding your G1, and it is also pretty clear that you aren't willing to listen to directions.
I told you that you could batch install applications through Droid Explorer and you blatantly ignored my directions then said that it wouldn't work because you have a 32 bit computer.
I then gave you directions on how to use busybox to install the application that you wanted and never got a response regarding whether you even tried it or not.
You responded further into the thread saying that now you are getting an exclamation point when booting into recovery which MEANS THAT YOU DON"T HAVE ROOT ANYMORE!!!!!!!!!!!!!!!!!!
Installing adb and getting it working isn't going to do anything for you as far as installing applications because you lost root access which means you don't have the correct permissions to do anything anymore.
I gave you the link to an updated post on rooting so either do that or update this thread with where you stand exactly. Can you get into recovery? Is it an exclamation point? Can you launch the terminal app? When you type "su" do you get a # or an $? Does it say permission denied? ETC ETC ETC
DirectMatrix said:
It seems pretty clear that you don't really know what you are doing when it comes to modding your G1, and it is also pretty clear that you aren't willing to listen to directions.
I told you that you could batch install applications through Droid Explorer and you blatantly ignored my directions then said that it wouldn't work because you have a 32 bit computer.
I then gave you directions on how to use busybox to install the application that you wanted and never got a response regarding whether you even tried it or not.
You responded further into the thread saying that now you are getting an exclamation point when booting into recovery which MEANS THAT YOU DON"T HAVE ROOT ANYMORE!!!!!!!!!!!!!!!!!!
Installing adb and getting it working isn't going to do anything for you as far as installing applications because you lost root access which means you don't have the correct permissions to do anything anymore.
I gave you the link to an updated post on rooting so either do that or update this thread with where you stand exactly. Can you get into recovery? Is it an exclamation point? Can you launch the terminal app? When you type "su" do you get a # or an $? Does it say permission denied? ETC ETC ETC
Click to expand...
Click to collapse
My whole point with the no market is if he would have flashed the gapps or found another way to get them he could have installed a file manager then installed the app off his sdcard.
This was a 1 - 2 minute procedure that he has not made an hour/s procedure.
I agree with droidexplorer, I use it quite constantly. However, if he would have correctly installed CM5 this issue would have never arisen.
As for OP, I strongly advise that you unroot and stick to stock. If you cannot successfully do this, there is a high chance you are going to brick and it's just not worth it.
this is not the first time i try this i have a understanding of what i am doing, for some reason i decided to try another sdcard and it magically booted fine, now the gapps link doesn't work for me, so i am trying to install astro threw terminal emulator (astro is on the root of the sdcard) so i can just install the rest of my apps
thank you busybox worked thank you so much
funny after all the stuff i tried i decided to try a diff sdcard and it booted fine and then changed back to the old sdcard and it works fine

[Q] OneClick Root Works, But Superuser App Missing?

Hi, I posted a similar question about this under the OneRoot thread, but I don't see a lot of activity there anymore, so I was hoping to get more responses in a separate thread. I've scoured this forum and everywhere else on the Net and I haven't seen anyone experience this same issue. Hopefully someone will understand the problem and have some idea how to rectify it.
So, I have an AT&T Samgsung Captivate with the stock 2.1 Android "Eclair" build on it. I do believe there was an AT&T issued OTA update for it not long ago that put the build number up to UCJH7. I followed the instructions for TGA_Gunnman's One Click Root/UnRoot method documented here. Everything seems to work fine, in terms of booting into the recovery mode and selecting the update file. After the phone reboots, however, I do not see the Superuser Permissions app with ninja icon in my Applications area. If I browse the directory tree in my internal SD card in /system/apps, I do see a SuperUser.apk file. However, clicking on that shows me the message "Install blocked: For security, your phone is set to block installation of applications not sourced in Android Market." So it appears that rooting procedure worked, all the necessary parts were installed, but I don't have permission to execute su. I see that the xbin folder has been created, and it does contain busybox, su and something called ipctool. Also, a link does exist in /system/bin between su and /syste/xbin/su. If I use the Terminal Emulator and type "su", the prompt sits there for 10 seconds and says "permission denied".
Any ideas on what could be preventing me from gaining superuser access here?
Thanks for your help,
Mike
Download and install "SuperUser" from the Android market
OK, so here is another strange thing about this. This doesn't seem like it'd be related to my original su permission problem, but you never know. I decided to try to un-root using the one click method. Now, during the un-root script, I see the adb daemon start, but it fails on the push command writing unroot.zip to update.zip in the /sdcard folder; it says that permission is denied!. Of course, after booting into recovery, applying the update file fails, as it wasn't found in /sdcard. I'm not sure how this could have happened, as the root script was able to push the root.zip to sdcard just fine initially. Now, after I open a shell against my phone using adb, I check the permissions for the sdcard folder, and this yields rwxrwxr-x. I'm not sure, but I believe there should be another w flag set for other on sdcard. How the heck could that have been cleared?
It does look like I can copy the update.zip to sdcard manually through Windows Explorer and just manually boot into recovery using volume up + down + power, so I'm not completely dead in the water. Yet, I'd like to fix the permissions for sdcard, or else I can no longer use the one-click method.
id10terror said:
Download and install "SuperUser" from the Android market
Click to expand...
Click to collapse
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
mskelton said:
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Click to expand...
Click to collapse
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
End points are HIGHLY important, and if you read your post carefully, you have not yet demonstrated that superuser access is broken, only the icon from which you inferred it is broken. Let me know then we can go from there
Sent from my SAMSUNG-SGH-I897 using XDA App
fatttire said:
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks, that was one of the first things I tried last night, but that did not work.
fatttire said:
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, you're right, now that I see that error message, I guess it is trying to install it. That's odd, because I thought that the oneclick method would have already installed this app during the recovery boot load?
Regarding ROM manager, funny you should ask, that was the entire genesis of why I'm trying to root, so I can backup my phone and install the custom ROMs. After I installed ROM manager and tried to run it was where I initially noticed I must not have root access. When I try to flash clockwork recovery, the app hangs for (oddly enough) around 10 seconds. I never see any prompt for granting root access to clockwork recovery, nor does it boot into the recovery mode.
Okay I have another idea.
If your goal is to simply make a backup to flash a ROM, try this:
1. Download Cog 2.3b6. Other ROMs may have the file I'm looking for but I know it is here. Also you may be able to search and find this file directly but I'm too lazy to find the link for you lol
2. Open the zip file on your computer and extract /sdcard/update.zip
3. Adb push update.zip /sdcard/update.zip
4. Reboot recovery, reinstall packages, you are in clockwork recovery and can back up your ROM.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to try that, except that it appears there is some type of permission snafu on /sdcard. I believe the permissions on that folder *should* be 777, but it is 775 (other has no write access) for some odd reason, and I have no clue how that happened. Hence, when adb tries to push the update.zip to the internal SD folder, it gets permission denied. As I mentioned, not sure if this is related to not being able to execute su, but it is strange nonetheless.
Guys, please disregard what I mentioned earlier about adb and not being able to push the root/unroot.zip to /sdcard. I'm a moron, and I had left the internal SD card mounted to Windows after connecting the phone via USB. Clearly for adb to push/pull off of /sdcard, the internal SD card must *not* be mounted by Windows. My mistake, sorry for the confusion.
The original theme of the thread is still unanswered though, which is how the one-click root could have worked and not installed the SuperUser app onto my phone.
I will try the recommendation earlier in the thread, to download and install the SuperUser app from Android Market to see if that fixes things.
OK, so I downloaded and installed the SuperUser app from the Market, and for whatever reason, this seems to have addressed the issue. I am now prompted to allow applications root privileges. I'm not sure why this was necessary or how it fixed things, perhaps because it overwrote the version of su that was on my phone with a newer one. In any case, it's working.

Categories

Resources