Onyx Boox Page bricked, can only access edl

[RIPBobDole]

I didn't know about taking the emmc image before messing with stuff and have managed to brick my Page trying to apply an update. I can get into 9008 mode using the test pins and the loader is working fine. I can print the gpt table still, just not sure what to do about getting back to recovery or fastboot.

Any help would be appreciated, thanks.

[RIPBobDole]

This is the output of "edl /g"

Found EDL 9008, configuring... ok
Requesting info on LUN 0... ok
Requesting GPT 0 header... ok, receiving... ok, requesting entries... ok, receiving... ok

 #  Name                   Start       Count  Type
──  ────────────────  ──────────  ──────────  ────────────────────
 1  xbl_a                 131072        7168  Inactive
 2  xbl_b                 138240        7168  Bootloader
 3  xbl_config_a          262144         256  Inactive
 4  xbl_config_b          262400         256  Boot config
 5  tz_a                  393216        8192  Inactive
 6  tz_b                  524288        8192  TrustZone
 7  rpm_a                 655360        1024  Inactive
 8  rpm_b                 786432        1024  Resource/power mgmt
 9  hyp_a                 917504        1024  Inactive
10  hyp_b                1048576        1024  Hypervisor
11  boot_a               1049600      196608  Inactive
12  boot_b               1246208      196608  Boot
13  super                1442816     8388608  Super
14  vbmeta_system_a      9961472         128  VB meta system
15  vbmeta_system_b      9961600         128  VB meta system B
16  recovery_a           9961728      196608  Recovery
17  recovery_b          10158336      196608  Recovery B
18  keymaster_a         10354944        1024  Inactive
19  keymaster_b         10355968        1024  Key master
20  cmnlib_a            10356992        1024  Inactive
21  cmnlib64_a          10358016        1024  Inactive
22  cmnlib_b            10359040        1024  Common lib
23  cmnlib64_b          10360064        1024  Common lib64
24  mdtpsecapp_a        10361088        8192  Inactive
25  mdtpsecapp_b        10369280        8192  MDTP secure
26  mdtp_a              10377472       65536  Inactive
27  mdtp_b              10443008       65536  MDTP
28  modem_a             10508544      368640  Inactive
29  modem_b             10877184      368640  FAT32
30  dsp_a               11245824       65536  Inactive
31  dsp_b               11311360       65536  DSP
32  abl_a               11376896        2048  Inactive
33  abl_b               11378944        2048  Android bootloader
34  ddr                 11380992        2048  DDR
35  bluetooth_a         11383040        2048  Inactive
36  bluetooth_b         11385088        2048  Bluetooth
37  ssd                 11403264          16  Secure SW download
38  dtbo_a              11403280       49152  Inactive
39  dtbo_b              11452432       49152  DTBO
40  imagefv_a           11501584        4096  Inactive
41  imagefv_b           11505680        4096  Image FV
42  uefisecapp_a        11509776        4096    be8a7e08
43  uefisecapp_b        11513872        4096  Inactive
44  persist             11517968       65536  Persist
45  metadata            11583504       32768  Metadata
46  misc                11616272        2048  Misc
47  keystore            11618320        1024  Key store
48  devcfg_a            11619344         256  Inactive
49  devcfg_b            11619600         256  Device config
50  featenabler_a       11619856         256    741813d2
51  featenabler_b       11620112         256  Inactive
52  qupfw_a             11620368         128  Inactive
53  qupfw_b             11620496         128  QUP firmware
54  frp                 11620624        1024  FRP
55  rawdump             11621648      262144  RAM dump
56  devinfo             11927552           8  Device info
57  dip                 11927560        2048  DIP
58  apdp                12058624         512  APDP
59  spunvm              12059136       16384  Spun VM
60  splash              12075520       66848  Splash
61  limits              12189696           8  Limits
62  toolsfv             12189704        2048  Tools FV
63  logfs               12320768       16384  Log FS
64  cateloader          12337152        4096  STI
65  logdump             12341248      131072  Log dump
66  vbmeta_a            12582912         128  Inactive
67  vbmeta_b            12583040         128  VB meta
68  storsec             12583168         256  Store secure
69  multiimgoem_a       12583424          64  Inactive
70  multiimgoem_b       12583488          64    e126a436
71  multiimgqti         12583552          64    846c6f05
72  secdata             12583616          50    76cfc7ef
73  catefv              12583672        1024  Cate FV
74  catecontentfv       12584696        2048  Cate content FV
75  uefivarstore        12586744        1024    165bd6bc
76  modemst1            12713984        4096  Modem ST1
77  modemst2            12718080        4096  Modem ST2
78  fsg                 12845056        4096  Modem storage
79  fsc                 12976128         256  FSC
80  onyxconfig          12976384       49152  System
81  userdata            13025536    48168671  User data

[Renate]

You can get into recovery by going to EDL mode, loading the loader, then writing a misc that will take you to recovery, then rebooting.

