Hello,
I have a Samsung Galaxy S10e, and recently I've decided to flash a custom ROM on it.
I upgraded from Android 10 Stock Samsung to Android 11 LineageOS 18.1 following this and this guide.
All successful.
However, after some minutes, I wanted to try out a different ROM, so I installed Pixel Experience (which was based on Android 10 -- big mistake). This ended up resulting in a soft brick, throwing me an 'REV Check Fail Device 9 Binary 8' error everytime I turned on the device. I couldn't get into recovery mode - only download mode.
I managed to fix this by waiting for the Samsung's Stock Firmware (based on Android 11) to come out (did after some hours, I was so lucky I didn't have to wait that long) so I could flash it and go back to stock using Odin. All good, the phone boots, everything works as expected -- no problems what so ever.
I should've made a backup in TWRP, in case something went wrong before flashing Pixel Experience (?), but I didn't. I also should've known that I couldn't downgrade. Anyway...
When I enter download mode, the following important info is displayed:
PRODUCT NAME: SM-G970F
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF (U)
Secure Download: Enabled
WARRANTY VOID: 1 (0x0e03)
I believe my bootloader is unlocked, since it's enabled and grayed out in developer otions. I also believe that I have no custom recovery (since I flashed Samsung's Stock Firmware), because when I press the recovery button combination, it doesn't boot into TWRP.
My questions:
1. Should I repeat the process in here when flashing TWRP again since I literally flashed the samsung stock firmware? I'm guess I'm comming from "stock" even though I already have some steps complete? Should I flash the " multidisabler-samsung-2.* " too? I already did once, do I need to do it again since I flashed the Stock Samsung firmware?
2. Is there anything you'd recommend me doing to prevent stupid actions like I had above?
3. As long as I have the Stock Samsung Firmware and the phone boots into download mode, I'm good right?
4. Is TWRP 3.5.0 compatible with the S10e Android 11? Or does android versions not matter with recoveries?
5. Which ROM would you recommend to have a good Pixel-Like Stock Android experience? I'm debating wether I should use the PixelExperience again (I used it on my nexus 5x and was happy with it) or if I should try out something else. I also believe it's not yet available unofficially, so I'd have to wait.
6. Would you recommend me installing a GSI?
Thanks!
Questions updated
bump!
Too bad you didn't get an answer... Did you find anysolution ?
Having issues installing TWRP with odin on a s10e..
Related
Okay so here's the info to the best of my knowledge,
Phone Model : Moto G 3rd Gen (XT1550, dual sim, 2gb RAM, 16gb ROM, India)
Bootloader Status : Unlocked
Root Status : Rooted
Recovery : Stock
ROM : Stock ROM 5.1.1
I've been running the stock Recovery & ROM with high hopes of getting an official OTA Marshamallow update.
To truly customize the device to my liking I flashed the xposed framework (the arm version) , it worked fine and all the modules I installed worked perfectly.
I also had Device Control, Xposed Gels, and some other apps to bring my Stock ROM experience close to that of Cyanogen MOD.
When the OTA Marshmallow update started rolling in , I was unable to install the update even after successfully downloading the file numerous times. But i was so comfortable with my device and all the customization I had on my device that I decided to keep using my customized Stock ROM.
4 months later (now) the lack of a gyro in this device and my eagerness to get into VR headsets has left me with no choice but to sell it and get another phone. So i needed it in a sale worthy condition, without the customization and with the Marshmallow update installed.
I uninstalled the xposed framework and all the modules but was still unable to install the OTA update.
So i figured i'd install CyanogenMOD with TWRP custom recovery.
I have done this for quiet a lot of my friends and am fairly used to the steps involved. I use the " minimalADB fastboot " kit and my device on fastboot to flash recovery. For some reason i was not able to flash the lastest TWRP image (twrp-osprey-3.0.0-r2.img ) for the device nor was i able to boot from it :crying:. The fastboot command prompt on my PC would show success but the devices would not restart into the custom recovery like it is supposed to, but the device would stay at the fastboot mode and kept restarting everytime i selected the recovery mode option.
I had an older image (twrp-osprey-2.8.7-r3.img ) which i couldn't flash either but i was able to boot into TWRP with this image. From here i tried installing the latest CM12.1 nightly available (cm-12.1-20160227-NIGHTLY-osprey.zip) as soon as i swiped the device would just reboot, i tried this numerous times and with other nightly builds as well.
In haste and frustration i wiped the cache/dalvik , internal storage and system through TWRP , thinking that changes made in the quest of customizing my device were causing this hindrance. I had no OS now. I went over trying to flash TWRP and CM12.1 many times again with the same issues.
I came about a thread on How to " Fastboot Flash Moto G (3rd Gen) Factory Firmware Images " (http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750) & used this firmware image " Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7 ". Still no progress.
The bootloader unlocked warning has come back (i flashed a stock MOTO logo there earlier) which keeps flashing on my screen again and again , no booting into OS or anything else. Not even an error. As if there is no OS installed.
I have gone about the procedure in the above thread a couple of times, with no success and the same problem.
Is there any reason why i'm unable to flash a custom recovery or ROM ??? What am i missing???
Please help i'm stuck, pulling my hair out with no phone and completely frustrated.
Thanks in advance.
Did you check your build no for stock ROM?
samirza692 said:
Did you check your build no for stock ROM?
Click to expand...
Click to collapse
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
ashrith.s said:
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
Click to expand...
Click to collapse
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
samirza692 said:
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
Click to expand...
Click to collapse
the link provided is the exact same link from where I flashed a stock rom before.
build number for stock rom??? am i missing something???
all i see is the model variant (xt1550 is my phone)
RAM specification (mine is 2gb)
and the region (mine is retails asia | india )
so i went with the following firmware
Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7
where does the build number come into the equation???
Please lemme know if im doing something wrong. Thanks for the replies.
So I've successfully flashed twrp-osprey-2.8.7-r3.img to my device and I've been able to boot into twrp. The touchscreen doesn't seem to respond though. It asks to swipe to begin and I'm stuck again.
I had the screen replaced a couple of days ago.
Could it be a faulty screen or a software issue?
P.S. I have not been able to flash any version of twrp after the above mentioned version (v 3.0.0 is the latest stable version) but the ones prior are flashable.
Hey, contact me via PM and il do my best to help you in this.
therealduff1 said:
Hey, contact me via PM and il do my best to help you in this.
Click to expand...
Click to collapse
Is not big issue
Is it still possible to boot back into the OS? If it is, check if you have OEM unlocking enabled, since you're on stock ROM, it might be gotten unchecked after unlocking your bootloader because that's what happened with me. If you do t wether or not that was checked, you're at a dead end and there's nothing you can do. You can try paying someone to fix it, i.e., Motorola.
Hey guys,
Hopefully someone can help me with my problem. So i did the following:
To get rid of the 7 day Block of oem-unlocking on my s8+ i downgraded back to Nougat. From here on I flashed TWRP + rooted my device with magisk. After That i flashed the RENOVATE_ICE_G95X-7.5 rom + the Flashable_G95xF_FD_Firmware_TWRP_AQL5_r8 Firmware. I've let my Phone start up and went back to TWRP To Update the rom to RENOVATE_ICE_G95X-10.1. To this point everything Worked fine, the Phone Boots completely fine. Now to my problem: im Sitting on the actual stable rom but with the Baseband-version of Nougat which is AQL5. When i try to Flash the actual Firmware (CRC7 or CRD7) via TWRP my Phone gets stuck on the first Samsung Logo and Shows the following red Message: "Only official released binaries are allowed to be flashed". I would be glad for any help.
If you can find a standalone modem file from the ROM you mentioned you should be able to flash it in TWRP recovery. Last time I did this was on a Note 3. I think that the process should be the same with S8.
Can't seem to find one, but i found out that the same error occurs when installing other custom-roms like the King Oreo Rom which installs the newest Bootloader and Modem via Aroma installer. Only solution after that is to Flash Nougat again via Odin.
I came from android nougat on my galaxy s8+, however, I wanted to update to oreo, so I flashed it through odin with all the necessary firmware files. I configured it all once after. However, OEM Unlock is missing from the developer options. I've read that you have to wait 7 days for it to appear but I don't have the time to wait as I have some projects to deal with. I'm wondering if I can dirty flash an old rom over stock rom to enable oem unlock through odin since I can't flash through twrp . Once I get the regular rom loaded, I'm going to flash twrp and find a custom rom based off oreo instead. Would be great if someone knows any work around for this.
TheFinalHawk said:
I came from android nougat on my galaxy s8+, however, I wanted to update to oreo, so I flashed it through odin with all the necessary firmware files. I configured it all once after. However, OEM Unlock is missing from the developer options. I've read that you have to wait 7 days for it to appear but I don't have the time to wait as I have some projects to deal with. I'm wondering if I can dirty flash an old rom over stock rom to enable oem unlock through odin since I can't flash through twrp . Once I get the regular rom loaded, I'm going to flash twrp and find a custom rom based off oreo instead. Would be great if someone knows any work around for this.
Click to expand...
Click to collapse
Did you get a valid answer? Tx
I tried to follow these instructions: https://www.xda-developers.com/t-mobile-oneplus-7-pro-root-tutorial/
I first flashed the phone to the international firmware and then installed the devleoper preview which allowed me to unlock the bootloader.
I then updated the developer preview to a beta version of oxygen os 10 which made it possible for me to use the fastboot mode in order to load the twrp and then install it with sideload
I then tried a few custom roms such as havoc os.
Unfortunately at that point I get kind of stuck because there is no service, which is strange considering that the article claims that the service would become available during a custom rom install.
After flashing the phone back to the international firmware the service works again.
I am not exactly sure what I am doing wrong.
Basically the main issue has to do with the fact that there is no service as the developer preview trick starts and me not getting it back until I flash back the international firmware which has the bootloader locked and has no custom recovery.
The main reason why I wanted to do all of this is to simply have root.
The solution ended up consisting of reinstalling the stock oxygen os with the TWRP recovery AFTER the whole unlocking thing was finished, at which point it should either be possible to jailbreak the oxygen or to install a custom rom.
Either way the service seems to be back.
If you ever encounter such an issue it's possible that reflashing the stock os with TWRP may fix it.
Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?
OEM unlock toggle in Developer's Options
Hi ยก...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers