I have been notified by a few Bugless Beast users that they have been receiving the OTA update notification and were wondering what to do. The reason for this is because Bugless Beast V0.5 is based on FRG22D, an earlier build than the new OTA update (FRG83D). A few months ago many of us would have simply renamed or removed otacerts.zip from /system/etc/security to block OTA updates but we quickly learned that this method drained battery life tremendously because it constantly caused the update to redownload. The patch I will provide below will update the build keys and fingerprint to "trick" the system into thinking it is the latest build. Therefore no more OTA update notifications.
Everyone running Bugless Beast V0.5 (or below) should flash this whether you have received an OTA update notification or not. If you have received the update and wish for the notification to go away first install my patch and reboot. If you are still prompted for an OTA update, press install so that your device will boot into recovery. The update will be blocked by ClockworkMod Recovery and SPRecovery. Reboot your device and you shouldn't have to worry about another update notification again.
Download link and installation instructions after the jump:
1. Download StopOTA.zip
2. Place on sdcard (rename to update.zip if using SPRecovery)
3. Reboot into recovery mode
4. Choose and install stopota.zip (do not wipe data or cache)
5. Reboot
Thanks, Pete!
ReplyDeleteOne more reason to love BB
ReplyDeleteThanks, Pete! That notification was kind of getting on my nerves.
ReplyDeletelol, I had recently downloaded Pete's FRG01B update and lost root. I then purchased Easy Root and was able to regain Superuser access. Tonight I did a restore back to v0.4 and then threw this little stopota badboy on.....Bring on v0.5 Pete! I can handle just about anything now....
ReplyDeleteJust what I was hoping for. Thank you.
ReplyDeleteIf you have beta Swype just uninstall and install it again. It thinks it is on a different phone now.
ReplyDeleteThe patch is not needed if your running clockwork recovery.
ReplyDeleteAfter selecting to update and rebooting clockwork just rejected the update. I rebooted again and found myself still with root and BBv0.4.
Thanks for the patch pete. \ (^_^) /
pete, im so glad you got your own site now, it makes looking for updates to much easier.
ReplyDeleteThanks,
ReplyDeleteThanks, Pete!!! This is great!
ReplyDeleteThanks for the update. Still waiting on v5 tho, not to push you or anything
ReplyDeleteThanks again Pete.
ReplyDeleteWhat if you give us BB.5 instead of tricking our phones into thinking its running a later version? I think that would work muchhhhh better.
ReplyDeleteInstalled this update this morning and swype quit working. Had to do an uninstall and reinstall. All is fine now.
ReplyDeleteWhere was the official OTA 45 megabyte file downloaded to on my phone. trying to find and delete it.
ReplyDeleteok i got the ota update today and just wondering if the new .5 or .6 is in our near future. i did this patch but seems like the patch is just like a band aid being used for a sore throat. very big fan of your work pete. and very anxious for the new release. Also for this not being a replacement for droid forums it sure seems to be the opposite haven't seen any pete post on df since this site has come into play
ReplyDeleteI've actually accepted 3! updates and all of them were blocked on reboot. I thought there were only 2...
ReplyDeleteAhhhhhhh! I'm sooo annoyed. This killed my swype too and I can't for the life of me get it working again. I keep uninstalling and reinstalling it while rebooting in between and I keep getting "Swype is already installed. Please uninstall and try again."
ReplyDeleteAnyone have a suggestion? I can't live without it. :-(
Thanks, Pete! That was driving me crazy.
ReplyDeleteI'll just wait for BB 0.5. For some reason the new Google Voice actions app won't install (signing error on install) and I really really want that app! Hopefully the donation helps BB 0.5 along :)
ReplyDeleteI'm using SPRecovery and when I installed the stopOTA patch, it broke the overclock script. My phone is now running at 600mhz instead of 800mhz, according to the cpuinfo script. Any idea how to get back to 800?
ReplyDeleteThanks for all your hard work, Pete!
Thanks, Pete! Installed using clockwork, rebooted, and within seconds that VERY annoying system update icon disappeared.
ReplyDeleteNow....about v0.5...... ;)
Using ROM Manager and it blocked and aborted the OTA install. No more notifications for me!!
ReplyDeleteUpdate worked great. Many seem to have rooting problems though.
ReplyDeleteTake your time on v0.5. Let it "simmer".
:)
I installed this using ClockworkMod Recovery. Installation seemed to have been successful, but now more than half of my downloads from the Market are missing from the list in the downloads section, but they are still in my app drawer.
ReplyDeleteI also installed the fix using sprecovery and now cpu is running max at 600
ReplyDeleteroylive
Worked Like a charm! Thanks pete!
ReplyDeletePete -
ReplyDeleteDo what you do, and release .5 it when it's ready. Thanks for the knowledge.
I suppose you are more polite than I would be, but for all these people whining about the next update, you should...
require people to post comments through their google account, and then on the .5 update use some fancy script that will recognize anybody who has posted whiney comments on your website asking you to hurry up with 0.5, and for those users only, make it so it removes root and throttles their processor down to 250. HA.
- B. Hurd
Had swype like many others but now I can't download swype installer... it only downloads a very small file that is useless
ReplyDeletePete, your the man. keep up the good work. <3
ReplyDeleteThanks Pete - you are awesome as always! Foolish as I am - I started getting these notifications this morning and wasted time Googling for the solution instead of coming straight here first. Should have known you would already have a fix made.
ReplyDeleteThis update worked but also has my phone stuck at 600 mhz! It seems the CPU scaling script has stopped working.
ReplyDeleteAnonymous said...
ReplyDelete"I'll just wait for BB 0.5. For some reason the new Google Voice actions app won't install"
Google Voice actions app installs fine for me BB 0.4.
PS: It's easy to act like you've donated when you're "Anonymous" lmao (=
Roy said...
"I also installed the fix using sprecovery and now cpu is running max at 600"
I have the same issue. However I changed the minimum CPU speed to 800 and now it is forced to stay at 800 MHz for me. But I still wish it was the way it was before.
Ran fix and it did change SetCPU to 600 max but I opened SetCPU and moved slide bar to Zero and back to 800. Fixed it. Rebooted...and it came back at 800. Done. Thanks Pete!
ReplyDeleteI tried this on my Mom's phone and now Listen won't work! I've uninstalled it several times. It says no Gmail account is available.
ReplyDeleteHi Pete.... I received a 2.2 update notification for your currently installed FRG22. Please let me know is I should follow your steps above... Thank you.
ReplyDeletePete could you address the under clock issue when you get a chance because it seems many are experiencing clock speed at 600mhz now including myself. Thanks for all the hard work.
ReplyDeleteThanks so much Pete, I was getting rather annoyed with the OTA pop up.
ReplyDeleteDo you see any real reason to update to the new rooted OTA if I'm currently running the Bugless Beast V0.4? Like is there really anything to gain, expect for possibly some problems caused by the FRG01B.
Thanks Pete. This worked great. Stopped the notifications that started this morning. Looking forward to v 0.5. :)
ReplyDeleteSo if I have ROM Manager ClockworkMod Recovery 2.5.0.1 do I really need this patch? I have not got any OTA notice yet.
ReplyDeleteAny chance this could be put on ROM Manager under "Bugless Beast"?
ReplyDeleteI too have the underclock issue, I am using OS Monitor to view / set my clock speeds, it happens every time I reboot now.
ReplyDeleteWorks great! Thanks
ReplyDeleteCPU Issues fixed, redownload the new version :)
ReplyDeleteI installed the new stopota1.zip file and it did appear to fix the overclock problem. But it also took away my root access. I'm restoring a backup now.
ReplyDeleteDude, A friend of mine has de FRG01 build and has the notifications too lol.
ReplyDeleteShould I just install the FRG22? lol
Cheers
Lost SU. Typing "su" in terminal gives "Permission Denied". Root File Explorer tells me I need root. Hmmm...but Rom Manager opens and doesn't say anything about root. Did I lose mu SU permissions? I installed the new zip that was supposed to fix the overclocking, but now I don't have su.
ReplyDeleteThanks Pete for your fast response to the cpu issue. Can't wait till BB v5
ReplyDeleteAwesome! Thanks for the fix! Luckily I still haven't gotten the OTA yet so I didn't have to deal with any issues before it even mattered.
ReplyDeletesuper user stopped working after running file renamed as update.zip using sprecovery. any ideas?
ReplyDeleteI believe you need the patch even with Clockwork recovery. The notification "goes away" just by accepting and rebooting, BUT, it comes back (in my experience). I have already accepted it twice.
ReplyDeleteIs there a way to download the zip directly to my phone? I got an "update failed, unsupported file type" from the browser download.
Thanks.
Installed the patch and now I'm also having Swype problems...I have uninstalled and tried to reinstall and no joy. It keeps saying that the download failed because Swype is still installed. I have to have Swype...any ideas?
ReplyDeleteActually found the fix for the Swype problem. You need to reboot after uninstalling Swype...then reinstall. I had to download via 3G too, WiFi for what ever reason would just hang during the download process. So, Swype is up and running again, all is well!
ReplyDeletePeter people want BB0.5.... when will it be showing off to download it??? a Beta version??? or something Men you are reminding me the Moto delay with 2.1
ReplyDeleteNevermind regarding the toolkit FC's. Re-updated toolkit from terminal and it opens fine.
ReplyDeletePete, you ROCK!! Keep it up! Waiting for your next awesomeness!!! Take your time and enjoy your summer while you can!!
ReplyDeleteI have a quick question...Like a typical man I only read part of the instructions then tried to figure it out on my own....I renamed it update.zip rebooted in Clockwork Mod...and rebooted. I see the instructions say rename if using SPR. Still works right?
ReplyDeleteThanks worked great!
ReplyDeleteThanks Pete, I am on a mororcycle ride from Florida to Michigan and back thru North Carolina to Florida. I have done 1200 miles so far. This morning I got the OTA notem, and said WTH? My next thought
ReplyDeletewas "Pete will have a fix". I went to the great all encompassing alldroid site and all I found was a link to the fix. I had not put your site in my favs yet, but your there now. Thanks for the fix Pete! 1200 miles from home on 3G updating my phone sitting in a cafe.
Well, after I did the update, I can't log into my wireless router. For some reason it just keeps trying, but obtaining an IP address is as far as it goes. Not sure what happened?
ReplyDeleteNice, many thanks! For some reason, booting into recovery mode always makes me smile...
ReplyDeleteTHanks for the fix. the OTA notification showed up today. This fixed it right up.
ReplyDeleteI have a question. I downloaded FRG01ODEXED.zip to get rooted 2.2 on my phone. Do I still install the above file to get rid of the OTA notification? I don't think this is Bugless Beast cause it doesn't say it anywhere. It is from Peter, though. Urghhhhh, I hate that notification!
ReplyDeleteThanks pete!!! ur the best man!!! cant wait for bb v.05!
ReplyDeleteI just got the notification today and downloaded the update from Pete's site on my phone and it installed fine. The system update popped up momentarily and then went away after booting. SetCPU widget went from 600 mhz for a second, then back to 800 mhz. Google Listen works fine. Seems like it did the trick. Thanks, Pete!
ReplyDeleteI started getting the OTA update a few days ago while on vacation and was thinking to myself "oh hell this is gonna be really annoying but there is no way I'm going back to stock". I figured Pete would be on top of this and bam there it is.
ReplyDeleteThanks man! can't wait for v.05!
HEY PETE CAN YOU MAKE DROIDWALL Work bugless on froyo or your latest roM???? please
ReplyDelete*crosses fingers, knocks wood*
ReplyDeleteSo far so good! :)
Haven't gotten an update notification yet =]
Using the updated file with BB0.4 & IndigoBlue theme on my phone & BB0.4 with GoldenElegance on wife's phone.
Results so far
--------------
Root :check
Wifi :check
800mhz :check
Swype :don't use it, no comment thus
Thanks a bunch Pete!
Pete- thnx for the GREAT work. I am a developer and out of all the roms I tried (I've tried them all) urs is the smoothest, snappiest version! Only thing is that this fix also stops rom manager from being able to update a rom. I applied this fix on bb v0.4, and went to try another rom. Doesn't really impact me, just wanted u to know! Keep up the good work, ill donate soon as this job comes through.
ReplyDeleteLong live the pete! Lol
Worked like a charrm Pete, thx.
ReplyDeletePete, I'm running BB v0.4. My droid downloaded the OTA update for 2.2 but I haven't installed it yet. Is that the FRG22 file that you're requesting in the downloads section?
ReplyDeleteI downloaded the patch and so far no more OTA notifications. I just have a few questions about how the patch works after reading all the negative posts about this fix. What are the adverse effects of the patch and will there be a permanent fix? Thanks for all your hard work Pete!
ReplyDeleteI had installed BB v4 and was working fine. Got the OTA update notice and it wouldn't disappear so I found this forum! Awesome! I downloaded and installed the patch and somehow lost root access. The Phone Info section shows Android Version 2.2; Baseband Version C_01.3E.01P; Kernel Version 2.6.32.9-g103d848 android-build@apa26 #1; Build Number Bugless Beast V0.4
ReplyDeleteAny thoughts on how I can get root access back? I didn't see any other comments in this posting about similar trouble...thanks in advance!
installed this fix and now Swype does not work anymore and no matter what I do to install it, it won't install properly. Do you know of a way to get swype to work again? I think I will restore back to a previous version and not install your OTA fix.
ReplyDeleteThink I found another workaround...appreciate it!
ReplyDeleteI had the root problem as well. I fell back to a previous nandroid backup and redownloaded from my PC (rather than on the phone) and installed and it worked this time.
ReplyDeletePete, This worked great! After a re-install of Swype, everything is working perfectly and I don't expect any more OTA notifications for this. Thanks so much for everything you do! It was my pleasure to make the donation I should have made when I first got BB working on my phone. Keep up the good work!
ReplyDeleteThanks Pete!
ReplyDeleteHey Pete,
ReplyDeleteWondering what you make of this:
When I install the barebones FRF84B and set my self up with all my programs, etc, StopOTA works brilliantly. However, within an hour after installing 928BlackGlassTheme for Bugless, I start getting the nag screen for OTA update. Any ideas???
Thanks,
Sister X
Guess the love affair is over, Pete don't love no old tech after all Droid 1 is all of 10 months old.
ReplyDeletePete have you moved, my DROID cries every night starring at the USB cable just waiting for your data day after day...
Hope all is going well, looking forward to your next release.
Hey Pete, is the next release gonna fix wifi? I tried to update to v0.4 and my wifi wouldn't connect, it just paused at Obtaining IP address. I spent a very long time trying to fix it, tried a bunch of stuff, no luck... anyone have a fix?
ReplyDeleteHey again Pete, just wanted to say thanks!! I got my wifi working using a static ip... and 0.4 is SO FAST I LOVE IT! Thanks again!
ReplyDeleteHi! I'm really new to Droids and this whole rooting and different ROM process. My Verizon salesman helped me install ROM Manager and I upgraded to Bugless Beast .4 with it.
ReplyDeleteMy question is this: is it normal for the home screen to refresh so slowly? It seems to take forever after leaving any given app. I've got Launcher Pro set up as my launcher of choice. The same refresh could be said if I use the native home launcher.
Any ideas?
Hi Pete! I am just new to BB but absolutely LOVE IT! Thanks for all your awesome work! Quick question, flash is reported to have been pushed yesterday, after the fix for the last ota notification I did not get any notification or push... should we wait on you to get it posted for us or will they put it on the market/push it again... any thoughts would be greatly appreciated! Again, thanks for all your hard work and awesomeness!
ReplyDeletePete.. in the process of going to the 22D I was prompted for 2 OTA.. one was 01B from ESE81 the other was.. 9046f5a3ec09.signed-voles-ota-45394 76 Meg.. you need it or anything
ReplyDeleteAfter installing this for some reason my gmail isnt syncing correctly anymore. Basically if i receive an email on my phone and delete it, the message disappears but the next time i get an email it will say i have 2 new messages. If i go into my web account sure enough there is the message still sitting there, any ideas.
ReplyDeletePete,
ReplyDeleteNow that there is a new OTA, I am getting the notification again. Do you have another fix for this new flash ready build?
Thank you
Anyone else getting the ota update notification again. I installed this patch when Pete released it and it worked, but this morning it came back.
ReplyDeleteAnyone else getting the ota notification again? I installed this patch back when Pete released it, and it worked fine, but it just came back.
ReplyDeleteHey Peter,
ReplyDeleteI don't know if anyone else is experiencing this but I received another OTA update.. I received one about 2 weeks ago and did what you said above and I was fine until 6:53am this morning (EST).
Anyone else have this issue?
Please advise.
Thanks
-Jeff
Pete...I just received another update. Could this be another update from Verizon
ReplyDeleteRunning BB v0.4 with Pete's OTA update to Android 2.2. Just got a notification this AM about the second update from VZ (1.6MB) which is to allow the install of Flash via the Market. Are we supposed to install this?
ReplyDeleteThanks pete, just got the OTA finally...and BAM! DENIED!!!
ReplyDeletePete,
ReplyDeleteI just got an update notice on my Droid. I do have your stopota.zip update and that worked until now. I'm wondering if this is the other update that Verizon was pushing out. My wife's droid hasn't received an update notice yet. Her's is still the stock ROM though Wondering if you know if you will have to provide another stopota.zip update for this or what I need to do. Ignoring the updates are a pain and I'm always afraid I'm going to accidentally accept it.
Just got another OTA Update request today. This is after I installed the stopota patcha bout 2 weeks ago. Will the same patch work again?
ReplyDeleteAnybody else seeing another OTA update from Verizon. I installed the stopota.zip update a while back that fixed the update. Verizon sent out another one today with the Adobe 10.1 update in it. So we are back to needing another update again?
ReplyDeleteHey pete I've installed this but I keep getting an ota 1.6 mb system update file anyway...
ReplyDeleteI installed this patch a few weeks ago. As of a few hours ago, I started getting OTA update notices again. Maybe this is the flash fix?
ReplyDeleteI got a ota again today. I ran the stopota.zip again and it seems to have worked. Come on BBv.5
ReplyDeletehey Pete Can you port the IM app out and make it work on BB for the Original Droid ??????
ReplyDeleteThis will not stop the latest update (FRG22D) this patch was created back before we knew about FRG22D so it will only stop FRG01B. I am hard at work on BB V0.5 so please be patient. School has started so I must be sure I keep up with homework as well. Thanks for visiting the site! :)
ReplyDeletePete, Im running your FRG22B ROM and keep getting the request to update. My update says its 77MB, and the reminder is relentless.
ReplyDeleteWill Clockwordmod still block the latest update (FRG22D) if I click install?
Thanks for everything pete.....keep up the great work and I would rather be patient knowing you are going to school too!!!
ReplyDeleteThank you, for the site Pete. It's been great getting all your stuff in one place now. Iv'e never run anything but bugless. But do you think I should maybe go to your rooted stock 2.2 untill you get done with v.05 ?? Just to get rid of the increasingly annoying notification. Or are we close enough to just wait.
ReplyDeleteIf you have root explorer, you can follow the directions here: http://androidforums.com/droid-roms/111881-rom-beta-bugless-beast-v0-4-android-2-2-frf84b-fully-deodexed-11.html and it will stop the OTA for FRG22D.
ReplyDeleteThanks for the update. School comes first. I really can't wait to see bb0.5!!!! Thank you for all of your hard work!
ReplyDeleteYep, I started getting OTA again. I don't like the nag.
ReplyDeleteHey Pete, I used your StopOTA.zip file and just woke up to a system update notification anyway! Time is against me here, as I really want to stick with Bugless Beast. NOW WHAT?
ReplyDeleteThe second ota were getting is for flash, here's what worked for me, backup rom. Run the update, it will fail verifacation, then reboot, no more nag. I did that 12 hours ago and so far so good, can't wait for .5 pete, but take your timee man.
ReplyDeleteI got the OTA update request as well and it says it is to allow flash install from market and other security features. I tried flashing the stopOTA again, but that did not work.
ReplyDeleteThanks and help!
I am getting the OTA as well this morning. I hope BB v .05 is around the corner with a fix, I can't wait. THANKS A TON to everyone working on this, people really appreciate your hard work!
ReplyDeleteJeezus. Doesn't anyone read the comments before they post? The Stopota.zip will not stop the latest update (FRG22D) and the stopota patch was created back before we knew about FRG22D so it will only stop FRG01B.
ReplyDeletePete I modded your old patch to work for frg22d for you. Its avail on droidforums.net in your bugless forum.
ReplyDeleteJust run the update and clockworkmod will block it and no more notifications with the rooted stock 2.2 rom. You're the man Pete! I'm also anxiously awaiting your BB 0.5 release.
ReplyDeleteHey Pete... What build would BB V0.5 be???
ReplyDeletePete,
ReplyDeleteQuick question. Will your BBv0.5 fix the "feature" that was added to Froyo where the screen unlocks whenever it is tilted horizontal? I have been plagued by this issue ever since I updated to Froyo based ROMs.
Thanks
what do i do if i just got a new droid stock on frg22 , is there a way to root this ? would rsdlite work or would it update itself automatically? i loved root before and want it back idk what to do ! please help alfonso ! anybody at that email me a solution triniboy515@gmail.com
ReplyDeleteOver 2 months and no bb 0.5...is Pete still around? Just asking as someone who has made a donation to the cause...
ReplyDeletei am getting this update too... i cannot believe it got through all of the security features
ReplyDeletePete,
ReplyDeleteThanks for the update! Glad you are aware of this and are working on it.
The only ROM I have used is the Bugless Beast ROM and plan on keeping it for a while! :)
Thanks again and we will wait patiently :D
-Jeff
clockwork blocked the ota's like a champ!
ReplyDeleteThis patch does not apply to the most recent update regarding security and adobe flash. we'll have to wait for that...
ReplyDeletego to the following link for patch + instruction to eliminate most recent OTA update notification regarding security + adobe flash player (frg22)
ReplyDeleteoops, click the link below if you still have problems. its the link to the most recent OTA notification regarding security and adobe flash
ReplyDeletehttp://www.droidforums.net/forum/bugless/76532-frg22d-stop-ota-notification-bb-froyo-v0-4-a.html
I am wondering if it is worth it for me to flash FRG22.
ReplyDeleteI am rooted and forced Froyo . I also forced flash.
I am running bb.04 and clockwork.
Does FRG22 have anything else I would want?
If I did flash it, would I wipe cache and data?
Thanks in advance for any help.
It stopped my FRG22D update from popping up, i just followed the instructions on this page
ReplyDeleteJust click install on the ota update. When it hangs on ! . Just hit your power button and select reboot. That's all I did and the notification went away.
ReplyDeletefollowing from the 9/1 post, and the info at (http://androidforums.com/droid-roms/111881-rom-beta-bugless-beast-v0-4-android-2-2-frf84b-fully-deodexed-11.html)
ReplyDeletethis works...
Required apps: ConnectBot, ASTRO
Procedure 1: modify file access to system information file (/system/build.prop)
- Open ConnectBot app
- Tap dropdown box in lower left hand corner (probably defaults to ‘ssh’)
- On the selection window (ssh/telnet/local), choose ‘local’
- Open Keyboard, press enter (‘Nickname’ not necessary)
- Type ‘su’ and press enter (the prompt should change to a ‘#’)
- Type ‘mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system’ and press enter (this changes the system file storage sector to read/write, from read-only)
- Type ‘chmod 777 /system/build.prop’ and press enter (this changes the file permissions to read/write)
- Type ‘exit’ and press enter (the prompt symbol should change back to a ‘$’)
- Type ‘exit’ and press enter to close the session
Procedure 2: modify the system information file to change the OS version number indicated to the server
- Open ASTRO app
- Press the ‘Up’ folder menu icon until you are at the highest level (the list of directories should start with acct,cache,config,… and end with …,sdcard,sys,system)
- Click on the ‘system’ directory
- Long Press on the file named ‘build’ until a File Options window pops up
- Click on ‘Open As’
- Click on ‘Text’
- Click on ‘File Editor’
- Look for the line that looks like ‘ro.build.fingerprint=verizon/voles/sholes/sholes:2.2/FRG22/46998:user/release-keys’ and change it to this: ‘ro.build.fingerprint=verizon/voles/sholes/sholes:2.2/FRG22D/50454:user/release-keys’
- Hit the ‘menu’ soft key (between ‘back’ and ‘home’)
- Click on ‘Save’
- Press the ‘home’ soft key to exit ASTRO
- Power cycle the phone
Downloaded the update.zip from efelix, and it worked like a charm. Thanks for the work.
ReplyDeleteWhere is number five? (Short Circuit, the movie,lol). I am starting to think if you own a Droid1 you better star learning how to make your own fixes. I know the Rom is free but since it is the current version and so many people use this as their default 2.2 Froyo update ( this is a huge compliment, ignoring a few small bugs in BB.4 and the fact it is from an older build it is by far the smoothest on my Droid1 and better than anything Verizon has ever given me ) that a quick patch should be available on this site. Pete make a patch and charge a dollar or two to download it. People in the community are very loyal to your work and enjoy using it. I also believe you should be making some serious coin! In addition to your "vanilla" release of BBv.5 you should also put out a donation only version of BBv.5 with some extra goodies
ReplyDeletePete, is the FRG22D in your downloads section, root compatible?
ReplyDeleteI'm fiending for V0.5 like a junkie fiending for some crack. Come on Pete, I'll suck your dick.
ReplyDeleteI did the update and install. Clockwork blocked it and I am back to system up to date. The update for me was only 1.7MB if that helps.
ReplyDeleteThis isn't exactly the place for the comment but I had no where else to post, apologies. Moto Droid1 owner. I just came from Pete's Rooted version of FRG01BDEODEXED to FRG22D-DEODEXED and now it seems like don't have root. I have the superuser icon, however apps like Titanium Backup(root), SetCPU, and ROM Manager all claim I don't have SU access/permission. Obviously I can't get into Clockwork Recovery... Any ideas?
ReplyDeleteI clicked on the OTA Update and let it install and when it reboot, it went to the ROM menu and I click reboot and it rebooted fine and the OTA message went away
ReplyDeletehttp://www.droidforums.net/forum/bugless/76532-frg22d-stop-ota-notification-bb-froyo-v0-4-a.html
ReplyDeleteFor those in need I have made a modified stopota1.zip using the instructions found in the above posts. I have tested this on my Droid and it worked but I am not responsible if you do not nandroid and take other similar precautions. I have called it stopota2.zip but I want to make it clear that this is NOT an official Pete release. Love your work Pete! Can't wait for more!
ReplyDeletehttp://www.megaupload.com/?d=5MPCWNC2
For those of you that lost root when you downloaded Pete's original FRG22D rom, it would be to your advantage to look up the instructions for how to Root Droid 1: Regardless of OS.
ReplyDeleteSeriously, it takes maybe 5 minutes of your time, and you don't have to wait for someone to upload a rooted version of your favorite stock rom.
Pete, I'm a software developer currently running BB0.4 on my Droid 1.
ReplyDeleteI was doing some testing on my personal phone (while I wait for the company to get one of theirs in my hands) and I noticed some SQLite Database errors in LogCat related to noshufou.android.su. Was wondering if you knew anything about this?
ERROR/Database(3778): close() was never explicitly called on database '/data/data/com.noshufou.android.su/databases/permissions.sqlite'
Seems more likely that whoever wrote the superuser.apk is at fault for this than it being a BB problem. The only thing I could google up was another guy running BB on his droid though...
Thanks for any help!
-jhoffman
Hey pete
ReplyDeleteJust making sure you are ok and alive. I know you are busy it just been quiet thats all!
Not sure the "right" place to post this so I'm asking it here with all the guys who I figure will know...The downloads section has "stock rooted roms." I assume they are just what they say, Stock roms that have root access. they are not BB0.4 on top of the latest OTA stock rom. I ask only because I would think Pete would have links to current BB in the downloads section. I have a current version but I don't see it on his site.
ReplyDeleteHelloooloooolooooloooo...? :)
ReplyDeleteTHANKS ----- Anonymous
ReplyDeleteThe fix as you have posted below works great! No more update nag.
http://androidforums.com/droid-roms/111881-rom-beta-bugless-beast-v0-4-android-2-2-frf84b-fully-deodexed-11.html and it will stop the OTA for FRG22D.
When V0.5?
ReplyDeleteI'm starting to wonder if 0.5 will ever get here.
ReplyDeleteLike a boss, thanks Pete.
ReplyDeleteWorked great nothing happened to my overclock on my droid 1 I am still running at 1 ghz with slayer kernal . I'm so happy to stop the enoying update notice . I can't wait for v6 .... I hope it makes my droid look like I am running gingerbread
ReplyDeleteThanks Pete, thought about patching the new ota to 05? It does have a few enhancements aside like corp calender and better touch screen. Otherwise we wait for 06 !!!
ReplyDeleteAwesome job again, Pete!
ReplyDeleteHey pete when version bb v6 comes out will it be based on frg83d if so do I have to update my phone to frg83d to use bb v6 when it comes out or will your rom update all the features that frg83d has when I install bbv6
ReplyDeleteWorks great Thanks Pete!
ReplyDeleteAccording to the changelog it is based off of FRG83D. I must have missed the 0.6 release since he already has 0.6.1 posted.
ReplyDeleteWorks great, thanks Pete!
ReplyDeleteWill this work to stop FRG83G update notifications? I couldn't find the GPA13 file you advised to flash at droidforums.net
ReplyDelete@Anonymous,
ReplyDeleteNo it will not stop the FRG83G update notifications. If you are still receiving them, please contact me, you could help me alot! You can reply back with your gmail address so we can chat. I will remove the comment so others dont get your email.
Pete,
ReplyDeleteI'm on 0.5BB and just got update.
Let me know how I can help.
Docthomas99 at gmail.com