Already rooted, is there a way to avoid upgrade notifications?

**ImCoKeMaN** · 07-04-2012, 10:32 AM

I'm probably just missing something, but I tried editing the hosts file as root and it wouldn't save. I want to make it so that my rooted playbook will remain that way even if someone else gets their hands on it and tries to "help" by updating it. Anyone have any thoughts?

**SifJar** · 07-04-2012, 12:52 PM

I believe if you reflash the current firmware using cfp it disables the update notifications. However, cfp is hard to find from what I have read (I think it's an internal RIM tool that was never meant to be made public, not 100% sure), and I'm not sure exactly what commands you need to use to reflash the firmware. I also think there's an extra command you have to enter at precisely the right time to disable the update notifications, after having flashed it.

**xsacha** · 07-04-2012, 09:09 PM

Edit the pps file that contains:
websl.blackberry.com

Change that to anything else and it won't find updates.

So, to find it:
grep -r websl.blackberry.com /pps/

**ImCoKeMaN** · 07-05-2012, 06:49 PM

Sweet, updated betaserverurls to .broken instead of .com and on reboot it doesn't find a new OS available!

Thanks!

**BullMarket** · 10-27-2012, 02:42 PM

Confirm...this works perfectly...PB is not able to connect to update server and update prompt is disabled

**Triads** · 10-27-2012, 03:12 PM

Took me awhile but reading what xsacha has wrote, you type "grep -r websl.blackberry.com /pps/" in the cmd console when you click on dingleberry button for ssh.
Says some kind of error but it shows you how to navigate to the file.
This gives you the location for WinSCP and you navigate there and open betaserverurls and change it to .broken as suggested.

**BullMarket** · 10-27-2012, 08:29 PM

Originally Posted by Triads

Took me awhile but reading what xsacha has wrote, you type "grep -r websl.blackberry.com /pps/" in the cmd console when you click on dingleberry button for ssh.
Says some kind of error but it shows you how to navigate to the file.
This gives you the location for WinSCP and you navigate there and open betaserverurls and change it to .broken as suggested.

Exactly how the procedure went for me...gives the navigation path...open the pps with notepad...change to .broken...save...i got an error message on the save write...but confirmed the change was made by opening in notepad again. Done...works like a charm!

**borceg** · 10-31-2012, 11:13 AM

Hmm, something is wrong with my root. Rooted it successfully (4869), dingle ssh works fine but can't connect it with winscp. Gives me connection refused, although dingleberry successfully opens ssh to pb.

**borceg** · 10-31-2012, 11:43 AM

or this

Code:

Authentication log (see session log for details):
Using username "root".
Server refused our key.

Authentication failed.

**SifJar** · 10-31-2012, 12:03 PM

Are you using the right key? "rsa.pub" from the dingleberry directory should work whenever SSH is running on the PB via dingleberry (start dingle SSH, once the prompt appears open WinSCP and connect using rsa.pub, making sure to leave dingle SSH running in the background so that the SSH server is still running on the PB).

**borceg** · 10-31-2012, 12:16 PM

This happens when using rsa.pub

Code:

Authentication log (see session log for details):
Unable to use key file "C:\Users\Apple\Desktop\ding\rsa.pub" (not a private key)

Authentication failed.

**SifJar** · 10-31-2012, 12:34 PM

Sorry, it must be "rsa", not "rsa.pub". I thought it was the public key, not the private (been a while since I SSH'd into my PB).

**borceg** · 10-31-2012, 01:25 PM

No matter what it simply refuses to work. Either with public or private key. Also it complaints about key format. It says the open ssh format is not supported by winscp. I converted it with puttygen but same error happens.

**BullMarket** · 10-31-2012, 04:29 PM

Originally Posted by borceg

Hmm, something is wrong with my root. Rooted it successfully (4869), dingle ssh works fine but can't connect it with winscp. Gives me connection refused, although dingleberry successfully opens ssh to pb.

I recall having an issue similar to this months back. You should try logging in via WinSCP with user name: devuser rather than: root

I might have posted about this several months ago...search devuser in the forums and that should perhaps help you get this resolved...Cheers!

**iggypop** · 10-31-2012, 05:47 PM

Turning off your wifi should do the trick *slaps knee*

**xsacha** · 10-31-2012, 06:53 PM

You realise you can't login with root borceg?
Log in with devuser with Shell Command: /tmp/setuidgid root /bin/sh

Dingleberry does this behind the scenes to make stuff easier for you.

**borceg** · 11-01-2012, 03:10 AM

Realized it now

Basically it's running ssh session with root privileges, but standard apps (filebrowser, files&folders, browser etc) never get root access right ?

**SifJar** · 11-01-2012, 03:45 AM

Originally Posted by borceg

Realized it now

Basically it's running ssh session with root privileges, but standard apps (filebrowser, files&folders, browser etc) never get root access right ?

As I understand it, they could get root access by calling the command "setuidgid root" or something like that. Without manually requesting it, it makes no sense for them to get given it.

**Anvil2k12** · 11-12-2012, 02:18 PM

can't get any sense of these hecking no-go messages (see attach)
source code read is not giving me any clue either.
I am stuck i.e can't access the cmd console (sys 2.0.0.4869).

is Dingleberry the only way to get rid of RIM's upgrade bullying?

Damian

**xsacha** · 11-12-2012, 06:20 PM

Where did you install Dingleberry? Can you make sure it is on a proper filesystem (eg. C:\ drive)?
That error is common of Dingleberry installed on networked drives.

If for some reason it is on C:\ already, then you have gone out of your way to change the permissions of rsa! Simply delete rsa and rsa.pub, then run Dingleberry again

**Anvil2k12** · 11-14-2012, 12:41 PM

cheers xsascha,

as you can see on c:\db full admin rights.
if I delete both rsa in the background I get
1st attach (dbrsa_del01.jpg).

re-ssh in that screen and I get an error
message 2nd attach (dbrsa_del02.jpg)

as far as I gathered from the source code rsa is created
independent from db, even if the Playbook is not connected.

I still can root on and on again and install the db given scripts
which do work (e.g. usb host mode on/off)
but I can't access the console.

Damian

**Anvil2k12** · 12-11-2012, 10:52 AM

Originally Posted by xsacha

Edit the pps file that contains:
websl.blackberry.com Change that to anything else...

well xsacha,
no further reply from you for almost a month,
suppose end of the given line for me here.
tried to gitbash my own keys and failed (predictable).

any chance you provide an db ssh script or
the name of the file you are talking about above?
subject its possible to locate and rename it with e.g.
Files&Folders anyway...

regards
Damian

**xsacha** · 12-13-2012, 11:51 AM

Sorry, didn't notice you were responding here.

No idea why it won't create a key for you on Windows. Is it possible that the app does not have permission to write to that folder (C:\db)?

Otherwise, no one else has had this problem before so I don't think I'll be able to resolve it.
Instead, try to generate the key. The command is (on Unix/Linux):
ssh-keygen -b 4096 -t rsa

Might need a special ssh-keygen app on Windows.
Good luck

**Anvil2k12** · 12-23-2012, 05:43 AM

"Edit the pps file that contains: websl.blackberry.com"

well, digital problems cannot be solved with luck.
unanswered questions regarding the name of the file may do.
or is there a reason for this mysterious mongering here?

Damian