Hi everyone,
well I tried all kind of ROMs on my Samsung SM-A750FN/DS and all had problems booting.
I started with the fully updated Stock ROM. I flashed TWRP through ODIN 3.14.4, rebooted into TWRP, patched RMM and installed Magisk 20.4.
After finding out, that the damn Samsung Stock ROM didn't want to boot (bootloop), I tried to install different ROMs.
Here a list what I tried:
- Installed TWRP from the Forum successfully.
- Patched RMM
- Installed Magisk 20.4.
- Stock ROM didn't boot. Bootloop.
- Booted into TWRP and tried GSI ROMs.
- GSI Vanilla ROM with Android 11 for ARM64 a-only.
- Boots into Download Mode.
- Installed ROM again, but after that I installed RMM Patch.
- Boots into Download Mode.
- Booted into TWRP and tried HavocROM Android 10 ARM64 3.8 aonly.
- RMM Patch
- Still only booting into Download Mode.
- Tried again, but this time I wiped DATA, Dalvic Cache, Cache, System.
- Installed ROM (Havoc ROM).
- Installed Patch RMM.
- Wiped Dalvic Cache.
- Still Boots into Download Mode.
What the hell am I doing wrong? I just want a Google and Samsung free ROM on this mobile.
I appreciate any help with this problem.
I don't get any error messages, which would help out with finding the problem.
You need to install the stock quantum kernal too
Link to thread:-
https://forum.xda-developers.com/ga...ernel-quantum-kernel-v1-0-updated-20-t4085585
and also you need to format data after going to TWRP and then flash other zips. After android 10 update this device is now in A/B mode
So I tried following things:
- Booted into TWRP
- FORMAT Data under Wipe selected
- Installed RMM_Bypass.zip
- Installed Quantum Kernel 2.5. (on 2nd try I rebooted here into Recovery).
- Went to Install, clicked on Install Image, choosed LeOS-R-arm64_bvN-20201122.img (Should be Arm64 AB)
- Rebooted into system (on 3rd try flashed the RMM_Bypass.zip again before reboot).
- Bootloop (on 1st, 2nd and 3rd try).
On my 4. try I wiped Dalvik Cache, Cache, System and ran FORMAT Data. Same result.
On my 5. try I tried a different Image by Phhusson (system-roar-arm64-ab-vanilla.img). It contains Android 11. Same results on all 4 attempts.
What am I missing? If you have any different ROMs, that could work better, tell me. Anything containing Android 10 or higher is welcome. I thought about Quantom Stock, but their Android is 9. I prefer 10 or higher.
So I narrowed it down to the problem I get.
Stuff I did:
- Flashed the Samsung Stock Rom with Odin
- Flashed TWRP with Odin
- Flashed RMM Bypass 2 (Bootloop)
- Redid all that, but flashed RMM Bypass 3. Same problem.
Looks like the RMM Bypass doesn't work with the newest Samsung Stock Rom, since the RMM Bypass got patched by Samsung.
Can anyone confirm this?
Another question: If I flash the Android 9 Samsung Stock Rom, does this RMM bypass work again?
Related
Happens in this order:
Flashed May full image to both a, and b slots
Fully booted into stock 7.1.2
reboot to bootloader
boot twrp RC1
flash twrp RC2
flash BootSigner - successful
reboot recovery to RC2
wipe cache, system and data
flash Resurrection Remix 7.1.2
flash twrp RC2
flash BootSigner - boot was already signed (also gave warning that there was no functional framework on active slot (active slot is b))
boot to system
White google boot then reboot
White google boot then ram dump
and loop
I was having issues with installing custom ROMs as well. I finally got it to work by not flashing twrp at all between flashing rom, bootsigner, SuperSU, etc. It was kind of a pain because I had to boot twrp from fastboot Everytime but I am now running a custom ROM and kernel.
Once I had everything installed I did finally flash twrp RC1, and everything is working.
I seemed to have issues with twrp RC2. Maybe I was doing something wrong though...
Sent from my Pixel using Tapatalk
bretrick30 said:
I was having issues with installing custom ROMs as well. I finally got it to work by not flashing twrp at all between flashing rom, bootsigner, SuperSU, etc. It was kind of a pain because I had to boot twrp from fastboot Everytime but I am now running a custom ROM and kernel.
Once I had everything installed I did finally flash twrp RC1, and everything is working.
I seemed to have issues with twrp RC2. Maybe I was doing something wrong though...
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
What did you wipe after TWRP booting from stock? (Cache, System, Data?)
I just did the wipe without changing any settings. I believe that includes cache, system, and data.
Sent from my Pixel using Tapatalk
A default wipe is just cache i think
I was able to update to the June build with no issue from the full image without losing data and was able to keep TWRP, install ElementalX, and Magisk with no issues. Followed https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347 (just replacing XL files with non-xl equiv)
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
mateuxi said:
I has a pretty big problem of that Crash Dump screen some hours ago and i still can't get to fix it. Here is the story, after trying Havoc 2.0 rom i decided to go back to stock so in TWRP i erased the system, cache (dalvik cache and cache), data and internal storage (i wiped internal storage because TWRP just couldn't decrypt it even though the passwd was correct), after that i flashed the stock OOS rom and the TWRP installer (all these being booted on twrp), but when i rebooted into recovery the twrp splash screen just froze there, so i tried to boot twrp through fastboot, but then the crash dump screen apeared, this post: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 said this was a way to recover from that problem so i tried it, it worked as far as booting into OOS is concerned, but when i try to boot into twrp through fastboot the crash dump screen keeps showing up.
Any ideas?
Click to expand...
Click to collapse
Use bluespark twrp not official
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
yldlj said:
Use bluespark twrp not official
Click to expand...
Click to collapse
akswap said:
ON rom 8.1 best is official twrp
on rom 9.0 best is blues park twrp
Click to expand...
Click to collapse
It worked!
Now i'm installing all my mods again.
Thanks!
UPDATE:
Nevermind, it boots into twrp, but it wont boot OOS, i already tried erasing all the partitions (system, data and cache) and installing OOS and bluspark TWRP.
It turns on, shows the bootloader unlocked screen and then it reboots back to twrp.
UPDATE 2:
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Fixed it by erasing all data on oneplus recovery, thanks again, my phone is back from the death (a quite unrooted one).
Click to expand...
Click to collapse
When u upgrade from os 8.1 to 9 .0 after flash install blues spark twrp.
When Downgrade 9.0 to 8.1 use official OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip
& flash official Twrp & Stable magisk only
for 8.1
1- must have a copy of Oxigen Fastboot ROM 8.1
2- Oxigen 8.1 rom ( Revovery) .zip
3- twrp-installer-enchilada-3.2.3-0zip & img file
for 9.0
4- twrp-3.2.3-x_blu_spark_v9.86_op6.zip & img file
5- magisk 16.7 beta & 17.1 Stable
6- official 9.0 Stable rom
7- tool all in One (PC)
Enjoy flashing
Hi guys,
I have made a bad decision in trying to clean install Lineage OS 17 and now my phone only goes to QUALCOMM CrashDump Mode or gets stuck in the TWRP splash screen.
I cannot even make it start in Fastboot mode.
What I did was:
- Install TWRP 3.3.1-4
- Wipe EVERYTHING from the advanced wipe option
- Sideload Lineage OS 17
- Reboot into recovery to discover that I had the OnePlus recovery back
- Install TWRP 3.3.1-4 again
- Reboot into recovery
- Install GApps
- Restart phone
- Get into infinite boot load of Lineage OS which after a couple of auto restart would take me to TWRP
- Panic
- Wipe EVERYTHING again
- By mistake sideload TWRP 3.3.1-4 instead of Lineage OS 17
- Reboot into recovery
- Get stuck in the splash screen of TWRP
- Reboot into Fastboot
- Get stuck in the OnePlus logo Fastboot Mode
- Somehow turned off the phone
Is there anyone that can help me please?
Flash fastboot stock ROMs
or
Use MSM Download Tool
Look here!
https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
What do you think about starting with reading the flashing instructions before you attempt flashing ROM's. That would've prevented all the troubles you are experiencing.
Mr.FREE_Bird said:
What do you think about starting with reading the flashing instructions before you attempt flashing ROM's. That would've prevented all the troubles you are experiencing.
Click to expand...
Click to collapse
I managed to reset the device following the guide linked above but I am not able to have a Custom ROM yet.
It doesn't look like there is any "official" guide as I've seen many and each of them gives different instructions!
Ultimately what I found (and tried with no success) is:
- Have the phone automatically update to stock (Oxygen OS 9.0.9) after the reset mentioned above
- Boot into TWRP 3.3.1-14
- Wipe => Format Data: "yes"
- Reboot into TWRP 3.3.1-14
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Wipe => Advanced Wipe => Data and Dalvik/ART Cache
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash OpenGApps arm64 10
- Reboot to system
After this the phone automatically boots into Fastboot Mode, there is no way to make it try and load the OS.
If you have any better guide, can you please tell me where I can find it?
Thanks
NamingIT said:
I managed to reset the device following the guide linked above but I am not able to have a Custom ROM yet.
It doesn't look like there is any "official" guide as I've seen many and each of them gives different instructions!
Ultimately what I found (and tried with no success) is:
- Have the phone automatically update to stock (Oxygen OS 9.0.9) after the reset mentioned above
- Boot into TWRP 3.3.1-14
- Wipe => Format Data: "yes"
- Reboot into TWRP 3.3.1-14
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Wipe => Advanced Wipe => Data and Dalvik/ART Cache
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash OpenGApps arm64 10
- Reboot to system
After this the phone automatically boots into Fastboot Mode, there is no way to make it try and load the OS.
If you have any better guide, can you please tell me where I can find it?
Thanks
Click to expand...
Click to collapse
Hold on, what exactly do you want to achieve?
You want to flash LineageOS 17.0 right? I see, just like your first attempt, a couple of things going wrong.
This should work.
● Backup all your data.
● Make sure you have the latest OOS Pie Stable installed on both A and B slots.
● Download the latest LineageOS 17.0 build and Gapps for Android 10.
● Boot to TWRP.
● Wipe data and dalvik cache.
● Flash the ROM zip followed by the TWRP installer zip.
● Reboot to recovery.
● Flash Gapps (if you need Google Services etc).
● Reboot to system.
● Go trough the setup and after that you can reboot to TWRP again to flash Magisk if you need root.
This should work. :good:
Mr.FREE_Bird said:
Hold on, what exactly do you want to achieve?
You want to flash LineageOS 17.0 right? I see, just like your first attempt, a couple of things going wrong.
This should work.
● Backup all your data.
● Make sure you have the latest OOS Pie Stable installed on both A and B slots.
● Download the latest LineageOS 17.0 build and Gapps for Android 10.
● Boot to TWRP.
● Wipe data and dalvik cache.
● Flash the ROM zip followed by the TWRP installer zip.
● Reboot to recovery.
● Flash Gapps (if you need Google Services etc).
● Reboot to system.
● Go trough the setup and after that you can reboot to TWRP again to flash Magisk if you need root.
This should work. :good:
Click to expand...
Click to collapse
I have done exactly what you said. This time I was able to make the Lineage OS load but shortly after it gave me an error saying that "Android Setup keeps stopping" without that the wizard even starts.
I read online that in some cases you need to do a minimal setup before installing the GApps so I will try like that.
Definitely I got 1 step further though, thanks!
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?
So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).
remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?
harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly
GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.
Hello,
I have Samsung J4 core (j410f) rooted with stock ROM.
I wanted to install a custom ROM and tried to flash lineage os 17.1 (unofficial). What i did is:
1. Flashed TWRP 3.1 using odin
2. Wiped every thing (Data, Cache, System)
3. Flashed lineage successfully
4. Rebooted the phone. But got straight to fastboot.
5. To fix this I flashed stock firmware and it booted normally.
I tried again with different versions of lineage, same result. Used other ROMs like havoc, again the same. Changed recovery with orangefox instead of twrp, no difference.
The thing is I can use custom recoveries with stock ROM without a problem. But I can't flash any ROM without resulting in fastboot. Can anyone help me here? Please??
Now, I know this forum is from a long time ago, but did you get any errors when installing LineageOS for the first time? (like E1001 or something)