Edit:
Problem solved - phone recovered, and rooted successfully. I think the problem was that I didn't use the most recent version of SuperSU. I was using version 2.46 iirc, but I finally got the root working with version 2.76 (filename UPDATE-SuperSU-v2.76-20160630161323). The TWRP version I used is twrp-3.0.2.0-0-h960a.img. (I used this version of twrp both in the failed root attempt as well as the successful one). After I attempted root with 2.46, the phone just hung at the "your device software can't be checked for corruption". To get my phone back, I booted it and connected to USB (you might have to enter fastboot by holding the down volume button and plugging in the USB cable, keeping the down volume pressed until the phone boots, or you might just boot the phone normally and plug it into the USB cable, even though the phone will "hang" doing this, lgup can detect it and you'll be able to "refurbish" with marshmallow kdz which you should have on your computer. I updated my phone to marshmallow before attempting the root, so I had the kdz already. The one I used is v20a. Anyway, after refurbishing, the phone is recovered and usable again, you still get the "can't check for corruption" screen on boot but it only stays for 5 seconds, and then the phone starts. This is normal for an unlocked bootloader. What I did after recovering the phone was to save SuperSU 2.76 (again, filename is UPDATE-SuperSU-v2.76-20160630161323) onto my phone's SD card. Then I reflashed twrp (boot into fastboot, then from console window "fastboot flash recovery twrp-3.0.2.0-0-h960a.img". Then I had to disconnect from the USB cable, and remove the battery. Apparently some phones will perform a factory reset if you attempt a reboot via the console after installing twrp - this is why I removed the battery - then I put the battery back in and booted into recovery mode. To do this (contrary to most instructions I found online which give the wrong button presses), I held the down volume arrow, and then pressed power until the LG logo showed up. Keeping the down volume pressed, I released only the power button, then tapped the power button until I got to a recovery screen (again, keeping the down volume pressed this whole time). Select "yes" both times and you should be in TWRP. Just follow instructions from there that you can find in rooting guides. When you're ready to restart the phone, you'll get the familiar "can't check for corruption" nag screen, but this will go away after a few seconds - LG logo will briefly appear, then disappear and back to that stupid nag screen. But after a few more seconds, the phone starts up. Confirmed rooted with rootchecker!
Below is my original thread where I describe the problem
So I unlocked bootloader, installed twrp and everything fine so far. I put supersu zip file into download folder, flashed with twrp, cleared cache, and went to system reboot - now the phone just hangs at "your device software can't be checked for corruption"
I should say that instead of pushing the supersu zip to sd card, I just saved it in 'downloads' folder of the phone. I also had to do the trick where I flash twrp, and then remove battery, restart phone to recovery mode, because a reboot of the phone would not allow me to use twrp (it just did factory reset)
I can get back into twrp via recovery boot via down volume + power, and I can get into fastboot via down volume + USB cable, but I can't get anywhere else.
I installed stock recovery image from here: droidviews. com/install-stock-recovery-on-lg-v10-using-fastboot/
Went into recovery boot, the android icon shows up and starts to work, but then goes right back to "your device software can't be checked for corruption"
How can I recover this phone? It's H960A
edit:
Ok, so lgup was not recognizing it, and I couldn't install kdz to recover android. I installed lgbridge, then plugged phone in via fastboot (down arrow + usb). lgup then recognized it, and I refurbished with mm kdz. Seems ok now, but still not rooted, and I still get the "your device software can't be checked for corruption" when I boot up (afaik this is because bootloader is unlocked). Tried to root again, same issue. Except this time lgup would not recognize from fastboot, so I just booted phone normally and connected via USB. Then lgup recognized it and I was able to refurbish again
How can I root this thing? at least I have a working phone again
================
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"
Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.