Question I broke my OnePlus Nord 2 while updating TWRP? Any help ? - OnePlus Nord 2 5G

Twrp updated from 3.5 to 3.6. I'm on A19. Rooted with Magisk 24.3. I flashed TWRP 3.6.img with Twrp 3.5. Flash OK, reboot in recovery mode OK. System reboot OK. Reboot in recovery mode to test Ok. Reboot system and there bootlooped with red point and white point turning.
I can reboot in TWRP. Il fastboot boo.img, vbmeta.img. Same pb Bootlooped.
I have a nandroid backup (data/boot/cache/DTBO/NVCFG/NVDATA/NVRAM/Persist/Persist Image/Protect F/protect S/Recovery/VBMeta).
I tried ti restore these partitions without erasing partitions. Restore OK but noway to boot. Bootlooped
I wipe all partitions. Restore without Data partition (with data, I have an error). Same bootlooped
I am trying to restore the data partition only. I have this error "Failed to mount '/data' (Invalid argument)
I have no more idea, I'm a little desperate. No solution ? Return the smartphone for repair?

1) flash stock recovery and stock boot via fastboot
2) flash patched vbmeta via fastboot with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2) format data via stock recovey
3) let it reboot to system
4) flash twrp via fastboot
5) restore only /data via twrp
6) reboot to system
7) UI will be broken, reboot again to fix it
8) remove any pin / password / pattern form the settings, and redo it.
9) Re flash twrp and magisk to root.

Thank you very much for this procedure Raygen. I was indeed able to recover my phone and restart it but it is very unstable. I had bootloopers again after reinstalling TWRP and Magisk. Now I have a problem with my security code or my fingerprints. Looks like they don't take them into account when I want to hand over a security code. Another problem is the camera no longer works. The app does not start. I tried to install the oneplus camera app loaded on Telegram v 3.422.2 but the installation failed.
A proposal to solve these problems ? Reinstall a partition other than Data that I backed up by Nandroid or is it back to OnePlus?

Try to restore the /persist partition from the twrp backup.
take a read here: https://forum.xda-developers.com/t/...rprint-to-become-completely-disabled.4363067/

Thanks very much. By restoring the "persist" partition, I recovered the camera and the fingerprints function. I hope the bootloops will stop there. Thank you very much, you are my saviour.

My OnePlus Nord 2 Indian version got hard bricked and I can't go in recovery or fastboot mode it is in a bootloop on OnePlus logo .
Any help???

Related

[Critical] Bootloader just boot into Recovery (TWRP) (more than one case and count.)

Hi everyone!
I'm facing a weird problem: I installed Resurrection Remix again (7.1.1) (it was my main rom) and TWRP started asking for the encryption key (although it was a pattern). I entered into recovery and did a wipe as the system requested.
Then, I realized that the encryption problem went further and I tried
Code:
fastboot format userdata
After that, the bootloader is able to boot just the TWRP recovery.
Then I tried from this link https://forums.oneplus.net/threads/beta-8-encryption-help.479290/page-2:
Code:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase recovery
fastboot erase boot
fastboot reboot
fastboot flash recovery <twrp28>
However, nothing changes.
I also tried to do all wipes, to format the data and system partition as EXT4, to reinstall RRemix 7.1.1 a lot of times, and, again, the system can just boot into recovery.
I saw a lot of user with the same problem, however, there is no solution for this problem yet.
OBS: the phone is booting successfully with the command:
Code:
fastboot boot boot.img
And then, after one manual reboot, the bootloader chooses the recovery again. The phone continues to boot into TWRP only.
The Encryption is gone, but I can only boot using this manual mode discovered by @Sompom
https://forum.xda-developers.com/oneplus-3/help/oneplus-3-bootloader-defaulting-to-t3529130
Could someone please help to fix this boot problem?
If there is any information than I can provide, please, let me know.
Thank you!!!
Please moderator, delete this post. Mine is Oneplus 3 (sorry).
Please moderator, delete this post. Mine is Oneplus 3 (sorry).

