Hello,
I'm trying to unbrick my lg p760 with the fastboot flashing. I've already installed all the drivers with no problems, but when I input the fastboot flash u-boot command it says that the partition does not exist.
I tried flashing the x-loader, but it gives me the same problem, partition does not exist. Is it possible to unbrick the phone? Thanks in advance.
Download Mode is a more primitive and thus reliable way to flash a complete KDZ file, online or offline.
I have never been able to use Fastboot at all with this phone since Windows 8.1.
Not with stock rom and not with various custom roms. Other devices work fine. ADB should work, tho this won't help much now.
I have OpenQ820 dev board which has Qualcomm Snapdragon820(APQ8096). which is hard bricked as I flashed custom emmc_appsboot.mbn. (curretly there is - No Fastboot, No recovery or adb, Only EDL mode is up)
As per my knowledge , there is aboot backup partition called as abootbak. Wondering how to make use of it to recover the board.?
or is there any other way to recover it.
Can anyone please help me with this.
Hi im have a redmi note 4x and i cant flash anything and my phone are unusable (boot stuck).
I try whatever you can imagine, so i want remove all (and when i say all, say ALL) files in the devices with TWRP File manager and then try to flash intro EDL or something like that.
What can happend if i do that?
Have you triend the unbricked method that was already posted?
I have flash many device of Nikel including Unlocked bootloader. I didn't have a problem on that.
If your bootloader is unlock, try flashing all the partitione image from CMD
I solved the problem, just remove all partitions from /Dev/block/mmcblk0 (couse was corrupted)(with adb Shell) and flash a old miui version in EDL Mode
I have extensively searched this forum and couldn't find to answers to the following!
Looking for experts to guide..
Query #1: TWRP Backup of Stock ROM causes bootloop!
I had unlocked Bootloader of Redmi Note 4 and used temporary TWRP (fastboot boot twrp.img) to take a backup of stock ROM and found that the device cannot boot back into Stock ROM.
I had tried to restore 'boot.img' using the TWRP stock ROM backup (and also from downloaded stock ROM) but that didnt help.
Same problem seen in Redmi 4 as well.
When booted to TWRP using fastboot boot (without flashing), in which partition TWRP is stored (boot or cache)?
After I had booted into TWRP (without flashing), is the backup of boot partition that I took still a stock version one?
Query #2: Relocking and unlocking Bootloader
I had unlocked bootloader using the MiFlash unlock tool (miflash_unlock-en-3.5.1108.44).
If I relock the bootloader using the MiFlash tool, would I need MiFlash unlock tool again to unlock or would 'fastboot flashing unlock' work?
Thank you!
n.dnivra said:
I have extensively searched this forum and couldn't find to answers to the following!
Looking for experts to guide..
Query #1: TWRP Backup of Stock ROM causes bootloop!
I had unlocked Bootloader of Redmi Note 4 and used temporary TWRP (fastboot boot twrp.img) to take a backup of stock ROM and found that the device cannot boot back into Stock ROM.
I had tried to restore 'boot.img' using the TWRP stock ROM backup (and also from downloaded stock ROM) but that didnt help.
Same problem seen in Redmi 4 as well.
When booted to TWRP using fastboot boot (without flashing), in which partition TWRP is stored (boot or cache)?
After I had booted into TWRP (without flashing), is the backup of boot partition that I took still a stock version one?
Query #2: Relocking and unlocking Bootloader
I had unlocked bootloader using the MiFlash unlock tool (miflash_unlock-en-3.5.1108.44).
If I relock the bootloader using the MiFlash tool, would I need MiFlash unlock tool again to unlock or would 'fastboot flashing unlock' work?
Thank you!
Click to expand...
Click to collapse
1. That bootloop *probably* happened because you swiped the "allow modification option" in twrp.
(One more advice : in twrp backup you should backup the "system image" and "vendor image" not the "system" and "vendor", If you don't want bootloop after restoring. (Or If you got a bootloop already flash that verity removal zip)
2. You will need mi unlock again.
I have a Realme U1 that I am trying to root. I already have the patched boot image. When I try to go to fastboot mode, it goes into ColorOS recovery mode. There is no option for fastboot in ColorOS recovery mode. Tutorials say that to go in fastboot mode in Realme, I have to do Power + Volume Up instead of Power + Volume Down. Tried that. Didn't work. Just booted normally. Adb is working as usual. BUT when I tried 'adb reboot bootloader', it doesn't work. But when I try 'adb reboot recovery' IT works. At this point, I don't even know what to do. Please help.
SamanwayK2077 said:
I have a Realme U1 that I am trying to root. I already have the patched boot image. When I try to go to fastboot mode, it goes into ColorOS recovery mode. There is no option for fastboot in ColorOS recovery mode. Tutorials say that to go in fastboot mode in Realme, I have to do Power + Volume Up instead of Power + Volume Down. Tried that. Didn't work. Just booted normally. Adb is working as usual. BUT when I tried 'adb reboot bootloader', it doesn't work. But when I try 'adb reboot bootloader' IT works. At this point, I don't even know what to do. Please help.
Click to expand...
Click to collapse
Hello and good afternoon, @SamanwayK2077
Welcome to XDA! I hope you'll alawys get the support your require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
SamanwayK2077 said:
BUT when I tried 'adb reboot bootloader', it doesn't work. But when I try 'adb reboot bootloader' IT works.
Click to expand...
Click to collapse
it works? so what's the problem here then?
Lol
aIecxs said:
it works? so what's the problem here then?
Click to expand...
Click to collapse
I made the question wrong. It is supposed to be:
When I try 'abd reboot bootloader', it does not work. But when I try 'abd reboot recovery', IT works to get me into RECOVERY mode (which I mention because this is proof adb works).
right, seems fastboot mode is disabled forcefully then.
you can unlock bootloader with mtkclient
Code:
python3 mtk da seccfg unlock
you can dump partitions and flash TWRP + vbmeta_disabled.img
Code:
python3 mtk rl out
python3 mtk w recovery twrp.img
python3 mtk w vbmeta vbmeta_disabled.img
vbmeta_disabled.img can generated from avbtool.py or you use copy of out/vbmeta.bin from phone dump and change a single byte with HxD editor
What is 02 in the magisk patched vbmeta.img?
According to the Additional Info given for rooting the Android device that doesn't have ramdisk but can be rooted via recovery: we need an empty vbmeta.img and I am trying to check what it actually
android.stackexchange.com
aIecxs said:
right, seems fastboot mode is disabled forcefully then.
you can unlock bootloader with mtkclient
Code:
python3 mtk da seccfg unlock
you can dump partitions and flash TWRP + vbmeta_disabled.img
Code:
python3 mtk rl out
python3 mtk w recovery twrp.img
python3 mtk w vbmeta vbmeta_disabled.img
vbmeta_disabled.img can generated from avbtool.py or you use copy of out/vbmeta.bin from phone dump and change a single byte with HxD editor
What is 02 in the magisk patched vbmeta.img?
According to the Additional Info given for rooting the Android device that doesn't have ramdisk but can be rooted via recovery: we need an empty vbmeta.img and I am trying to check what it actually
android.stackexchange.com
Click to expand...
Click to collapse
Gonna try this. I hope this will not wipe my data. Will it?
Edit: I dont wanna do any of the aforementioned things. I want to just root and/or enable fastboot mode. How do I do that?
I don't know how to enable fastboot, but for rooting the aforementioned things are recommended.
factory reset is mandatory for rooting. except you use vulnerabilities that allows rooting on locked bootloader.
on old devices like this it might possible to flash magisk patched boot.img on locked bootloader, as avb/dm-verity implementation was weak on mediatek devices up to Android 7. to try this, you need a flash tool like mtkclient or SP Flash tool.
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
aIecxs said:
I don't know how to enable fastboot, but for rooting the aforementioned things are recommended.
factory reset is mandatory for rooting. except you use vulnerabilities that allows rooting on locked bootloader.
on old devices like this it might possible to flash magisk patched boot.img on locked bootloader, as avb/dm-verity implementation was weak on mediatek devices up to Android 7. to try this, you need a flash tool like mtkclient or SP Flash tool.
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
Click to expand...
Click to collapse
not rlly sure, but i think that after i unlock the bootloader i can enable fastboot mode. ill post an update after i have backuped the phone
[DISCUSSION] A thread to collate and share what is known about unlocking fastboot on Oppo devices
Admin: Please move/delete this thread if it is in the wrong place or against the rules. I wanted to create a thread to discuss unlocking fastboot mode on Oppo devices in general, rather than discussing it in terms of any one device in...
forum.xda-developers.com
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016 I was surprised to not find this information in any of the forums. This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone...
forum.xda-developers.com