I've bricked my Page trying to root it

Yvon · 03-22-2025, 02:25 PM

Hello everyone.

I just bricked my Page 7 while trying to root it, and of course I didn't make a backup of my partitions

I followed the instructions of this page:
https://www.mobileread.com/forums/sh...d.php?t=357269

I actually followed instructions for a Poke 5 because I had understood that the rooting process was the same.

I skipped the update because I already had the latest firmware. I downloaded a version on my computer following https://www.redditmedia.com/r/Onyx_B..._firmware_for/.

It was only at the last flashing step that I had to improvise because the command wasn't available from flashboot.

So I tried to do the same thing from EDL:

Code:

$ edl w boot_a magisk_patched-28100_xGayU.img
$ edl w vbmeta_a vbmeta.img

No error but the device is now bricked. On boot it gets stuck on the logo. It flashes and restarts, indefinitely.

I can enter EDL mode with a cable following these instructions: https://www.mobileread.com/forums/sh...d.php?t=361279.

How can I get out of this mess?

Thank you very much for your help.

Renate · 03-23-2025, 01:37 AM

You probably Magisk'ed a boot image that was not the same as the boot image that was actually on your device. You should always pull your current boot image off your device with EDL (if you can).

You can try doing an update to the latest version using recovery.
Is your problem getting to recovery?
You can flash this to the misc partition with EDL and it will go to recovery.
Be aware that if you have some problem with the recovery it will keep going back there until you clear misc.

Yvon · 03-23-2025, 02:48 AM

Thank you very much Renate.

That was indeed the problem, and what took me time to realize yesterday is that I could sideload a new firmware from recovery to start from scratch.

The system is no more bricked and I even allowed myself to start over: it is now successfully rooted!

However, I no longer have WiFi: impossible to activate it! It's not that it refuses to connect, it won't even turn on and scan. I tried from the console without any more success. I tried to reset the device several time with and without the patch. I finally wrote to Boox.

Code:

$ cmd wifi status
Wifi is disabled
Wifi scanning is only available when wifi is enabled
BOOX:/ $ cmd wifi set-wifi-enabled enabled
BOOX:/ $ cmd wifi status
Wifi is disabled
Wifi scanning is only available when wifi is enabled

Thank you again, and even though I'm struggling, I'm learning a lot of things.

Renate · 03-23-2025, 03:24 AM

Quote:

Originally Posted by Yvon

I no longer have WiFi...

I can't say with certainty, but WiFi is usually implemented in a kernel module which has to exactly match the kernel in the boot image.

Code:

adb shell
lsmod
...
wlan
...

If you don't see anything, it's not loaded.

I don't know where yours is, but mine is /vendor/lib/modules/qca_cld3_wlan.ko

Code:

modinfo /vendor/lib/modules/qca_cld3_wlan.ko
...
vermagic:       4.19.157-perf-g351a76a7468f SMP preempt mod_unload modversions aarch64
...
uname -u
Linux localhost 4.19.157-perf-g67951f32e775-dirty #7 SMP PREEMPT Fri Jan 24 19:53:05 CST 2025 aarch64

Yvon · 03-23-2025, 04:13 AM

Everything seems ok

Code:

127|BOOX:/ # lsmod
Module                  Size  Used by
wlan                 8093696  0

Code:

BOOX:/ # modinfo /vendor/lib/modules/qca_cld3_wlan.ko
(...)
vermagic:       4.19.157-perf-gb60ba6d87d35 SMP preempt mod_unload modversions aarch64

Code:

1|BOOX:/ # uname -a
Linux localhost 4.19.157-perf-g6400ae12a133-dirty #2697 SMP PREEMPT Mon Sep 9 12:42:26 CST 2024 aarch64

Renate · 03-23-2025, 07:22 AM

Well, if you're rooted look at dmesg when you try to turn on WiFi. logcat might have something too.

Yvon · 03-23-2025, 08:01 AM

dmesg: the "Time-out!!!" seems realted to the wifi as I don't see this message otherwise.

Code:

