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
Hi, i update the guide for Android 10 -BTC4- (only UB)
-Need UNLOCK BOOTLOADER if you try on LOCKED BOOTLOADER you have a nice brick
1. Download stock Firmware (i downloader by samfirm)
2. Disable Autoreboot in odin options
3. Enter Download Mode : Turn Power Off. Press and hold Volume Up key + Power Key
4. Flash on Odin Stock Firm: BL, AP, CSC (i use CSC_HOME but CSC work any), CP. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
-This step its obligatory.
5. Press and hold Volume Down key + Power Key, device reboot, then quickly press and hold Volume Up key + Power Key Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears and device restart, quickly press again Vol Up and Power Key, dont release Vol Up Android Recovery Mode Appears, now you are in stock recovery.
6. Do a Factory Reset and then reboot to bootloader again.
7. Flash in odin only AP the TWRP in this thread, press and hold Volume Down key + Power Key, device reboot, then quickly press and hold Volume Up key + Power Key Samsung Logo appears release Power Key only, keep pressing Volume Up key until TWRP appears.
8. Format Data type YES (TWRP cannot use encrypted data partition).
9. Flash multidisabler zip.
10. In TWRP select reboot to recovery.
11. Success, now you have rooted and twrp in A505F
I used the system and its very stable, i used riru + edxposed never have a random reboot, in my opinion its more stable than other pie roms.
Link drive folder with multidisabler and TWRP: Download
Credit to: @ianmacd for create multidisabler
Post original
And telegram A50 group for TWRP :highfive:
very very thanks bro.
no random reboots?
arash.ajdary said:
very very thanks bro.
no random reboots?
Click to expand...
Click to collapse
I dont have any random reboot.
My config:
Magisk 20.3
Riru core
Riru Xposed Yafha
Substratum theming
Magisk Hide
Hostless module.
Good Jobs! I have tested it and it works on A50 SM-A505F BTC4
I faced stuck on Samsung logo at the first time I select reboot to Recovery. To solve it, first time we should reboot to system and setup the phone, then Reboot to Recovery ( If you faced stuck on Samsung logo, to get out and enter TWRP just press and Volume down + power key ). Install Magisk Manager and Open it.. There is no random reboots or boot loops
This is complete video about that:
redymedan said:
Good Jobs! I have tested it and it works on A50 SM-A505F BTC4
I faced stuck on Samsung logo at the first time I select reboot to Recovery. To solve it, first time we should reboot to system and setup the phone, then Reboot to Recovery ( If you faced stuck on Samsung logo, to get out and enter TWRP just press and Volume down + power key ). Install Magisk Manager and Open it.. There is no random reboots or boot loops
This is complete video about that:
Click to expand...
Click to collapse
Thank u for make video sir. :highfive:
Can I enable camera2api after rooting the device?
You're awesome bro , thank you so much.
nice work , no random reboot and that's great
just one minor issue so far , cannot control brightness in twrp.
arvind7955 said:
Can I enable camera2api after rooting the device?
Click to expand...
Click to collapse
Nope, camera2api need more than root.
What do you mean by "only UB" ? Can this be flashed to all SM-A505 variants?
aligatro2010 said:
What do you mean by "only UB" ? Can this be flashed to all SM-A505 variants?
Click to expand...
Click to collapse
UB= Unlock Bootloader if I am not wrong
redymedan said:
Good Jobs! I have tested it and it works on A50 SM-A505F BTC4
I faced stuck on Samsung logo at the first time I select reboot to Recovery. To solve it, first time we should reboot to system and setup the phone, then Reboot to Recovery ( If you faced stuck on Samsung logo, to get out and enter TWRP just press and Volume down + power key ). Install Magisk Manager and Open it.. There is no random reboots or boot loops
This is complete video about that:
://youtu.be/2s7tPwLprnk
Click to expand...
Click to collapse
Hi friends. This link says 'oops something went wrong' can you please update this link?
Thank you.
Hi friends! I need to know something. I purchased this phone 1 year ago. 6GB ram model.as I remember this phone was DS version. In purchased day I flashed Indian firmware. Now showing this device as a505F. I'm in Android 10.
So I need to know can I proceed with skipping 1 to 6 steps and continue from step 7?
And if successfuly don flashing twrp, how I getting new update? As I understand I need to manually download from Sam mobile and flash the twrp again.is that correct?
I NEED ROOT BADLY please help guys.
I'm attaching my device info and software info.
hansaka said:
Hi friends. This link says 'oops something went wrong' can you please update this link?
Thank you.
Click to expand...
Click to collapse
The correct link is youtu.be/2s7tPwLprnk just copy and paste to your browser
hansaka said:
Hi friends! I need to know something. I purchased this phone 1 year ago. 6GB ram model.as I remember this phone was DS version. In purchased day I flashed Indian firmware. Now showing this device as a505F. I'm in Android 10.
So I need to know can I proceed with skipping 1 to 6 steps and continue from step 7?
And if successfuly don flashing twrp, how I getting new update? As I understand I need to manually download from Sam mobile and flash the twrp again.is that correct?
I NEED ROOT BADLY please help guys.
I'm attaching my device info and software info.
Click to expand...
Click to collapse
Your device model number is SM-A505F, DS ( Dual SIM ) is only for identify that your phone is DUAL SIM card.
If your phone installed TWRP, you will not get new update notification. You can update it manually and flash TWRP again
aligatro2010 said:
What do you mean by "only UB" ? Can this be flashed to all SM-A505 variants?
Click to expand...
Click to collapse
I tried on SM-A505F only, test on your device.
When i say UB i refeer to Unlocked Bootloader, check a guide of this.
hansaka said:
Hi friends! I need to know something. I purchased this phone 1 year ago. 6GB ram model.as I remember this phone was DS version. In purchased day I flashed Indian firmware. Now showing this device as a505F. I'm in Android 10.
So I need to know can I proceed with skipping 1 to 6 steps and continue from step 7?
And if successfuly don flashing twrp, how I getting new update? As I understand I need to manually download from Sam mobile and flash the twrp again.is that correct?
I NEED ROOT BADLY please help guys.
I'm attaching my device info and software info.
Click to expand...
Click to collapse
Yes, this TWRP only work on BTC4 indian firmware, if you update maybe lost twrp
Bro, @Darkcannibal why you don't try develop TWRP for A50s SM-A507FN, there is no TWRP for this model up to now
redymedan said:
Good Jobs! I have tested it and it works on A50 SM-A505F BTC4
I faced stuck on Samsung logo at the first time I select reboot to Recovery. To solve it, first time we should reboot to system and setup the phone, then Reboot to Recovery ( If you faced stuck on Samsung logo, to get out and enter TWRP just press and Volume down + power key ). Install Magisk Manager and Open it.. There is no random reboots or boot loops
This is complete video about that:
Click to expand...
Click to collapse
hi redymedan. i just installed twrp and installed magisk manager but showing magisk not installed. your video show magisk is installed and that extra step thing. but clik in install magisk, says downlaod as zip or select and patch. so what i need to do? something will get wrong if i flash that downloaded zip file with twrp?
hansaka said:
hi redymedan. i just installed twrp and installed magisk manager but showing magisk not installed. your video show magisk is installed and that extra step thing. but clik in install magisk, says downlaod as zip or select and patch. so what i need to do? something will get wrong if i flash that downloaded zip file with twrp?
Click to expand...
Click to collapse
please off your phone
and on your phone join the TWRP
and select reboot the recovery
finish
or
on your phone volom+ + power key
This only works on the v7 and v8 bootloader(for now)
I am proud to present a new rom pre-installed with supersu!
Make sure to follow instructions. You will also be able to downgrade to 7.0 if you have 9.0
This tutorial is easy and will take a max time of 30 minutes to complete.
The samsung s8+ snapdragon has been hard to root to only have temp root, to bricking, but now, I have found and modified some files that you can use to permanently root your s8+ G955U and..You...can...install...TWRP!!!
TWRP will be installed as you go threw the process. Safetrap will be disabled and like all of the other rooting methods, your phone will only charge to 80%. YOUR WARRANTY WILL VOID DUE TO ROOTING AND INSTALLING A CUSTOM ROM. I AM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE(some idiot will accidentally brick there device. Like bruh, this method is easy. I don't see any way how you could accidentally brick your phone. If your reading this after bricking your phone...read the damn title next time. This method is only for the u.s versions of the s8+ aka Snapdragon.)
Let's get started!
You will first need to download this custom rom. It will disable safetrap and install twrp!
While the files are downloading, take that time to factory reset the phone and clear the cache.
Mod edit: Link removed.
This file package includes a modified version of odin.
There will be two firmware files. DO NOT FLASH BL AS IF YOU HAVE A BOOTLOADER 8 IT WILL NOT WORK. If you have bootloader 7 then it might work.
Next, put the phone into download mode. Hold Power + Volume Down + Bixby Button until the blue screen shows up. Press the volume button to continue after the blue screen shows up.
After that, open up odin and connect your phone with your cable to your computer using a USB 2.0 port. You can try USB 3.0 but might suffer a failure like a Auth error.
Once your phone is connected to your computer., odin should be showing (added!) and also will show a bar saying com. It doesn't matter what the number is.
After that, download the bootloader file for v8. You might be able to tell if your bootloader is 8 or seven(if you try flashing, it might say 8 > 7 or it just might say error. If you have v7 flash the file that came with the first download.
IF YOU FLASH SOMETHING AND IT FAILS, YOU HAVE TO RESTART THE PHONE INTO DOWNLOAD MODE AGAIN TO CLEAR THE ERRORS. IF NOT THE PHONE WILL NOT ALLOW YOU TO DOWNLOAD OTHER THINGS.
V8 BL download
Link removed.
If v8 fails then you might have to flash v7( located in folder from first download) if v7 fails flash v8(second download)
Flash the BL by clicking the BL button and navigating to the file location of the BL file.
In odin, go to the options table and unchecked f reset time and auto reboot. After that click flash! It will be quick when flashing the BL. After that once it says pass! Reboot the phone into download mode again. After that, click the reset button next to start and click on the AP button. Go to the folder where the AP file is located and load it into odin. It will freeze odin for a few seconds as it checks the MD5. Once your phone is in download mode and odin is responding again, click start and wait for the system to flash over! Depending on the speed of your pc it might go slow or fast.
Once it is done, it will said Failed! but that's ok. It has successfully completed installing and now you can reboot the phone normally. After it loads, safetrap should be disabled if a screen pops up saying continue or recovery. If none of that pops up that's fine, we still have some more files to flash.
Give the phone time to boot. The phone is not usable yet as android is still locked down. Wifi will not work but you will have temporary root access to the phone. You will see a app called flash fire. Open it but before you do, download the system file below!
Link removed.
Give it time to download. Extract the file from the 7z(have a file extractor that supports 7z). There should be a img file. Right click on it and press Send to the click on the phone. It will send it to the internal folder not downloads. Once it's on the phone, open flashfire then on the plus button. Then press the flash system(not Ota button) look for the img file and then press flash once you loaded in the .img Give it a few minutes to flash. After it's done flashing it will auto reboot. It might say that you flashed unauthorized files onto the phone and to contact your carrier. If not then skip this step. Go into odin. Select a BL file(remember if you think you have v8 flash the second download you downloaded. If you have the v7 bootloader, flash the BL that came with odin aka the first download. Uncheck f reset time and auto reboot. Flash the BL then wait. Once its done reboot the phone normally(hold Power button + down button) The error should be gone. The phone should reboot itself with a new boot logo animation. If that does happen, congrats you finished step one successfully . Now on to step two!
Shut down the phone and wipe the data and cache(factory reset)
Download the pre-installed supersu rom below:
Link removed.
Extract the files and only keep the AP file.
Go. Ack into odin and click on the AP button. Load in the AP file you just downloaded. Odin will freeze while checking the MD5. Once unfrozen, select the BL file you have. Remember, if you have v8 use the second download. If you have v7 use the first download or the one that came with odin. After that flash the two selected files and wait for the system to install.
Once the system is done it will say failed! Which is still good! Then reboot the phone and wait for it to load again. It will load into safe mode on first startup. Setup phone without Google until you want to login. Keep wifi off until your done setup. Once setup is done reboot phone by pressing power off. Once phone powers off, hold Power button until boot. Congrats if you made it this far! You have successfully rooted the samsung s8+ 955U snapdragon!
Will be making a video soon for people who had trouble installing.
@Flinnyd Please check your PM inbox. Thank you.
-Regards: Badger50 FSM
THANK YOU HAVE ...i made It as a NOOB !!! best user noob level guidance ever !!! I am trying to get to pixel simulation rom ...any pointers
jeetjeet said:
THANK YOU HAVE ...i made It as a NOOB !!! best user noob level guidance ever !!! I am trying to get to pixel simulation rom ...any pointers
Click to expand...
Click to collapse
So you were able to get your s8+ rooted?Look for any rom that might support your phone or cpu. As you learn, you might be able to edit rom files to work with your phone. The only problem is that phone companies are making it harder to make custom roms and also there's increasing security. I would say go for it!
Yes i fully rooted the SM 955u Snapdragon using the instructions above word by word and step by step ! Thanks a lot !
jeetjeet said:
Yes i fully rooted the SM 955u Snapdragon using the instructions above word by word and step by step ! Thanks a lot !
Click to expand...
Click to collapse
Yay!!!! Glad it helped
I am trying to flash other ROMS like Pixelexperience using the safestrap4.06v>Install>the zip file of the ROM ...i keep getting errors that "This package is for device greatlte etc" and the process stops , could you help with any ROMS suggested for snapdragon 955u
Sure. I'll try to find some roms then I'll pm you
jeetjeet said:
I am trying to flash other ROMS like Pixelexperience using the safestrap4.06v>Install>the zip file of the ROM ...i keep getting errors that "This package is for device greatlte etc" and the process stops , could you help with any ROMS suggested for snapdragon 955u
Click to expand...
Click to collapse
Forgot to mention installing other roms like pixel experience will remove your root.
I was able to root my S8+ with your method, thank you!
Now, I tried to use a module through Xposed but it doesn't work. I activated the module, rebooted and Xposed will detect it but it will not work even when it says that the module is active. Any suggestions?
Xpose probably broken pre installed. Try to reinstall xpose if you can
HEllo,
thank you for your work.
I am after all the stuff for SM-G955F
any idea?
thanks for the help
chandler132 said:
HEllo,
thank you for your work.
I am after all the stuff for SM-G955F
any idea?
thanks for the help
Click to expand...
Click to collapse
Will post for 955F but might not work and will need testers since i don't have the 955F
Flinnyd said:
Will post for 955F but might not work and will need testers since i don't have the 955F
Click to expand...
Click to collapse
thanks, I will test for you. Quick question, is it possible to bypass the FRP, if I flash the phone?
chandler132 said:
thanks, I will test for you. Quick question, is it possible to bypass the FRP, if I flash the phone?
Click to expand...
Click to collapse
From what I know, I believe it has to be bypassed to install a custom rom.
Flinnyd said:
From what I know, I believe it has to be bypassed to install a custom rom.
Click to expand...
Click to collapse
ok, so it means, that the installation will erase everything as well as the FRP?
Installing a custom rom will disable it
Does this work with the SM-G599U1? My BL is V8 and I had trouble installing this, and another root. It soft bricked my device and I had to flash stock BL I think? Anyways I'm a bit rusty and haven't done this since the Galaxy S3 was the biggest thing lol, so that may have contributed. Would love to hear some feedback on a link if this isn't the place to be rooting my device. Thanks!
AntyGuy77 said:
Does this work with the SM-G599U1? My BL is V8 and I had trouble installing this, and another root. It soft bricked my device and I had to flash stock BL I think? Anyways I'm a bit rusty and haven't done this since the Galaxy S3 was the biggest thing lol, so that may have contributed. Would love to hear some feedback on a link if this isn't the place to be rooting my device. Thanks!
Click to expand...
Click to collapse
I believe you can flash the 955U1 with this firmware but maybe I'm wrong. If you have bootloader v8 then flash the BL V8 file with odin with the AP file(second AP file download saying SAMFAILED) try that again and tell me if it works. If it doesn't then I'll release another method for the 955U1.
Thanks!
Flinnyd said:
I believe you can flash the 955U1 with this firmware but maybe I'm wrong. If you have bootloader v8 then flash the BL V8 file with odin with the AP file(second AP file download saying SAMFAILED) try that again and tell me if it works. If it doesn't then I'll release another method for the 955U1.
Thanks!
Click to expand...
Click to collapse
I tried again and I was successful. It was definitely confusing with all of the failed messages. but I got it. You can add that the 955U/1 works if you haven't tested yourself. Thanks again as a lot of the other methods seemed outdated and didn't work, or maybe I did it wrong lol.
Anyways, cheers!
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
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 :/