i have the same error
I got the same problem noone here explaind it very well!Okay so it managed to startup finally back here:
![]()
Before I make any more mistakes. What is the clear avenue from here
Edit-----
Alright I've managed to get back to fastboot and have PartitionBackup working. But I'm back to square one. I'm experiencing an issue after flashing Super, where it reboots to stock fastboot (not sure what it's called, says Fastbootd), and it hangs there. If I reboot back to the small text fastboot, it continues, but with serious sounding errors citing not available in locked state, but I'm pretty sure the bootloader is unlocked. Until it finishes and gets stuck on a boot loop.
I attached the PBlog.txt
I'll deal with it in the morning. If someone could help here I'd be eternally greatful, seriously.![]()
I got the same problem noone here explaind it very well!
The thing is this phone got 2 fastboot-modes:
1 fastboot reboot bootlaoder - "bootloader fastboot"
2 fastboot reboot fastboot - "userspace fastboot"
the partitions you can't flash is because you cant boot into the "userspace fastboot" after messing with the phone!
but don't worry you can easy fix it!
my recommend way is to go boot into bootloader fastboot (with key combo) and flash twrp + vbmeta from the twrp threat!
in twrp go into -> reboot -> reboot fastboot
then go and restore everything with partionsbackupper!
after 1 frist boot go into bootloader again and flash vbmeta (maybe not neccesery)
your phone should now boot again!
Are you using windows ? check it in device-manager when you are in "userspace-fastboot" it should report as adb-bootlaoder-interface. If not click on use driver - > adb bootlaoder interfaceHey,
So I've managed to flash twrp again, however when entering the twrp fastboot mode, the device is still undiscoverable.
Others in this thread said the stock "userspace fastboot" should have worked as well, but for some reason the device isn't being recognized in either of these methods. Only the small text "bootloader fastboot" shows the device, but I get errors there.
I've also tried flashing the provided preloader_ul1.bin in the OP, but that's made no difference in detecting the device in these modes.
I'm also pretty sure the persist is gone, as the partition shows 0mb. And the backup of these partitions failed in TWRP. So it looks like an RMA. I mean people give warnings about bricking your phone in rooting, but hell I didn't expect the guides to be this bad. I won't be rooting my replacement that's for sure.
Are you using windows ? check it in device-manager when you are in "userspace-fastboot" it should report as adb-bootlaoder-interface. If not click on use driver - > adb bootlaoder interface
No problem brotherThank you! You beautiful person Kingslayer! It's unbricked!
Sometimes you overlook the obvious when you're dealing with issues, and for me it was as you said - not installing the device as 'adb bootloader interface' from device manager while in the userspace fastboot. I also started PartitionBakckupper from TWRP as you said so that may have helped as well. But also, as a note for anyone who may face this issue - after it all completed, I received the same red boot error message as earlier, but by booting into fastboot from that screen and reflashing the vbmeta.img from the latest a.16 stock in the OP, it allowed it to boot fine. Is that what you meant at the end there?
Fingerprint scanner and camera are working fine as well, so the persist is actually still intact too.
Bloody hell, what a relief. Thank you again man, you saved me the stress of an RMA request I was prepared to make in the morning. And thanks as well Raygen for the tool, once you understand how to actually work it, it does the trick.
Persist partation is Device specific so author removed that from partation backup folder similarly he also removed nvdata(responsible for imei etc) and userdata.hey,
the rom is not 100% complete, there is no rewriting of the persist partition. Anyone know how to solve this problem?
python mtk wl img
python mtk w lk,lk2,boot,recovery,vbmeta lk.img,lk2.img,boot.img,recovery.img,vbmeta.img
python mtk w name_1,name_2 name_1.img,name_2.img
I've encountered the same issue a couple of times. Bootlooped out of the blue, without doing anything to the phone.I still have no idea what triggers it, also because I cannot find a way to replicate the issue, it just happens randomly afaik.Hello everyone ... a post about the sadness of rutting, unfortunately 3 times this is not an accident .. after 3 times recovery from the bootlap, the device lives with the root for literally a month and a half. then miracles happen... bootlap out of the blue, NOT installing anything new before (updating magisk modules, etc.)... those kernel seems to be counting the lifetime with root.. figuratively, fun! I didn’t find how to overcome the problem anywhere, rather it’s because of the core of the firmware under the media library and the locked seLinux .... can anyone know how to overcome this problem?
The persist partition is unique to your phone only, you cannot flash one from another phone.Thanks for all the help, I followed all the instructions here and now I got back my phone with stock firm and flashing locked but now I cant set a lock screen password it just doesnt work. In some desesperate tries to recover the phone I've deleted locksettings.db I dont know if this can be the prob. Can anybody could share persist.img to reflash that partition on my phone? thanks
For locking the bootloader you need to have everything stock, vbmeta included, or it will not boot telling you the boot partition is corrupted.I have a problem, I have returned to the EU rom and perfect, when doing the flash lock, now it tells me that it can not boot.
The problem I have is that to enter fastboot I can only do it from adb (with the phone booted) with the buttons I am not able to enter fastboot (I can only go to recovery).
What can I do?
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research yourself before asking or use anything on this thread.
* I do not offer private assistance via Telegram or any other social outside XDA.
*/
pip3 install -r requirements.txt
python mtk_gui
to start Mtkclient GUI.python mtk r partition_name_1,partition_name_2,partition_name_3,... img_bak/partition_name_1.img,img_bak/partition_name_2.img,img_bak/partition_name_3.img,...
. Example: python mtk r boot,vbmeta,super img_bak/boot.img,img_bak/vbmeta.img,img_bak/super.img
. You'll find all your backups inside the /opt/mtkclient/img_bak folder (copy them back to your pendrive to not loose them).python mtk wl img
. Be sure that the file names have the same name of the partition they're meant to write! Example: The file named "boot.img" <---> Will write the "boot" partition.
python mtk r preloader img_bak/preloaderdump_backup.bin --parttype=lu1
to backup your preloader partition. You'll find your backup inside the /opt/mtkclient/img_bak folder (copy it back to your pendrive to not loose it).python mtk w preloader img/preloaderdump_stock.bin --parttype=lu1
to flash the preloader partition.fastboot flashing unlock
does not work.Are you using windows ? check it in device-manager when you are in "userspace-fastboot" it should report as adb-bootlaoder-interface. If not click on use driver - > adb bootlaoder interface
python mtk wl img
python mtk w lk,lk2,boot,recovery,vbmeta lk.img,lk2.img,boot.img,recovery.img,vbmeta.img
python mtk w name_1,name_2 name_1.img,name_2.img