Rename the silly file misc-recovery.img so you don't get confused.

edl /w /pmisc misc-recovery.img /z

[RIPBobDole]

Progress!

It's definitely alive again, here's what all has happened

I flashed the misc-recovery.img but using /z didn't bring me directly to recovery, so to finally get there I had to hold the power button a bit when the led lit up again and press the power button a repeatedly to eventually make it in.

I managed to make it into recovery and sideload the firmware, then using recovery I rebooted to system successfully, but I don't think using the power button normally is letting me boot properly to system, it just stays stuck on the onyx logo unless I do the same trick I used to get to recovery initially. If I use adb reboot I also have to do the trick with the power button.

Thanks again for the help, was really worried this thing was just going to be a paperweight

[RIPBobDole]

Something I just noticed, it only stays booted to system or recovery when the usb cable is connected. It does detect the battery level fine. If the usb cable is disconnected it stays powered on for a few moments and then shuts off and it refuses to show anything except the onyx logo until the usb cable is connected again.

[Renate]

Sounds like the battery is dead.

[RIPBobDole]

It says it's at 100% at the top right and the battery status in the power section shows full

[Renate]

If removing USB makes it die within seconds you might have the voltage but not the current.

[RIPBobDole]

Are there any other issues that could cause this? The battery did not have this issue prior to me messing up the update and the led stays turned on even though the rest of the device doesn't. I left the led on overnight and the os now reports 45% battery instead of a full battery.

[Renate]

You can use my UsbMode.apk (in my sig). That shows battery voltage. Pull the USB and see how fast it drops.

[RIPBobDole]

This is what it shows when it's plugged in to my computers usb port



This is what it shows once disconnected from usb



The battery voltage stays stable at 3.839 V until the device powers off. After it powers off, the blue led turns back on but the screen and everything else remains off.

[Renate]

One Ampere is a heck of a lot of current going out. Something is grinding this down.

adb shell top

[RIPBobDole]

This is the output of adb shell top

Tasks: 624 total,   1 running, 623 sleeping,   0 stopped,   0 zombie
  Mem:  2692216K total,  2480184K used,   212032K free,   3690496 buffers
 Swap:  1572860K total,   367004K used,  1205856K free,  1060688K cached
800%cpu   5%user   1%nice  18%sys 772%idle   0%iow   3%irq   1%sirq   0%host
   PID USER         PR  NI VIRT  RES  SHR S[%CPU] %MEM     TIME+ ARGS
   386 root         20   0    0    0    0 S  9.3   0.0   0:10.82 [epdc_msg_thre+
   299 root         RT   0    0    0    0 S  3.0   0.0   0:02.50 [crtc_commit:1+
   300 root         RT   0    0    0    0 S  2.3   0.0   0:01.75 [crtc_event:11+
  4437 shell        20   0  12G 4.7M 3.2M R  2.0   0.1   0:01.76 top
   811 root         -2  -8  12G  32M  25M S  2.0   1.2   0:07.63 surfaceflinger
  4909 u0_a121      10 -10  14G  99M  81M S  1.6   3.7   0:00.73 com.temblast.u+
   674 root          0 -20    0    0    0 I  1.6   0.0   0:01.07 [kworker/u17:3+
   246 root         20   0    0    0    0 I  1.3   0.0   0:01.11 [kworker/u16:7+
  1367 system       18  -2  17G 232M 203M S  1.0   8.8   0:46.37 system_server
   778 system       -3   0  12G 4.0M 3.2M S  1.0   0.1   0:02.63 vendor.qti.har+
   302 root         20   0    0    0    0 D  1.0   0.0   0:01.24 [mdss_fb_epdc]
   297 root         RT   0    0    0    0 S  1.0   0.0   0:02.28 [crtc_commit:7+
   241 root         20   0    0    0    0 I  1.0   0.0   0:00.70 [kworker/u16:4+
  2319 u0_a70       20   0  15G  84M  67M S  0.6   3.2   0:01.63 com.onyx.float+
  2200 root         RT   0    0    0    0 S  0.6   0.0   0:00.64 [irq/46-1b8e30+
   384 root         RT   0    0    0    0 D  0.6   0.0   0:03.04 [epdc_refresh_+
   247 root         -3   0    0    0    0 S  0.6   0.0   0:00.56 [kgsl_worker_t+
  2097 u0_a92       20   0  15G 217M 163M S  0.3   8.2   0:23.58 com.google.and+
  1719 network_sta+ 20   0  15G  29M  22M S  0.3   1.1   0:00.87 com.android.ne+
   987 system       20   0  12G 2.4M 2.2M S  0.3   0.0   0:00.87 cnss_diag -q -+

[Renate]

It looks like it's all idle.
Try to watch it die.

adb logcat

Or, if you're rooted:

adb shell
su
dmesg -w

[RIPBobDole]

Here is the output of dmesg -w