Onyx Nova 3 bricked - Page 2

LinuxReaderer · 01-07-2022, 02:56 PM

Quote:

Originally Posted by Renate

Edit: Oops, sorry, my bad.

Does printgpt give results or just an error?

Just an error.

It looks like I have no partitions.

$ edl r boot boot.img --memory=eMMC
Qualcomm Sahara / Firehose Client V3.53 (c) B.Kerler 2018-2021.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected

main - Mode detected: firehose
firehose - TargetName=
firehose - MemoryName=emmc
firehose - Version=
firehose_client - Supported functions:
-----------------
firehose_client
firehose_client - [LIB]: Error: Couldn't detect partition: boot
Available partitions:

The last two lines are in red on the console.

Renate · 01-07-2022, 03:16 PM

Well, if you've got 32 GB of space do an "rf" that copies the whole emmc. That should work. Then you can start doing forensics on that.

LinuxReaderer · 01-07-2022, 04:39 PM

I have the space locally, but this is what I get trying rf (removing the stack traces):

Code:

$ edl --loader=Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek.bin --memory=eMMC rf test.bin --debugmode
Qualcomm Sahara / Firehose Client V3.53 (c) B.Kerler 2018-2021.
main - Using loader Loaders/qualcomm/factory/sdm636/000cc0e100000000_7be49b72f9e43372_fhprg_bqx2_peek.bin ...
main - Waiting for the device
UsbClass
UsbClass - [LIB]:   CONFIGURATION 1: 2 mA ====================================
   bLength              :    0x9 (9 bytes)
   bDescriptorType      :    0x2 Configuration
   wTotalLength         :   0x20 (32 bytes)
   bNumInterfaces       :    0x1
   bConfigurationValue  :    0x1
   iConfiguration       :    0x0 
   bmAttributes         :   0xa0 Bus Powered, Remote Wakeup
   bMaxPower            :    0x1 (2 mA)
    INTERFACE 0: Vendor Specific ===========================
     bLength            :    0x9 (9 bytes)
     bDescriptorType    :    0x4 Interface
     bInterfaceNumber   :    0x0
     bAlternateSetting  :    0x0
     bNumEndpoints      :    0x2
     bInterfaceClass    :   0xff Vendor Specific
     bInterfaceSubClass :   0xff
     bInterfaceProtocol :   0xff
     iInterface         :    0x0 
      ENDPOINT 0x81: Bulk IN ===============================
       bLength          :    0x7 (7 bytes)
       bDescriptorType  :    0x5 Endpoint
       bEndpointAddress :   0x81 IN
       bmAttributes     :    0x2 Bulk
       wMaxPacketSize   :  0x200 (512 bytes)
       bInterval        :    0x0
      ENDPOINT 0x1: Bulk OUT ===============================
       bLength          :    0x7 (7 bytes)
       bDescriptorType  :    0x5 Endpoint
       bEndpointAddress :    0x1 OUT
       bmAttributes     :    0x2 Bulk
       wMaxPacketSize   :  0x200 (512 bytes)
       bInterval        :    0x0
main - Device detected :)
UsbClass
UsbClass - [LIB]: connect:0x200
UsbClass
UsbClass - [LIB]: Timed out
UsbClass
UsbClass - [LIB]: bytearray(b'')
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: TX:<?xml version="1.0" ?><data><nop /></data>
UsbClass
UsbClass - [LIB]: connect:0x200
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="Binary build date: Feb  4 2018 @ 00:51:33
UsbClass
UsbClass - [LIB]: RX:"/>
UsbClass
UsbClass - [LIB]: RX:</data>
main - Mode detected: firehose
UsbClass
UsbClass - [LIB]: connect:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="fh.attrs.Verbose is set to 0"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: connect:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="Chip serial num: 0 (0x0)"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: connect:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke "/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: connect:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<response value="ACK" />
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: connect:0x1000
UsbClass
UsbClass - [LIB]: Timed out
UsbClass
UsbClass - [LIB]: bytearray(b'')
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: TX:<?xml version ="1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" Verbose="True" MaxPayloadSizeToTargetInBytes="1048576"/></data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="Call to stringToNumber failed on attribute 'Verbose' with value 'True'"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="AssignAttribute failed"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<response value="NAK" />
UsbClass
UsbClass - [LIB]: RX:</data>
firehose - TargetName=
firehose - MemoryName=emmc
firehose - Version=
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: TX:<?xml version="1.0" ?><data><read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="1" physical_partition_number="0" start_sector="1"/>
UsbClass
UsbClass - [LIB]: TX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="Attribute 'SECTOR_SIZE_IN_BYTES'=512 must be equal to disk sector size 0"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="ERROR 4: Line 2226: STORAGE_READ_FAILURE"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<response value="NAK" />
UsbClass
UsbClass - [LIB]: RX:</data>
firehose_client - Supported functions:
-----------------
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: TX:<?xml version="1.0" ?><data><read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="2" physical_partition_number="0" start_sector="0"/>
UsbClass
UsbClass - [LIB]: TX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 

UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="Attribute 'SECTOR_SIZE_IN_BYTES'=512 must be equal to disk sector size 0"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="ERROR 4: Line 2226: STORAGE_READ_FAILURE"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<response value="NAK" />
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: TX:<?xml version="1.0" ?><data><read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="2" physical_partition_number="0" start_sector="0"/>
UsbClass
UsbClass - [LIB]: TX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="Attribute 'SECTOR_SIZE_IN_BYTES'=512 must be equal to disk sector size 0"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<log value="ERROR 4: Line 2226: STORAGE_READ_FAILURE"/>
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: xmlsend:0x1000
UsbClass
UsbClass - [LIB]: 
UsbClass
UsbClass - [LIB]: RX:<?xml version="1.0" encoding="UTF-8" ?>
UsbClass
UsbClass - [LIB]: RX:<data>
UsbClass
UsbClass - [LIB]: RX:<response value="NAK" />
UsbClass
UsbClass - [LIB]: RX:</data>
UsbClass
UsbClass - [LIB]: [Errno 16] Resource busy

Renate · 01-07-2022, 05:40 PM

I dunno, it works for me.

Code:

C:\Prog64\Python\python.exe edl.py rf e:\trash
Dumping sector 0 with sector count 61071360 as e:\trash.
firehose -
Reading from physical partition 0, sector 0, sectors 61071360
Progress: |--------------------------------------------------| 0.6% Read (Sector 335893)Traceback (most recent call last):

The thing is, the whole Sahara/Firehose protocol is very fragile/stupid.
If you encounter an error, reset fresh, load the loader, get the printgpt.
If it doesn't print out 20 nice lines reset and start again, this time with just the load, then rf.

LinuxReaderer · 01-07-2022, 06:25 PM

Renate, thank you so much for your patience.

As a last ditch effort I switched to a different machine, and I got it working after a few more resets! I can view the partitions and everything. Currently dumping the entire flash before proceeding with trying to push boot, recovery, etc.

Thank you again.

Renate · 01-07-2022, 06:39 PM

Ok, but I'm still confused what happened to recovery. Did that get broken too? Or is that it just doesn't have any way for you to fix from there?

LinuxReaderer · 01-07-2022, 06:55 PM

I'm not able to get into recovery as far as I can tell, or I am able to get into it, with nothing on screen, and abd not authorized to connect, if its the mode I can get into by holding down home as turning it on/plugging it in.

Actually, even after writing boot.img to boot I can't boot, and I don't see recovery.img in the update zip, so I may have to do some more reading on what system.new.dat.br is or what other partitions I have to restore.

EDIT: I decompressed system.new.dat.br then used dat2img to get an img and sent it, and finally got a boot animation. Getting there!

Renate · 01-07-2022, 08:22 PM

Well, if you can get a recovery with an unauthorized ADB you're 99% there.
Pull a copy of it off with an edl r and park it somewhere and I'll authorize and root it.

LinuxReaderer · 01-07-2022, 10:37 PM

I think what might have been happening is the phh GSI image I had silly-ly loaded to /system but didn't seem to work may have been partially booting, and giving the adb unauthorized error (with adb defaulted to enabled on that image).

Now that I've replaced system with the original image, I get the "starting up" boot animation but nothing further, it just spins endlessly. I've tried to boot into recovery every way I could find online, and none of them worked. I must have replaced recovery without backing it up, and don't have a way to get into fastboot or recovery to try to clear userdata or cache (if that's what is breaking the system and preventing it from booting).

I have this arriving tomorrow (per your PM if I understood it correctly, maybe that will give me more options to see what is going on or get to the bootloader).

Renate · 01-08-2022, 04:56 AM

Starting animation running could be as trivial as not having a home app to as serious as total flailing and self destruction. If you had ADB running you'd know which.

Yes, the hardware console can help. Just hit the space bar every second or so while booting and it will stop at the u-boot command line. You can get to fastboot from there.

As I said, get me whatever you have as a recovery image and I can help you.

LinuxReaderer · 01-08-2022, 01:55 PM

I'll PM you a link to the recovery image that I dumped off of it, but I suspect that I either wrote an incompatible recovery onto here before or otherwise messed it up. I appreciate you taking a look.

Renate · 01-08-2022, 03:06 PM

Na? Check your PM.

Ya don't make it easy. You Magisk'd your recovery.
Try this. You can flash it to recovery (if that's easier) or simply fastboot boot.

LinuxReaderer · 01-08-2022, 05:21 PM

Yeah, I had things set up great awhile back, with AFWall+ to block traffic, then messed with things a little too much and got it into this state.

OK, so using the serial connection I was able to determine that if I hold down the back/home button while the device is turning on (and the USB is NOT plugged in), I can get it into fastboot mode.

I tried erasing and re-flashing boot, system, vendor, etc from the files in the update.zip, but now system doesn't seem to be booting at all. I was able to use fastboot to boot the recovery image you sent (thank you!) but despite wiping/formatting cache and userdata using fastboot I'm getting these errors in recovery: https://imgur.com/a/je8iiHB

adb sideload didn't work either.

Renate · 01-08-2022, 05:44 PM

Let's go a little bit slow now because I'm dense.

You said that previously recovery would not even show a menu.
Now it's showing a menu, yes? Because it's my recovery?
You said that previously recovery did not have ADB working.
Is it working now? Is it rooted? Is it permissive?

Code:

# id
...
# getenforce
...

Edit: I don't recall asking you to wipe/format or even adb sideload anything. To tell the truth, I've never even used "adb sideload" and don't have any idea why I'd want to.

LinuxReaderer · 01-08-2022, 07:02 PM

Sorry. I will go slower. I was trying to not have to bother you with steps I thought I could accomplish, but I guess I don't know as much about this as I thought I did.

Yes, recovery is only working if I fastboot boot the image you sent me, and adb is only working when that is the case.

This is what I get running those commands in an adb shell:

Code:

# id
uid=0(root) gid=0(root) groups=0(root) context=u:r:su:s0
# getenforce
Permissive

01-07-2022, 05:40 PM	#19
Renate Wizard Posts: 2,303 Karma: 9599999 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	I dunno, it works for me. Code: C:\Prog64\Python\python.exe edl.py rf e:\trash Dumping sector 0 with sector count 61071360 as e:\trash. firehose - Reading from physical partition 0, sector 0, sectors 61071360 Progress: \|--------------------------------------------------\| 0.6% Read (Sector 335893)Traceback (most recent call last): The thing is, the whole Sahara/Firehose protocol is very fragile/stupid. If you encounter an error, reset fresh, load the loader, get the printgpt. If it doesn't print out 20 nice lines reset and start again, this time with just the load, then rf.

01-07-2022, 06:55 PM	#22
LinuxReaderer Member Posts: 20 Karma: 10 Join Date: Dec 2021 Device: None	I'm not able to get into recovery as far as I can tell, or I am able to get into it, with nothing on screen, and abd not authorized to connect, if its the mode I can get into by holding down home as turning it on/plugging it in. Actually, even after writing boot.img to boot I can't boot, and I don't see recovery.img in the update zip, so I may have to do some more reading on what system.new.dat.br is or what other partitions I have to restore. EDIT: I decompressed system.new.dat.br then used dat2img to get an img and sent it, and finally got a boot animation. Getting there! Last edited by LinuxReaderer; 01-07-2022 at 08:03 PM.

01-08-2022, 05:44 PM	#29
Renate Wizard Posts: 2,303 Karma: 9599999 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	Let's go a little bit slow now because I'm dense. You said that previously recovery would not even show a menu. Now it's showing a menu, yes? Because it's my recovery? You said that previously recovery did not have ADB working. Is it working now? Is it rooted? Is it permissive? Code: # id ... # getenforce ... Edit: I don't recall asking you to wipe/format or even adb sideload anything. To tell the truth, I've never even used "adb sideload" and don't have any idea why I'd want to. Last edited by Renate; 01-08-2022 at 05:48 PM.

01-08-2022, 07:02 PM	#30
LinuxReaderer Member Posts: 20 Karma: 10 Join Date: Dec 2021 Device: None	Sorry. I will go slower. I was trying to not have to bother you with steps I thought I could accomplish, but I guess I don't know as much about this as I thought I did. Yes, recovery is only working if I fastboot boot the image you sent me, and adb is only working when that is the case. This is what I get running those commands in an adb shell: Code: # id uid=0(root) gid=0(root) groups=0(root) context=u:r:su:s0 # getenforce Permissive

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Ended Onyx Boox Nova 2	downeaster59	Flea Market	6	02-14-2022 11:19 PM
Sell Onyx Nova 2	mtreader	Flea Market	4	12-18-2020 02:38 PM
Onyx nova 2 and chrome	La Mergouille	Onyx Boox	0	05-05-2020 09:37 PM
Onyx Nova Pro	Like_to_read	Onyx Boox	6	09-03-2019 08:21 AM

01-07-2022, 03:16 PM	#17
Renate Wizard Posts: 2,303 Karma: 9599999 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	Well, if you've got 32 GB of space do an "rf" that copies the whole emmc. That should work. Then you can start doing forensics on that.

01-07-2022, 06:25 PM	#20
LinuxReaderer Member Posts: 20 Karma: 10 Join Date: Dec 2021 Device: None	Renate, thank you so much for your patience. As a last ditch effort I switched to a different machine, and I got it working after a few more resets! I can view the partitions and everything. Currently dumping the entire flash before proceeding with trying to push boot, recovery, etc. Thank you again.

01-07-2022, 06:39 PM	#21
Renate Wizard Posts: 2,303 Karma: 9599999 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	Ok, but I'm still confused what happened to recovery. Did that get broken too? Or is that it just doesn't have any way for you to fix from there?

01-07-2022, 08:22 PM	#23
Renate Wizard Posts: 2,303 Karma: 9599999 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	Well, if you can get a recovery with an unauthorized ADB you're 99% there. Pull a copy of it off with an edl r and park it somewhere and I'll authorize and root it.

01-07-2022, 10:37 PM	#24
LinuxReaderer Member Posts: 20 Karma: 10 Join Date: Dec 2021 Device: None	I think what might have been happening is the phh GSI image I had silly-ly loaded to /system but didn't seem to work may have been partially booting, and giving the adb unauthorized error (with adb defaulted to enabled on that image). Now that I've replaced system with the original image, I get the "starting up" boot animation but nothing further, it just spins endlessly. I've tried to boot into recovery every way I could find online, and none of them worked. I must have replaced recovery without backing it up, and don't have a way to get into fastboot or recovery to try to clear userdata or cache (if that's what is breaking the system and preventing it from booting). I have this arriving tomorrow (per your PM if I understood it correctly, maybe that will give me more options to see what is going on or get to the bootloader).

01-08-2022, 04:56 AM	#25
Renate Wizard Posts: 2,303 Karma: 9599999 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	Starting animation running could be as trivial as not having a home app to as serious as total flailing and self destruction. If you had ADB running you'd know which. Yes, the hardware console can help. Just hit the space bar every second or so while booting and it will stop at the u-boot command line. You can get to fastboot from there. As I said, get me whatever you have as a recovery image and I can help you.

01-08-2022, 01:55 PM	#26
LinuxReaderer Member Posts: 20 Karma: 10 Join Date: Dec 2021 Device: None	I'll PM you a link to the recovery image that I dumped off of it, but I suspect that I either wrote an incompatible recovery onto here before or otherwise messed it up. I appreciate you taking a look.

01-08-2022, 03:06 PM	#27
Renate Wizard Posts: 2,303 Karma: 9599999 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5	Na? Check your PM. Ya don't make it easy. You Magisk'd your recovery. Try this. You can flash it to recovery (if that's easier) or simply fastboot boot.

01-08-2022, 05:21 PM	#28
LinuxReaderer Member Posts: 20 Karma: 10 Join Date: Dec 2021 Device: None	Yeah, I had things set up great awhile back, with AFWall+ to block traffic, then messed with things a little too much and got it into this state. OK, so using the serial connection I was able to determine that if I hold down the back/home button while the device is turning on (and the USB is NOT plugged in), I can get it into fastboot mode. I tried erasing and re-flashing boot, system, vendor, etc from the files in the update.zip, but now system doesn't seem to be booting at all. I was able to use fastboot to boot the recovery image you sent (thank you!) but despite wiping/formatting cache and userdata using fastboot I'm getting these errors in recovery: https://imgur.com/a/je8iiHB adb sideload didn't work either.

Advert

Advert