Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Rockbox Ports are now being developed for various digital audio players!

+  Rockbox Technical Forums
|-+  Rockbox Development
| |-+  New Ports
| | |-+  Shanling Q1
« previous next »
  • Print
Pages: 1 ... 5 6 [7]

Author Topic: Shanling Q1  (Read 9237 times)

Offline mambo5king

  • Member
  • *
  • Posts: 9
Re: Shanling Q1
« Reply #90 on: October 28, 2022, 02:45:22 PM »
Quote from: amachronic on October 28, 2022, 12:32:32 PM
Quote from: mambo5king on October 13, 2022, 08:30:37 AM
[...] Mine must have been corrupted or the backup process didn't work.

Your backup contains rockbox-info.txt... what appears to be random junk... and apparently a copy of bootloader.q1! Whatever the case, that backup can't have come from a bootable device.

I'll add some basic sanity checks to the restore process to prevent it flashing total garbage, but honestly, I have no idea how all that junk got into your backup in the first place. Especially rockbox-info.txt, since it doesn't exist anywhere except inside the .rockbox folder, and the bootloader doesn't open it.

Yeah, not sure what happened.  The sequence of events was as follows:
1. Used Q1 for 6 months with stock firmware
2. Tried rockbox for a month
3. Decided to go back to stock firmware, restored backed up bootloader
4. Used Q1 for 2 months
5. Decided to try rockbox again, backed up bootloader
6. Decided to switch back, restore failed.
Logged

Offline 7o9

  • Member
  • *
  • Posts: 117
Re: Shanling Q1
« Reply #91 on: October 29, 2022, 01:59:08 AM »
Quote from: amachronic on October 28, 2022, 12:55:49 PM
Quote from: 7o9 on October 28, 2022, 12:49:36 PM
Is restoring a backup of the stock bootloader that you are suppose to make when installing Rockbox the way to revert to the stock firmware?
Yeah, that's supposed to be the tried & true method.
I understand and read all the warnings when initially installing but it would still be good if there was an independent way to return to stock.

But given that the Shanling firmware apparently does not touch/contain the bootloader, there is no such thing as a '2.2' bootloader? Anyone with an original Q1 and the latest tools could donate a bootloader for the greater good.

Having said that, I am very happy with Rockbox on my Q1 and with the option to hold a button to boot the OF, I have best of both worlds.
Logged

Offline amachronic

  • Developer
  • Member
  • *
  • Posts: 260
Re: Shanling Q1
« Reply #92 on: October 29, 2022, 08:25:10 AM »
I've uploaded my Q1 and M3K bootloader backups to the wiki. They're found on the JztoolInstall page in the "Removing Rockbox" section.
Logged

Offline amachronic

  • Developer
  • Member
  • *
  • Posts: 260
Re: Shanling Q1
« Reply #93 on: October 31, 2022, 06:41:26 AM »
Here's a new bootloader release for the Q1, version b4e7c60c6d-221029. Download it here or from the wiki.

This version fixes a few bugs:

The old Rockbox bootloader interrupted the original firmware's update process, preventing OF updates from being installed. This is fixed in the new version, and you can now update the Q1's firmware from the Shanling player app. There are a couple things to be aware of: Shanling's updates don't include the bootloader, so the Rockbox bootloader will remain installed after an OF update. If you want to remove Rockbox you need to restore from a bootloader backup. Second, after the update finishes you will be rebooted into Rockbox. The update has succeeded at this point, but some leftover files will remain on the SD card; you can either remove them yourself or reboot to the Shanling app, which should clean up the files automatically.

The bootloader backup and restore functionality will now display an error message if it looks like the backup is corrupted. The level of protection is minimal but it's better than the old bootloader, which had no such safety checks.

The Linux loader had a bug which added garbage to the end of the kernel command line. This has been fixed.
« Last Edit: October 31, 2022, 05:34:42 PM by amachronic »
Logged

  • Print
Pages: 1 ... 5 6 [7]
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox Development
| |-+  New Ports
| | |-+  Shanling Q1
 

  • SMF 2.0.19 | SMF © 2021, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.024 seconds with 15 queries.