Related
Okay, I'm not sure exactly what you'll need to know to help, so I'll just tell you what I think is important....
Current situation:
- If I boot the phone normally it freezes at the SONY screen and goes no further.
- If I attempt to boot into recovery mode, it loads the CWM screen (logo in the middle with instructions at bottom), but no actual menu or options. After about 5 seconds, this screen disappears, the phone reboots and then gets stuck on the SONY screen.
- If I connect the phone to the computer in Flashmode Flashtool recognizes it as being connected, but regardless of what I do, after about 2mins the phone reboots, loses connection with the computer, and freezes on the SONY screen as before mentioned.
- If I connect the phone to the computer normally while stuck on the SONY screen, the PC recognizes it though doesn't allow me to do anything to it, and Flashtool says I need to install drivers (I have installed every driver that comes with Flashtool).
How I got here:
- I've rooted the phone
- I've flashed Z2_DooMLoRD_AdvStkKernel_FW-438-v05
- I've unlocked the bootloader (via Flashtool)
- I've installed [Rom][Unofficial]Slim Rom 4.4.4 based on CM11.0, ROM for the Sony Xperia Z2
The phone was okay up until this point, however I wasn't happy with the ROM so I tried to reboot into recovery mode to wipe and install Carbon. This is when the trouble began.
Now it seems I can't do anything :/
Please help. This phone is literally 3 days and it looks like I've completely screwed it >.<
Thanks!
How to recover your device from almost any kind of brick
Requirements
Check the pinned sites
Flashtool
FTF of choice for your device
2 Rubber bands (I am serious but only if your device has no response)
Step1
unplug your device from anything
open flashtool on your pc
plug your cable into your PC
do not plug the cable into your device
Step2
Hold your power button and your volume up button at the same time
your device should buzz 3 times
(this should take a few secconds)
if it does not take a few seconds then you need to put a rubber band around your device holding your power button and your volume up button, DO NOT LEAVE MORE THAN IT NEEDS TO BE LEFT, wait patiently for your device to buzz 3 times
Step 3
once your device has buzzed 3 times you are free to flash a FTF as your device is powered off
step4
if you dont know how to flash a FTF but have gotten as far as installing flashtool,Z2 drivers and downloading a FTF FOR YOUR DEVICE... then folow this step
within your flashtool window click on the lightning icon at the top left
select flashmode
navigate to where you downloaded your FTF (OR put your FTF in your /flashtool/firmwares folder)
select your FTF
Flashtool should give you a prompt to plug in your device
hold volume down and plug in your device
step5
wait for it to finish flashing
step6
your device is now recovered, enjoy...
Sent from my D6503 using XDA Premium 4 mobile app
I bricked my phone doing this:
- root with eazyroot
- installed dual recovery
- full wipe
- install carbon + gapps
bum... bricked
i cant even see the Sony logo
Then i use the method mentioned by Envious_Data and my phone returned from hell
Good luck dude... hope u can fix that
carloscarvalho said:
I bricked my phone doing this:
- root with eazyroot
- installed dual recovery
- full wipe
- install carbon + gapps
bum... bricked
i cant even see the Sony logo
Then i use the method mentioned by Envious_Data and my phone returned from hell
Good luck dude... hope u can fix that
Click to expand...
Click to collapse
You didn't unlock your bootloader?
Isn't Carbon ROM AOSP?
If it is, it needs an unlocked bootloader or it will get bricked
Unbalanced said:
Okay, I'm not sure exactly what you'll need to know to help, so I'll just tell you what I think is important....
Current situation:
- If I boot the phone normally it freezes at the SONY screen and goes no further.
- If I attempt to boot into recovery mode, it loads the CWM screen (logo in the middle with instructions at bottom), but no actual menu or options. After about 5 seconds, this screen disappears, the phone reboots and then gets stuck on the SONY screen.
- If I connect the phone to the computer in Flashmode Flashtool recognizes it as being connected, but regardless of what I do, after about 2mins the phone reboots, loses connection with the computer, and freezes on the SONY screen as before mentioned.
- If I connect the phone to the computer normally while stuck on the SONY screen, the PC recognizes it though doesn't allow me to do anything to it, and Flashtool says I need to install drivers (I have installed every driver that comes with Flashtool).
How I got here:
- I've rooted the phone
- I've flashed Z2_DooMLoRD_AdvStkKernel_FW-438-v05
- I've unlocked the bootloader (via Flashtool)
- I've installed [Rom][Unofficial]Slim Rom 4.4.4 based on CM11.0, ROM for the Sony Xperia Z2
The phone was okay up until this point, however I wasn't happy with the ROM so I tried to reboot into recovery mode to wipe and install Carbon. This is when the trouble began.
Now it seems I can't do anything :/
Please help. This phone is literally 3 days and it looks like I've completely screwed it >.<
Thanks!
Click to expand...
Click to collapse
Okay I used to get into this kind of situation when I used HTC One, and what I did is try to flash recovery and unlocked bootloader again "using command".
And problem has solved. I think it is pretty much same for Xperia Z2, (ftf flashing method is not useful in this situation.)
I hope you know how to flash custom recovery using command. If not I think there is some thread that explains how to flash recovery and unlock the bootloader using command, if you can't find it plz let me know. Hope you have recovered phone next time I check this thread. Good luck mate :good:
HussainQ said:
You didn't unlock your bootloader?
Isn't Carbon ROM AOSP?
If it is, it needs an unlocked bootloader or it will get bricked
Click to expand...
Click to collapse
Yeah... I know... A newbie mistake...
I Just follow the instruction available in the site. And there is just "root and recovery"
No bootloader mentioned
But u r right... Thats the reason
Sent from my awesome Xperia Z2 using XDA Premium
@Envious_Data: Bro, thank you so much for that. I my z2 have only 1 day, and i god damn it bricket, that even screen wasn't working. So for other people who had bad luck: first I rooted using Community Rootkit, then unlocked bootloader, and at the end I flashed via fastboot boot.img which one i extracted from zip file from this thread - http://forum.xda-developers.com/showthread.php?t=2702001. Command prompt showed that it works. I rebooted phone sony logo showed up, but then disappeared, and then was crying and sorrow. Three years of rooting,flashing without any problem, and now that. Thank you one more time, that's a great lesson
I do have some advice for people
1. Try to find help threads for your device, i have one for Z2 that gives some useful info, ill be adding more soon
2. Once you have got the jist of flashing then try to expand on that, i do recomend roms first because its harder to brick from a rom than a kernel or a non stock based rom such as CM11 or AOSP
3. Always keep a stock flashable rom (kernel too if you have a unlocked bootloader) on your device
Sent from my D6503 using XDA Premium 4 mobile app
I too hard brick my Z2, only solution is the same as for Z1 http://forum.xda-developers.com/showthread.php?t=2646405
Sorry friend :`
discipuloosho said:
I too hard brick my Z2, only solution is the same as for Z1 http://forum.xda-developers.com/showthread.php?t=2646405
Sorry friend :`
Click to expand...
Click to collapse
A hard brick is by definition not recoverable by the user, requiring either special equipment ie jtag or RMA to fix.
I am quite surprised, and intrigued, at people flashing cm or AOSP on a two day old phone, was Sony experience that awful? You'd maybe be better served with a nexus device.
ghostofcain said:
A hard brick is by definition not recoverable by the user, requiring either special equipment ie jtag or RMA to fix.
I am quite surprised, and intrigued, at people flashing cm or AOSP on a two day old phone, was Sony experience that awful? You'd maybe be better served with a nexus device.
Click to expand...
Click to collapse
True friend, but I had an Xperia MT11i (Neo V) and all (fastboot, flashtool, CM, etc) was always no problem.
I've taken today for service (with CM11 (and cm kernel)) and see what happens ...
@Unbalanced I don't think your Z2 Hardbricked, if it were not ignite. Luck
Hi all, if it helps I did the same thing last night. Flashed CM11 without a recovery and wanted to revert back to my nandroid backup. I flashed doomloards kernal via fastboot. CWM started with no menu and just bootlooped. I then thought it may be a CWM issue, maybe no file structure or something. I flashed XZDuelKernal via fastboot and booted into CWM again and experienced the same issue. As this is a duel recovery, I then booted into TWRP. Recovery started and I was able to flash another zip then recover my nandroid backup. If you get this menu issue with CWM,try and flash a TWRP recovery and boot into that.
Also, as mentioned before, this is not a hard brick. It's just incompatible software and is easily fixed if you know what you are doing and prepared (nandroid backup, knowledge about fastboot and flashmode, ftf, recovery, unlocked bootloader).
Sent from my D6503 using Tapatalk
Stuck
Hi.
I believe (although I'm not sure) that I have bricked my Xperia Z2 in some way. When I press the 'power' button, the phone vibrates once and does nothing. I have tried to hold the 'power on' and 'volume up' buttons for a long time (half an hour with rubber bands), and nothing happens (as explained earlier in the thread).
I believe I am able to access the fastboot though, through 'Terminal' app on OSX. From there I can " ./fastboot devices " and get confirmation that they have loaded. I am also able to perform other tasks from here, such as flashing a recovery and " fastboot erase system -w " (which I believe may have got me to where I am now). I've been following things on this thread: http://forum.xda-developers.com/showthread.php?t=2277112
I have no experience in rooting or flashing, but attempted to flash a custom ROM because there were step by step instructions.
Anyway, I firstly used Sony's rooting procedure whereby an unlock code is generated etc. Eventually I gained access to the Recovery mode (via clockwork), and wiped the phone, installed the ROMAur zip and GApps zip. However, when I booted, it kept giving me warnings saying the apps were crashing. I've since gotten lost completely and need someone to help bail me out.
I'm hoping I can sort things out via the fastboot.
Thanks in advance for your help.
scoobard said:
Hi.
I believe (although I'm not sure) that I have bricked my Xperia Z2 in some way. When I press the 'power' button, the phone vibrates once and does nothing. I have tried to hold the 'power on' and 'volume up' buttons for a long time (half an hour with rubber bands), and nothing happens (as explained earlier in the thread).
I believe I am able to access the fastboot though, through 'Terminal' app on OSX. From there I can " ./fastboot devices " and get confirmation that they have loaded. I am also able to perform other tasks from here, such as flashing a recovery and " fastboot erase system -w " (which I believe may have got me to where I am now). I've been following things on this thread: http://forum.xda-developers.com/showthread.php?t=2277112
I have no experience in rooting or flashing, but attempted to flash a custom ROM because there were step by step instructions.
Anyway, I firstly used Sony's rooting procedure whereby an unlock code is generated etc. Eventually I gained access to the Recovery mode (via clockwork), and wiped the phone, installed the ROMAur zip and GApps zip. However, when I booted, it kept giving me warnings saying the apps were crashing. I've since gotten lost completely and need someone to help bail me out.
I'm hoping I can sort things out via the fastboot.
Thanks in advance for your help.
Click to expand...
Click to collapse
Download ftf file for your device and flash via flashtool.
mariosraptor said:
Download ftf file for your device and flash via flashtool.
Click to expand...
Click to collapse
Thanks for the quick reply Mario. I did just that (using Kuwait FFT for the D6503), and everything appears to be back to normal. Unfortunately I still have not got root access and can't remove the bloatware. As for the bricking issue however, it's solved. Thanks.
R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.
Hi everybody,
I tried to install Magisk 21.2 on my stock Oreo rom with Magisk 20.4 already installed. I've used the recommended method for installation in Magisk Manager, and I left the AVB/dm-verity option unchecked. It resulted in a bootloop.
Before updating I did a backup of the boot partition, so I could restore the previously working Magisk 20.4. Now I have two questions:
1) Is there something else I should do other than restoring the boot partition after a bootloop?
2) Is there a way to install the new Magisk or should I just dismiss the update notification?
Happened to me As well on my G6.
I had to reinstall the rom. good thing i had backup.
I've downloaded the zip file of Magisk 21.2 and flashed it with the rom after wiping almost everything, and even tried flashing a different rom with it (I'm using stock A9)., but it seems it resulted in a bootloop every time.
There is a new magisk 21.3 from yesterday, which i hope fixed those issues as i am not planning to go though that hassle again.
I tried the new 21.3, and still it causes bootloop, at least I'm glad I'm not the only one.
DannyynnaD said:
Happened to me As well on my G6.
I had to reinstall the rom. good thing i had backup.
I've downloaded the zip file of Magisk 21.2 and flashed it with the rom after wiping almost everything, and even tried flashing a different rom with it (I'm using stock A9)., but it seems it resulted in a bootloop every time.
There is a new magisk 21.3 from yesterday, which i hope fixed those issues as i am not planning to go though that hassle again.
Click to expand...
Click to collapse
It happened to me, same setup as the OP and did the direct install method from Magisk Manager. My phone is stuck in bootloop at the triangle/! scrren and I can't access TWRP via the normal buttons manner. Also, can't get any ADB to detect the phone (I am using a new PC that probably never connected to this phone despite loading ADB, drivers, etc. - I am going to resurrect the previous PC to see if can connect).
May I ask how you restored the saved boot image? via TWRP restore?
I've rooted and played with many ROMs on various android devices, but I'm no expert and this one has me stumped.
Yes, I did a backup of the boot partition before flashing Magisk and then I restored using TWRP restore. It's not the first time that a new Magisk version causes bootloops on the G5, to I was prepared this time.
By the way, if you don't have a backup, you may try to flash the Magisk Uninstaller zip, and without rebooting, the old Magisk 20.4. In theory it should do the job.
tremalnaik said:
Yes, I did a backup of the boot partition before flashing Magisk and then I restored using TWRP restore. It's not the first time that a new Magisk version causes bootloops on the G5, to I was prepared this time.
By the way, if you don't have a backup, you may try to flash the Magisk Uninstaller zip, and without rebooting, the old Magisk 20.4. In theory it should do the job.
Click to expand...
Click to collapse
Thanks, But how to access TWRP or flash the zip? I haven't found any technique to access recovery (Power+VolDn doesn't work, only allows Factory Reset screen). How to access Fastboot to use ADB (I assume that would be the technique)? I did manage to bring up some odd screen that had a two-line message about fastboot by, I believe, using Power+VolUp.
For clarification this is what I now have:
Phone off (remove battery). Insert battery. Press power button until brief vibrate (1-2 seconds). Release power button. Triangle with "!" displayed "Your device cannot be checked for corruption. Lock the bootloader. " screen displays for about 3 seconds, screen goes black a second or less. Back to the previous warning screen.
Press and hold Power button + Vol Dn acts just like the above, but if I press power + press/release/press/release... I can get the factory data reset (Yes or No(Exit) options) - I haven't accepted that.
I've tried connecting PC to the USB port and two things: as soon as I connect it, the phone powers on and does the looping again. My PC doesn't see the phone in Device Manager and ADB won't list it. I did (one time) manage to bring up the two-line fastboot message at the top of the screen.
BTW: when it first tries to power on, before the Lock the bootloader screen, there is a small, scrambled white area (text?) at the bottom of the screen.
I don't know when was the last time (if ever) I attached to the phone via USB (probably a few years ago when I initially installed TWRP). Haven't really done much other than upgrading TWRP (via TWRP), Magisk (via Magisk Manager), and the very occasional nandoid backup via TWRP (I have one from 3 months ago).
Any further assistance or info would be greatly appreciated.
To access TWRP, turn off the phone, then keep pressed Volume down+Power and once you see the LG logo release the power button and press it again. The phone should ask you if you want to reset everything: if you press yes and then confirm, you will:
1) Enter in TWRP, if you have TWRP installed, or
2) Erase the whole internal memory, if you don't have TWRP installed.
As you already have TWRP installed, it should be quite safe to go through the reset procedure, or at least that's what happens on my phone. If you don't want to take the risk, you can still use fastboot to boot a TWRP image you have on the pc, just write
Code:
fastboot boot <path_to_twrp.img_on_pc>/twrp.img
To do so, you first need to boot into fastboot: you can just turn off the phone and, keeping the Vol- pressed, connect the USB power cable to the phone. It will boot into fastboot.
One more method could be booting into download mode (Vol+ and connect the USB cable) and flashing an original firmware using LGUP, but that is way too much for a phone that already has both TWRP and fastboot accessible.
tremalnaik said:
To access TWRP, turn off the phone, then keep pressed Volume down+Power and once you see the LG logo release the power button and press it again. The phone should ask you if you want to reset everything: if you press yes and then confirm, you will:
1) Enter in TWRP, if you have TWRP installed, or
2) Erase the whole internal memory, if you don't have TWRP installed.
As you already have TWRP installed, it should be quite safe to go through the reset procedure, or at least that's what happens on my phone. If you don't want to take the risk, you can still use fastboot to boot a TWRP image you have on the pc, just write
Code:
fastboot boot <path_to_twrp.img_on_pc>/twrp.img
To do so, you first need to boot into fastboot: you can just turn off the phone and, keeping the Vol- pressed, connect the USB power cable to the phone. It will boot into fastboot.
One more method could be booting into download mode (Vol+ and connect the USB cable) and flashing an original firmware using LGUP, but that is way too much for a phone that already has both TWRP and fastboot accessible.
Click to expand...
Click to collapse
My phone never got past the bootloader screen (i.e. never got to the LG logo screen). When I booted into fastboot mode with the Vol+ button, I could issue commands like "fastboot devices" which would return that it saw my phone, but attempting to use fastboot to reload TWRP didn't work - some say the LG fastboot has been neutered.
Eventually, I had to indeed use LGUP/Uppercut and reload the stock Oreo and the phone came back up. BUT attempting to reboot into bootloader not only didn't come up in TWRP, but I got the little dead Android image. I ultimately had to downgrade to OEM nougat, jump through a few hoops, and finally got TWRP installed. Then it was just a matter of restoring a backup or reflashing a newer ROM (I ended up loading lineage 16, no gapps, with microg etc.).
Somehow the magisk upgrade really trashed my recovery partition somehow (??). I've always made sure to have at least a couple of TWRP backups, but this time I was screwed royally when I couldn't access recovery. I forgot what an ordeal it was to get TWRP & root on this phone originally.
Thanks for your help.
================
Update 4: All issues fixed! I'll briefly explain all my issues, what I think caused them, and how i resolved them incase it helps others.
(You can find 3 posts of my original issues by scrolling down, but TL;DR)
4th post (at the top) : Brief summary of all solutions for my 3 big issues.
3rd post: nandroid backup applied, fingerprint+camera stopped working. Fix: reflash Persist partition manually, using the "persist_image.emmc.win" file from the TWRP backup folder
2nd post: Bootloop due to... miscelaneous user errors. Fixed by using TWRP reformat then restoring to nandroid backup.
1st post: Bootloop due to wrong boot.img. Fix: reflashed boot.img downloaded from post#8 of this thread
================
context: I'm using a DN2103 (international Nord 2) phone variant, which received the .A12 operating system update in the past couple days. Meanwhile, Indian users received the .A13 update.
In my process to unroot and update to the new OTA operating system, I used the stock boot.img provided by an indian user, which was the boot.img for the .A13 update which was incompatible with the european .A12 OTA operating system.
Basically I had the wrong boot.img
BOOTLOOP FIX: (this assumes you have the appropriate MTK drivers and ADB drivers, if not, lookup how to get those installed or you can't run ADB or fastboot commands)
Download the correct stock boot.img for your version: I got mine from https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw
Transfer the new boot.img and a copy of vbmeta.img (optional) into the folder where your adb.exe is located (usually platform tools folder). I use the stock vbmeta from the OTA updates from from: https://mega.nz/folder/rQhhHQpA#nNHvPlmzBXwPjmaFpuDa2Q
Reflash your downloaded stock boot image using commands "fastboot devices" to see if you device responds, if it does, then send "fastboot flash boot boot.img".
Reboot phone. If it's still stuck in a bootloop, try flashing vbmeta with command "fastboot flash vbmeta vbmeta.img" similar to the boot image flash.
If you don't have ADB and Mediatek drivers installed, but have TWRP installed, you can do the same from Step 2: Transfer files onto phones internal storage, and step 3) Use the install button in TWRP to flash boot.img to the "Boot" partition. You can also do the same for vbmeta.img to the vbmeta partition if you phone doesn't boot after that.
Hopefully it works. If not, I'm afraid you'll need to boot into TWRP, (if you ahve it installed) and press Wipe, and wipe data/dalvik/cache, then press Wipe again, and reformat the whole phone. If you can get into stock recovery, then you can also use that to format all data. That should get your phone completely wiped to fresh and should boot into a welcome screen, for first time setup.
(note: If you used TWRP to restore or wipe all partitions, PERSIST partition will not be functional leading to camera/fingerprint issues, solution below)
To get into TWRP whilst your phone is bootlooping, you can hold volume up + power to force your phone to reboot, as soon as logos fade, you can press volume down + power to get your phone into fastboot mode. Connect PC, open powershell terminal, phone should respond to "fastboot devices" command. You can then send "fastboot reboot recovery" comand to get it into TWRP.
Fix for Fingerprint scanner and Camera not working:
Apparently when you restore to a TWRP backup, TWRP does not correctly flash the PERSIST partition, so you simply need to do it manually. The persist partition contains sensor calibration data for the fingerprint and camera.
Steps I took for this fix
1) Went to my nandroid/TWRP backup which I had saved to my PC
2) Located file "persist_image.emmc.win"
3) On PC, open ADB terminal in the same folder containing the "persist_image.emmc.win" file (on windows shift+right click to open powershell)
4) Connected phone to PC, sent command "adb devices" to check if device responds, if listed, sent command "adb reboot bootloader" to get device into fastboot mode
5) Sent command "fastboot devices" to see if device responds, if listed, sent command "fastboot flash persist persist_image.emmc.win"
6) Took 1.5 seconds to send 54000 ish KB. Shoud see OKAY's on powershell screen
7) sent command "fastboot reboot" to boot phone up.
Big thanks to @HofaTheRipper for providing the stock A12 boot.img and the persist partition fix!
===============
Post 3 (you can find original post and 2nd post below too)
Phone no longer bootloops, but fingerprint scanner +camera no longer work.
Solution in post #24 of this thread by @HofaTheRipper
Basically caused by TWRP not flashing the Persist partition correctly, so it's solved by finding the "persist_image.emmc.win" file from a Nandroid backup, and flashing that manually.
===============
So phone no longer bootloops which is great, but the camera and fingerprint sensor currently don't work or respond at all
Fingerprint scanner: Trying to register a fingerprint results in the phone vibrating nonstop saying "TRY AGAIN" in big letters, with small letters "unable to complete finger print settings please retry". It continues to vibrate until the settings app is closed or minimised, and won't register a new finger at all. In fact, the fingerprint sensor doesn't even light up, and hte vibrates are the kind of vibrate the phone does to let you know theres an "error" or "not accepted try again" kind of vibration.
Camera issues: Using the option to register facial recognition in the settings app can't open camera due to error message; "camera being used by another app. Please retry later." Even just opening the stock camera app itself instantly crashes. All other apps that use a camera say they do not have permissions to access the camera, despite very clearly having been granted permission.
What I've tried so far:
-Rolling back to A11 OS
-OTA updating afresh back to A12 (again)
-using TWRP wipe darvik/cache/data
-using TWRP to reformat all data
-using settings app, android's wipe data and factory reset option
-googling and searching xda a tonne to find any possible leftover remnants of fingerprints left behind from my previous OS install
One of the thread i found suggest there could be fingerprints i could delete; https://forum.xda-developers.com/t/...ng-or-not-working-after-flashing-rom.3858845/ but I can't find the relevant files on my device.
My 2nd bootloop did indeed force me to do a TWRP wipe+reformat whilst the device was encrypted/ had a pincode, so perhaps theres some kind of security feature that's getting tripped here.
I tried the backup to Nandroid on A11, then used the OTA update to update to A12, so something tells me that perhaps a stock os reflash wouldn't help in my case.
It would be nice to have to full stock OS's for A11, A12, and A13 just to try them out and help troubleshoot.
Any help finding a solution to the camera/fingerprint issue is appreciated, or any help hunting down where I can download the full OS versions. (even for older OS's for the nord2)
My new working theory is perhaps android's innate permission system is messed up, or there's some data stored in the security module that isn't being wiped that's withholding these features relating to the fingerprint/facial unlock security features.
Every single app that tries to access camera is giving back a "please grant permissions" error, despite very clearly have permissions to use the camera.
Any ideas on how to resolve this would be great!
=============
EDITTED: Part 2, BOOT LOOPING AGAIN. Flashing boot.img doesn't resolve bootloop this time around and the phone has a pincode that I forgot to remove.
This is most likely caused due to magisk trying to modify the boot.img for the wrong stock A13 boot image, which no longer existed as I had flashed in the boot image for stock A12 as part of my first bootloop fix; But the phone still had its old data and magisk installation running.
Solved it by using TWRP Wipe option to factory reset and format data. After that, I was able to get the device to boot - current issue is just that the camera and fingerprint sensor don't work
=============
SECOND BOOTLOOP DETAILS; (resolved)
After flashing boot.img for A12, I managed to boot the phone, solving the initial bootloop. However, it didn't take me long to notice issues, and walk straight into another bootloop.
Series of events;
-Phone asked for initial setup including forcing me to apply pincode (can't skip that step)
-Part of pin setup, noticed fingerprint reader not working (vibrates and error message "unable to complete finger print settings please retry")
-Part of pin setup, noticed comera not working during facial recognition step (error message "camera app used by another app")
-Noticed camera app crashes instantly.
-forgot to remove passcode as was in the app drawer and was exploring what was going on, got distracted.
-I checked settings page -> About phone -> Phone is running A12
-checked for latest update to see if A13 is available for OTA update in my region; Nope. "You are up to date!"
Then I made the big mistake. As I was in the app drawer and just checking the state of the phone, and concerned about the fingerprint scanner and camera app not working, I found the magisk app still in the app drawer. Curious as to magisk's state; I clicked on the app and launched it.
-Note; my initial boot loop (orignial post below) was caused when I clicked magisk for the first time after rooting phone, let it the magisk app do it's first time setup thing about "installing full version"; As soon as i hit reboot it bootlooped phone. Now that i resolved that bootloop, I figured magisk might be fine now? Was curious to see what happened to magisk hence my temptation to click it and see. Didn't think to remove pincode first.
-This time, as soon as I clicked magisk, the screen IMMEDIATELY went black, popped up a message saying "restarting", and the phone immediately rebooted.
Phone is now stuck in bootloop again. And to make matters worse, phone has a pincode, which i didn't have time to remove, so stuff is encrypted.
Obviously I tried what worked before; Booted to TWRP, this time, TWRP had to ask for my pincode to decrypt device, but accepted my pincode and decrypted User0 successfully.
-Flashed boot.img for A12 device again, rebooted.
Still stuck in bootloop. Same symptoms as before; Stuck on 2 rotating white dots around the big red dot; If i wait long enough it reboots and shows 1+ symbo land orange state warning message, after a few reboots it boots to TWRP.
So now I have a pincode, and same problem as before, aka bootlooping, TWRP is still installed and working, but also probable issue with fingerprint scanner and camera (remnant from last bootloop perhaps?)
Most likely because magisk is still set to reboot when launched and to modify the boot.img, as thats the step where my first bootloop happened.
===============================
ORIGINAL POST BELOW;
initial bootloop was fixed by flashing boot.img for A12 provided in the comments below
Supposedly the boot.img I originally used was for A13; Supposedly these boot images are similar enough that they seem to mostly work for each other, until magisk touches it - issues with magisk in my 2nd bootloop post above.
================================
My Nord 2 is stuck in a bootloop
TL;DR
I was running a rooted .A11 update just fine, updated to .A12 following a guide, lost root access, so re rooted phone just like i originally did. Got to the point where i used TWRP to flash magisk.zip, that part worked fine, phone booted just fine, launched the magisk app from the app drawer, let magisk install full version, it automatically rebooted, then immediately got stuck in a bootloop.
Full story for troubleshooting context: (in case you can see where I goofed)
- I updated from .A11 to .A12 successfully which meant the phone was unrooted; Followed @pankspoo 's guide except using my own OTA update.zip after clicking download in my settings app (I'm EU region); https://forum.xda-developers.com/t/...rooted-nord-2-any-incremental-update.4347813/ (following the comment to find the update.zip folder at /data/OTA-package/update.zip
- Verified my phone was fine running the .A12 update properly; opened settings app, checked about phone page, .A12 listed and "newest version installed". Launched the root checker app and confirmed phone was "not rooted" anymore so proceeded to follow @pankspoo root guide again https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/ , the same guide I originally used successfully back on .A11 (worked great!)
- Got to the point in the guide where I flashed and installed TWRP, it worked just fine. Nothing unusual so far.
- Used TWRP to flash magisk.zip, also worked fine. Still nothing unusual.
- Used TWRP to make a full backup (ticked all boxes) here, but this backup file seems to be GONE (did not transfer it to PC)
- Rebooted to system, phone booted just fine, found magisk icon in the app drawer, launched the magisk app and let it do its first time setup thingy, where it "installs full magisk" and so on. I let it do it's thing, eventually it rebooted the phone;
- Phone now immediately stuck in bootloop. Don't know if Magisk even installed itself properly; Waited out the first bootloop long enough that the phone ended up rebooting multiple times and ended up automatically booting into TWRP so its not a "just wait longer" issue.
Symptoms:
Its a standard bootloop aka stuck on 2 rotating white dots around the larger red dot. If i wait longer enough, phone reboots, initially shows the 1+ icon and the "orange state not trusted boot in 5" message that we're probably all used to seeing. After a few reboots it eventually ends up booting into TWRP.
Holding Volume up+power forces the phone to reboot, but obviously, still gets stuck in the same bootloop.
Holding Volume down+power when the phone reboots places the phone into fastboot mode, which lets me connect my computer, open the powershell window, and use the "fastboot reboot recovery" command to get into TWRP instantly.
TWRP is working fine! I can still flash things and do all the normal stuff in TWRP... But not idea what to do right now.
Stuff I've already tried: (against my better judgement)
-Clicked "restore" button on TWRP; I made a TWRP backup whilst on A11, and the device does not seem to want to boot with that A11 boot image and old nandroid restored.
-renamed magisk.zip file to uninstall.zip and used TWRP to flash it; Nothing seems to have happened. Error code: "magisk will not be uninstalled please uninstall manually"
-Tried reflashing magisk.zip normally.
-Tried to manually reflash my old boot.emmc.win file form TWRP backup on the phone (this is most likely my old A11 boot image)
How do I proceed from here? All help appreciated. Edit: Turns out, i was flashing the A13 boot image from indian devices whereas I have a phone running A12. Bootloop issues were instantly resolved when the A12 boot image was flashed again;
However, magisk was still set to reboot the phone and patch the boot.img so I ended up having to wipe all data to get rid of magisk and stop magisk from corrupting the boot image.
@pankspoo
Zombnombs said:
My Nord 2 is stuck in a bootloop; VERY new user here so definitely appreciate any help immensely, androids and rooting phones is totally alien to me; and this is probably the most stressful thing I've dealt with in a LONG time.
TL;DR
I was running a rooted .A11 update just fine, updated to .A12 following a guide, lost root access, so re rooted phone just like i originally did. Got to the point where i used TWRP to flash magisk.zip, that part worked fine, phone booted just fine, launched the magisk app from the app drawer, let magisk install full version, it automatically rebooted, then immediately got stuck in a bootloop.
Full story for troubleshooting context: (in case you can see where I goofed)
- I updated from .A11 to .A12 successfully which meant the phone was unrooted; Followed @pankspoo 's guide except using my own OTA update.zip after clicking download in my settings app (I'm EU region); https://forum.xda-developers.com/t/...rooted-nord-2-any-incremental-update.4347813/ (following the comment to find the update.zip folder at /data/OTA-package/update.zip
- Verified my phone was fine running the .A12 update properly; opened settings app, checked about phone page, .A12 listed and "newest version installed". Launched the root checker app and confirmed phone was "not rooted" anymore so proceeded to follow @pankspoo root guide again https://forum.xda-developers.com/t/tutorial-twrp-and-root-nord-2.4340477/ , the same guide I originally used successfully back on .A11 (worked great!)
- Got to the point in the guide where I flashed and installed TWRP, it worked just fine. Nothing unusual so far.
- Used TWRP to flash magisk.zip, also worked fine. Still nothing unusual.
- Used TWRP to make a full backup (ticked all boxes) here, but this backup file seems to be GONE (did not transfer it to PC)
- Rebooted to system, phone booted just fine, found magisk icon in the app drawer, launched the magisk app and let it do its first time setup thingy, where it "installs full magisk" and so on. I let it do it's thing, eventually it rebooted the phone;
- Phone now immediately stuck in bootloop. Don't know if Magisk even installed itself properly; Waited out the first bootloop long enough that the phone ended up rebooting multiple times and ended up automatically booting into TWRP so its not a "just wait longer" issue.
Symptoms:
Its a standard bootloop aka stuck on 2 rotating white dots around the larger red dot. If i wait longer enough, phone reboots, initially shows the 1+ icon and the "orange state not trusted boot in 5" message that we're probably all used to seeing. After a few reboots it eventually ends up booting into TWRP.
Holding Volume up+power forces the phone to reboot, but obviously, still gets stuck in the same bootloop.
Holding Volume down+power when the phone reboots places the phone into fastboot mode, which lets me connect my computer, open the powershell window, and use the "fastboot reboot recovery" command to get into TWRP instantly.
TWRP is working fine! I can still flash things and do all the normal stuff in TWRP... But not idea what to do right now.
Stuff I've already tried: (against my better judgement)
-Clicked "restore" button on TWRP; I made a TWRP backup ticking all boxes like 10 minutes before the bootloop issue started; Right after I used TWRP to flash magisk.zip successfully; However, my NORD 2/Internal Storage/TWRP folder is currently empty; There is no backup folder there! I did not transfer it to my computer so no idea where it went.
-renamed magisk.zip file to uninstall.zip and used TWRP to flash it; Nothing seems to have happened. I did read the text on the phone and saw a bit saying "magisk will not be uninstalled please uninstall manually" so i guess something went wrong.
-Tried reflashing magisk.zip normally.
-Remembered I made a TWRP backup a few weeks ago, so used TWRP's Restore feature to restore to that backup. This is a backup was when the phone was running .A11 and obviously working fine, not sure if that matters much. (didn't help either so I assume TWRP backups don't restore stock os or anything like i thought it did?)
Obviously, none of the above resolved the boot loop and I have no idea what to do from here. Phone still stuck in the same old rotating 2 white dots around the larger red dot animation.
Not sure if I should reflashed anything at all as I'm pretty inexperienced. Scared to try anything else without consulting you guys for help first. Most google results for bootloop fixes seem super sketch and outdated so I'm scared to try much else, and already thinking I may have made things worse with the things I did already do.
How do I proceed from here? All help appreciated. Not sure if using .A12 was the wrong call here but i suspect it was.
Click to expand...
Click to collapse
Which version u r on now when u bootloop Ed tell. Me I will give u boot image flash that done
pankspoo said:
Which version u r on now when u bootloop Ed tell. Me I will give u boot image flash that done
Click to expand...
Click to collapse
Hey thanks so much for posting the guides!
OHHHHHHHH I see now. I updated to .A12 using the European OTA update.zip file, and the boot.img I used was from your guide which you said was
"2) upgrade from v11 to v13(indian)"
That must be why. Do you have a boot.img for .A12?
Or do you perhaps think I should download .A13 because it's more recent?
Zombnombs said:
Or do you perhaps think I should download .A13 because it's more recent?
Click to expand...
Click to collapse
If u r on A12 on which u r bootloop Ed then use A12 EU only boot image to. Flash and reboot i don't have A12 EU boot. Img
pankspoo said:
If u r on A12 on which u r bootloop Ed then use A12 EU only boot image to. Flash and reboot i don't have A12 EU boot. Img
Click to expand...
Click to collapse
Do you mean I have to find the boot img for A12 and nothing else will work? I'm not too sure where to find boot images.
Do you think If i download the update.zip for A13, I can flash that, while the device is bootlooped, and it might work? Would I need to use incremental update from A12 to A13 or would I use incremental from A11 to A13?
Also, I don't know how to download from your telegraph links, it doesn't seem to work for me, clicking the file doesn't download.
Is there another way to resolve the bootloop, including wiping all data just so the phone works again?
A12 Stock EU boot img:
HofaTheRipper said:
A12 Stock EU boot img:
Click to expand...
Click to collapse
@Zombnombs u got it do it now
The a12 boot image worked a charm! Thanks guys!
Okay. Phone's in a bootloop again! Literally about to cry or something
I think I need a recovery image or something? OR a way to get phone back to completely stock.
Full story;
After flashing a12 boot image, phone booted up andI checked
-Phone was running A12(checked "about phone" in settings app)
-Root access was granted (used "Root Checker" app)
-Magisk app still in the app drawer
At this point for some reason I ran the "click here to set up your phone" because the popup/notification was annoying. During this, you're forced to enter a passcode. I never got the chance to remove the passcode so the device is now "encrypted"
Things I did notice during this time whilst exploring the phone;
-Fingerprint scanner is totally broken; The white light doesn't even appear, phone vibrates constantly like it's error'ing out, and shows "unable to complete finger print settings please retry" as an error on screen
-Facial recognition step of the setup wizard also had a strange error message, saying "Camera is in use by another app".
-Camera app immediately crashed when I click it to check why facial recognition was failing.
Anyway, still thinking i was just exploring the state of the phone, I decided to click the magisk app in the app drawer to see what was happening with it;
IT INSTANTLY RESTARTED MY PHONE. Screen went black, the words "restarting" popped up and the phone rebooted without any chance for me to stop it.
And what do you know, PHONE IS BACK IN A BOOTLOOP.
First thing I tried was booting into TWRP again, which had to decrypt User0 now that I have a passcode on, but that was fine, because entering the pincode worked. I flashed the boot.img for A12 again; But it didn't help.
What should I do now? boot.img didn't work, I'm really inexperienced with this stuff. I'm new to rooting, but keen to learn and get into modding/rooting androids so I guess this is a good learning experience, albeit extremely frustrating >.>
Due to issues with finger/camera, and the fact it's still bootlooping anytime I click magisk, best option is probably to restore to complete stock? Google search says I need a recovery image for my device, but i can't find Oneplus's recovery image for Oneplus Nord 2 so I guess I'm back to asking here for help.
@HofaTheRipper @pankspoo (sorry for the tag) do either of you happen to have a recovery image?
^ Phone is back in a bootloop.
Updated the initial post again because this problem is getting kinda long winded.
TL;DR for my 2nd bootloop boot.img isn't working to fix the bootloop. Bootloop occured after clicking on magisk app, which instantly restarted phone without warning (before I could remove pincode), and put the phone into bootloop state.
Phone has a pincode on it now so TWRP has to decrypt User0, not sure if that's the reason why boot img doesn't resolve this boot loop. Even though I can enter pincode when TWRP asks for it, and TWRP manages to decrypt User0 successfully.
I did notice after fixing first bootloop, fingerprint scanner and camera didn't work, so it's probably best to just start over anyway. Add in the new bootloop, and I don't really see any reason to continue with this attempt at the root, probably best to fully reset to stock and try again, try get the fingerprint and camera working again.
Recovery Image time I guess?
Ok
Zombnombs said:
Updated the initial post again because this problem is getting kinda long winded.
TL;DR for my 2nd bootloop boot.img isn't working to fix the bootloop. Bootloop occured after clicking on magisk app, which instantly restarted phone without warning (before I could remove pincode), and put the phone into bootloop state.
Phone has a pincode on it now so TWRP has to decrypt User0, not sure if that's the reason why boot img doesn't resolve this boot loop. Even though I can enter pincode when TWRP asks for it, and TWRP manages to decrypt User0 successfully.
I did notice after fixing first bootloop, fingerprint scanner and camera didn't work, so it's probably best to just start over anyway. Add in the new bootloop, and I don't really see any reason to continue with this attempt at the root, probably best to fully reset to stock and try again, try get the fingerprint and camera working again.
Recovery Image time I guess?
Click to expand...
Click to collapse
Ok
I have the same problem(( bootloop after rebooting in magisk
IgorSamsonov said:
I have the same problem(( bootloop after rebooting in magisk
Click to expand...
Click to collapse
TL;DR of what worked for me was making sure i had the right boot.img flashed and then also flashing vbmeta afterwards. That's all it initially took.
I also seemed to solve another one by using TWRP to wipe cache/dalvik/data, then also pressing wipe, and hitting reformat (losing all data)
Finally I think if you made a TWRP backup, you should be able to restore to that, then wipe do a dalvik/cache/data wipe.
Just what worked for me, I'm pretty new at this stuff so I literalyl don't really know what I'm doing either
Zombnombs said:
TL;DR of what worked for me was making sure i had the right boot.img flashed and then also flashing vbmeta afterwards. That's all it initially took.
I also seemed to solve another one by using TWRP to wipe cache/dalvik/data, then also pressing wipe, and hitting reformat (losing all data)
Finally I think if you made a TWRP backup, you should be able to restore to that, then wipe do a dalvik/cache/data wipe.
Just what worked for me, I'm pretty new at this stuff so I literalyl don't really know what I'm doing either
Click to expand...
Click to collapse
r u root ur device after this?
IgorSamsonov said:
r u root ur device after this?
Click to expand...
Click to collapse
Nope, I'm trying to deal with my camera/fingerprint sensor issues
Zombnombs said:
Нет, я пытаюсь решить проблемы с камерой / датчиком отпечатков пальцев
Click to expand...
Click to collapse
how do you enter recovery mode without waiting for a couple of reboots ?
IgorSamsonov said:
how do you enter recovery mode without waiting for a couple of reboots ?
Click to expand...
Click to collapse
You can hold power+vol up to force a reboot, and when the logos disappear, hold Vol down + power to enter fastboot mode. You can then plug in your computer and send powershell window to send "fastboot reboot recovery"
I have succesfully been rooted and for more than 3 years but I needed to uninstall root because some bank apps were updated and I couldn't use them anymore. After trying a bunch of stuff I wanted to uninstall stable Magisk and try the alpha version., so I pressed the Uninstall Magisk button in the app. My phone didn't want to reboot anymore (bootloop) and I lost TWRP, so i did the button dance and factory reset it. The reset seemed to only take a few seconds, no matter how many times i retried it (so possibly something went wrong there). It rebooted after a long wait (5-10 min) and I entered the setup. A few problems are now present: wifi doesn't work, random freezes and reboots (e.g. opening camera app freezes the device), every reboot takes 5-10 min etc. I enabled usb debugging in order to try the whole process of rooting the device again but only when starting the process I notices download mode loads (the blue dots) but is never entered and the device just reboots instead. It is recognized by adb but not by fastboot. LGUP recognizes the devices when it's turned on but when starting the downgrade to 10d, the device never enters download mode and reboots. LGUP just throws an error.
What are my options now?
EDIT:
So the currently i can access some basic mode which tells me it has been unlocked once and how to unlock it (no clue what this mode would be called), the loading screen for the download mode and normal turned on system mode.
EDIT2: I have a twrp backup.ab on my pc (backed up everything I think) from just before the changes. Can I somehow restore this without twrp? if I use adb restore backup.ab while the phone is on it sayw restore started and a few seconds later restore ended but nothing changes.
I am running into the EXACT SAME ISSUE. I have been trying different things such as flashing and wiping in different TWRP versions and orangefox. Also tried restoring previous backups and partitions. Nothing yet, will let you know if a solution comes along. I was messing around with flashing GSI and android 12 using GSI when this became a problem
Full wipe and data format, inti support via orange fox then Flashing kdz of 20H in recovery fixed my DL mode.