LG v30 10F firmware

Hey everyone.
All the links for downloading 10F appear to be broken. I need to downgrade from 10V to 10F so I can root, but can't file the firmware anywhere.
Anyone any ideas where I can find a working link?
Ta!
Sent from my LG-H930 using Tapatalk
Why would you need to downgrade to V10f for root ?
Im running V10v and have no problem at all.
flash TWRP in fastboot (fastboot flash recovery twrp.img), then boot that image (fastboot boot twrp.img)
Now youre in TWRP, enable modifications, reboot into recovery again (so you boot the one thats actually flashed)
then flash lg-rctd, no-verity-opt-encrypt-6.0, completly wipe data (factory reset, includes internal memory to get rid of encryption, optional) and flash Magisk
Now you have a rooted stock rom. Optionally with disabled encrpytion (only if you completly wiped /data ), so you can actually take a backup of that partition too and twrp is able to mount it
Some ppl had problems with V10v installing TWRP like me. Tried 1000 times to no avail, downgraded to V10f and TWRP worked the very first time w/o any problems on the lower FW vers.
SGCMarkus said:
Why would you need to downgrade to V10f for root ?
Im running V10v and have no problem at all.
flash TWRP in fastboot (fastboot flash recovery twrp.img), then boot that image (fastboot boot twrp.img)
Now youre in TWRP, enable modifications, reboot into recovery again (so you boot the one thats actually flashed)
then flash lg-rctd, no-verity-opt-encrypt-6.0, completly wipe data (factory reset, includes internal memory to get rid of encryption, optional) and flash Magisk
Now you have a rooted stock rom. Optionally with disabled encrpytion (only if you completly wiped /data ), so you can actually take a backup of that partition too and twrp is able to mount it
Click to expand...
Click to collapse
Hey, ta for the reply.
Like the guy said below, I've tried a few times and never been able to get TWRP to stick.
No harm me trying again though, I'll give it another spin just to make sure.
Sent from my LG-H930 using Tapatalk
Thats what the fastboot boot twrp.img and then reboot recovery (inside that twrp) commands are for
To actually make it stick and not get it overriden again.
Edit: had todo that twice actually, because i ****ed up the system one time, and went back to completly stock to find out what i did wrong (result, a magisk module was causing some error)
SGCMarkus said:
Thats what the fastboot boot twrp.img and then reboot recovery (inside that twrp) commands are for
To actually make it stick and not get it overriden again.
Edit: had todo that twice actually, because i ****ed up the system one time, and went back to completly stock to find out what i did wrong (result, a magisk module was causing some error)
Click to expand...
Click to collapse
Well fair play, followed your instructions and it worked first time! Not sure why it didn't before but I'm all rooted now.
Just need some custom ROMs to be developed now
Sent from my LG-H930 using Tapatalk
SGCMarkus said:
Why would you need to downgrade to V10f for root ?
Im running V10v and have no problem at all.
flash TWRP in fastboot (fastboot flash recovery twrp.img), then boot that image (fastboot boot twrp.img)
Now youre in TWRP, enable modifications, reboot into recovery again (so you boot the one thats actually flashed)
then flash lg-rctd, no-verity-opt-encrypt-6.0, completly wipe data (factory reset, includes internal memory to get rid of encryption, optional) and flash Magisk
Now you have a rooted stock rom. Optionally with disabled encrpytion (only if you completly wiped /data ), so you can actually take a backup of that partition too and twrp is able to mount it
Click to expand...
Click to collapse
it doesnt work on v11m tried 5 times every time when I try to boot twrp (fastboot boot twrp.img)
it starts
shows me the V30 logo
stays for 3-4 seconds
shuts down
restarts normally....
I think i will try it with v10v again tomorrow
Edit: also didnt work with v10v after i flash twrp and try to boot into twrp(fastboot boot twrp.img) the phone restarts normally

