Database Develop

What to do with a rooted Nexus One?

I'm considering rooting my phone, but I'm kind of on the fence. First, I don't really want to void my warranty, but since I bought the phone used do I even have a warranty anymore? Second, I'm not really that interested in custom ROMs at this point since I'm new to Android OS and I'm happy with the way things are stock for now. So my question is... What can I do with a rooted phone running the stock Froyo ROM? Anything cool/interesting, or does it not even pay to bother rooting if I'm going to keep it stock?

I waited 3 months before rooting and I thought the same as you, wasn't interested in custom ROMs and all. Once I finally rooted and loaded cyanogen ROM, it completely changed my thinking. I highly highly recommend using cyanogen if you root. I can't stress enough. Things wkt can do with root are many, 720p video hack, black notification bar, themes, meta morph, audio volume hack, ROM manager, titanium backup, nand backups! The list is endless. Hell nand backup alone is worth rooting.

Is there a place or a link I can find more information about just stuff that I can do with a rooted phone BESIDES installing custom ROMs? Everything I usually find is just about ROMs. I want to just get my feet wet a little before I decide to just jump right in. For now I'm just interested in stuff I can do with plain old vanilla android once it's been rooted.

Look for apps that require root, see what they are and if you need any of them.

Here's my current list of things "to root for", I haven't yet..
Reasons to root:
Just root, nothing else:
- Adblock host file
- ClockSync
- GScripter
- Remove built-in crap (Amazon MP3)
- Screenshots
After installing recovery image
- Nandroid
After installing custom rom
- Black notification bar

Depending on where you live, you might still have warranty. For example, in Europe, the warranty is by default 2 years on the device. So it doesn't matter if you got it second hand, as long as the device still has warranty, you're OK.
Secondly, you can root your device without unlocking the bootloader. Check this thread for more info. At step 18, before doing the 2 'exit' commands, also take the time to rename /system/etc/recovery-install.sh & install + make executable a file called flash_image (google it to find a download) into /system/bin. This way you can install a custom recovery (e.g. for doing nandroid backups) and will make installing custom ROMs later a lot less painful.
A rooted stock FRF91 can already do many things, search for 'root' in the market and you can find tons of apps that require root privileges and that will run fine on stock. However, the really interesting things (like color trackball alert, firewalling, proxy support, ...) will require you to install a custom ROM.
I rooted my stock N1 with the above procedure a couple of weeks ago, and installed Cyanogen6 RC2 ROM to get some of the more advanced functionality. Been working like a charm and I've actually managed to get a lot more out of my device AND have longer battery life

[Q] In what Heroic direction do I go?

