i was trying to find a custom recovery for my nokia 3.2 and accidentally mistaken a nokia 3 unofficial twrp as a nokia 3.2 one so i flashed the wrong one (not knowing so at the time) and then it just wouldnt boot into os anymore. When i did try and flash the recovery i flashed it into the boot_a and boot_b partitions because there were some forums that said "fastboot boot twrp.img" but i thought they said "fastboot flash boot twrp.img". I tried to flash boot and system and all other files in the stock rom to no avail. I found a nokia 3.2 unofficial twrp here: https://forum.xda-developers.com/nokia-3-2/development/twrp-nokia-3-2-ported-thinhx2-t4055023 and there is 2 different versions. I tried flashing that in boot_a and boot_b and still nothing. Also note that there was a text file with the wrong twrp (nokia 3) that said to flash no verity or ssomething like that or the phone wont boot to os so maybe it has to do with that?
Related
Hi all!
Occasionaly flashed blue spark twrp v41 (for OOS 3.x) while on Sultans ROM with locked bootloader.
No root access, didn't flash supersu. Kingroot and other 'on one click' methods somehow don't work.
Now, when I try to use fastboot to flash recovery it denies as bootloader is locked. When I try to unlock bootloader using 'oem unlock' it tries to boot recovery which doesn't boot (stucks on logo).
Any chance to solve without hardbricked solution?
I'm on OOS 2.2.2 and have done the same thing (flashed blu spark v41)... same result as you though, a phone I can only boot into fastboot mode
This was the advice I was given (from OnePlus forums)...
https://forums.oneplus.net/threads/...lus-logo-help-me-please.462406/#post-15248530
Here are the steps to get TWRP without messing up your recovery partition
>> Grab Bootloader file (emmc_appsboot.mbn) from OxygenOS Lollypop stock rom
>> Place it in Adb& fastboot folder and flash it via fastboot
fastboot flash aboot emmc_appsboot.mbn
>> Now Type
fastboot reboot-bootloader
>> Now temporarily boot TWRP official recovery for OPX with fastboot
fastboot boot "yourTWRPfileNAME.img"
You should be able to boot to TWRP recovery now
After Flashing and stuff reboot to fastboot and
>> Grab Bootloader file (emmc_appsboot.mbn) from Oxygen OS Marshmallow stock rom
>> Place it in Adb& fastboot folder and flash it via fastboot
fastboot flash aboot emmc_appsboot.mbn
Reboot and enjoy
Click to expand...
Click to collapse
Edit: Maybe you'll need to flash the emmc_appsboot.mbn file from the Sultans ROM though???
The above didn't work for me. I had to UnBrick
You cannot install a recovery on locked bootloader,your phone is not going into stock recovery because of some boot failure, just turn off your phone remove battery if its removable then try again to go into recovery
Sent from my HUAWEI TIT-AL00 using XDA Forums
I installed the 135 update for my BLA-L29 (C605) Mate 10 Pro and noticed the face lock got really slow after I flashed HyperX Kernel. I then thought I found a stock kernel for the Mate 10 Pro and flashed it. Now I cannot get past the boot screen, I cannot get into TWRP, eREcovery isn't able to wipe my phone, error trying to update, all the fun! I can get to fastboot no problem and my phone shows "Phone Unlocked," and "FRP Unlock." Bootloader is unlocked and I'm pulling my hair on trying to figure out how to get it back to the 135 update which was running just fine until I decided to get cute with Hyper X. I'm at the brink of buying credits through Funky but I don't want to do that. Can someone please walk me through how to unbrick using DC Phoenix. I've got the 135 update file downloaded but could use some more help. Thank you!
can you descripe the step, how you flashed the kernel? Over fastboot in this form: fastboot flash kernel filename.img? or fastboot flash boot filename.img? fastboot flash kernel filename.img is the correct one. But if you have flashed it to the boot partition (fastboot flash boot filename.img) then you need to find the stock boot partition. Follow this thread and unpack kernel.img and boot.img. Then flash kernel.img in this form: fastboot flash kernel kernel.img and boot img in this form fastboot flash boot boot.img
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/
Hello!
Now I have a trouble with my Nokia 7.1.
When I try to boot twrp or another kernel (boot.img) it stuck. I do '"fastboot boot twrp.img" or "fastboot boot boot.img" and my phone frozes on Android One logo.
And if problem with twrp can be solved (first enter "fastboot flash recovery twrp.img" and only than "fastboot boot twrp.img"), problem with boot.img is still relevant.
I noticed, that after "fastboot boot ..." phone restarts into download mode.
My phone is unlocked.
Thank
Hi, before any boot command, you'll need to do that flash recovery counterpart. You can do it on a standard boot image as well, not just TWRP. There's no recovery partition, so, nothing gets flashed. But it somehow allows us to boot our bootable img files.
So,
Code:
fastboot flash recovery boot.img
fastboot boot boot.img
singhnsk said:
Hi, before any boot command, you'll need to do that flash recovery counterpart. You can do it on a standard boot image as well, not just TWRP. There's no recovery partition, so, nothing gets flashed. But it somehow allows us to boot our bootable img files.
So,
Code:
fastboot flash recovery boot.img
fastboot boot boot.img
Click to expand...
Click to collapse
Yes! Thank you.
I recently came to this conclusion, but what is it?
Does it bootloader bug or anything else?
i have similar problems and just started a new request
Tried to install TWRP for REDMI NOTE 11S, but just after a few seconds into the recovery, the phone shuts down and keeps on a loop.
Is there any recommendable MIUI version i shall use to avoid this? Or any extra step im missing?
here are the command im using:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot recovery.img
fastboot reboot recovery
I don't think there is any reliable and stable versions of custom recovery for this phone yet.
Even I tried installing orange fox and it kept bootlooping.
You can try flashing the twrp install zip file after booting to twrp and see if the problem still exists. But I have a feeling it won't.
The best you can do to stop bootlooping is to not have a custom recovery at all.