Database Develop

Have Froyo early what next?

I have put Froyo on my phone early as many others have and there are a few bugs on it, so what I am wondering is when it officially comes out will there be "some" additional updates since it is already on my phone or will I have to reinstall it with the official version from the market? What I am wondering is just update any further updates from the market with the Froyo I have? or with the public release in the next couple weeks install that? does it matter? if this makes any sense what I am saying LOL

I have the exact same question in my mind. Remember the 2.1-update?
-------------------------------------
Sent via the XDA Tapatalk App

My wife and I both have the Nexus One. I decided to stay on CM 5.0.7 Test 3 until he gets the chance to work on his 2.2 rom, I'm in no hurry.
My wife wanted it on hers because she wouldn't allow me to root her phone.
After putting 2.2 on hers there is some pretty bad stability issues. Her phone has straight up frozen at least 8 times since yesterday requiring a battery pull.
When he phone isn't being a temperamental babby its great but when it starts to chug the whole house of cards comes crashing down.
Since I rooted mine I just make nandroid backups and restore from that so life is simple for me but with hers how do I restore back to total stock?
Do I reboot into the bootloader and at the screen where I would typically apply the update.zip just use the restore option or would the restore option in the phones settings work? I.e Factory Default.
While she is semi tech savvy I just don't have the time or patients to deal with her phone issues right now so I guess she'll just need to be on 2.1 until the official release.

[Update] Froyo May Have Been Launched Prematurely
http://phandroid.com/2010/05/24/froyo-may-have-been-launched-prematurely/

rensky said:
I have the exact same question in my mind. Remember the 2.1-update?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
sorry I am a newbie 2.2 is my first update that's why I am posting this to see if I didn't f*** up my phone or something. other than that it seems to be working fine with a few bugs here and there and 2 things updated today from the market, so am wondering leave it be or get rid of it and reinstall the official one? thnx for responses

Enndr said:
My wife and I both have the Nexus One. I decided to stay on CM 5.0.7 Test 3 until he gets the chance to work on his 2.2 rom, I'm in no hurry.
My wife wanted it on hers because she wouldn't allow me to root her phone.
After putting 2.2 on hers there is some pretty bad stability issues. Her phone has straight up frozen at least 8 times since yesterday requiring a battery pull.
When he phone isn't being a temperamental babby its great but when it starts to chug the whole house of cards comes crashing down.
Since I rooted mine I just make nandroid backups and restore from that so life is simple for me but with hers how do I restore back to total stock?
Do I reboot into the bootloader and at the screen where I would typically apply the update.zip just use the restore option or would the restore option in the phones settings work? I.e Factory Default.
While she is semi tech savvy I just don't have the time or patients to deal with her phone issues right now so I guess she'll just need to be on 2.1 until the official release.
Click to expand...
Click to collapse
From what I understand, if you want to go back to ERE27/EPB54, you would need to either restore a Nandroid image that has those ROM's or download an unsigned original ERE27/EPB54 image.
When you say battery pull, are you actually physically pulling the battery whe the phone freezes? I've read a couple of posts/articles where that might be harmful to the phone and so what's recommended instead is to perform a soft-reboot.
You can do so by holding down the power button + volume down key + trackball at the same time. If done so correctly, the phone will automatically reboot in a few seconds.

Enndr said:
but with hers how do I restore back to total stock?
Click to expand...
Click to collapse
No can do. No unlocked bootloader = no regression. You either unlock the bootloader or live with Froyo.
I would consider a factory reset though, as I have no stability problems what so ever.

[Q] To Root or Not?