Hi guys... I have a few questions for you about my Hero. Forgive me for not yet having the same level of knowledge that many of you guys have. I am certain that I can contribute in some way, as well. My phone details:
Firmware version: 1.5
Baseband version: 1.04.01.09.21
Kernel version: 2.6.27-533ce29d
Build number: 1.56.651.2 CL5027
Software version: 1.56.651.2
Hardware version: 0002
1. I've read several stories where a number of phones were returned because they couldn't be updated when the new update was released. Is this an absolute fact, that it can't be updated, or is there an error in code somewhere that made it reject the update and there is a known workaround? The answer to this question obviously dictates my forward motion.
I have the typical problem apps, and am getting no joy from youtube. Presently, I'm surfing with good speeds, but market is non-existent.
I like having Sprint tv, when I'm having to sit and wait somewhere.
I have time today and tomorrow to get things ironed out, but will be extrmemly busy after that, like 20 hours a day studying. I'm hoping to get some direction that will give me complete functionality, but will require the least setup. I am quite computer savy, and repaired this phone, to this point, in a day or 2, without asking a single question of anyone. I traced down problems, and solved issues. Seen APN, and TCP errors (don't believe it completely, since I can authenticate on the web). Know that some issues are url problems, etc.
The following questions are based upon the answer to question number 1.
2. Can this phone be updated?
2a. If yes, What do you recommend... 2.1? What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction? (pancake??, superhero??)
2b. If no, What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction?
Before repairing the phone, I actually tried to update it from my computer, but it was rejected. I turned off my security software and tried again. I noticed that while using XP sp2, a windows program that was incorporated starting with sp2, DEP (data execution prevention) didn't like the actions that the update was taking, and arrested it very shortly after starting (yet the window cycled forever). I assume that many people wouldn't be this observative, and recognize that this was happening. It was halting an HTC file that utilized storage memory (similar to buffer overrun exploits - the reason DEP halted it), for temporary storage of the files to be used for the update. That file was as follows:
C:\Program Files\HTC\HTC Sync\Mobile Phone Monitor\FsyncServer.exe
And the way to prevent it from continuing to do so is:
1. Click Start
2. Select Control Panel
3. Select System
4. Click the Advanced tab
5. In the Performance region select Settings
6. Click the Data Execute tab in the dialog box that opens
7. Select Turn on DEP for all programs and services except for those I select
8. Click Add.
9. The open dialog box will open. Browse and select your application.
10. Click Open
11. Click Apply
12. Click Ok
I guess what I'm sort of suggesting, is that this might be why anyone ever had problems updating, with the exception that OTA also said there wasn't an update.
So, back to the original question. Is it true that some Heros can't be updated? I don't want to force something, and brick, if you know what I mean. I completed the setting that will allow it to go forward (listed above), but haven't tried to update since. I felt that I really needed to ask you guys first, before I made a mistake that I'd regret. Should I try again? Before I started working on the phone I did try OTA and it said there wasn't an update. Now I don't have that option anymore. After repairing the phone, I've lost updates. Am I stuck with 1.5? With my run of the mill phone desires (except that it be fully functional), should I keep 1.5?
I did see gmail 2.3 apk, but is that compatible with 1.5? This looks like is would solve the market issue, if I could use it.
I did read about gscript and addressing mms (although I'm sure that's very old news to you guys), but if in fact I can't update this phone, it might be one of my only alternatives. If that is my only choice, are their also additional scripts to address everything I need to fix (all the normal issues)?
Additionally, it seems that many apps register with the phone/user. So, when you are using a used phone, many apps are still registered as functional. Does flashing a new rom affect the OS and apps? Will I loose the already registered/functioning apps? With a complete upgrade, will I gain functionality of some key features, but lose all other previously enabled apps? In other words, will I gain update, and market, and lose sprint tv?
I have read a lot. With things the way they should be, I've not been able to quite determine what I need to do. With all this being said, How do I go forward and achieve a fully functioning phone? What is the best choice of path's to take for me?
Rooting? I have seen the one-click, and think I'd be correct in that I need something containing Sense UI. Forgive me for asking a stupid question... but the rom is only the menu accessibility, correct? Is there something straight out of the box setup, or do all roms contain configuration notes?
I'm satisfied with stock features, if they work, and adding other useful things like tethering. Since I'll be so busy, I'll have little time to do much else. But don't get me wrong. I have 10 PC's in my house, with only 2 people living here. I'd love to customize the crap out of it. It's just not going to happen any time soon, due to my brutal study schedule. So for now, I just want it to work like it should, on a B mvno.
Do I go north, south, east, or west????
Could someone chime in that can give me direction, based on everything I've stated. Your response is so graciously appreciated.
Cheers!

Umm well I'm not sure why you're having problems with any update, someone who's far more experienced can maybe tell you but as far as roms I think it depends on whether you like sense or wanna go froyo. Cyanogen mod 6.1 stable (2.2) is nice & highly customizable however there's also AOSP roms (2.2) that some people feel is quicker than cyanogen however they aren't as customizable as cyanogen, in addition there are tons of GREAT themes for both. Also we've had a ton of work on an odex AOSP gingerbread rom (2.3) not yet stable but works good for most & on that note a great themer also put together a themed AOSP gingerbread rom (2.3) that looks good & about stability I'm not so sure on but I would recommend those roms. Although with these roms YES you will lose sprint apps like TV & vvm etc. However people have posted these apks in the theme thread section to work on roms like cyanogen & AOSP. If you do like sense roms there's a couple that are still live in the development section like nfinite & nfx I believe. Hope some of that info helps

Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?

inkblots said:
Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?
Click to expand...
Click to collapse
Sort of. I can't remember which version I was at when I rooted but I remember I downgraded to do it. But if you go in the development section you will find a thread that shows & gives you what you need to root. So you should root. Then flash a recovery image such as clockwork mod or amon ra. When I rooted I used the recovery from the downloadable app (Rom manager) in the market & that one was clockdwork mod. It's worked great for me so I've been using it ever since. Then backup whatever you are running currently. Then flash whatever rom you want. I'm about to see if I can link you to a root thread then once you do so I can give you a dl link to cm 6.1 stable. Will you be able to root on 1.5?? I don't completely know...
Edit: Ok this is the way I rooted mine, hopefully this will work for you
http://theunlockr.com/2010/09/27/how-to-root-the-htc-hero-androot-method/

[Q] Autonooter for 1.2?

Any word on an autonooter for 1.2? Or maybe a rough time frame as to when there will be one? All I can find is manualnooter...

No real time frame as of right now. When the network location stuff is ironed out in a safe way, then an autonooter version might come out. The autonooter format seams to do a better job of implementing everything that it is written to do. ManualNooter is still a great safe product that can be used right now, it is just lacking the network location information.