RMX1825 IMEI lost after enable OrangeFox recovery's DM- Verity Disable option

Here is the full description with recovery logs files that how my RMX1825 lost IMEI :-
1. I flashed TWRP recovery after unlock bootloader.
2. After that I am trying to get full backup through TWRP but the error was occurred every time, So I flashed OrangeFox Recovery and take the full backup through it, But it not include all partitions. So I backup only of these partitions:- System, Vendor, Vendor Image, Boot, Data(Excel. etc) and recovery.
3. After that I flashed "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" and also flashed magisk. And reboot my phone, But due to this DM- Verity zip file I am unable to access my any type of lock, like fingerprint lock, Password, pin or face lock. And also I am unable to access app drawer.
4. So I flashed stock rom of RMX1821 .ozip file through official recovery, and everything will be fine, Then I decided to enable DM-Verity disable option of Orangefox recovery and when I reboot my phone then IMEI goes to "Null" and also network goes.
5. Then I search the solution of this problem on XDA, And one Junior member said that to Run two commands through Fastboot mode, I execute these commands - "fastboot erase nvram" and "fastboot erase nvdata". But my problem is not solved.
After this process I tried lots of methods to recover nvram and nvdata partitions but all are failed.
6. I have .ofp file of RMX1825 but I need it to extract for flash this ROM through SP Flash tool.
Please help me to fix my phone.
Drive Link of Recovery Logs:-
https://drive.google.com/open?id=13RL4FreFQ7uye7Kcow_X78InPED6Q8Gi

How to go back to stock and install the latest update