Hi so I just heard that the D3 was rooted two days ago (been keeping up until a week ago). I'm not exactly a pro in this area or have ever rooted a device before but I have spent quite a few hours today reading up on the process and any info I could find.
Basically I just want to know if I should root my D3 or wait out another week or so? I heard that a SBF (?) hasn't been found yet so the stock rom can't be recovered and there is really no recovery net yet so should anything go wrong, there aren't a lot of options.
There is a one-click method to root but I'm going to try the original method using the adb shell (lol still researching what on earth to do with that still, just installed the android sdk :x). I'm not concerned about the process of rooting my droid, it's what comes after that makes me hesitant in doing so.
I read that there is a (seemingly simple) method to unroot the D3 by deleting the su file in some directory and rebooting (can't remember, it seemed legit however). Would "unrooting" have any consequences or would your device be back to the exact same state it was in right before you rooted? I'm not planning to drastically mess around with my D3 should I root it. Just want to take a few screenshots in an app to help out a dev, freeze any bloatware that won't cause problems, do a complete nand backup, and... thats about all that comes to mind right now.
I guess what I'm trying to ask is if rooting my D3 tonight would have any irreversible consequences and if there is any benefit in holding off the root?
Oh! Btw the OTA, I know that rooting won't affect ones ability to receive the update but that it will unroot your device and keep it that way. Would the rooting-discovery process have to start anew for people who update using the OTA (Thinking Verizon might patch the root-exploit) ? I know that updating via OTA isn't too bright anyway because devs just take the update and build on it before releasing it on their own custom ROMs and whatnot, but I feel official updates are somehow more stable (most likely flawed thinking, feel free to correct me on that lol).

Yes - SBF is an important component which would guarantee 100% pre-root configuration.
Removing the su binary and the superuser app would however put the phone back in factory state for this exploit. But anything you do while rooted inside /system is your responsibility to correct. Motorola patches usually verify only file existence/checksums and not creation/modification dates, so you should be fine with simple push of the removed (or renamed) stuff back. I remember I was able to update my D2G without unrooting in the past, but that's not necessarily granted for any other updates of that or any other Motorola phone. Ideally, you want phone in factory state to guarantee update will pass.
Another issue is nand backup you mentioned. Custom recovery isn't yet available for this phone. You can't do nand backups. So even this "safety net" isn't here. Installing custom recovery is a "100% secure way" to have OTA updates fail to apply since it messes up with phone's /system files. Un-doing CWM is a bit more complex than unrooting only and if not done carefully - a sure way for a soft brick. SBF is what we all want before start messing with anything, IMO.

So if an OTA updates fails for whatever reason, your phone will get soft bricked or?
I don't think ill be updating anway, but its good info to know for the future.
Sent from my DROID3 using Tapatalk

I would say root the device and don't worry about unrooting. If you have to return it to the store or something, unfreeze the apps and delete su. Once you mess with it though, it will be very difficult (impossible?) to ever make /system binary identical to the factory image without an sbf. That said, I doubt VZW takes the time to investigate this very closely.
But I don't see any other reason to ever unroot. When the OTA update comes down, just don't install it. In a few days after its first released, the community developers will tell you how to install it with root and not botch anything up.

Dmw017 said:
So if an OTA updates fails for whatever reason, your phone will get soft bricked or?
I don't think ill be updating anway, but its good info to know for the future.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
No - fortunately not. It will just say "Update failed" and phone will reboot back to normal.
Regarding updates - you may want to reconsider - updates usually fix bugs, bugs like the bluish camera or the wrong geotagging. Or stuff like phone shooting at max brightness after removal from HD dock.
But as the other poster mentioned - the community would do the hard work for you 'back-porting' the update to a rooted phone. Sure enough - we need custom recovery to be made before we can install any 'backported' updates or other customizations.
But all will come with time.
If you need to use an app that requires root (like openvpn or VPNC), or if you want to remove some of the unwanted apps Verizon stuck on the phone, you should root of course, but if you don't care about such stuff and want to be 'compliant' with stock software - stay as is, until at least SBF comes.

Yeah I rooted already but should an update come, I could always unroot my device. An update would be really welcome too. Yeah the bluish tint on the cam is bad but there are soft fixes for that. What I really really want out of the update is the huge improvement in battery life I've heard about. Im using the extended battery right now and straight up, it sucks. I've heard good things about the extended battery but mine lasts ... maybe 10 hours under light - medium usage, playing music for several hours and having the display on for about an hour. I expected a lot more. Numerous people have reported getting 24-48 hrs of life while others got 15 under normal/heavy use.
There have been a few reports of peope already receiving an OTA update (devs/testers most likely) but have said many pf the d3s current issues were fixed with it, primarily the blue tint on cam and the battery life.
Honestly, with root, I figured my battery would outlast a day like a champ, but there have been no/minimal improvements, even with every piece of bloat frozen. I even froze google Maps because it constantly showed up as using cpu (and therefore battery), have my radio set to cdma, and only have 1 gmail account syncing.
Sent from my DROID3 using Tapatalk

unroot & stock droid 3

Hey guys I was wondering what I can do to unroot my droid 3 and also revert it back to completely stock. I had frozen and removed some apps due to this being my first time using titanium back up and I'm wondering what I can do to do this. The reason I want to do this is so that I can go back to verizon and get a replacement phone because mine has just been messing up too much. I removed or froze all the apps that were safe to remove but it'll keep pressing space or backspace, it will stop with its service and not send calls or receive texts, it will have half a green screen when I push back and it's all just really annoying.
So please if anyone has any suggestions please tell me. I've tried to restore from titanium back up but it ends up just "clocking" when I try to restore sometimes. Also I dunno how to unroot.

here
i did the same thing... lol check out this link
http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
good luck its easy

More power to you but from my experience I bought the d3 when it came out 2 days later I got the same problems green blobs when it redraws screen, space and backspace buttons sticking so I called verizon they sent me a new one, this was about 15 days ago guess what's back to affecting my phone?

I know that there have been reports of the green screen thing from people that use youtube a lot. But out of curiosity, have you flashed any of the ota's? Because I noticed the same thing until I went to 5.6.890
Sent from my STEELdroid3

I haven't done anything more then remove / freeze some apps. I was thinking of trying to use the steel droid and I wasn't sure what the difference was from using 5.6.890. I'm still pretty new to all this so I was worried about what to do. Ill read up on how to do it today and possibly try upgrading to 5.6.890 and changing to steel droid.

I haven't yet installed the ota but my first glitches happened when I was unrooted completely stock and now their back and im rooted with bloat gone.................................................... < just spammed the period button damn phone

[Q] CM9 Question with going back to Stock

If I just create a backup through ROM manager (will that even work with this phone since there's no recovery?) could I just reflash that to come back from CM9?
I really want to try it, but I'm afraid I may want to go back to stock since its in the early stages. Normally, getting back to stock (on my D1, Captivate, Atrix, LG Thrill, GSII, GSII Skyrocket) was never a problem but I'm not so sure with this phone lol.

Go read up on safestrap. Follow the link in the safestrap thread to HashCode's site explaining it. Basically you will install CM9 to your "safe" system and dualboot. That way you can return to stock whenever you want.
Sent from my DROID4 using XDA

Back to stock...
There is a program called Safestrap, which works and looks a lot like Clockworkmod. Be careful, though, because I accidentally bricked my brand new Droid 4 through an error by not saving the webtop to the backup files.
If you're an adventurer, and you want to contribute, I say go for it. Eventually they will come out with fastboot files for your phone if you brick it. However, I had to go back to Amazon for a replacement phone, which was over-nighted, and I get to keep the soft-brick for 40 business days to tinker around with it.
So you paid some money for the phone, and are a little gun shy, right? My advice, start by rooting the phone, disabling the non-essential apps, change the launcher around, upping the screen resolution, and doing what you can to make the motoblur livable, for the time being. Give it a month or two and we'll have roms aplenty... unlocked bootloaders galore.
If you do brick your phone, it's likely you'll be able to hang on to your phone, and just reflash it when the time is right.
Cheers.

We can change the resolution? How would we do that, and how do we tinker with the launcher? Seemed pretty locked down.

I think he means you can change the DPI, which you can do by going to the "/system" directory, and editing "build.prop". You should create a backup, and then edit the original such that ro.sf.lcd density is your desired DPI. Then save, reboot, and you should have your changes.

First off, your screen will look 10 times better when you're in an ICS rom. The overlay and bloatware are all horribly configured for the Droid 4 and other screens.
Root your phone, and just search for screen resolution in the google play app, you'll find some stuff to that is easy to understand. Tinker around with it. Download the CM spareparts app for some decent tinkering stuff. Rooting can help, and a little extra time can make the current stock rom livable until ICS comes out.

[Q] How to stop auto update to 5.9.905?

I am wondering how stop an update on a Droid Bionic?
I understand you need to "move the update from /cache to your SD card" once downloaded.
However, I do not know where "/cache" is located, how it is accessed, or how the moving process is done.
I connected my phone to a PC via USB and could not find "/cache" stored on the phone. The only thing close was a cache folder within "com.google.android.apps.maps", which doesn't seem like what I'm supposed to be looking for. I've also tried looking in Menu>Settings>Storage but do not see any 'cache' info.
I've been searching the forums but have had no luck; plenty of references to a 'cache' from
people who clearly know what they are talking about, but I can not find any explanations or instructions.
Any help is appreciated. This is my first Android device btw! (though I've been reading this forum for a week or two now)

Wow, you're wanting to stop .905 while most people are chomping at the bit to get 6.7.xxx. You can't do it with your PC, you will need to do it from your phone with a file manager app.
I think you need to be rooted to see the cache'. you will also need a root file manager like "root explorer" to move the update to your SD Card.
ICS is much much better than the GB OS. I would reconsider the update, better things are coming around the corner.
If you choose to stay at .902, I would suggest doing some reading about the rooting process. Bad things can happen if you haven't done some research.
There are many here that will be glad to help you, but you will need to be a little knowledgeable to "help them, help you"
root .902
http://www.droidforums.net/forum/droid-bionic-hacks/198045-902-root-method.html
advanced root and play with leaks and return (well written, read 1st post several times,) also has links to current drivers
SamuriHL spends his life supporting that thread and spends too much time helping others
http://www.droidforums.net/forum/droid-bionic-hacks/214902-downgrade-902-no-app-data-loss.html
I'm not sure if I helped or confused, mainly just want you to be aware

greeneink said:
Wow, you're wanting to stop .905 while most people are chomping at the bit to get 6.7.xxx. You can't do it with your PC, you will need to do it from your phone with a file manager app.
I think you need to be rooted to see the cache'. you will also need a root file manager like "root explorer" to move the update to your SD Card.
ICS is much much better than the GB OS. I would reconsider the update, better things are coming around the corner.
If you choose to stay at .902, I would suggest doing some reading about the rooting process. Bad things can happen if you haven't done some research.
There are many here that will be glad to help you, but you will need to be a little knowledgeable to "help them, help you"
Click to expand...
Click to collapse
thanks; that's really what I needed, a point in the right direction. I confess it's a bit new to me. I just got this phone, programmed it using steps found here (great forum!), and activated it on pageplus, but this was the first time I just got 'stuck' on something.
I read that 3G worked much better with 902 than with 905. this is why I was thinking of sticking with 902, at least until a legit/finalized version of ICS gets released (which allegedly, is very soon...maybe). Since I don't know much about the OS yet I figured I could survive the wait without 'knowing what I'm missing' so to speak.
whoa, just googled and saw that a new leak is out. I picked an odd time to be a newb working on a Bionic.
Thanks again!

If you do take the plunge into a leak, you should probably stick to one where FXZ to 902 isn't blocked so you can return to stock if needed. Everything 235 and after is poison, so to speak, and you won't be able to go back, which (thanks Moto) makes it really difficult to go forward (thanks Moto). I'm on 232 and I'm happy as a clam. It's stable and doesn't have many issues. Now when the official update comes out, they should release an FXZ and we'll be safe again and can all take the dive into ICS.

so, I realized you could postpone the update by just not accepting it when the prompt comes up.
so, I use my Bionic for a while and am quite happy. Then today, I noticed I no longer had 3G service. I tried restarting it, removing the battery,
toggling some of the data changes, no luck. I figured since ICS is (allegedly) right around the corner, there was really no reason not to go ahead and update.
I ran the update. I now have no phone service, no texting, and no 3G/1x.
My question is: how far in the process do I need to go back to get things running again? Right now what I have is a blinking white triangle in the notifications bar. My phone is stock in every way.
Edit: in "about phone/status" I have no phone number (it's blank). no MIN, no network. My PRL version is 'unknown'. so, basically I think I need to just start over, using the info I used successfully before (adam3rd is my hero), beginning with flashing a pageplus PRL. but I shouldn't need to reactivate it on pageplus, or need a new sim card, right? I feel like whatever happened wouldn't have effected my status with PP or the sim card, but I can't find a clear answer....any help appreciated

The white triangle is your phone searching for a signal to activate itself. Take your sim card out and re-insert it. you may need to wipe the dirt off the gold metallic area

greeneink said:
The white triangle is your phone searching for a signal to activate itself. Take your sim card out and re-insert it. you may need to wipe the dirt off the gold metallic area
Click to expand...
Click to collapse
thanks for the response. I actually had 4 bars of signal strength along with the white triangle. I'd assumed this meant I could 'detect' the verizon/PP network but wouldn't be able to get out of 'roaming' status until it was activated for the network.
I actually contacted PP via chat to reactivate it. they did it, but the problem wasn't resolved so I tried a factory reset. boom, activation screen came up! now I have fone and text again.
my real problem now is getting data to work consistently. gonna wait until the legit ICS comes out before tackling that one again.

You're going to love .246
no signal drops, fast reaction on apps. it's truly a who;e new phone experience

greeneink said:
You're going to love .246
no signal drops, fast reaction on apps. it's truly a who;e new phone experience
Click to expand...
Click to collapse
yes, I'm very excited. a little paranoid about updating since I'm on PagePlus and haven't seen anyone use Pageplus and .246 yet. but I may just try using the info on howardforums; I know it 'should' work, but that's just not the same as confirmation.
on a side note; I believe I may have discovered what my data problem was; I think I'd just disabled the 'connect with data over mobile network' option and forgotten I'd done so a month later. pretty funny. but it's been a good learning experience, heh