Samsung Note 10+custom ROM got stuck in boot - Samsung Galaxy Note 10+ Questions & Answers

Hi Folks,
I recently installed multiple custom ROM(pixel, LineageOS) in my Samsung Note 10+ (SM-N975F) and it always gets;s stuck at boot.
Steps I performed:
- Unlocked the bootloader
- flashed vbmeta image using Odin
- flashed TWRP using Odin
- booted into recovery and wiped data (clicked on wipe-->format--->yes) then rebooted in recovery again
- transferred the custom OS zip files and installed them using TWRP
- rebooted the phone to the system.
TWRPversion - 3.7.0_9-0
LIneage ROM = lineage-19.1-20230117-nightly-d2s-signed.zip
Pixel ROM = PixelExperience_Plus_d2s-13.0-20230108-1426-OFFICIAL.zip
P.S. - I just Flashed Lineage recovery using Odin but my phone is still booting in TWRP

Related

Urgent Help Needed Flashing CM13 On a GT-I9195 LTE

Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.
I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.​
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?

Twrp is being replaced by stock recovery

I have flashed twrp recovery on my mobile after flash i booted to twrp it worked and then booted to system and again i booted to recovery to check if twrp is working or not but it has been replaced by stock recovery
I have tried every possible way that I found in XDA for my mobile but it was no use every time twrp is being replaced by stock recovery so anyone can give me a solution for this issue.
Mobile : Lenovo k8 note
Android : 8.0.0
Model : XT1902-3
Build : OMB27.43-70

[Fixed] OnePlus 5t keep rebooting into recovery

As mention in the title, i have unlocked bootloader & OOS 9.0.11 with magisk + xXx No Verity 4.0.zip "downloaded from here, i wanted to try Pixel Experience custom rom, so i backed up everything using twrp backup, wiped every thing including internal storage, installed Pixel Experience Full package "Android 10 plus edition 14/3/2020", cleared cache then its never boot to system. when i click "Reboot system" it reboots then show me that bootloader warning then oneplus logo powered by android then reboot again automatically to recovery, so i tried the following:
Wiped EVERYTHING then restore backup = same problem
Wiped EVERYTHING then Clean Flash [OFFICIAL] OxygenOS 9.0.11 (Android Pie 9.0) OTA = same problem
I can access to twrp recovery and its working fine, but i can't reboot to system
FIX: Wiped EVERYTHING, flashed stock recovery using twrp, locked bootloader, flashed OxygenOS 9.0.11 using adb sideloader from stock recovery "install from adb" = booted into system successfully
can anyone tell me where was the problem? :/
FIX: Wiped EVERYTHING, flashed stock recovery using twrp, locked bootloader, flashed OxygenOS 9.0.11 using adb sideloader from stock recovery "install from adb" = booted into system successfully
can anyone tell me where was the problem? :/
You forgot to flash the firmware (9.0.11), flash it before you flash the ROM and it should work without any problems.
If you need the file check the crDroid thread links and download it from there.

stuck in bootloader/recovery, can't flash ROMs.

Hello,
i'm stuck in a particular situation: i can use fastboot and i can flash recoveries but none of them can succesfully flash a rom. i want to go back to the stock Realme UI, my device is RMX1993.
i tried to follow the guide (https://forum.xda-developers.com/realme-x2/how-to/to-stock-rom-howto-t4014773) but the last recovery (rmx1993-sde20-stock_recovery-c05) can't flash neither RMX1993EX_11_OTA_1040_all_tSZ3Sf5A77NS nor RMX1993EX_11_OTA_1050_all_loALrMDyMrbs.
tried to flash trough orangefox or the last twrp that support ozip decription but the result is a "succesful flash" but a phone that does not go over the boot screen and it reboot.
i succesfully installed color os trough the proper old stock recovery and it said the installation was succesfull, but the problem was the same.
someone know where could be the problem?
You need to successfully flash Android 10 (Realme UI 1.0) before you can flash custom Android 10 roms.
Have you tried this guide: https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
As for why your colorOS back up is not working i'm not quite sure...have you wiped your cache before booting to the color os backup?

I need help!!

I was trying to install custom rom (evolution X 4.6) on my redmi note 8 pro and it went a little bad
I started off normal by unlocking the bootloader and flashing TWRP then I closed avb 2.0 and installed root and everything was fine and my phone was booting normally so then I went TWRP and wiped the default wipe then i clicked install and flashed the rom and so then i clicked reboot and i was greeted with a bootloop and i don't know what to do i tried flashing global MIUI 12 but when it tries to boot it ends up opening TWRP i also made the big mistake of not backing up my device before attempting to flash custom rom someone please help I'm trying to rollback to the factory firmware but i don't know how
i just found out you had to be android 9 to flash custom roms
now I can't even enter twrp and I tried reflashing it and I still can't enter it the only thing I can do rn is enter fastboot
NVM i fixed it using mitoolv2 www .xiaomitool.com/V2/

Categories

Resources