[  310.142879] Wifi Turning On from UI
[  312.806654] onyx_charging_temp_check_work: batt temp: 193, charger temp: 183, current charger level: 0
[  315.152210] onyx_pm_notifier_list_call_chain:onyx-pm-notifier: need onyx_pm_notifier_chain, state:0x10
[  315.152219] onyx-tp-power: get notifier: old_state:1, new_state:0
[  315.152222] onyx-tp-power: ignored notifier: old_state:1, new_state:0
[  315.152225] PM: ONYX_PM_STATE from freeze[1] to on[0]
[  315.487471] healthd: battery l=100 v=4386 t=19.3 h=2 st=5 c=0 fc=2396000 cc=0 chg=a
[  323.047213] onyx_charging_temp_check_work: batt temp: 193, charger temp: 182, current charger level: 0
[  323.676588] healthd: battery l=100 v=4386 t=19.3 h=2 st=5 c=0 fc=2396000 cc=0 chg=a
[  325.159844] onyx_pm_notifier_list_call_chain:onyx-pm-notifier: need onyx_pm_notifier_chain, state:0x01
[  325.159853] onyx-tp-power: get notifier: old_state:0, new_state:1
[  325.159856] onyx-tp-power: ignored notifier: old_state:0, new_state:1
[  325.159859] PM: ONYX_PM_STATE from on[0] to freeze[1]
[  330.720189] Timed-out!!

Logcat is more verbose

Code:

09-11 03:57:41.657  1400  1946 I WifiService: setWifiEnabled package=com.android.shell uid=0 enable=true
09-11 03:57:41.660  1400  1531 D WifiActiveModeWarden: Starting ClientModeManager
09-11 03:57:41.660  1400  1531 D WifiClientModeManager7: Starting with role ROLE_CLIENT_SCAN_ONLY
09-11 03:57:41.660  1400  1531 D WifiController: DisabledState.exit()
09-11 03:57:41.660  1400  1531 D WifiController: EnabledState.enter()
09-11 03:57:41.660  1400  1531 D WifiClientModeManager7: entering IdleState
09-11 03:58:01.739   759   759 E android.hardware.wifi@1.0-service: Failed to write driver state control param: Invalid argument
09-11 03:58:01.739   759   759 E android.hardware.wifi@1.0-service: Failed to load WiFi driver
09-11 03:58:01.739   759   759 E android.hardware.wifi@1.0-service: Failed to initialize firmware mode controller
09-11 03:58:01.739   759   759 E android.hardware.wifi@1.0-service: Wifi HAL start failed
09-11 03:58:01.740  1400  1531 E HalDevMgr: Cannot start IWifi: 9 ()
09-11 03:58:01.740  1400  1531 E WifiVendorHal: Failed to start vendor HAL
09-11 03:58:01.740  1400  1531 E WifiNative: Failed to start vendor HAL
09-11 03:58:01.740  1400  1531 E WifiNative: Failed to start Hal
09-11 03:58:01.740  1400  1531 E WifiClientModeManager7: Failed to create ClientInterface. Sit in Idle
09-11 03:58:01.740  1400  1531 D WifiScanRequestProxy: Sending scan available broadcast: false
09-11 03:58:01.741  1400  1534 I WifiScanningService: Received a request to disable scanning, UID = 1000
09-11 03:58:01.741  1400  1534 I WifiScanningService: wifi driver unloaded
09-11 03:58:01.741  1400  1531 I WifiScanRequestProxy: Scanning is disabled
09-11 03:58:01.742  1400  1531 D WifiClientModeManager7: received an invalid message: { when=-20s82ms what=2 arg1=2 target=com.android.wifi.x.com.android.internal.util.StateMachine$SmHandler }
09-11 03:58:01.742  1400  1531 D WifiController: STA disabled, return to DisabledState.
09-11 03:58:01.742  1400  1531 D WifiController: EnabledState.exit()
09-11 03:58:01.742  1400  1531 D WifiController: DisabledState.enter()

Also I can read the following lines above:

Code:

01-02 02:12:59.073  1127  1127 I cnss-daemon: /data/vendor/wifi/wlfw_cal_00.bin cal file does not exists
01-02 02:12:59.073  1127  1127 I cnss-daemon: /data/vendor/wifi/wlfw_cal_01.bin cal file does not exists
01-02 02:12:59.073  1127  1127 I cnss-daemon: /data/vendor/wifi/wlfw_cal_02.bin cal file does not exists
01-02 02:12:59.073  1127  1127 I cnss-daemon: /data/vendor/wifi/wlfw_cal_03.bin cal file does not exists
01-02 02:12:59.073  1127  1127 I cnss-daemon: /data/vendor/wifi/wlfw_cal_04.bin cal file does not exists
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_read_file: No such file /data/vendor/wifi/wlfw_cal_00.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_build_cal_table: not read /data/vendor/wifi/wlfw_cal_00.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_read_file: No such file /data/vendor/wifi/wlfw_cal_01.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_build_cal_table: not read /data/vendor/wifi/wlfw_cal_01.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_read_file: No such file /data/vendor/wifi/wlfw_cal_02.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_build_cal_table: not read /data/vendor/wifi/wlfw_cal_02.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_read_file: No such file /data/vendor/wifi/wlfw_cal_03.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_build_cal_table: not read /data/vendor/wifi/wlfw_cal_03.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_read_file: No such file /data/vendor/wifi/wlfw_cal_04.bin
01-02 02:12:59.441  1127  1256 I cnss-daemon: wlfw_build_cal_table: not read /data/vendor/wifi/wlfw_cal_04.bin

