Archive for July, 2018

Yeastar Password Reset

1. Power on your MyPBX U520 device, with Putty connected to console (baud rate 57600)

2. As soon your device got power, press any key several times to interrupt the boot process of device and get to the u-boot prompt, in my case it was


3. Enter the printenv command to get the u-boot constant values.

4. You should see this type of output:

update-sf=tftp 0x88000000 u-boot.spi;sf probe 0;sf erase 0 0x40000;sf write 0x88000000 0 ${filesize}
bootargs=console=tty01,57600n8 rw mem=768M root=/dev/ram
ramboot=run nandboot1;run nandboot2;run tftp-boot

and other output

5. Now you need the bootargs row. Copy the bootargs value.

6. Set the boot arguments to boot the single user mode.
For this, enter this command:
setenv bootargs ‘paste your bootargs + keyword single

For me it was like this:

pbx300>setenv bootargs 'console=tty01,57600n8 rw mem=768M root=/dev/ram single'


Changes made by setenv are lost after reboot!

7. After you set the new boot arguments, you can process to boot into the system.
If you will enter the saveenv command, you will save the current configured bootargs, and will enter single mode every time after reboot, so DONT saveenv!

8. Enter the boot command to boot with configured single mode.

9. You should boot in the system with the @(none):/# prompt.

10. Type /dev/ and press Tab twice. You should get the list of devices. You are interested in mtdblock2 device. This is the NAND memory the PBX normally boots from.

11. Create temporary mount point, using this command:

@(none):/# mkdir /mnt/temp

12. After mount point was created, mount mtdblock2 device to your running system, like that:

@(none):/# mount -t yaffs2 /dev/mtdblock2 /mnt/temp

-t yaffs2 = indicates that mounted device has YetAnotherFlashFileSystem

13. Now access memory through mount point.

@(none):/# cd /mnt/temp

Enter ls command and check if there is present /etc directory. If yes, cd into it

@(none):/mnt/temp# cd ./etc/

14. ls again, you should find passwd file.

15. Now you are going to purge the forgotten root password. For this you need to edit the passwd file, where all password are saved in encrypted form.

Check your prompt, it indicates that you are int the etc directory:


Open passwd file using ‘vi’ text editor

@(none):/mnt/temp/etc# vi passwd

See the row (in my case):


The random bunch of letters and characters


is the encrypted password.
CAREFULLY DELETE it, so you get the following row:


15. Enter :wq command to save and exit from the editor. Enter vi passwd command again and check if anything is ok and password is purged. Enter the :q command to just exit the vi text editor.

16. Enter the reboot command. Now your PBX will boot in normal way, because after reboot your setenv settings will be lost, because these was  not saved with the saveenv command. However, root password is purged now.

17. After PBX boots up and login as: prompt apperas, try to login as root. When the password prompt will appear, just hit ENTER.

You should be able to log in console with root privileges. Now enter passwd command and enter the new password.

That’s all. Be careful and don’t forget your passwords, like i did, haha! 😀



Posted in: Blog, Technical

Leave a Comment (0) →

Magento not able to log in with chrome. No Error

I had a customer update their Magento install and after got reports that chrome users couldn’t log in some times. I found a post that point me in the right direction after spreading a while researching the issue.


The trick was to create the directory app/code/local/Mage/Customer/Model and copy the file Session.php from app/code/core/Mage/Customer/Mode  into it.

Then comment out $this->renewSession(); from the setCustomerAsLoggedIn Function.

So it looks like this.

    public function setCustomerAsLoggedIn($customer)
    Mage::dispatchEvent('customer_login', array('customer'=>$customer));
    return $this;

Make sure to clear out all login cookies using ./n98-magerun.phar cache:clean config

If this doesn’t work try running  n98-magerun.phar sys:check and check if there are any issues listed.

Posted in: Blog, Technical

Leave a Comment (0) →