+Galaxy F23 5g
twrp recovery built and working. But being replaced by stock recovery after booting to system.
Screenshots attached.
xda article: Galaxy F23 5g
code name: m23xq
pinakini said:
This is great news. May we expect custom rom in future.
Click to expand...
Click to collapse
Yes, once the recovery is ready without bugs. I have been busy recently and so no progress has been made yet.
Some pics of the recovery are attached.
Bugs to be fixed:
1) After booting to recovery the touch starts responding only after approx 1 minute.
2) If you lock the screen in recovery the recovery stops eesponding to touch.
3) Cannot mount system partition. So problem with flashing roms.
4) Stop automatic replacement of twrp with stock recovery after boot to system.
Can you upload the sources and device tree so that someone else can continue the work on it ?
xdadev2022 said:
Yes, once the recovery is ready without bugs. I have been busy recently and so no progress has been made yet.
Some pics of the recovery are attached.
Bugs to be fixed:
1) After booting to recovery the touch starts responding only after approx 1 minute.
2) If you lock the screen in recovery the recovery stops eesponding to touch.
3) Cannot mount system partition. So problem with flashing roms.
4) Stop automatic replacement of twrp with stock recovery after boot to system.
Click to expand...
Click to collapse
How long is it going to take to build it though? My phone's practically dead after Android 13 update... Wishing to get TWRP...
Kim Jae Ha said:
How long is it going to take to build it though? My phone's practically dead after Android 13 update... Wishing to get TWRP...
Click to expand...
Click to collapse
Why is your phone dead after Android 13 update ? Works fine for me.
I've been facing several bugs... Like half side of screen not working if unlocked with fingerprint... A lot of lag... Bluetooth disconnecting at random times and wifi not connected randomly... Plus I want to flash a Custom Rom or GSI on it... So I need TWRP...
Please make a build... I'll be very thankful to you...
....
xdadev2022 said:
Yes, once the recovery is ready without bugs. I have been busy recently and so no progress has been made yet.
Some pics of the recovery are attached.
Bugs to be fixed:
1) After booting to recovery the touch starts responding only after approx 1 minute.
2) If you lock the screen in recovery the recovery stops eesponding to touch.
3) Cannot mount system partition. So problem with flashing roms.
4) Stop automatic replacement of twrp with stock recovery after boot to system.
Click to expand...
Click to collapse
How can i get this recovery for My Samsung F23 5G.
Related
OK, I know this is a problem that many before had and I've researched the subject thoroughly. But I've only found ways to recover your phone from the soft-brick (one of those fake rubber bricks used in movies:laugh status which was something I did by myself by flashing a stock recovery via odin.
Now my problem is a different one: I have updated my s6 to stock 6.0.1 and all went fine. I then rooted the phone by installing SpaceX kernel and went on to flash recovery via odin. That is when the problem occurred and I've not been able to solve it. I tried flashing also via flashify but with the same result, i.e. phone frozen at the samsung galaxy s6 screen with the damn "recovery is not ......".
What could I try? Anyone knows how to circumvent this issue?
Thanks for any help.
Luca
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
DJPops said:
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
Click to expand...
Click to collapse
Thanks: I will try that right away and report back here. Is the procedure of rebooting and shutting down the phone permanent or is it just the 1st boot (I sense it is a permanent thing, but I hope it isn't). If, later on I flash a custom rom and then re-flash the recovery, will this thing go away?
Why is this seandroid thing happening? Are you able to explain it to me?
It's not permanent
Just the first boot. "It erase a boot script that say to your device to boot into recovery" (small explanation, it's not exactly that).
This happen sometimes when you try to update the Su binary via the SuperSU app (it try to reboot the device into recovery, but sometimes it doesn't work and the device is "stuck" on the recovery)
This message shows up on every boot if you have a custom kernel, and if you boot on recovery, it will maybe shows up (depend of your recovery).
It was stucking on this screen because the recovery that you tried to flash is not compatible with marshmallow bootloader. The link in my first answer is a working marshmallow TWRP, for S6 (not S6 edge/+).
DJPops said:
Just flash this TWRP http://www.mediafire.com/?16c1zxj8gdz3mj4 (AP in Odin with F. Reset Time and Auto Reboot checked), it will boot automatically to recovery,
You will have a working recovery, but it can't reboot or shutdown the phone.
For that, click to "Advanced", "Terminal", and when the keyboard shows up, just type "reboot" or "halt"(without the ") et click on "enter".
Reboot: reboots the phone (the phone will reboot in system)
Halt: shutdown the phone
Click to expand...
Click to collapse
Woohoo! It worked! I have a custom recovery, although i have to reboot the phone with a crank
Thanks a lot. Now I'm gonna go on messing it up some more!
DJPops said:
It's not permanent
Just the first boot. "It erase a boot script that say to your device to boot into recovery" (small explanation, it's not exactly that).
This happen sometimes when you try to update the Su binary via the SuperSU app (it try to reboot the device into recovery, but sometimes it doesn't work and the device is "stuck" on the recovery)
This message shows up on every boot if you have a custom kernel, and if you boot on recovery, it will maybe shows up (depend of your recovery).
It was stucking on this screen because the recovery that you tried to flash is not compatible with marshmallow bootloader. The link in my first answer is a working marshmallow TWRP, for S6 (not S6 edge/+).
Click to expand...
Click to collapse
Alas, it seems that it is permanent! It doesn't reboot into anything (neither system nor recovery. Haven't tried download, but I assume it would be the same thing). Furthermore it gets stuck and needs to be rebooted by pressing voldown and power. then it turns on into recovery again. It is a small price to pay, so no worries, but I always like to understand why things happen!
Could I have done another mistake?
Out of interest what random recovery did you give him? lol
Try arter97s mod of twrp 3.0.0-0
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Seems to be the best working mod of latest twrp at the moment. No issues booting etc, just no USB otg support currently.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Out of interest what random recovery did you give him? lol
Try arter97s mod of twrp 3.0.0-0
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/
Seems to be the best working mod of latest twrp at the moment. No issues booting etc, just no USB otg support currently.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Oh yes!! This one really works all the way, reboot and all. However, af as you know, is there any of the previous version of TWRP that "agrees" with M bootloader?
Thanks mate
Luca
ManhIT modded recovery not a random recovery you know :mrgreen:
Haha, I was just wondering since it was just a mediafire link saying flash this.
Glad that arters recovery worked a bit better for you.
Recovery's are a bit hit and miss at the moment. That's the best one I've found so far.
I still haven't even got marshmallow, still rocking the latest lollipop which suffers similar problems.
Sent from my SM-G920I using Tapatalk
Oh okay, I'm french and I found this link on a french forum...
I used this recovery on my 920F and apart the reboot, it's working perfectly !
Project Spectrum for F1 is released on the official oppo forum. This is a official rom based on Android M AOSP. It Does include some color os features:-
1. Screen-off Gestures:
Project Spectrum now supports double tap to wake up/turn off the screen, draw a circle to open the camera app and custom a gesture to open an application.
This feature is turned off by default, to use it please enable it in Settings -> Accessibility -> Screen-off gestures
After you've added a custom gesture to delete or modify it please swipe the item left
2. ColorOS Camera
The Camera app ported from ColorOS is supporting the following plugins: Beautify, Filters, Panorama, HDR, GIF, Double exposure and Expert Mode
3. ColorOS Photos
The Photos app is a simplified version from ColorOS with key features needed to work properly with the Camera App
4. Beautiful Wallpapers
We've carefully selected some beautiful wallpapers from ColorOS as preset wallpapers for you
5. OTA package support
For future Project Spectrum versions OTA package will be available along with the full wipe package.
This is still in Beta. F1 Project Spectrum V1.0i Beta released now. Please follow the below link for download and instruction:-
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46517&extra=
For any update and all oppo f1 official downloads follow this link:- http://community.oppo.com/en/forum.php?mod=oppo_category&fid=301
Project spectrum is a pure AOSP and it is safe to use as a daily driver but I am still waiting for CM13.
There is plenty of action here
https://github.com/CyanogenMod/android_device_oppo_f1f
Hope it will be released soon
Project Spectrum ended up bootlooping on my wife's F1. It also seems to have problems with Google Play services.
I'd just exercise a bit of caution if you're going to use this as a daily driver based on my experience.
Also has SD card detections issues, no matr how many tyms reinserted it stil wont detect
UPDATE: i had dis issue last month so i reverted back to color os , but todiah i again instaled spectrum and the SD card bug is gone, sd works fine now
mikeysteele said:
Project Spectrum ended up bootlooping on my wife's F1. It also seems to have problems with Google Play services.
I'd just exercise a bit of caution if you're going to use this as a daily driver based on my experience.
Click to expand...
Click to collapse
Can I ask how you fixed the boot loop issue? I picked up an F1 on Thursday from Optus and installed Spectrum, decided to return to ColorOS this morning, so followed instructions on Oppo website and downloaded the file etc. then when the phone attempted to install ColorOS, it started boot looping and the black screen where it shows the install process. I don't know what to do since it has been doing it for two hours now (boot loops to that screen each time is 'starts' itself again.
Local Optus store where I purchased the phone advised they cannot help me and referred me to OPPO, so I am sitting back at home with no idea what I should do (my phone has not been rooted or anything).
Thanks
o0xx0o said:
Can I ask how you fixed the boot loop issue? I picked up an F1 on Thursday from Optus and installed Spectrum, decided to return to ColorOS this morning, so followed instructions on Oppo website and downloaded the file etc. then when the phone attempted to install ColorOS, it started boot looping and the black screen where it shows the install process. I don't know what to do since it has been doing it for two hours now (boot loops to that screen each time is 'starts' itself again.
Local Optus store where I purchased the phone advised they cannot help me and referred me to OPPO, so I am sitting back at home with no idea what I should do (my phone has not been rooted or anything).
Thanks
Click to expand...
Click to collapse
I just did exactly what you attempted - flashed ColorOS back on. Mine is the optus variant too. Which version of ColorOS are you trying to flash?
mikeysteele said:
I just did exactly what you attempted - flashed ColorOS back on. Mine is the optus variant too. Which version of ColorOS are you trying to flash?
Click to expand...
Click to collapse
It was the latest version from the link that Ricky supplied in the OPPO forum. I cannot do anything with the phone. It just brings up the message on the screen each time the phone is turned on:
Updating, please wait
Don’t uninstall the battery or do other operations!
Estimated time remaining is 3 minutes
I have spoke to OPPO Australia (very unhelpful) who advised that I need to plug the phone into the computer and turn it on (which I did) and it still does the same thing. The consultant has referred me back to OPTUS to send the phone off for warranty. I've had the phone less than 48 hours.
Sorry to hear that man. I'm not sure what that could be. Have you made sure the download wasn't corrupted by comparing the MD5?
mikeysteele said:
Sorry to hear that man. I'm not sure what that could be. Have you made sure the download wasn't corrupted by comparing the MD5?
Click to expand...
Click to collapse
As instructed by OPPO technical support, I went to the Optus store who advised that they will send it off next week for assessment by their technicians.
Does it work for F1 Plus or just normal F1??
my phone is f1f unlocked TWRP recovery
I installed this rom all working fine .. but I lost recovery
now i can't install any roms
and i can't install any recovery
i had the same issue. After flashing the spectrum beta I decided to go back to stock. then when I flashed the file that was given by that Ricky guy my phone started to bootloop then. i tried a file which I downloaded from the oppo website it wont flash its saying that my system has been modified. install failed. i think that Ricky guy wants us to be stuck with the firmware he made so when we want to go back to stock colorOS he will ask for money.
I ask you how to restore the official original android 5.1.1 because my current recovery model is twmp 3.0.2.0
help with recovery
I have f1f and i flashed official project spectrum. I wanted to root my phone and i tryed to flash twrp and it didnt work and i soft bricked my phone so i have no recovery. So i had to get the boot.img and use fast boot to unbrick my phone. Now i turn my phone on by vol down and power. I have no recovery.
I need help getting stock recovery back because customs recoverys dont exist for project spectrum. Help please
Jamie_oppo said:
I have f1f and i flashed official project spectrum. I wanted to root my phone and i tryed to flash twrp and it didnt work and i soft bricked my phone so i have no recovery. So i had to get the boot.img and use fast boot to unbrick my phone. Now i turn my phone on by vol down and power. I have no recovery.
I need help getting stock recovery back because customs recoverys dont exist for project spectrum. Help please
Click to expand...
Click to collapse
Open the project spectrum update zip with 7zip(or similar) and drag and drop the recovery.img from project spectrum into your fastboot folder them put your phone into fastboot mode and connect to pc. Open fastboot folder in cmd line and type fastboot flash recovery recovery.img (if recovery .img name is wrong then replace with correct name). This should put back project spectrum recovery so you can flash back to official colouros from there.
If this doesn't work I suppose I could right a fastboot script that will flash back to colouros.
MiniBlu said:
Open the project spectrum update zip with 7zip(or similar) and drag and drop the recovery.img from project spectrum into your fastboot folder them put your phone into fastboot mode and connect to pc. Open fastboot folder in cmd line and type fastboot flash recovery recovery.img (if recovery .img name is wrong then replace with correct name). This should put back project spectrum recovery so you can flash back to official colouros from there.
If this doesn't work I suppose I could right a fastboot script that will flash back to colouros.
Click to expand...
Click to collapse
i did what you said. These are all the img in project spectrum. recovery.img, recovery_4_4, recovery_4_3 , reserve 4 img and boot.img. so i tryed using fastboot for all of them. None of the recovery ones give back my recovery it just bricks my phone and cant turn on. So i then have to do fastboot flash recovery boot.img and my phone turns on. So i cant get my recovery back and i have to flash boot.img just to turn in on and from then on i have to hold vol down and power to turn phone on . for some reason recovery.img does nothing just bricks phone
may i ask that why am i not able to flash back to stock ROM for f1f using the same stock recovery?? and now i am even not able to connect my phone through adb! can somebody help me
help with recovery
droid man said:
may i ask that why am i not able to flash back to stock ROM for f1f using the same stock recovery?? and now i am even not able to connect my phone through adb! can somebody help me
Click to expand...
Click to collapse
If u can see the image thats whats in project spectrum. boot.img reserve4.img and when i try to get my recovery ( because atm i dont have a recovery) i use fastboot flash recovery reserve4.img and it says remote size to large. can any1 please help and try and get my stock recovery back please
Can it root?
Can it root?
CAN SOMEONE PLEASE MAKE A RECOVERY FOR PROJECT SPECTRUM. BECAUSE THE TWRP FOR F1F IS FOR 5.1.1 AND WE CANT FLASH IT. I DONT KNOW HOE TO MAKE RECOVERIES BECAUSE IM A BEGINNER. many people have no recovery because they tried to flash twrp after the flash to spectrum. This would solve soooo many peoples problems
I'm trying to load TWRP or any custom recovery on my above mentioned tablet but i'm just not able to load it. nor even boots normally. Only ODIN mode.
when i try recovery boot, a screen saying 'TEAMWIN' will appear shortly but soon closes and 'Samsung Galaxy Note 10.1' bootscreen comes up. I can only access ODIN(Download) mode and even tried to flash different custom recovery files and it says Passed but still again getting the same TeamWin screen loading in recovery mode and crashes in the middle and then bootloop happens.
Not sure whats the problem.
PLS Help !
Wrong TWRP installed as a guess .
JJEgan said:
Wrong TWRP installed as a guess .
Click to expand...
Click to collapse
so, how can i solve this prob? pls help with detailed steps
Sorry you will have to read for yourself.
Sent from my SM-G935F using XDA-Developers mobile app
I was having issues at first.
Maybe give this a try and see if it works for you.
I had to install CWM via odin, and wait a good while for the "pass."
Then I had to make sure not to let it reboot on its own.
I powered off manually, and then booted into recovery like this:
1. Volume down and power on at the same time.
2. Immediate release power when you see anything pop up, but continue holding volume down.
3. Release vol down when you see the teamwin logo.
That got me passed the part where it would automatically bypass TWRP.
I then used the toolbox to do the rest including the "fix."
I had to manually boot into TWRP at first, even with the toolbox, but that was the issue I had, and how I got around it.
Philz Recovery works.
Sent from my SM-G935F using XDA-Developers mobile app
bladebarrier said:
I was having issues at first.
Maybe give this a try and see if it works for you.
I had to install CWM via odin, and wait a good while for the "pass."
Then I had to make sure not to let it reboot on its own.
I powered off manually, and then booted into recovery like this:
1. Volume down and power on at the same time.
2. Immediate release power when you see anything pop up, but continue holding volume down.
3. Release vol down when you see the teamwin logo.
That got me passed the part where it would automatically bypass TWRP.
I then used the toolbox to do the rest including the "fix."
I had to manually boot into TWRP at first, even with the toolbox, but that was the issue I had, and how I got around it.
Click to expand...
Click to collapse
thanx, but not working for me here.
i tried installing cwm thru odin n it passed.
but again getting the same old teamwin screen when trying for recovery mode.
even normal mode leads to boot struck with cyanogen logo
JJEgan said:
Philz Recovery works.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
not working either
JJEgan said:
Wrong TWRP installed as a guess .
Click to expand...
Click to collapse
same problem no one can reply
REPLY
Its all answered .
JJEgan said:
REPLY
Its all answered .
Click to expand...
Click to collapse
Probably, but that doesn't mean the issue was ever solved.
I'm having the EXACT same issue as OP... All of a sudden I got bootloop when starting the tablet normally, going to recovery only shows TeamWin logo briefly and tablet reboots, and download mode works (Odin detects the tablet) but it always says "DOWNLOADING... Do not turn off target.".
Already tried installing stock rom, Philz recovery, CWM Recovery, EFS Repair... Nothing worked.
marianito10 said:
Probably, but that doesn't mean the issue was ever solved.
I'm having the EXACT same issue as OP... All of a sudden I got bootloop when starting the tablet normally, going to recovery only shows TeamWin logo briefly and tablet reboots, and download mode works (Odin detects the tablet) but it always says "DOWNLOADING... Do not turn off target.".
Already tried installing stock rom, Philz recovery, CWM Recovery, EFS Repair... Nothing worked.
Click to expand...
Click to collapse
If the TWRP screen is still there after you've flashed for example the stock ROM, than it's clear that your eMMC is locked.
In this case it need's to get replaced, I'm doing this weekly, so this problem is to solve.
Here is a beta working TWRP for V60.
Do NOT flash until you have a complete backup of your phone.
Flash at your own risk, you been warned
If and when you do flash it report back with bugs, what works what doesnt and what variant you used it on. helps with getting a better working recovery and fixing bugs
TWRP_LG_V60_BETA_2.0.img.7z
drive.google.com
tested on tmobile variant so far flashing and usb storage works, BUT backup system fails and does not reboot system. only reboots back to twrp, touch screen works on the first time use. If the screen times out and blacks out, you push on the power button to wake up the screen But the touch screen stops working. until the force reboot again. flashed stock abl_a and stock recovery but didnt go back to stock until you flash your stock boot.img.
blaze2051 said:
tested on tmobile variant so far flashing and usb storage works, BUT backup system fails and does not reboot system. only reboots back to twrp, touch screen works on the first time use. If the screen times out and blacks out, you push on the power button to wake up the screen But the touch screen stops working. until the force reboot again. flashed stock abl_a and stock recovery but didnt go back to stock until you flash your stock boot.img.
Click to expand...
Click to collapse
doesn't work with v60 ATT,boots in recovery ,but touch screen not working . (first attempt screen time was out ,but 2nd attempt booted in twrp while screen was on)
Karol75 said:
doesn't work with v60 ATT,boots in recovery ,but touch screen not working . (first attempt screen time was out ,but 2nd attempt booted in twrp while screen was on
Click to expand...
Click to collapse
So no touch screen functionality with att, got it thanks
i noticed that touch doesnt work if boot via commands touch only works with button combo
Could we get some info on where exactly to install this img to? Do we install to boot_a, boot_b or both?
MrHomebrew said:
Could we get some info on where exactly to install this img to? Do we install to boot_a, boot_b or both?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
And the version listed above is certainly not current. TWRP 3.6.0-11 can be found on TG. Hopefully you know your way around Qfil.
hooutoo said:
fastboot flash recovery recovery.img
And the version listed above is certainly not current. TWRP 3.6.0-11 can be found on TG. Hopefully you know your way around Qfil.
Click to expand...
Click to collapse
(update) never mind i took care of it
you should provide a link instead if thats the case
Hello.
My SM-G930F stock ROM was rooted with TWRP 3.3.1-0 from many years ago.
Until a few months ago i was facing somes freeze and reboot.
Now it's getting worse ,it freeze and reboot often (more than 5 times a day) and it freeze also at Samsung boot logo and need Download mode (Home + Volume down + Power) for power off but often still freeze at boot logo again.
In Download mode ,when i flash any others TWRP than 3.3.1.0 and reboot in Recovery ,it show the right flashed TWRP but in yellow mode (can do nothing , like freezed).
It only accept TWRP 3.3.1.0 but problems are same.
I flashed the whole latest stock ROM G930FXXU8ETI2 ,so loose TRWP but seems ok .
Now i flashed TWRP upper than 3.3.1.0 but still yellow mode, only 3.3.1.0 work but freeze come back.
I think NAND is corrupted in Recovery ,and when reading a particular part of it ,it freeze.
How test NAND?
Thank you for reading.
I am facing the same situation with my note FE. Until a few months ago I was using the same TWRP version on stock pie. The freeze then restart occasions started out of nowhere and the kept increasing, and now the phone is not usable. I was thinking of it being a hardware issue, because the restarts are still too frequent in stock pie without any modifications, so I might send it for repair.
I was told about this https://technastic.com/odin-nand-erase-samsung/, but didn't test it yet. Please let me know if you found any solution.
Hello.
roughlyadvanced said:
I was thinking of it being a hardware issue
Click to expand...
Click to collapse
I think too because when boot on official recovery it cannot reboot to system but still reboot to recovery...