ManualNooter for all intents and purposes is AutoNooter.
The only thing stopping MN from becoming an AN is before I started school I had been looking for a viable way to make CWM flashable cards Auto-run compatible. I have a method of getting the cards to run the updates automatically but for CWM to do it based on an auto-run script it has to be modified to run the script and therefore the "AutoNooter" update.zip. While I have done this to a couple of versions I started school before I could hammer out the best way to implement this in such a way that other users wouldn't have to reflash for an auto-run capable card and therefore an AN capable card.
The old method of AutoNooter that was used for all pre 1.2 versions is a deprecated method and honestly no one should be trying to recreate that method for new B&N version updates. With ManualNooter and when I can put some time into it, AutoNooter, users have a way of actually seeing when the process is done as opposed having to wait for that reboot or just randomly turning it off cause they thought 30 seconds was too long to wait.

GabrialDestruir said:
ManualNooter for all intents and purposes is AutoNooter.
The only thing stopping MN from becoming an AN is before I started school I had been looking for a viable way to make CWM flashable cards Auto-run compatible. I have a method of getting the cards to run the updates automatically but for CWM to do it based on an auto-run script it has to be modified to run the script and therefore the "AutoNooter" update.zip. While I have done this to a couple of versions I started school before I could hammer out the best way to implement this in such a way that other users wouldn't have to reflash for an auto-run capable card and therefore an AN capable card.
The old method of AutoNooter that was used for all pre 1.2 versions is a deprecated method and honestly no one should be trying to recreate that method for new B&N version updates. With ManualNooter and when I can put some time into it, AutoNooter, users have a way of actually seeing when the process is done as opposed having to wait for that reboot or just randomly turning it off cause they thought 30 seconds was too long to wait.
Click to expand...
Click to collapse
One of the two remaining issues for MN is IMEI apps force closing. Has anyone gotten the [Beta] IMEI generator... to help with this issue in MN roms?

lschroeder said:
One of the two remaining issues for MN is IMEI apps force closing. Has anyone gotten the [Beta] IMEI generator... to help with this issue in MN roms?
Click to expand...
Click to collapse
I don't believe DizzyDen's IMEI program will work with the ManualNooter flash. It should however work to patch the full stock 1.2 ROMs but obviously this is undesirable unless you wish to go back to bone stock.
Dizzy's latest betas however have a feature to pull the framework.jar and your S/N via ADB (or ADB wireless), patch the framework.jar with a psuedo IMEI based on your S/N, and push the modified framework.jar back to your device via ADB. I see no reason why this method wouldn't work with rooted stock.
If you try it be sure to post in Dizzy's thread and let him know what happed.
Martian21

[Q] Plan for Bionic root/unroot for ICS, PLEASE REVIEW

