Related
Hi guys, I decided to start modding this smartphone, now that I have a computer capable of compiling in a few hours.
I ported TWRP 3.0, based on Omni 6.0 source to this device. There are a few things not working and I need other people's help and feedback.
READ FULL GUIDE AND NOTES BEFORE FLASHING!!!
-Necessary steps:
Unlock bootloader. Here's a guide from Sony
-How to install:
1)From computer, open a terminal (Linux and MacOS) or command prompt (Windows) where you saved the file (download below). (Linux And MacOS. On Linux you'll need to flash with sudo) or where you have the platform-tools (Windows)
2)Poweroff your phone.
3)Boot into bootloader by pressing Volume+ button while connecting the usb cable into the usb port (the usb cable has to be inserted into the computer's port too, to successfully boot into fastboot)
4)With unlocked bootloader, type fastboot flash recovery twrp_3.0.2-0-seagull-UNOFFICIAL.img, if you renamed the files, substitube "twrp_3.0.2-0-seagull-UNOFFICIAL.img" with your file name or the directory where you saved the file.
5)When you see the OK message from fastboot, disconnect your phone.
6)Press Power, Volume+ and Volume- untile the phone vibrates.
7)Release Volume+ key. When you see the Sony logo appear, wait 3-4 seconds and then release Power button.
8)You should see TWRP bootscreen after a few seconds
-What's working:
Almost all. I could succesfully flash GApps and Root packages from this recovery, Backup, Restore and Wipe partitions. Settings work fine. Terminal and File manager work.
-What's NOT working:
Can't read files MicroSD or USB-OTG, can't browse in them and can't wipe. Investigating about it.
-Download:
(GDrive) Version 3.0.2-1
(AFH) Version 3.0.2-1
-Source and guide to build:
https://github.com/EmaMaker/device-sony-seagull/tree/twrp-3.0
Changelog:
30/04/2018: I think I fixed the screen problem by using the Lollipop kernel instead of the Marshmellow one
Thanks Everyone
Cool, although upon booting into recovery the screen isn't operating normally, similar to what happens when flashing the fxp lollipop. Might be because I'm on stock ROM/kernel though.
What do you mean with "isn't operating normally"? The screen only displays coloured bands? If so, it should have be fixed, maybe only the download link is wrong. Tell me, I'll fix in a minute
EmaMaker said:
What do you mean with "isn't operating normally"? The screen only displays coloured bands? If so, it should have be fixed, maybe only the download link is wrong. Tell me, I'll fix in a minute
Click to expand...
Click to collapse
Yes, sorry for not being more specific xD, I'm indeed getting the white-grey bands on screen.
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
It's possible it's the lollipop kernel that's to blame, since I've had the same problem with other lollipop builds.
Fixed
Download link fixed with working version
EmaMaker said:
Download link fixed with working version
Click to expand...
Click to collapse
Will try it and report back ?
Tried the updated one, still no luck. It could be just my device though.
Try the one from AFH. I really don't know why. The 3.0.2-1 version works on both my two seagulls
EmaMaker said:
Try the one from AFH. I really don't know why. The 3.0.2-1 version works on both my two seagulls
Click to expand...
Click to collapse
Tried both versions, so it's probably my device.
(However, if it is it's fine, since I do have working twrp.)
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Don't know
goosnarrggh said:
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Click to expand...
Click to collapse
One of my two seagulls came back from assistance and I tried to flash TWRP on it without any problems. I don't know if it had an updated bootloader or what, but the firmware was stock
goosnarrggh said:
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Click to expand...
Click to collapse
In order to flash recovery, you first need to download and install the Emma flashtool and restore your phone through it. That will add a recovery partition so you can flash twrp. (The Emma flash tool supports only the D5103 model of the T3 as far as I know)
I tink you will have the same as the eagle (m2) device, you need to update your bootloader and then flash recovery...
EmaMaker said:
Hi guys, I decided to start modding this smartphone, now that I have a computer capable of compiling in a few hours.
I ported TWRP 3.0, based on Omni 6.0 source to this device. There are a few things not working and I need other people's help and feedback.
READ FULL GUIDE AND NOTES BEFORE FLASHING!!!
-Necessary steps:
Unlock bootloader. Here's a guide from Sony
-How to install:
1)From computer, open a terminal (Linux and MacOS) or command prompt (Windows) where you saved the file (download below). (Linux And MacOS. On Linux you'll need to flash with sudo) or where you have the platform-tools (Windows)
2)Poweroff your phone.
3)Boot into bootloader by pressing Volume+ button while connecting the usb cable into the usb port (the usb cable has to be inserted into the computer's port too, to successfully boot into fastboot)
4)With unlocked bootloader, type fastboot flash recovery twrp_3.0.2-0-seagull-UNOFFICIAL.img, if you renamed the files, substitube "twrp_3.0.2-0-seagull-UNOFFICIAL.img" with your file name or the directory where you saved the file.
5)When you see the OK message from fastboot, disconnect your phone.
6)Press Power, Volume+ and Volume- untile the phone vibrates.
7)Release Volume+ key. When you see the Sony logo appear, wait 3-4 seconds and then release Power button.
8)You should see TWRP bootscreen after a few seconds
-What's working:
Almost all. I could succesfully flash GApps and Root packages from this recovery, Backup, Restore and Wipe partitions. Settings work fine. Terminal and File manager work.
-What's NOT working:
Can't read files MicroSD or USB-OTG, can't browse in them and can't wipe. Investigating about it.
-Download:
(GDrive) Version 3.0.2-1
(AFH) Version 3.0.2-1
-Source and guide to build:
https://github.com/EmaMaker/device-sony-seagull/tree/twrp-3.0
Changelog:
30/04/2018: I think I fixed the screen problem by using the Lollipop kernel instead of the Marshmellow one
Thanks Everyone
Click to expand...
Click to collapse
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Lord Sithek said:
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Click to expand...
Click to collapse
Maybe you can try by holding down the volume down button when rebooting, it may work.
In other case, I think the only option is fixing the button
Best regards
EmaMaker said:
Maybe you can try by holding down the volume down button when rebooting, it may work.
In other case, I think the only option is fixing the button
Best regards
Click to expand...
Click to collapse
Oh, thx for your reply, I didn't expect it really after so many days This method doesn't work, unfortunately. But I won't bother fixing the power button, actually Ive just being using my old Xperia for testing purposes only. But thank you anyway :good:
Regards
Sent from my mido using XDA Labs
Boot loop
Lord Sithek said:
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Click to expand...
Click to collapse
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
sushil lad said:
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
Click to expand...
Click to collapse
Sorry bro, I don't own this device anymore and I truly don't remember the procedure...
Sent from my SM-T720 using XDA Labs
sushil lad said:
Boot loop
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
Click to expand...
Click to collapse
same me too
So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?
can you get into bootloader and does it detect?
passion8059 said:
can you get into bootloader and does it detect?
Click to expand...
Click to collapse
Okay, so how do I even get it into bootloader?
TheShinyEnd said:
Okay, so how do I even get it into bootloader?
Click to expand...
Click to collapse
Power + Vol - (down)
passion8059 said:
Power + Vol - (down)
Click to expand...
Click to collapse
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?
TheShinyEnd said:
So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?
Click to expand...
Click to collapse
You must have flashed the boot.img that someone else uploaded from their phone? I did the same yesterday with the same result.
Fix....Use Android flash tool to flash the Aug update;
*****MAKE SURE TO UNCHECK lock bootloader, wipe device, force flash partitions. after it is finished.... copy boot.img to your phone and patch it with magisk. Then copy the magisk patched boot.img back to your PC and then flash your patched boot.img to both slots using Platform Tools CMD Good Luck
Okay I manage to get it into Fastboot, thank you very much both! much appreciate the help and your time!
TheShinyEnd said:
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?
Click to expand...
Click to collapse
TheShinyEnd said:
So I am right now am seeing the battery icon/logo(powered off) and when i press the power button with the vol down it doens't seem to move.. unless it's like a 20sec press?
Click to expand...
Click to collapse
remove any cables wait till nothing on screen & try again
jcp2 said:
You must have flashed the boot.img that someone else uploaded from their phone? I did the same yesterday with the same result.
Fix....Use Android flash tool to flash the Aug update;
*****MAKE SURE TO UNCHECK lock bootloader, wipe device, force flash partitions. after it is finished.... copy boot.img to your phone and patch it with magisk. Then copy the magisk patched boot.img back to your PC and then flash your patched boot.img to both slots using Platform Tools CMD Good Luck
Click to expand...
Click to collapse
Diff question:
I tried to(tmp) boot with the patched magisk boot.img but it doesn't seem to be willing to boot with it. how did you manage to get it to boot with the patched boot.img? is it any different than the normal android 12?
-- edit: I use my own patched files, that are not "made" by others. using the android 13 image file
I always download the full zip in order to get the boot.img for the zip, then I use Android Flash Tool to download and flash the full zip update. Let the phone reboot unrooted. If you have the magisk patched boot.img from your phone, copy it to your PC and use Platform tools to flash it to both slots using the CMD prompt.
Open a Command Prompt in the folder you copied the patched boot.img to.
Flash the boot.img (Magisk Patched) to both slots: fastboot flash boot <drag and drop boot.img> --slot all
TheShinyEnd said:
Diff question:
I tried to(tmp) boot with the patched magisk boot.img but it doesn't seem to be willing to boot with it. how did you manage to get it to boot with the patched boot.img? is it any different than the normal android 12?
-- edit: I use my own patched files, that are not "made" by others. using the android 13 image file
Click to expand...
Click to collapse
Before you do any more modding, have you flashed the A13 bootloader to both slots so you don't get in trouble with the new ARB? If not, I suggest you do so before you do anything.
If you have, never mind, lol...
I've used the android flash tool, now shows that the phone is corrupt, Android Recovery -- cannot load Android system Your data may be corrupt. If you continue to get this message...
Try again or Factory data reset.
13.0.0 (TP1A.220624.021, Aug 2022)
Yes I got in trouble with the ARB
I don't really understand on how this works, I just follow a YouTube tutorial. not that i'm new(to rooting, been doing this from March~) but that just I don't understand on how android works, especially if a13 is different than a12
The tutorial I've used :
Spoiler
I'll try to recover the phone will see how it'll go, and if i won't manage i'll reset the device, I backed up via Google one.. i'm less worried -- data reset. was unable to recover
TheShinyEnd said:
I've used the android flash tool, now shows that the phone is corrupt, Android Recovery -- cannot load Android system Your data may be corrupt. If you continue to get this message...
Try again or Factory data reset.
13.0.0 (TP1A.220624.021, Aug 2022)
Yes I got in trouble with the ARB
I don't really understand on how this works, I just follow a YouTube tutorial. not that i'm new(to rooting, been doing this from March~) but that just I don't understand on how android works, especially if a13 is different than a12
The tutorial I've used :
Spoiler
I'll try to recover the phone will see how it'll go, and if i won't manage i'll reset the device, I backed up via Google one.. i'm less worried -- data reset. was unable to recover
Click to expand...
Click to collapse
Fixed it.
so a little back story, at a random point in my day the phone(p6p) said restart to apply update, and I was rooted at the time and thought it would failed, and I went for it. it did manage to install(2nd "July" august update). then I saw a vid about A13 and thought I might aswell try to install A13 on my phone, I opted in the beta and downloaded A13, took a little bit but I manage to install it aswell.
I think this was the problem. I don't know as to how, but maybe magisk or some module manage to make the device itself think it's not rooted.. albeit it shows that the bootloader is indeed unlocked.
Needless to say, I managed to fix the problem, gained root perms again. thanks for the help and your time! much appreciated
TheShinyEnd said:
I opted in the beta and downloaded A13, took a little bit but I manage to install it aswell.
Click to expand...
Click to collapse
Opting into the Beta wasn't necessary before manually downloading Android 13 - if that's what you meant.
Now that you've opted into the Beta program, you should unopt out of it, otherwise you will continue to get beta versions of Android as opposed to stable.
roirraW edor ehT said:
Opting into the Beta wasn't necessary before manually downloading Android 13 - if that's what you meant.
Now that you've opted into the Beta program, you should unopt out of it, otherwise you will continue to get beta versions of Android as opposed to stable.
Click to expand...
Click to collapse
I meant the System update downloading phase
TheShinyEnd said:
So I updated my phone to Android 13, after I updated my phone I needed to regain root perms, so I flashed a patched magisk boot.img file, it went wrong here.
so now(after) I am unable to start my pixel 6 pro, all I get is "Your device is corrupted it cannot be trusted and may not work properly", + the bootloader is unlocked message.
and whenever I start the phone it either shows a battery icon(as in it has no battery? idk it was on 20%) or the colorful "Google" logo, no it doesn't show the colored "G"/doesn't get to that point(as in it's stuck).
I cannot get the phone to show up in "adb devices" it has worked before.
I very much need help, I went throughout all of YouTube and Google(search) and found nothing.
Any idea?
Click to expand...
Click to collapse
same issue here, did you find any solution buddy??
snaptube
vidmate
paulanswer240 said:
same issue here, did you find any solution buddy??
Click to expand...
Click to collapse
explain? can you not boot or you don't have root? or both
I need to install Lineage OS on this phone.
After multiple tries several months apart, I am still not in success.
Followed all internet tutorials and sites.
I don't want to install any G apps or any special root-things like magdisk..
I only want pure Lineage OS without any extra applications.
Way I tried and probably ended up like before:
Get newest official samsung ROM installed, update, enable usb debigging and oem, go download mode and go factory reset, get back in, sign in to wifi again, again enable develop. settings and usb debugging, go into download mode, take odin and install through the AP option the TWRP now that the phone is in download mode a 3rd time, supposed to be possible now with OEM unlock.
Most of the names on the way I don't understand, just follow tutorials.
I need to get to TWRP to then finally, as used to always, install Lineage from zip.
But I never get rebooted into TWRP recovery, just forver the samsung one, even when firmware is no longer there - after flashing in ap option the twrp tar again it never boots into TWRP afterwards.
Is there something else i must do? is not getting into oem unlock and flashing TWRP enough to get there?
And after, will the zip install finaly get me to have lineage installed?
Did you try the official guide?
https://wiki.lineageos.org/devices/beyond0lte/
I hope I picked the right phones, otherwise check devices overview.
Alternatively, perhaps this helps:
https://forum.xda-developers.com/t/...-a-graphical-installer-for-lineageos.4509995/
PS: Usually LOS doesn't do TWRP anymore but comes with its own recovery (a/b)
Why they don't do TWRP now?
I saw TWRP tuorial fot s10 on tutorials and it worked
Do I have to give up on TWRP way and od it with the adb commands from PC
frustrateduser118 said:
Why
Click to expand...
Click to collapse
It's because of this new double recovery scheme:
https://forum.xda-developers.com/t/help-understanding-a-b-partitions.3748003/post-75545902
https://source.android.com/docs/core/ota/ab
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
EOD: It's safer, updating happens in the background, then just a quick reboot et voila.
frustrateduser118 said:
I saw TWRP tuorial
Click to expand...
Click to collapse
Yes, it's still there but perhaps you post a link to your guide (or ask there). To me it seems you had TWRP just in your RAM but not your phone?
As for me, I finally gave up on TWRP and use the "crappy" LOS recovery Have way more important things to waste my time on...
PS: Sorry to bring such "bad" news, wasn't too happy with that change myself
Great, I finaly made it work.
I followed the site with turotial on installation and did not try TWRP
First I had to install samsung ROM again
It turned out to still stay unlocked so went straight to download mode and this time flashed Lineage recovery sucesfuly with heimdall
Then it booted up and a half samsung sreen made it seem like there is trouble
but Lineage recovery launched
The adb load from PC did not work so i chose to instal zip from SD even there
Now Lineage is installed
Still don't know how much is randomness, luck and so on
But it's done and hopefuly repeatable
frustrateduser118 said:
hopefuly repeatable
Click to expand...
Click to collapse
I am afraid it is
Well, most of times: Far too often I forget some little prerequisite, too... so started a little text file with steps/reminders.
anyway glad for support sigmund
you re my friend now
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Do you have TWRP installed?
webhook said:
Do you have TWRP installed?
Click to expand...
Click to collapse
No
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Rooting pixel phones are pretty straight forward and not much difficulties. Two different approaches:
1. If you are an experienced user and 100% sure what you are doing, then go back to your rooting process step by step to make sure you didn't miss anything.
2. If you are not sure that you have done everything correctly, then I would suggest you that you follow the steps which describe in this thread, believe it still the most detail explanation for rooting the pixel phones even today. https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356231/
Also posting your question on this thread could get you quicker response.
If after your trying of everything you still couldn't get it done, then describe your entire process when you ask for help without people have to guess what could went wrong.
PS: The only information which you shouldn't follow with that thread is "NOT" to use the latest platform tool, stay with version 33.0.3, version 34.0.1 has problem.
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Stupid question also could be the wire your using and usb port
If you guys are bootlooping after flashing Magisk patched image...
You should use the Google's official Android Flash Tool to reset your device to a working state...
Then you should use badabing2003's PixelFlasher to root; it automates most of what's needed to root, and it has checks and protocols to make sure files are correct, versions are correct, and the right procedure happens in the right order -- taking out a lot of guesswork or mis-steps that might be happening that is causing bootloops.
Many/You would be surprised how many times PixelFlasher succeeds where many have failed; almost miraculously and/or inexplicably! It's why it's become rather famous tool for Pixels...
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
fluxfield said:
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Click to expand...
Click to collapse
Previously rooted with Magisk modules?
Incompatibility with newer updates is more often than not the cause of bootloops.
Rebooting into safe mode will disable them.
Press and hold volume down when the bootloader unlocked warning screen appears. Then let go as soon as you feel a vibration.
You will boot into safe mode and modules will be disabled.
Then reboot normally and go into Magisk and re-enable only safe modules such as USNF.
Test the others one by one until you find the culprit. Usually it will be a font changing module or an AOSP mod .
It's pretty straightforward provided you have an unlocked bootloader, USB debugging and platform tools, The latest works for root alone btw.
In terminal
Code:
adb devices
Authorise adb in the popup window
Code:
adb reboot bootloader
If fastboot isn't recognising your phone install the USB driver
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Code:
fastboot reboot
Profit.
Assuming you've patched the right boot.img file from the .zip within the factory image zip file and you're using magisk from github.
fil3s said:
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Click to expand...
Click to collapse
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
simplepinoi177 said:
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
Click to expand...
Click to collapse
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
fil3s said:
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
Click to expand...
Click to collapse
aaahh...i see now...
sorry, i just made that assumption because you put the fastboot command to installing/flashing the image right after the sentence -- i made the mistake of connecting the two...
i should've known better as i was already initially confused as you don't install the driver AS a fastboot command...!
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
You need to connect type c cable to boot into twrp.
Connect your phone to computer or laptop or tv with cable , then use key combination to boot to twrp.
Press power key and volume up at the same time when your phone connected to pc with cable.
Sharath Mane said:
You need to connect type c cable to boot into twrp.
Connect your phone to computer or laptop or tv with cable , then use key combination to boot to twrp.
Press power key and volume up at the same time when your phone connected to pc with cable.
Click to expand...
Click to collapse
Type C cable has been connected from pc to the phone since booting into download mode, as it is required. Even after exiting the download mode and trying to boot to TWRP the phone is still connected onto it, but it just boot loops.
but it just boot loops
Click to expand...
Click to collapse
You see some red text... something like only official crap allowed...
Then maybe try other Firmware.... because """funny""" Bootloader...
IMHO similar problem like in this thread...
can't flash with odin even though bootloader being unlocked
i've got an a50 that i want to install TWRP on so i won't have to use the abomination that download mode is. i've unlocked bootloader, yet when i try to flash the TWRP .tar in odin it fails and the phone gives the following error code: "Only...
forum.xda-developers.com
Only idea....
I can not see your device nor I have Crystal Ball.
Best Regards
EQuak said:
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
Click to expand...
Click to collapse
I had the same issue. If u are on the newest binary flash that stock https://samfw.com/firmware/SM-A505FN/DCO/A505FNXXS9CUF1 after set it up w wifi u dont need to log in to a google account and flash ur recovery and it will work
EQuak said:
Steps I've done:
1. Unlocked bootloader, OEM unlock is enabled
2. Downloaded and installed Samsung Drivers
3. Download TWRP / SHARP Recovery
4. Downloaded Odin
5. Got my phone into Download mode (KG State - Checking, FRP - off, OEM LOCK - off)
6. Ran Odin, device detected in Odin
7. Put the tar file into the AP
8. Clicked "Start" in Odin, passed successfully
9. Holding Volume Down, Volume Up & Power Button
10. Released Volume Down on black screen
11. Released Power Button on Samsung logo
12. Still holding Volume Up button
That's how far I was able to come. The device just bootloops itself and I can't get it to open TWRP / SHARP. Got it into download mode again and flashed it with the stock firmware, but want to install custom ROM through the TWRP / SHARP. First time trying to flash custom rom, am I doing something wrong? Any help appreciated.
Reference:
[RECOVERY][Official] TWRP 3.7.0_11 for Galaxy A50
*** Disclaimer I am not responsible for any damage you made to your device You have been warned Features: Android 11, 12 and 13 support Supported Devices: A505F A505FN A505G A505GN A505GT Downloads...
forum.xda-developers.com
GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI.
Automated TWRP and SHRP recovery builds with Fresh Core for the Samsung Galaxy A50. Built with GitHub Actions as CI. - GitHub - TenSeventy7/android_recovery_exynos9610_ci: Automated TWRP and SHRP r...
github.com
Click to expand...
Click to collapse
I got exactly the same problem....no I am facing a bootlooping device.....jay! ... :-(
@EQuak did you read the Stickies before posting in Development?
Your post does not qualify for Development and has been moved to Questions and Answers.
You are REQUIRED to read and follow the Forum Rules!
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
Click to expand...
Click to collapse
TabletopDock9 said:
I had the same issue. If u are on the newest binary flash that stock https://samfw.com/firmware/SM-A505FN/DCO/A505FNXXS9CUF1 after set it up w wifi u dont need to log in to a google account and flash ur recovery and it will work
Click to expand...
Click to collapse
Did it, still boot loops...
EQuak said:
Did it, still boot loops...
Click to expand...
Click to collapse
Hmmm. What twrp version u use?
TabletopDock9 said:
Hmmm. What twrp version u use?
Click to expand...
Click to collapse
Originally I've used the version 3.7.0_11 (reference: https://forum.xda-developers.com/t/...-7-0_11-for-galaxy-a50.4581017/#post-88552901) but have tried also one more version from 1 youtube vid (saddly don't know the version of twrp), but they both failed. I've also tried to use a different recovery called "SHRP" but it failed again.
EQuak said:
Originally I've used the version 3.7.0_11 (reference: https://forum.xda-developers.com/t/...-7-0_11-for-galaxy-a50.4581017/#post-88552901) but have tried also one more version from 1 youtube vid (saddly don't know the version of twrp), but they both failed. I've also tried to use a different recovery called "SHRP" but it failed again.
Click to expand...
Click to collapse
I use this https://t.me/androidhowto2020/126453
TabletopDock9 said:
I use this https://t.me/androidhowto2020/126453
Click to expand...
Click to collapse
Just tried it and it boot loops. I'm gonna try and record a step-by-step video of my process to see if you could spot any mistakes I make during the process, because I'm really at my wits' end.
EQuak said:
Just tried it and it boot loops. I'm gonna try and record a step-by-step video of my process to see if you could spot any mistakes I make during the process, because I'm really at my wits' end.
Click to expand...
Click to collapse
Did you solved this yet? Im facing same problem, Ive tried about 4 different TWRP and SHRP also but non of them worked. Also first time doing this. Only option I could now do is to flash back some random stock ROM to atleast have functioning phone. But I cannot set up Gpay anymore because it says the device is rooted - And in reality it is not, even system says state of phone as Official. I dont know what to do.
DracieVajko said:
Did you solved this yet? Im facing same problem, Ive tried about 4 different TWRP and SHRP also but non of them worked. Also first time doing this. Only option I could now do is to flash back some random stock ROM to atleast have functioning phone. But I cannot set up Gpay anymore because it says the device is rooted - And in reality it is not, even system says state of phone as Official. I dont know what to do.
Click to expand...
Click to collapse
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
EQuak said:
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
Click to expand...
Click to collapse
I was thinking about it too. Like, my phone is from Orange, so probably there is something which is blocking the whole thing. Only way I was able to install system was through Odin. But for Odin Ive found only stock roms, custom roms work only with TWRP...
EQuak said:
No, I haven't found any solution so far to it since the problem occurred. Guessing It may be caused by a CSC code since we are both form Slovakia? Really don't know...
Click to expand...
Click to collapse
Maybe I found something now. I had one old Galaxy J3 2016, Also from Orange operator as my A50. And it did worked perfectly on the first try and only thing I've did was enabling USB debugging in developer options, which I've forgot on my A50 before. So maybe this could be the problem at least in my scenario? But yet I didn't got time to try it on A50 again.
DracieVajko said:
Maybe I found something now. I had one old Galaxy J3 2016, Also from Orange operator as my A50. And it did worked perfectly on the first try and only thing I've did was enabling USB debugging in developer options, which I've forgot on my A50 before. So maybe this could be the problem at least in my scenario? But yet I didn't got time to try it on A50 again.
Click to expand...
Click to collapse
You're a lifesaver, just tried it with the A50 and I successfully booted into TWRP. Definitely works!
Edit: Another thing that may fixed the issue is just not updating the software. I just went through the process of setting it up but right after I booted into the android, I just turned it off and got it into download mode and flashed it with TWRP.
EQuak said:
You're a lifesaver, just tried it with the A50 and I successfully booted into TWRP. Definitely works!
Edit: Another thing that may fixed the issue is just not updating the software. I just went through the process of setting it up but right after I booted into the android, I just turned it off and got it into download mode and flashed it with TWRP.
Click to expand...
Click to collapse
Im happy it worked. But sadly for my A50 it still bootloops and nothing, I have no idea why so Im stuck with stock OS on which Google Pay and few Samsung apps wont work cause "phone is rooted" (no it isnt, its on official rom) and since I cant flash TWRP I cant do anything Ive also tried your method to quickly set up fresh android (without wifi) and right after I went to reboot and flashing :/