Here is the full logcat logs (grep -i wifi): https://gist.github.com/yvon/4063ed6...64afa8213e6a3c

And here is the full dmesg (grep -i wifi too): https://gist.github.com/yvon/d25182b...21e1c04f27bec6

In both logs we can see files missing in /data/vendor/wifi.

Here are the files in /data/vendor/wifi

Code:

BOOX:/ # ls /data/vendor/wifi/
cnss_diag.conf  hostapd  sockets  wigig_hostapd  wlan_logs  wpa  wpa_supplicant

Renate · 03-23-2025, 09:50 AM

I see the same stuff in /data/vendor/wifi
I don't get any mention of wlfw_cal or find any file like that anywhere.

One of the problems with software today is that it's so shoddy that even when it works there is a train wreck of error messages.

I think that you're problem is:

Code:

Failed to write driver state control param: Invalid argument

03-22-2025, 02:25 PM	#1
Yvon Junior Member Posts: 4 Karma: 10 Join Date: Mar 2025 Device: Page	I've bricked my Page trying to root it Hello everyone. I just bricked my Page 7 while trying to root it, and of course I didn't make a backup of my partitions I followed the instructions of this page: https://www.mobileread.com/forums/sh...d.php?t=357269 I actually followed instructions for a Poke 5 because I had understood that the rooting process was the same. I skipped the update because I already had the latest firmware. I downloaded a version on my computer following https://www.redditmedia.com/r/Onyx_B..._firmware_for/. It was only at the last flashing step that I had to improvise because the command wasn't available from flashboot. So I tried to do the same thing from EDL: Code: $ edl w boot_a magisk_patched-28100_xGayU.img $ edl w vbmeta_a vbmeta.img No error but the device is now bricked. On boot it gets stuck on the logo. It flashes and restarts, indefinitely. I can enter EDL mode with a cable following these instructions: https://www.mobileread.com/forums/sh...d.php?t=361279. How can I get out of this mess? Thank you very much for your help.

03-23-2025, 02:48 AM	#3
Yvon Junior Member Posts: 4 Karma: 10 Join Date: Mar 2025 Device: Page	Thank you very much Renate. That was indeed the problem, and what took me time to realize yesterday is that I could sideload a new firmware from recovery to start from scratch. The system is no more bricked and I even allowed myself to start over: it is now successfully rooted! However, I no longer have WiFi: impossible to activate it! It's not that it refuses to connect, it won't even turn on and scan. I tried from the console without any more success. I tried to reset the device several time with and without the patch. I finally wrote to Boox. Code: $ cmd wifi status Wifi is disabled Wifi scanning is only available when wifi is enabled BOOX:/ $ cmd wifi set-wifi-enabled enabled BOOX:/ $ cmd wifi status Wifi is disabled Wifi scanning is only available when wifi is enabled Thank you again, and even though I'm struggling, I'm learning a lot of things.

03-23-2025, 09:50 AM	#8
Renate Onyx-maniac Posts: 3,671 Karma: 15675331 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	I see the same stuff in /data/vendor/wifi I don't get any mention of wlfw_cal or find any file like that anywhere. One of the problems with software today is that it's so shoddy that even when it works there is a train wreck of error messages. I think that you're problem is: Code: Failed to write driver state control param: Invalid argument Last edited by Renate; 03-23-2025 at 09:54 AM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Boox Tab8C got bricked after root attempt	alonerbg	Onyx Boox	10	03-23-2025 01:00 PM
Root Boox Page	ebenash	Onyx Boox	4	05-19-2024 07:42 AM
Anyone able to root the Boox Page?	parkaymang	Onyx Boox	21	02-04-2024 05:35 AM
PRS-T1 Unable to root prs-r1 with rupor minimal ever again, no 3rd page...	svemir	Sony Reader	1	10-15-2012 04:09 PM
PRS-T1 Bricked Device After Some Changes in Root	borzeh	Sony Reader	2	01-24-2012 03:03 PM

03-23-2025, 07:22 AM	#6
Renate Onyx-maniac Posts: 3,671 Karma: 15675331 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	Well, if you're rooted look at dmesg when you try to turn on WiFi. logcat might have something too.

Advert

Advert