[Please help] Tecno NX bricked
[Please help] Tecno NX bricked
(19-09-2018, 06:35 PM)RMT ...
After I unpacked the boot backup. And after comparing with stock, I conclude it's the same.
screenshot : (stock boot on the left and boot backup on the right) https://1drv.ms/u/s!AmUA1o5VkY3Xkh8Lj19rRb8uTwZx
Root folder is the same.
(19-09-2018, 10:20 PM)X3non(19-09-2018, 06:35 PM)RMT ...
After I unpacked the boot backup. And after comparing with stock, I conclude it's the same.
screenshot : (stock boot on the left and boot backup on the right) https://1drv.ms/u/s!AmUA1o5VkY3Xkh8Lj19rRb8uTwZx
Root folder is the same.
OK this is good tests you've carried out
in section 3, which backup is this "previous successfully whole stock rom backup" ?
the one you got from wwr_mtk or a different one?
Quote:So,
because I came back to philz now, I tried few things and I found 2 interesting things that maybe could help :
First, I'm able to perform a full backup! Before, I can just backup boot, recovery and system. I think it can be possible because no data has been encrypted.
Just look at this log in philz :
…
Quote:And, it wasn't actually the stock recovery as I said earlier.
(20-09-2018, 02:37 AM)RMT Sorry, I've done lot of mistake in that section.
I'm talking about of my previous PHILZ backup that I said here :
...
(20-09-2018, 02:41 PM)X3nonYes, actually, it is the only thing that works.(20-09-2018, 02:37 AM)RMT Sorry, I've done lot of mistake in that section.
I'm talking about of my previous PHILZ backup that I said here :
...
ok, thats all sorted out now. its definitely not emmc issue or flashing issue.
during the time you flashed TWRP into recovery partition, did the phone boot straight into TWRP when you tried booting it up or rebooting?
(20-09-2018, 03:51 PM)RMT Yes, actually, it is the only thing that works.
And yes, after I type fastboot reboot and without pressing any button, it boots straight to twrp. Even when I long press the power button to reboot.
Also, according to xda troubleshooting tips, I didn't try the flashing Magisk option, using Magisk manager, patch boot.img then flash through fastboot. Maybe that could resolve the issue ?
I'll try that.
fastboot -w
fastboot reboot
(20-09-2018, 09:00 PM)X3non(20-09-2018, 03:51 PM)RMT Yes, actually, it is the only thing that works.
And yes, after I type fastboot reboot and without pressing any button, it boots straight to twrp. Even when I long press the power button to reboot.
Also, according to xda troubleshooting tips, I didn't try the flashing Magisk option, using Magisk manager, patch boot.img then flash through fastboot. Maybe that could resolve the issue ?
I'll try that.
you can try that, while at it also check and ensure your vol up button isn't somehow stuck
Edit: also try this if you haven't
flash stock boot and system using fastboot
then wipe userdata and cache using the code
Code:fastboot -w
fastboot reboot
(24-09-2018, 09:30 AM)RMT Sorry if it's only now I answer. I wasn't at home during the weekend.
So, I have a problem with Magisk manager. When I launch it, it only show "Magisk is not installed". The install button doesn't show up. I think Magisk is doing that because it needs internet connection. And now either I have connection and any working phone or a working phone without connection.
Please, can you patch the boot.img for me ? And upload it after ?
And with the code, I'll do that after flashing the custom rom or after flashing the stock rom ?
(24-09-2018, 11:24 AM)X3non(24-09-2018, 09:30 AM)RMT Sorry if it's only now I answer. I wasn't at home during the weekend.
So, I have a problem with Magisk manager. When I launch it, it only show "Magisk is not installed". The install button doesn't show up. I think Magisk is doing that because it needs internet connection. And now either I have connection and any working phone or a working phone without connection.
Please, can you patch the boot.img for me ? And upload it after ?
And with the code, I'll do that after flashing the custom rom or after flashing the stock rom ?
you should do that after flashing stock boot and system - i'm suspecting philz badly formatted /userdata
btw here is patched_boot at http://www.datafilehost.com/d/1402b02a
(24-09-2018, 04:24 PM)RMT Ok,
...
The only thing that I think could be the issue is the system partition state that I said before. It might be in non-bootable state, this maybe explains why it always boots into Philz and why I never have bootloop. And using the command -a, --set-active[=<slot>] (that I don't know how to use) could solve it.
fastboot getvar current_slot
OR
fastboot getvar all
fastboot -a, --set-active=A
fastboot -a, --set-active=B
...
this depends on which slot you want to set active. it should also notify you if you device doesn't support slots
(26-09-2018, 12:15 AM)X3non(24-09-2018, 04:24 PM)RMT Ok,
...
The only thing that I think could be the issue is the system partition state that I said before. It might be in non-bootable state, this maybe explains why it always boots into Philz and why I never have bootloop. And using the command -a, --set-active[=<slot>] (that I don't know how to use) could solve it.
very much doubt your device support slots. you can try checking if your device even support different slots
Code:fastboot getvar current_slot
OR
fastboot getvar all
if there's a current slot you'll get output like this
<bootloader> current-slot: _a
Code:fastboot -a, --set-active=A
fastboot -a, --set-active=B
...
this depends on which slot you want to set active. it should also notify you if you device doesn't support slots
try this as well, boot philz > mounts and storage >
there should be three items here <cache, data and system>. lets know if all three are mountable