I'm hoping to get some eyes on this plan I've made for hacking my new Droid so I can avoid bricking it at all costs.
I bricked my old Bionic 2 days ago due a combination of problems with Clockword Recovery Mod and the leaked ICS update, as well as my battery frying for some reason. Thankfully Verizon was none the wiser and they are sending me a new phone and battery in a few days. Although I'm cautious about hacking now, I still plan on rooting the new phone so I can recover my apps and data from the old phone's SD card.
Here are my plans for the new phone. If anyone could tell me if it makes sense or if they see any issues that will arise from following these steps, please let me know:
1. Root new Bionic with Motofail.exe root
2. Restore apps and such with Titanium Backup (restoring individual apps so I don't get any old clockwork garbage or other random stuff)
3. Download Voodoo Root OTA Rootkeeper.
4. Wait for official ICS OTA (don't want to mess around with the leaks anymore) and backup root with voodoo
5. Unroot with voodoo, install ICS and re-root after update (I've read on some posts that Voodoo works with the ICS OTA but I'm not 100% sure)
I'm more concerned with the OTA installing properly than keeping the root after ICS, though while it would be simpler just to not root, I really want to restore the TiBu backup from my old phone.
If anyone sees any flaws with this plan or if you think it sounds like there won't be any problems, please respond! I really don't want to brick a second phone so any help would be invaluable.

No one can say for sure if this will work since no one has the official OTA yet.

That sounds like a plan that may work. Even if OTA Root keeper fails I see a thread with a root method that is working on ICS leaks so it should
[should being the operative word here as stated this is all subjective reasoning from my time and use of Android and many different devices there is NEVER 100% certainty EVEN IF we had access to the OTA and had a method there is no accounting for any errors caused by a multitude of things [download corruption, bad blocks in memory during flash, you missing a step and borking the whole process, etc.] so no one will ever be able to say with 100% certainty that you will not have some rare issue and have a problem even with a tested method [and if someone does try to tell you something is 100% they have not dealt with technology and computers long enough to realize nothing is ever guaranteed even fully certified OTAs have caused bugs not accounted for and been stopped, recalled, or otherwise modified when users try to apply them and have issues ]
Anyways, I did read where you flashed the ICS leak via CWM recovery and everything I have been reading about flashing ICS on a Bionic involves the STOCK recovery and not CWM [most postings even SPECIFICALLY state to NOT USE CWM AND ONLY USE STOCK Recovery [but then again I read a lot] so if I had to trace the issue you had the with the limited information you have provided about your specific experience I would prolly point to that as prolly causing the problem. See the ICS with files thread here and that is again specified as part of procedure [basically format EVERYTHING restore it back to out of the box 902 then using STOCK recoveries to apply .905 then the ICS leak THEN after ICS is running they have a rooting batch file in there as well [so no worries about rooting in .902 and using OTA Rootkeeper to sustain it in .905 and on just get stock .905 unrooted to the phone then flash ICS with stock and root once it is fully completed and drivers and all on computer side are good [dont forget to enable USB Debugging [and in ICS there is an option to allow SU to apps only OR APPS AND ADB and after rooting you may need to enable the ADB side for any super user root checks if checking via ADB] but dunno if that is CM9 only option, but seems to be stock ICS setting in developer [it protects you if you use and leave enabled the ADB over the network function from others who may find your device over a network and getting SU access].
Sorry, I digress, all to say sorry to here you had the issue, but I think you may have missed something in the install process and here's how to address it, and your methodology seems sound in theory, but there is other information already available to augment your procedure and make it easier on you, my bad.
Hope all the info helps....
Here is that thread mentioned above that seems to distill what I have read on numerous boards in to one easy to download pack with instructions that has users replying that they have had great success with it: [Guide} Bionic to ICS w/Files

[Q] VZW OS Upgrade, nandroid questions, and other issues

OK so here's my situation:
I got the official Verizon upgrade from 2.3 to 4.0 back in August. Since then, my phone has been giving me major issues. I won't get into them, because I know I just need to do a factory reset and it should fix everything.
I have some experience with bootstraps and custom roms on the Droid 1 and Droid 2, but it's been so long. I've done some research, but could still use some guidance.
The phone was rooted on 2.3 but the 4.0 update took that off.
My questions are:
- Can I make a nandroid (or similar) image of the system in its current state, before it's re-rooted with custom roms?
- Is CM9 in any kind of final stage?
- What's the best SMS backup utility that will PRESERVE THE MESSAGE TIMESTAMPS upon restore?
Thanks in advance!!!

kman13 said:
OK so here's my situation:
I got the official Verizon upgrade from 2.3 to 4.0 back in August. Since then, my phone has been giving me major issues. I won't get into them, because I know I just need to do a factory reset and it should fix everything.
I have some experience with bootstraps and custom roms on the Droid 1 and Droid 2, but it's been so long. I've done some research, but could still use some guidance.
The phone was rooted on 2.3 but the 4.0 update took that off.
My questions are:
- Can I make a nandroid (or similar) image of the system in its current state, before it's re-rooted with custom roms?
- Is CM9 in any kind of final stage?
- What's the best SMS backup utility that will PRESERVE THE MESSAGE TIMESTAMPS upon restore?
Thanks in advance!!!
Click to expand...
Click to collapse
- You cannot make a nandroid backup without root. To make a nandroid backup you'll need a custom recovery (SafeStrap in the case of the D4) and you cannot install SafeStrap without root. Once rooted and with SafeStrap installed you can then make a nandroid of your stock system.
- I believe CM9 has been abandoned in favor of CM10 on the D4. CM10 (and other JB ROMS) run PRETTY well with a few caveats. Main bugs include bluetooth not working correctly, screen re-size when switching between landscape and portrait is a little janky, and the camera flash does not work. Personally, I don't even really notice the screen re-size thing anymore. The bluetooth issue is irritating but not a deal breaker for me. On the rare occasions when I want the camera flash I switch back to stock, which is quite easy and fast with SafeStrap 3.05. If you need something a little less buggy try out Eclipse. Pretty sure it's bug free.
Edit: Forgot one other CM10/JB ROM issue. You'll need a workaround to get MMS to work You can turn off auto-retrieve in the original app. You can flash an inverted gapps package. Or you can use a third party text app like GoSMS (that's what I'm currently doing).
- I use SMS Backup and & Restore. It preserves the timestamps so everything is in the correct order when you restore your messages. It's free on the Play Store: https://play.google.com/store/apps/...mNvbS5yaXRlc2hzYWh1LlNNU0JhY2t1cFJlc3RvcmUiXQ..
I also use Call Logs Backup & Restore by the same dev. Also free and on the Play Store.

You probably had issues after the update because you need to do a factory data reset.
As far as all the info kwyt said, he is correct.