Hi all,
So I've inherited an old S7 and I'm trying to install LineageOS on it. I've got the build for the OS done already, but to sideload it, I need the custom recovery TWRP installed on my phone, but I haven't been successful getting it installed on my phone, and after talking with the folks on the LineageOS subreddit, it's unclear if my phone's bootloader is unlocked, which it needs to be to install TWRP. I've enabled developer options on my phone, enabled USB Debugging, and I've enabled OEM unlock. However, when I follow their instructions to install TWRP, I boot into recovery mode, and the stock recovery mode loads.
I can't tell if my bootloader is unlocked or not, and any test I've followed apparently doesn't work on my phone because Samsung. I found this tutorial on this forum about unlocking my particular phone model - https://forum.xda-developers.com/t/unlock-bootloader-sm-g930vl-straighttalk.3436986/ - but I have 2 problems.
1) The first response links to a guide, but almost all the download links the author listed no longer work - https://forum.xda-developers.com/t/...ning-to-stock-a-galaxy-s7-or-s7-edge.3411039/ - I believe I already have the Samsung drivers and ADB setup on my computer; I was able to find a download for Odin; but I have no idea where to get the root images, and nobody else in the comments posted an alternate link that I could see.
2) In the original thread, other users suggested just using the Eng boot instead of the guide I listed, but nobody listed a download link, and I don't know what it is, or how I would tell an official download link from a questionable reupload.
If anybody can help clarify some of my confusion, or point me to where I could get the downloads I'm looking for, I would very much appreciate it.
OK so, I have a SIM unlocked oneplus 7 pro, but the OEM unlocking option is greyed out in the settings, and rebooting into the bootloader shows DEVICE STATE - locked.
I'm trying to follow the instructions here (and by extension here) , but neither of the archive links are working, and the guacamole.21 file isn't downloading from androidfilehost.com.
Does anyone have a working version of these files? I've been able to download the MSMDownloadTool, and the L2+ drivers, but not the guacamole rar.
Any help would be greatly appreciated!
Once I get this all sorted out I'd like to make my own full tutorial on how to set up dual booting with lineageOS and stock android!
Update:
I got it to work! I didn't realize there was a difference between the sprint version and the T-mobile version! Phone is fully rooted with no issues so far!
Hi,
While trying to root the OnePlus Nord CE 2 5G (European Edition), I managed to mess up my phone completely by flashing wrong files to the phone using fastboot.
I recieved the A13 update, and I think I flashed the wrong boot.img and some other mismatching files using fastboot. I know, it's the first time I attempted this and probably a beginners mistake. Shame on me.
The phone is stuck at the bootloader (I think), because it's not going past the boot logo from OnePlus.
I tried searching online and the OnePlus support pages for the original OxygenOS image to perform a full recovery, but I have been unsuccessful.
Can anyone provide this image or provide some guidance how I would be able to make it workable again?
Thank you in advance!
Sorry to hear about your phone. From my knowledge, the A13 firmware hasn't been shared yet. You could try your luck contacting OnePlus support. Otherwise you'll just have to wait until someone shares it, but that could take quite a while.
@mr_munch, thank you for your reply. I'll reach out to OnePlus support.
GeneratedUnique said:
@mr_munch, thank you for your reply. I'll reach out to OnePlus support.
Click to expand...
Click to collapse
Have you have any luck? Looks like they released a rollback package that includes the A.13 boot image as part of their Android 12 beta program. Maybe that could help you out if you still need it: https://community.oneplus.com/thread?id=1110424001643544581
Hi @mr_munch,
Unfortunately, so far no luck.
I've reached out to OnePlus support, they asked me to go to one of their service centres, called The Phone Lab in the Netherlands. They tried to flash the phone with the original ROM. It's now giving the error message "the serial is not match" while booting up. According to them this is due to a hard brick and I had to file a case with OnePlus support, but haven't heard anything yet.
I'll keep you posted.
Thank you for all the help!
Hi,
OnePlus repaired the phone, by replacing the motherboard/soc, all under the warranty. Luckily, I got a working phone back.
Thank you all for your support.
GeneratedUnique said:
Hi,
While trying to root the OnePlus Nord CE 2 5G (European Edition), I managed to mess up my phone completely by flashing wrong files to the phone using fastboot.
I recieved the A13 update, and I think I flashed the wrong boot.img and some other mismatching files using fastboot. I know, it's the first time I attempted this and probably a beginners mistake. Shame on me.
The phone is stuck at the bootloader (I think), because it's not going past the boot logo from OnePlus.
I tried searching online and the OnePlus support pages for the original OxygenOS image to perform a full recovery, but I have been unsuccessful.
Can anyone provide this image or provide some guidance how I would be able to make it workable again?
Thank you in advance!
Click to expand...
Click to collapse
Hi,
Same issue here with OnePlus Nord CE 2 5G (European Edition), I'm stuck on the boot logo (the three dots turning around) after flashing boot.img.
A11 update,
I tried to flash stock boot.img but no luck,
I tried a factory reset via TWRP, I tried to flash via fastboot stock firmare following this guide: https://www.getdroidtips.com/oneplu...nstall-Stock-Firmware-on-OnePlus-Nord-CE-2-5G
I don't know what to do to get it working. Do you have any advice?
...sorry, I posted to the wrong device board
Hello, I've been searching and lurking.. I've unlocked the bootloader on my Pixel 3a. I've rooted before, restored before, nandroids etc etc. So I've been in the game for a little while. (all the way back to my LG Ally!) Anyways. I was wondering what would be the best method of Rooting and installing TWRP on the Pixel 3a at this point in time, and if TWRP is even possible at this point. (September 2022) Should I use Magisk? NetHunter seems to rely on the device having TWRP in order to flash the kernel. (but we don't NEED it to flash the kernel do we?) I keep coming across old posts which do not apply to the build of my phone and I'm feeling very lost. This phone is not my daily driver, and I am confident when it comes to restoring a soft-brick. It's a Google Fi pixel, bought from the google store, maybe that helps.
Android 11, RQ2A.210405.005 (info from recovery)
BL Version : b4s4-0.3-7062600 (fastboot)
Baseband Ver: g670-00105-210113-B-7078968 (fastboot)
Secure Boot - Yes (fastboot)
HW Ver - MP1.0 (fastboot)
EDIT: Rooted phone successfully using Magisk/patched boot.img.
NEW ISSUE! : The phone is showing up as a Pixel 5 now. In rootchecker, my first successful root shows Pixel 3a as the device. This has never happened to me before. Any input would be greatly appreciated!
XDA, we've had a problem here.
Hello everyone!
I'm throwing a bottle into the sea because I don't feel that other people have had the same problem.
I've been on the latest version of Lineage OS 18.1 until now. Having seen the latest version released (20.0) I tried to update my smartphone but the screen became unresponsive (plus there was no network: I'm in France #andr01dfr3ak).
So I used Scrcpy and I could use the phone "normally". I decided to redo a fresh installation from OOS (I had to downgrade) and install the latest version of Lineage OS 19.1 (and wait for the 20.0 to be stable).
So I used MSM and installed an Indian version of OOS on my phone. My screen was responding again. Wanting to put the latest version of OOS in order to reinstall Lineage OS, I have updated OOS via OTA and I had the same problem as before: the screen does not respond anymore but now without any possibility to activate anything in the developer options.
Thus, in summary: I'm currently stuck with (the last?) OOS because the screen that doesn't respond anymore (but it's on and all the buttons work) and I have no possibility to activate anything in the developer options (so no USB debugging etc.).
What do you think I should do?
When you flashed the wrong firmware and wonder why the display doesn't work. The firmware you flashed thinks your phone is the India 9r version and all updates will only give you india stuff now. You must flash EU version of firmware. Link https://github.com/libxzr/FastbootEnhance