Related
Q&A for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][nozomi] TWRP 2.8.5.0 touch recovery [2015-02-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
locked bootloader
m1st3r1 said:
for cwm, there is cwm (and twrp also) for locked bootloader, but it cant flash any kernel (due to locked bootloader). in summary you stuck with stock kernel (that can only be flashed with flashtool or similar tools (if any ) with locked bootloader.
Click to expand...
Click to collapse
Sorry, I'm a bit beginner...
Does this mean that
1. if I use the procedure on page http://teamw.in/project/twrp2/144 in section Download - Stock Kernel:
2. then I can install any ROMs? For example this one? http://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516
?
Mickey8881 said:
Sorry, I'm a bit beginner...
Does this mean that
1. if I use the procedure on page http://teamw.in/project/twrp2/144 in section Download - Stock Kernel:
2. then I can install any ROMs? For example this one? http://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516
?
Click to expand...
Click to collapse
Flashing TWRP would require unlocked bootloader. First unlock Your bootloader, then follow the procedure from here.
From Your other post, it turns out You cannot unlock bootloader, so You can flash only sock based ROM's which work on Stock kernel.
Why is there no version 2.8.6.0 for Xperia S?
Hello guys,
I'm just download and install TWRP manager from google play and i'm trying to install the recovery. I'm choosing device name as LT26i but no recovery file is detected.
If i choose device name as "nozomi" i can find everything but my original device name is LT26i.
What to do? Are you suggest to try with nozomi and install the recovery?
Captainlag said:
Hello guys,
I'm just download and install TWRP manager from google play and i'm trying to install the recovery. I'm choosing device name as LT26i but no recovery file is detected.
If i choose device name as "nozomi" i can find everything but my original device name is LT26i.
What to do? Are you suggest to try with nozomi and install the recovery?
Click to expand...
Click to collapse
Nozomi is the code name for LT26i/LT26ii, so You can use it with no problems.
Unable to recovery
I can't flash any recovery file !!!
While I'm trying to install it returns this:
Something is wrong
------------------------
Flashing recovery was
unsuccessful.Either you already
have this recovery installed or
another error has occured.Would
you like to attempt rebooting to
recovery now?
NO YES
Captainlag said:
I can't flash any recovery file !!!
While I'm trying to install it returns this:
Something is wrong
------------------------
Flashing recovery was
unsuccessful.Either you already
have this recovery installed or
another error has occured.Would
you like to attempt rebooting to
recovery now?
NO YES
Click to expand...
Click to collapse
Which method are You following? Try the method from here.
Thank you for your help Mirhawk, but it doesn't work
Captainlag said:
Thank you for your help Mirhawk, but it doesn't work
Click to expand...
Click to collapse
What error are You getting?
Mirhawk said:
What error are You getting?
Click to expand...
Click to collapse
There is no error but I'm trying to reboot in recovery mode and it's immpossible
Captainlag said:
There is no error but I'm trying to reboot in recovery mode and it's immpossible
Click to expand...
Click to collapse
Hope You are pressing volume up button 2-3 times when Sony appears while booting the phone. Also, what ROM are You on?
Mirhawk said:
Hope You are pressing volume up button 2-3 times when Sony appears while booting the phone. Also, what ROM are You on?
Click to expand...
Click to collapse
Of course I'm pressing volume up button 2-3 times ....
My phone is on 6.2.B.1.96 stock with unlocked bootloader
Captainlag said:
Of course I'm pressing volume up button 2-3 times ....
My phone is on 6.2.B.1.96 stock with unlocked bootloader
Click to expand...
Click to collapse
I just wanted to clarify the first point since I have come across some people who didn't follow correct procedure. Glad You are doing it properly.
Ah yes, that is the problem. This method doesn't work on stock firmwares. Use the method from here to get recovery.
Mirhawk said:
I just wanted to clarify the first point since I have come across some people who didn't follow correct procedure. Glad You are doing it properly.
Ah yes, that is the problem. This method doesn't work on stock firmwares. Use the method from here to get recovery.
Click to expand...
Click to collapse
I suppose that i have to follow "method 2", right?
And what to do with the .zip file?
Captainlag said:
I suppose that i have to follow "method 2", right?
And what to do with the .zip file?
Click to expand...
Click to collapse
Method 1. You need recovery for method 2. If You have unlocked bootloader, You can simply flash the DoomKernel too. You can find it here. Use the blue "Download Now" button, and the file has .elf extension. You can flash it via flashtool, it consists of CWM and TWRP and works with stock ROM.
@Mirhawk: Many many thanks !!! :victory:
Finally , I have recovery with Doomkernel.
Thanks a lot and keep moding
I think I messed up my S
Hi
Trying to root my S and install nAOSProm I followed the instructions in the main thread. I successfully unlocked the bootloader and got the device rooted (SuperSU installed and updated in play store), but when attempting to use the TWRP manager to install TWRP I just got an error message that it wasn't successful. I then did this as I read earlier in this thread: fastboot flash boot 2.8.4.1.img. When I started the phone, it immediately boots into the TWRP but I can't get anywhere from there. Impossible to continue to the OS. When I connect it to the computer I just get an exclamation point in the device manager and I can't seem to find the correct drivers (I've installed the FlashTool Xperia Driver Pack). The phone worked perfectly in windows in both normal mode and fastboot previously. Since the phone doesn't have an external memory card, and since I can't transfer any files to it from Windows, I'm stuck in TWRP.
Is it bricked or can I get out of here?
nielsen81 said:
Hi
Trying to root my S and install nAOSProm I followed the instructions in the main thread. I successfully unlocked the bootloader and got the device rooted (SuperSU installed and updated in play store), but when attempting to use the TWRP manager to install TWRP I just got an error message that it wasn't successful. I then did this as I read earlier in this thread: fastboot flash boot 2.8.4.1.img. When I started the phone, it immediately boots into the TWRP but I can't get anywhere from there. Impossible to continue to the OS. When I connect it to the computer I just get an exclamation point in the device manager and I can't seem to find the correct drivers (I've installed the FlashTool Xperia Driver Pack). The phone worked perfectly in windows in both normal mode and fastboot previously. Since the phone doesn't have an external memory card, and since I can't transfer any files to it from Windows, I'm stuck in TWRP.
Is it bricked or can I get out of here?
Click to expand...
Click to collapse
Flash stock firmware ftf using flash mode in flashtool and then follow the instructions from here.
Or else:
Boot Your phone into recovery. Connect it to PC. Right click on the device in Device Manager, select update drivers, "browse my computer", then "let me pick from list" then select the driver similar to "Sony a0109 ADB drivers" (number may vary). Then You will be able connect to phone via adb. Then use following command to push the ROM and gapps to the phone internal memory:
Code:
adb push ROM.zip /sdcard/
adb push gapps.zip /sdcard/
This will copy the the ROM and gapps to phone which You can flash via recovery easily then.
worked perfectly! thanks for your time and help, much appreciated!
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.
edit on 2017 03 20
many thanks to lullca
i buy a new cable
reinstall drivers
install cfautoroot
now it's ok
odin 3.10.6 new usb drivers
my further messages are now obsolete
thanks to the community
hello guyes
smt-520 10.1 cyanogen 5.1
twrp 3.0
install twrp 3.1
then t-520 reboots continuously on samsung logo
i put the tablet in samsung loader mode ( power sound- home & sound+ )
odin can access the tablet ( green yellow tab ) but impossible to install older twrp
can someone help me to find loaderboot ...tar to use with odin
can someone help me in any way
regards
Reboot to Odin mode (vol down + home + power) and push TWRP 3.02 TAR file over USB.
https://dl.twrp.me/picassowifi/
hi thanks
but doe'nt work
regards
validatus said:
hi thanks
but doe'nt work
regards
Click to expand...
Click to collapse
Bite the Bullet, and restock, then start over.
Beyond all that, assuming you can get into TWRP.... Try flushing the Cache.
It's not a 100% fix 100% of the time, but that trick has been known to fix more then a fee Bootloader in its time.
Looks like I, too, bricked by SM-T520:
- had Resurrection Remix ROM installed;
- installed TWRP 3.1.0.0 a couple days ago, rebooted to system, worked fine.
Today, noticed a new RR build; downloaded and copied onto the tablet's SD card.
Tried to reboot into recovery.
Now it keeps rebooting to Samsung logo, there seems to be no way to turn it off.
Following an earlier suggestion here, I tried to use Odin, but the tablet is not visible in Odin.
Is there any way to at least turn it off? Or should I just wait for the battery to drain?
[Edit]
I was able to use Odin to push TWRP 3.0.2.0 to the device after switching to a different USB cable.
Wiped the device, re-flashed the latest RR ROM, Open GApps, and SuperSU.
The ROM has been trying to boot for a good 30 minutes now...
hello lullcat
thanks for your notice
what odin have yu used
perhaps a good thing to try another recovery
regards
validatus said:
hello lullcat
thanks for your notice
what odin have yu used
perhaps a good thing to try another recovery
regards
Click to expand...
Click to collapse
As I mentioned in my edited post, I have been able to push the previous TWRP version to the tablet, I just needed to use a different USB cable.
Odin version I used was possibly 3.02 - I searched for "Odin for SM-T520" and downloaded the first result.
hello lullcat
thanks
i tried a new cable: no effect
i think to an hardware brick
regards
Hi @ all,
same here, i had 'lineage-14.1-20170427-nightly-n2awifi-signed.zip' installed and running fine with TWRP 3.0.2,
then i upgraded first with the TWRP APP to v3.1.0.
After a reboot i got a bootloop on the Samsung Logo.
Then i tried to flash again in the 'download mode' with Heimdall under Linux, TWRP 3.1.0, still bootloop, and also with 3.0.2 bootloop.
What happen?
What can i try to flash in 'download mode' ?
Thanks in advance!
Greetings
@cocolocko
first message red part
regards
@validatus
i tried 3 different cabels, nothing worked! :crying:
regards
validatus said:
@cocolocko
first message red part
regards
Click to expand...
Click to collapse
twrp 3.1 bootloop fixed
I too updated twrp from 3.02 to 3.1 and ended with a bootloop.
Using Heimdall on macOS I extracted the pit table and then explicitly flashed the recovery partition with twrp 3.02 (the .IMG not the .tar file). Then I rebooted the tablet and it booted up as usual.
Just for completeness sake: I also tried JOdin3 to flash twrp, both 3.1 and 3.02(the .tar file). Every time the application said that the flashing worked but I was still seeing the bootloop. I don't think JOdin3 actually performed the flashing because it took only seconds whereas Heimdall took 1 minute but then it actually worked.
I'm on LineageOS 14.1 20170427. After fixing the bootloop I updated to the build from the 4'th May and I'm having fun with Jelly.
If needed I can share some more resources that I used, but basically I googled around for anything I needed.
Best of luck.
hello
a probem with recovery??
install an antic recovery: cmw with cfautoroot
then use the last odin to install twrp
regards
Solution
read from here:
https://forum.xda-developers.com/showthread.php?t=2679825&page=119
i found my solution: in post #1188
also new TWRP out !
Greetings
Здравствуйте нужна помощь
hello
twrp 3.1.0.1 ok
but very very slow
wait time: acces, boot
regards
Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
i cannot acces Download mode or recovery or boot the phone
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response
wolkengold said:
Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response
Click to expand...
Click to collapse
Can you boot to download mode? If you can, flash latest oreo.
iloveoreos said:
Can you boot to download mode? If you can, flash latest oreo.
Click to expand...
Click to collapse
no i cant... at least not with button combinations...
wolkengold said:
no i cant... at least not with button combinations...
Click to expand...
Click to collapse
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.
iloveoreos said:
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.
Click to expand...
Click to collapse
thanks, i will try if smart switch will help me.
wolkengold said:
thanks, i will try if smart switch will help me.
Click to expand...
Click to collapse
There is a small chance.
iloveoreos said:
There is a small chance.
Click to expand...
Click to collapse
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...
wolkengold said:
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...
Click to expand...
Click to collapse
Cool! Now what happens when you reboot to download mode from twrp?
SnowFuhrer said:
Cool! Now what happens when you reboot to download mode from twrp?
Click to expand...
Click to collapse
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.
SnowFuhrer said:
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.
Click to expand...
Click to collapse
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Flash stock firmware using Odin?
wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.
SnowFuhrer said:
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.
Click to expand...
Click to collapse
sorry for the late response. You were right, i accidentally downloaded an older oreo release and thats why i could not flash it. I now downloaded the newest stock rom from updato.com and it worked perfect.
Thanks for your support
wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked
jack364030 said:
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked
Click to expand...
Click to collapse
You are correct but...He sorted this 4 months ago.
Hello Friends!
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first.
Then it got all messed up -- you can read about the issues I was having at the end of this post.
Fortunately, the phone works again with the stock ROM after reflashing the BL/AP/CP/CSC files using Odin!
Now I am trying to figure out the best method for rooting with Magisk and installing TWRP or CWM. (if that is needed)
Any suggestions? Any recommendations for posts I can read, videos, or other tutorials?
I don't want to screw this up again!
I *really* appreciate any tips, directions or help of any kind!
And I apologize for being pretty inept at this stuff
BACKGROUND ====================================================
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
I deleted some modules in Magisk that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I decided to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it would reboot within 30 seconds of android starting - I could not get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-...0-with-magisk/)
Now I cannot access recovery.
The phone is just stuck on the Samsung Galaxy A50 screen.
I am able to get into download mode using volume +/- & USB-C. But reflashing the patched ROM or trying to install TWRP using the methods that I know are not working.
I am really not sure what to do now.
===> I am currently reflashing the BL/AP/CP/CSC files using Odin.
The place that I am at is at the top of this post.
Thanks for your help!!
doctadocta said:
Hello Friends!
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first.
Then it got all messed up -- you can read about the issues I was having at the end of this post.
Fortunately, the phone works again with the stock ROM after reflashing the BL/AP/CP/CSC files using Odin!
Now I am trying to figure out the best method for rooting with Magisk and installing TWRP or CWM. (if that is needed)
Any suggestions? Any recommendations for posts I can read, videos, or other tutorials?
I don't want to screw this up again!
I *really* appreciate any tips, directions or help of any kind!
And I apologize for being pretty inept at this stuff
BACKGROUND ====================================================
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
I deleted some modules in Magisk that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I decided to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it would reboot within 30 seconds of android starting - I could not get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-...0-with-magisk/)
Now I cannot access recovery.
The phone is just stuck on the Samsung Galaxy A50 screen.
I am able to get into download mode using volume +/- & USB-C. But reflashing the patched ROM or trying to install TWRP using the methods that I know are not working.
I am really not sure what to do now.
===> I am currently reflashing the BL/AP/CP/CSC files using Odin.
The place that I am at is at the top of this post.
Thanks for your help!!
Click to expand...
Click to collapse
Uncheck auto reboot in Odin. Flash twrp, then hold your hard key combo to boot straight into recovery. You have to go from fastboot (odin mode) straight to recovery after you first flash it, or the stock recovery will replace twrp with itself. Once you get it to stick you won't have to worry about how you boot up.
Spaceminer said:
Uncheck auto reboot in Odin. Flash twrp, then hold your hard key combo to boot straight into recovery. You have to go from fastboot (odin mode) straight to recovery after you first flash it, or the stock recovery will replace twrp with itself. Once you get it to stick you won't have to worry about how you boot up.
Click to expand...
Click to collapse
Thanks for the response, Spaceminer!
When I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folders/1brK12SaoQ4gRbhuqLm7k0ZaW_iiaqfde
I get stuck on the Samsung Galaxy A50 screen.
I am basically trying to follow the directions here:
https://forum.xda-developers.com/galaxy-a50/development/recovery-twrp-galaxy-a50-t3916199
after trying to flash TWRP, I am now stuck on the Samsung screen.
I am now going back to the download screen (volume up, vol down + usc-c) and reloading the stock ROM stuff.
I can't seem to get TWRP to work - I think I may be using the wrong file.
Any suggestions on what TWRP file I should flash for a Samsung A50?
Like I mentioned above, I get stuck on the Samsung Galaxy A50 screen when I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folde...7k0ZaW_iiaqfde
any help is deeply appreciated!
doctadocta said:
after trying to flash TWRP, I am now stuck on the Samsung screen.
I am now going back to the download screen (volume up, vol down + usc-c) and reloading the stock ROM stuff.
I can't seem to get TWRP to work - I think I may be using the wrong file.
Any suggestions on what TWRP file I should flash for a Samsung A50?
Like I mentioned above, I get stuck on the Samsung Galaxy A50 screen when I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folde...7k0ZaW_iiaqfde
any help is deeply appreciated!
Click to expand...
Click to collapse
Do you have a copy of your stock boot.img and stock recovery? I'll take a look at that tar file in the mean time. You might need an updated package.
Spaceminer said:
Do you have a copy of your stock boot.img and stock recovery? I'll take a look at that tar file in the mean time. You might need an updated package.
Click to expand...
Click to collapse
Hello Spaceminer! Thanks for the support.
I ended up going back to the stock ROM using Odin ===> installing magisk patched ROM
so now I have everything up and running with root access.
Do you recommend that I do anything from here?
Should I install TWRP or CWM on the Samsung A50 even though I have root access using the patched magisk ROM method using Odin?
Thank you for the support!!
be well.
doctadocta said:
Hello Spaceminer! Thanks for the support.
I ended up going back to the stock ROM using Odin ===> installing magisk patched ROM
so now I have everything up and running with root access.
Do you recommend that I do anything from here?
Should I install TWRP or CWM on the Samsung A50 even though I have root access using the patched magisk ROM method using Odin?
Thank you for the support!!
be well.
Click to expand...
Click to collapse
Me personally, I would just for sake of making a backup. If you don't plan on modifying system files, then skipping it isn't going to hurt anything.
As I just spent like 8~hours getting my device out of bootloop.. (after trying to root + twrp...) I might as well take the time to post how I got it working.
DISCLAIMER: Only do this if you are desperate - I have no idea why this worked for me to be honest..
Here is how I managed to get my phone(A505FN btw) to boot again it:
download currently used firmware
extract boot.img + place it on external sd
Flash TWRP.tar (see roms&kernels forum section)
hold up + power while flashing until you are in TWRP
now flash boot.img for bootloader
reboot to system
IT BOOTS (I never got it passed samsung logo + text complaining about non offical firmware)
//edit
RIP it installed on SD card, anyone got any tips on how I move it onto internal?
It doesn't show internal storage anymore..
Shout outs to all the non english youtube videos about flashing android phones lmao
Im having kind of same issue but i only tried to install twrp via odin but then it got stuck on samsung logo boot loop. Later i tried creating recovery tar file and tried flashing it in odin but it wont go to the recovery mode although it came as Pass in odin and now im stuck on downloding screen fml any help is appreciated. can some please suggest my next course of action? is my phone gone>?
As far as I understand no one could manage to root sm-a505f.
Still no solution?
Sent from my [device_name] using XDA-Developers Legacy app
Spaceminer said:
Me personally, I would just for sake of making a backup. If you don't plan on modifying system files, then skipping it isn't going to hurt anything.
Click to expand...
Click to collapse
The twrp gives problems but since I rooted with just the patched bootloader in magisk and flash it with Odin. It works stable and I don't have issue's.
ebayusuff said:
As far as I understand no one could manage to root sm-a505f.
Still no solution?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
i tried but stucked at modem_debug.log. can't proceed further. go back to SC to restore the default rom.
Thinking on having magisk but not TWRP. as TWRP may cause many malfunctioning.