Hi, I'm having some issues trying to install the newest update of A10.
I was on A9 with unlocked bootloader, root and twrp of recovery.
I first tried to install the .rar image via recovery but I couldn't find in the memory, but I already wiped system vendor and data.
So when I rebooted to try if the file was there or not, there was no recovery anymore.
Now I'm trying to flash the newest rom via fastboot but through the flash_all.bat it gives me fastboot tz_a error, so I'm trying to install a recovery through fastboot using this guide https://forum.xda-developers.com/mi-a3/how-to/basic-guide-to-flash-recovery-rom-via-t3989603 but of course it doesn't work and when I reboot it doesn't enter the recovery but always in fastboot (even tho I press the + button).
What should I do now? Is there anyway to erase everything and install a clean OS from 0 just from fastboot? (Without the flash_all or miflash because it doesn't work)
P.S. I don't care about the data, I've done a backup of all my important files before
Thanks for the help
Sapper Morton said:
First, you have to understand what you did. You wiped your system and vendor image, and didn't installed a newer one afterwards, you didn't wiped your recovery (it's inside boot partition).
Further, .rar files will not be flashed through TWRP, .zip must be used instead, with proper format, there must be a compatible flash script inside.
You can't access your recovery, just because you wiped system; inside your bootloader there's a component responsible to manage the slots, bootctl and by default if it detects a corrupted or invalid system partition, it will always boot onto bootloader mode.
As for the tz_a error, you must unlock critical partitions flashing, just because, tz is a critical partition, thus, run in Fastboot:
Code:
fastboot flashing unlock_critical
If you want to know your current state, use:
Code:
fastboot oem device-info
Your current slot is blocked by bootctl, but this doesn't mean your inactive is too, so, use:
Code:
fastboot set_active other
And reboot into TWRP again, that is, if you do have it installed in your inactive slot.
Fastboot/ADB and other tools, you will find it in here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
If you want to restore using recovery firmware, please do the favor, and read the post below:
https://forum.xda-developers.com/showpost.php?p=82595733&postcount=379
Click to expand...
Click to collapse
Thanks for the help but I managed to get into the recovery and install the rom via fastboot, the thing I was missing was a recovery working for Android10 (even though I remember recovery doesn't have nothing to do witg the installed OS), so I managed to install the recovery and root, and everything went fine after a few tries between various guides. Probably my partitions now are all messed up, but if I boot normally it goes into system (slot A), if I boot into recovery it goes into twrp and also works fastboot. Probably I also installed the OS on slot b, but I don't care as long the first partition works well

Asus Zenfone Max M2 [X01AD] not booting into system after flashing cutsom ROM(s)

I have unlocked my bootloader using official Asus tool, I then went on to flash TWRP 5.3.x.x. using fastboot and also formatted userdata and cache from fastboot itself to remove encryption. Recovery works fine.
I have tried flashing both these ROMs. [links below]
[ROM][OFFICIAL][11.0][X01AD] Arrow OS
[ROM][11][5.R] Project Sakura [2021/03/19][UNOFFICIAL]
I followed the instructions, formatted data using TWRP, wiped system, vendor, cache, data, dalvik.
I then flashed the ROM from TWRP itself, and I have also tried to install it through ADB sideloading. Then I wipe dalvik/cache.
Both instances, the installation happens fine but when I reboot phone gets stuck in fastboot mode. I resolve that by flashing 'vbmeta.img'.
Then phone starts booting but gets stuck in a loop bootloader-->ASUS logo-->"Powered by Android"-->bootloader
So basically, it does not boot into system.
I have even flashed stock A10 firmware from here Stock Vendor and Firmware images for Asus Max M2 but still no resolution.
I have also tried manually mounting system partition from TWRP, doesn't work.
Any help would be much appreciated.
Connect phone and PC via USB-cable and in Windows command prompt run this command sequence
Code:
fastboot devices
fastboot reboot
to take back phone to it's normal ANDROID mode.
arko2000 said:
I have unlocked my bootloader using official Asus tool, I then went on to flash TWRP 5.3.x.x. using fastboot and also formatted userdata and cache from fastboot itself to remove encryption. Recovery works fine.
I have tried flashing both these ROMs. [links below]
[ROM][OFFICIAL][11.0][X01AD] Arrow OS
[ROM][11][5.R] Project Sakura [2021/03/19][UNOFFICIAL]
I followed the instructions, formatted data using TWRP, wiped system, vendor, cache, data, dalvik.
I then flashed the ROM from TWRP itself, and I have also tried to install it through ADB sideloading. Then I wipe dalvik/cache.
Both instances, the installation happens fine but when I reboot phone gets stuck in fastboot mode. I resolve that by flashing 'vbmeta.img'.
Then phone starts booting but gets stuck in a loop bootloader-->ASUS logo-->"Powered by Android"-->bootloader
So basically, it does not boot into system.
I have even flashed stock A10 firmware from here Stock Vendor and Firmware images for Asus Max M2 but still no resolution.
I have also tried manually mounting system partition from TWRP, doesn't work.
Any help would be much appreciated.
Click to expand...
Click to collapse
hello did you finally find the solution? I also can't move on any custom rom starts in fastboot mode
Is it possible that no one has a solution to this problem? I've been getting annoyed for three days and trying...
Is there any resolution anyone found out? I am stuck at the same problem for days. @N3I3 @arko2000
@Drigio @N3l3 @arko2000
FIX "BOOTLOOP ISSUE" AFTER FLASHING CUSTOM FIRMWARE IN ANDROID 10
Click to expand...
Click to collapse
Requirements:
vbmeta.img (For A10)
ADB & Fastboot (In case you don't have one)
Instructions:
Install ADB-and-Fastboot++_v1.0.6.exe and run.
Copy the commands below.
Commands:
Code:
fastboot erase vbmeta
- OPTIONAL
Code:
fastboot flash --disable-verity vbmeta 'location of vbmeta'
- OR DRAG THE A10 vbmeta
Code:
fastboot reboot
Hope this helps!
I HAVING ALSO SAME PROBLEM CAN ANY ONE FIX IT..

Categories

Resources