Hi, I wrote it in ROM thread but here is maybe better.
I try to install custome ROM Omega 27.So I flashed stock ROM with android 5. Everythings works but now I wanted to flash custome recovery TWRP 2.8.7.0 for my LTE ROM and wanted to flash with Odin 3.09. And it didn't worked.
I browse twrp file to AP part in Odin and start to flash but it stops on beginning and nothing happens. I had to turn off Odin and tried it 5 times. Without success.
Pls. any suggestions?
Sorry , my bad, it was samsung drivers on computer.
Related
As per title, I'm trying to install a different recovery via Odin, and it seems to install it correctly but when I try to go into recovery it just reboots? I've tried twrp, and various cwm releases but they all do the same. Even the stock recovery now does it once I'd given up and installed that again? Anyone know what I'm doing wrong?
Turns out Odin 3.07 wasn't working properly, worked fine with 3.04 instead.
i've found Odin3 v1.85 to be very stable as well for flashing recoveries
Hello everybody,
I have a SM-G900F and i'm on Lollipop with ALEXNDR rom. Just tried to flash a zip with Mobile Odin and got stuck on rebooting recovery. It didnt flash anything. Now everytime it boot in Recovery and get stucked.
I read something about reflash stock recovery. So i got the recovery.tar like here described http://howto.highonandroid.com/sams...extract-stock-recovery-from-samsung-firmware/ from G900FXXU1ANE2 and tried to flash it with odin.
Now Im stucked on flashing the recovery because the blue progressbar doesn't move on. The flash finally has failed.
So i need yuor help! What to do know???
Should i flash the BL? Or can you point me to the right recovery?
BlackMonkey said:
Hello everybody,
I have a SM-G900F and i'm on Lollipop with ALEXNDR rom. Just tried to flash a zip with Mobile Odin and got stuck on rebooting recovery. It didnt flash anything. Now everytime it boot in Recovery and get stucked.
I read something about reflash stock recovery. So i got the recovery.tar like here described http://howto.highonandroid.com/sams...extract-stock-recovery-from-samsung-firmware/ from G900FXXU1ANE2 and tried to flash it with odin.
Now Im stucked on flashing the recovery because the blue progressbar doesn't move on. The flash finally has failed.
So i need yuor help! What to do know???
Should i flash the BL? Or can you point me to the right recovery?
Click to expand...
Click to collapse
Hello blackmonkey
Two years ago i used odin mobile on my sg3 i9300
After an zip on odin mobile i get an issue : phone dont boots i repaired this softbrick by installing Stock rom with odin pc :
You can check installed Samsung drivers
choice windows 7 or reinstall Os PC if it's old ....
Since that desinstalled Odin mobile and never used it
yanis488 said:
Hello blackmonkey
Two years ago i used odin mobile on my sg3 i9300
After an zip on odin mobile i get an issue : phone dont boots i repaired this softbrick by installing Stock rom with odin pc :
You can check installed Samsung drivers
choice windows 7 or reinstall Os PC if it's old ....
Since that desinstalled Odin mobile and never used it
Click to expand...
Click to collapse
@BlackMonkey It happened to me several times. What I had to do: flashed the stock ANE2 rom from sammobile (it allows to download for free, but it is slow). Flashed the BL and CP from ANE2 (I don't remember where I found it but it was on google. Actually, you should try the next step first, as I am not sure that it is required). Rebooted in recovery mode. Wiped cache. Rebooted. Root with towelroot. Install mobile odin. Flashed rom with option everroot. And you got lollipop in knox 0x0. Once in lollipop, mobile odin as failed each time for me, the same as you describe. It could be an issue with rom that use AROMA which are not supported. I had to use flashfire which works great.
ps : i did that as I wanted to keep knox 0x0. If you don't, you should install TWRP.
alexbelgium said:
It happened to me several times. What I had to do: flashed the stock ANE2 rom from sammobile (it allows to download for free, but it is slow). Flashed the BL and CP from ANE2 (I don't remember where I found it but it was on google. Actually, you should try the next step first, as I am not sure that it is required). Rebooted in recovery mode. Wiped cache. Rebooted. Root with towelroot. Install mobile odin. Flashed rom with option everroot. And you got lollipop in knox 0x0. Once in lollipop, mobile odin as failed each time for me, the same as you describe. It could be an issue with rom that use AROMA which are not supported. I had to use flashfire which works great.
ps : i did that as I wanted to keep knox 0x0. If you don't, you should install TWRP.
Click to expand...
Click to collapse
Thank you for your answer. I alredy did exactly this because i wanted to use again my phone and didnt see other solution. I hoped for a solution without a factory reset but it was necessary. Lost some picture and messages and have work for some hours So at that point be warned:
DON'T USE MOBILE ODIN WITH LOLLIPOP!!!
The problem is MOP doesn't support Lollipop.
So if u want to save data flash via odin the same rom but stock.
Hi,
I had several problems with custom rom, so I went back to stock ROM (latest MOB version) to start everything new.
Now I got the problem that it is not possible to flash CWM or TWRP again (tried different versions to flash with odin). I also tried to get back to UHOL2 bootloader and modem, bootloader is now UHOL2 but also custom recovery not working.
Any ideas how to get TWRP working again?
Thx
Jürgen
Can you root it?
Then you might be able to use flashify to flash the recovery.img
xdajuecat said:
Hi,
I had several problems with custom rom, so I went back to stock ROM (latest MOB version) to start everything new.
Now I got the problem that it is not possible to flash CWM or TWRP again (tried different versions to flash with odin). I also tried to get back to UHOL2 bootloader and modem, bootloader is now UHOL2 but also custom recovery not working.
Any ideas how to get TWRP working again?
Thx
Jürgen
Click to expand...
Click to collapse
Uncheck auto-reboot before flashing TWRP trough Odin.
used CF Auto root - Phone Info says that root is working
which recovery.img should I try - CWM or TWRP doesn't matter for me
TWRP. CWM is outdated.
Uncheck auto-reboot before flashing TWRP trough Odin and removing battery was the solution!
Thx
Selecting auto reboot after flashing twrp causes the stock recovery to overwrite twrp and this is why the phone should be booted into twrp right after flashing.
So I rooted my Samsung Galaxy J5 (SM-J500FN) by flashing CF-Autoroot with ODIN, and then I wanted to flash TRWP so I could install XPosed Framework.
After flashing TRWP with no errors on ODIN, if I try to reboot normally or in recovery the screen slowly turns green?
I managed to get into Download mode and connected to ODIN, but I cannot flash a new ROM as you cannot flash .zip files. (I have a LineageOS rom and my Stock ROM with build number J500FNXXU1BQA4)
up2 said:
So I rooted my Samsung Galaxy J5 (SM-J500FN) by flashing CF-Autoroot with ODIN, and then I wanted to flash TRWP so I could install XPosed Framework.
After flashing TRWP with no errors on ODIN, if I try to reboot normally or in recovery the screen slowly turns green?
I managed to get into Download mode and connected to ODIN, but I cannot flash a new ROM as you cannot flash .zip files. (I have a LineageOS rom and my Stock ROM with build number J500FNXXU1BQA4)
Click to expand...
Click to collapse
The screen turns green when you flash the wrong TWRP (not corresponding to your Android version) or when you flash Lollipop roms over Marshmallow and vice versa (except MM/N cm/aosp roms which must be flashed on LP).
You can flash only stock rom (.tar format file) with Odin.
TWRP for lollipop 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 .
TWRP for Marshmallow 6.0.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 .
Flash the correct TWRP according to your Android version. I believe you must reflash stock rom with Odin first since you're screen is turning on, but try to flash the correct TWRP first and see if you get rid of your problem. If not, then reflash stock rom and then flash TWRP again.
#Henkate said:
The screen turns green when you flash the wrong TWRP (not corresponding to your Android version) or when you flash Lollipop roms over Marshmallow and vice versa (except MM/N cm/aosp roms which must be flashed on LP).
You can flash only stock rom (.tar format file) with Odin.
TWRP for lollipop 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 .
TWRP for Marshmallow 6.0.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 .
Flash the correct TWRP according to your Android version. I believe you must reflash stock rom with Odin first since you're screen is turning on, but try to flash the correct TWRP first and see if you get rid of your problem. If not, then reflash stock rom and then flash TWRP again.
Click to expand...
Click to collapse
Wow, thanks a lot.
The thread where I got the TWRP from didn't show that it was for 5.1.1, I flashed TRWP for 6.0.1 and my phone worked again and the TWRP works!
Thanks!!
Hey guys. I'm trying to update my TWRP recovery but now I get the yellow triangle when to put the phone into recovery and lock icon before booting. I'm currently running 7.1.1 octos rom. The phone can boot fine but I don't have any working recovery right now. I tried using odin to flash several tar twrps but it constantly fails. I've used several cables too and 2 pc's to rule out connection problems but still the same. I'm out of ideas right now. I don't want to go flashing back to stock rom if I can get a working recovery thru odin. Thank you....
P.S. I tried to update my TWRP supposedly to 3.1. . . as it is preferred for flashing lineage oreo rom that's when my recovery goes bad.
Try reinstalling the TWRP that was working. It seems like the new TWRP isn't too compatible with our phones on the MDL bootloader. You might have to ODIN back to stock to fix it.