Onyx Note 3 bricked

[cicabum]

Thanks to Renate I rooted my Onyx Note 3, but afterwards I did something very very stupid: I installed Busybox module via Magisk and now if I turn on my device it remains stucked on Onyx Logo, reboots many times or something like that. I can only use fastboot, but Adb doesn't work. I have no idea what to do. I really need help

[Renate]

Oops, sorry. There were a few things that I should have suggested for you to do as insurance.
If you have a copy of the original (unmodified) boot.img (3.1 or 3.2) you can simply fastboot boot that. If you have a copy of the recovery.img, that can be modded to add ADB. What do you have for images? Does a TWRP exist?

In any case, the first thing to do is see if you really lost ADB. On my Poke3 it goes to the big seashell and the dots that count up. If you didn't screw things up too badly you should still have ADB even if the Android home screen never shows up.

C:\>adb shell
$ su
# stop
# cd /data/adb/modules/Whatever
-- delete whatever is necessary --
# reboot

[cicabum]

Originally Posted by Renate

Oops, sorry. There were a few things that I should have suggested for you to do as insurance.
If you have a copy of the original (unmodified) boot.img (3.1 or 3.2) you can simply fastboot boot that. If you have a copy of the recovery.img, that can be modded to add ADB. What do you have for images? Does a TWRP exist?

In any case, the first thing to do is see if you really lost ADB. On my Poke3 it goes to the big seashell and the dots that count up. If you didn't screw things up too badly you should still have ADB even if the Android home screen never shows up.

C:\>adb shell
$ su
# stop
# cd /data/adb/modules/Whatever
-- delete whatever is necessary --
# reboot

I've already tried "fastboot boot" the original 3.1 boot.img but it doesn't help.
I don't have neither the recovery image nor TWRP, but I can decrypt one more time the firmware 3.1 if it's necessary and get the recovery image. I'm trying to enter in recovery mode but usual steps with power button and back button do not work:
"1] With pressed home button connect your turned off Max Lumi with USB C to a charger.
[2] You get the Onyx splash boot screen.
[3] Release the home button.
[4] LED next to power button is blue. Recovery mode starts."

I don't think I'll be able to use ADB, because today I've deactivated "USB Debugging" in Onyx Settings. It's a complete disaster, because I use this device for work

[Renate]

The original 3.1 boot.img boot loops???
Are you sure that you're not mixing up your images?
See if you can get recovery out of an update (if it's there).
If you find it, try to fastboot boot it.
If it doesn't have ADB working, PM me a copy of it and I'll try to add it.
(This would all be a piece of cake if I had a Note3.)

[cicabum]

Originally Posted by Renate

The original 3.1 boot.img boot loops???
Are you sure that you're not mixing up your images?

Not exactly. It seems to me that it reboots every time I press the power button.
It's for sure the originale 3.1 boot.img

Yesterday I sent an email to Ereader.store and was contacted today. This is true customer care! Unfortunately I can't get into recovery mode so I have to send my device back to them. Renate, thanks anyway for your help

[Renate]

Seriously? You're going to ship this out?

There's so many ways to fix this if you can get to fastboot and that's not even talking about EDL mode.

Somebody with a Note3 could send you a non-Magisk 3.2 boot.img
You (I) could modify a boot.img or recovery.img
Did you even look for a recovery.img in an update?
Even the Magisk 3.2 boot.img could be modified, although that's a bit more work.
If you haven't sent it off already, PM me some kind of image.

[cicabum]

Yes, I have already sent the device to ereader.store. Since I don't live very far from them and they offer excellent technical support, it's much more convenient for me, especially in terms of time, to send it back for repair than to try to fix the problem myself. I thank you anyway for your helpfulness and kindness