Hello, I have a galaxy A52s 5G and I'm trying to bypass pattern lock so I don't lose data by factory resetting. USB debugging is disabled and bootloader is not unlocked.
I can access download mode/stock recovery but that's about it. Doesn't seem like there's an official TWRP either. Is there a way to flash a custom recovery? Would flashing A52 4g's TWRP work? If not, what can I do
Arobase40 said:
Flashing A52 4g's TWRP onto a A52S 5G will lead to a soft brick phone !!! ^^
Someone else pretended he/she built a working TWRP for the A52S 5G but it doesn't work at all and even didn't test it him/herself before releasing it.
Another guy accepted to be a guinea pig but he bricked his phone by the way... ^^
We are all waiting after such a TWRP but there is none atm.
I'm myself trying to build one but I don't have enough time to build it because I don't have a good Windows PC and I don't feel comfortable with Android studio yet !
I have the source code but I have to put all things together so unless someone else build a working one you have to wait after it as we all do... ^^
Click to expand...
Click to collapse
Once someone builds a working version, would I be able to simply flash it using Odin in download mode or would bootloader need to be unlocked? Because otherwise I'm not sure what to do
Arobase40 said:
You can't install a TWRP without unlocking the bootloader anyway.
Click to expand...
Click to collapse
Is it worth trying to flash Aroma file manager through download mode? I'm not sure if aroma is compatible with any device
Arobase40 said:
This is a very old and dead project ! So you're on your own if you still want to use it.
Click to expand...
Click to collapse
It would supposedly allow me to delete gestures.key. I dont know what else to flash since theres no TWRP
u can try to use samsung find my
Arobase40 said:
Flashing A52 4g's TWRP onto a A52S 5G will lead to a soft brick phone !!! ^^
Someone else pretended he/she built a working TWRP for the A52S 5G but it doesn't work at all and even didn't test it him/herself before releasing it.
Another guy accepted to be a guinea pig but he bricked his phone by the way... ^^
We are all waiting after such a TWRP but there is none atm.
I'm myself trying to build one but I don't have enough time to build it because I don't have a good Windows PC and I don't feel comfortable with Android studio yet !
I have the source code but I have to put all things together so unless someone else build a working one you have to wait after it as we all do... ^^
Click to expand...
Click to collapse
I am using this guide - https://www.droidwin.com/create-port-twrp-recovery-android/
But at step 7, the fstab.devicename_or_chipsetname file is missing.
And how do we edit default.prop file? Tried with notepad++, root explorer android, but the file only has a single line as
!<symlink>ÿþp r o p . d e f a u l t
Abhishek Junghare said:
I am using this guide - https://www.droidwin.com/create-port-twrp-recovery-android/
But at step 7, the fstab.devicename_or_chipsetname file is missing.
And how do we edit default.prop file? Tried with notepad++, root explorer android, but the file only has a single line as
!<symlink>ÿþp r o p . d e f a u l t
Click to expand...
Click to collapse
Try get from kernel
oli231 said:
Try get from kernel
Click to expand...
Click to collapse
There is a mistake in the guide. It's not 'default.prop', it's 'prop.default' in step 6 (13)
So after all the work, I got TWRP booting. But it's only booting, no touch response.
Arobase40 said:
I'm trying to build one from source code but I still have errors so might be some things missing.
I'm still working on it...
Click to expand...
Click to collapse
Firmware recovery.img has some files missing. These are present in recovery.img backed up from TWRP app. Or maybe this is just the way it is, I don't know.
Attached is backed up from the TWRP app. Maybe this will help.
Abhishek Junghare said:
Firmware recovery.img has some files missing. These are present in recovery.img backed up from TWRP app. Or maybe this is just the way it is, I don't know.
Attached is backed up from the TWRP app. Maybe this will help.
Click to expand...
Click to collapse
Search on firmware and Samsung kernel
Arobase40 said:
What do you want me to do with a recovery that is not working for you ??? lol
I already have the device tree for A528B as source code but need to know how to include it in a Android tree source code : omni, cm or aosp..., but I need to know what is missing to build it and get it working... ^^
Click to expand...
Click to collapse
I am not building from source code like you. I took TWRP from A52, as the two devices are very similar. Then followed the guide - www.droidwin.com
I don't have any technical knowledge about this. It booted somehow. No boot-loop. But there is no touch response. And I don't OTG nearby, so couldn't test with a mouse.
Yes, ofc. You would know better. I am not a developer. I was only trying with that guide.
Abhishek Junghare said:
Firmware recovery.img has some files missing. These are present in recovery.img backed up from TWRP app. Or maybe this is just the way it is, I don't know.
Attached is backed up from the TWRP app. Maybe this will help.
Click to expand...
Click to collapse
Arobase40 said:
This is what I said : no touch response so simply useless as you won't even know if processes behind the touch options are even working... ^^
I remember someone else who pretended he/she will build a TWRP without source code but with some kind of "kitchen" and released it in this section but didn't even test it him/her/self. Someone else tried it but it didn't work. Then we never got any feedbacks from he/she... ^^
Click to expand...
Click to collapse
I never said that I am building TWRP for public. I was only trying for myself. The recovery.zip attached in the previous message is just the stock recovery backed up from TWRP app as it has some missing files from recovery extracted from the stock firmware.
Abhishek Junghare said:
I never said that I am building TWRP for public. I was only trying for myself. The recovery.zip attached in the previous message is just the stock recovery backed up from TWRP app as it has some missing files from recovery extracted from the stock firmware.
Click to expand...
Click to collapse
Build.prop can get out from rooted phone
oli231 said:
Build.prop can get out from rooted phone
Click to expand...
Click to collapse
https://www.droidwin.com/create-port-twrp-recovery-android/
It's default.prop in the guide. Build.prop is different right?
I am only following that guide. I don't know about how to build TWRP from source.
Abhishek Junghare said:
https://www.droidwin.com/create-port-twrp-recovery-android/
It's default.prop in the guide. Build.prop is different right?
I am only following that guide. I don't know about how to build TWRP from source.
Click to expand...
Click to collapse
NOPE! Build.prop is on A52s no from this website, on this website is incorrect
oli231 said:
Build.prop can get out from rooted phone
Click to expand...
Click to collapse
I got the Build.prop. Thanks.
How do I get fstab.samsung (or similar fstab.----) It's not in the recovery.img
Abhishek Junghare said:
I got the Build.prop. Thanks.
How do I get fstab.samsung (or similar fstab.----) It's not in the recovery.img
Click to expand...
Click to collapse
fstab is in kernel
Related
Has anyone got, or able to flash for me, the boot.img from stock N2506EX_23_150108?
Many gratitude points if you could upload for me ?
Thanks.
2nd
babelmonk said:
Has anyone got, or able to flash for me, the boot.img from stock N2506EX_23_150108?
Many gratitude points if you could upload for me
Thanks.
Click to expand...
Click to collapse
Hey I am also looking for this....on a side note are you looking for this because of wifi issues? has anyone found a fix?...pretty bummed wifi is not working on this thing
Could you install the dumps in http://forum.xda-developers.com/oppo-n3/help/looking-dump-boot-img-t2998030 Post #5, then unroot and run the OTAs to get you back up to current?
...
Lum_UK said:
Could you install the dumps in http://forum.xda-developers.com/oppo-n3/help/looking-dump-boot-img-t2998030 Post #5, then unroot and run the OTAs to get you back up to current?
Click to expand...
Click to collapse
I doubt that any stock rom will flash with twrp recovery....in the past with oppo phones (n1, 7a) its always needed stock recovery to flash stock roms...I guess we just play the waiting game until someone can upload the boot image from the updated rom. I'm pretty sure flashing that alone will get wifi back up and running. 07 Or if someone has the stock recovery they could upload....I am unsure if you can just rip it directly out of the rom and flash it....Also on oppo forums they have posted the rom for 5207 I am also unsure if you can flash that to the 5206.
The zip in that thread is images to flash in fastboot?
...
I would think you would have to flash each image individually.... system, boot, recovery ....unless if we start by flashing only the unmodified boot.img to see if it will fix wifi....but i doubt it because i suspect the wrong boot image is what screwed up wifi in the first place...someone please correct me if im wrong
c0dysm1th said:
I would think you would have to flash each image individually.... system, boot, recovery ....unless if we start by flashing only the unmodified boot.img to see if it will fix wifi....but i doubt it because i suspect the wrong boot image is what screwed up wifi in the first place...someone please correct me if im wrong
Click to expand...
Click to collapse
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Yes you'd have to flash all the images by hand one after the other.
edit: Replied before seeing babelmonk's response, please ignore this post.
steps?
babelmonk said:
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Click to expand...
Click to collapse
Can u please list the steps u took I'd like to get back up and running but don't want to screw this phone up any more ....(dd from recovery ) I'm not familiar with this if it is a command
babelmonk said:
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Click to expand...
Click to collapse
I can't get the OTA to work even after downgrading, but I do have a working system running 141228 with that hacked kernel, root and non-broken wireless.
Anyone want a nandroid of it? It's a slight upgrade at least
please
Lum_UK said:
I can't get the OTA to work even after downgrading, but I do have a working system running 141228 with that hacked kernel, root and non-broken wireless.
Anyone want a nandroid of it? It's a slight upgrade at least
Click to expand...
Click to collapse
please hook it up with that nandroid that i can flash in twrp
c0dysm1th said:
please hook it up with that nandroid that i can flash in twrp
Click to expand...
Click to collapse
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
THANK YOU
Lum_UK said:
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
Click to expand...
Click to collapse
Thank you how can i buy you a beer paypal?
c0dysm1th said:
Thank you how can i buy you a beer paypal?
Click to expand...
Click to collapse
Don't worry about it
Seems there's only about 4 or 5 people actively working on this phone here, so I'm sure we'll all end up helping each other at some point.
Lum_UK said:
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
Click to expand...
Click to collapse
Thanks for that, though I haven't tried it yet. Can I ask what it changes? Is it worth the upgrade? My original firmware +root seems to work pretty well already so I may well leave it alone until L or CM comes out.
babelmonk said:
Thanks for that, though I haven't tried it yet. Can I ask what it changes? Is it worth the upgrade? My original firmware +root seems to work pretty well already so I may well leave it alone until L or CM comes out.
Click to expand...
Click to collapse
I have no idea what it changes as it's the firmware my International N5706 was shipped with when it was released last week. It may be different to the US model (though I believe the only difference between the two is the baseband) and is definitely different to the N5707 for Chinese users.
Dude, thanks!!! You saved my life!
I got wifi back AND root!
sivxo said:
I got wifi back AND root!
Click to expand...
Click to collapse
Hi ! when the zip file is downloaded, what is steps to install it please ?
thanks
marakud said:
Hi ! when the zip file is downloaded, what is steps to install it please ?
thanks
Click to expand...
Click to collapse
Sorry. Missed this. Did you manage?
Oppo neo 7 a33f custom recovery plzzz send me
Below you will find my procedure to root the SM-J730G/GM Galaxy J7 Pro - Exynos 7870
(may also work for J730F, see post #3)
This procedure has been tested on J730GMDXU1AQF8 firmware. It may work for future releases or it may not.
If an updated firmware becomes available my advice is to update with FLASHFIRE to maintain root.
DISCLAIMER: YOU FLASH THESE AT YOUR OWN RISK. THE KNOX COUNTER WILL BE TRIPPED AND WILL POTENTIALLY VOID YOUR WARANTY. HAVING THE STOCK FIRMWARE TO HAND IS ALSO ADVISED
NOTE: BEFORE MAKING MODIFICATIONS, ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Instructions:
◘ 1. Download the files below:
sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32
ODIN 3.12
SAMSUNG_USB_Driver_for_Mobile_Phones
◘ 2. Install the USB driver and ODIN to Windows.
◘ 3. Boot your device to RECOVERY mode then select FACTORY RESET. THIS WILL WIPE YOUR DEVICE AND YOU WILL LOSE ALL DATA. (This procedure is required to remove encryption or your device won't boot)
◘ 4. From RECOVERY, IMMEDIATELY Boot your device to DOWNLOAD mode then connect your USB cable. (DO NOT LET YOUR DEVICE REBOOT NORMALLY OR YOUR DEVICE WILL RE-ENCRYPT)
◘ 5. Run ODIN and place the sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32.tar file as is in the AP slot. Don't change any options and hit START.
◘ 6. Wait for the device to flash and reboot.
◘ 7. Install the SuperSU apk from Play store and you should be rooted.
◘ 8. Have fun!
Credits: Me, @Chainfire(for supersu), @mottx(for testing)
PLEASE LEAVE FEEDBACK IF YOU FIND MY WORK USEFUL. THANKS.
IF YOU APPRECIATE WHAT I DO AND WISH TO DONATE ME A COFFEE/BEER THEN CLICK HERE OR HIT THE THANKS BUTTON IF I HELPED YOU
Great work Thanks hit.
Sir, flashing zips thru Flashfire? I Hope TWRP will be released soooon.
works for 730F
Hi ashyx, thanks you! I can confirm that this method is working for the J7 730F/DS model whith Version J730FXXU1AQF4.
Does anyone know why the bloatware can not uninstall on Android 7 Nougat? I have rooted my J730G and use Link2SD app to uninstall the default apps, but the apps can not remove. I can use link2sd app on Android 6 Marshmallow to remove default app.
I use System App Remover from Playstore.
ilsor76 said:
I use System App Remover from Playstore.
Click to expand...
Click to collapse
I have used the apps and others apps but It failed, It looks like storage protection.
Update:
I could removed the apps using ES File Explorer by activated Root Exlorer -> Mount R/W
Great buddy
Is this boot image built from kernel source ? Whats the difference in 64 bit and 32 bit version u gave at oves thread? Pls explain as it will help me for future development
Sent from my SM-J730GM using Tapatalk
Berong said:
Great work Thanks hit.
Sir, flashing zips thru Flashfire? I Hope TWRP will be released soooon.
Click to expand...
Click to collapse
TWRP already available here:
https://forum.xda-developers.com/galaxy-j7-2017/how-to/guide-j7-pro-2017-t3647101/post73181512
v00d007 said:
TWRP already available here:
https://forum.xda-developers.com/galaxy-j7-2017/how-to/guide-j7-pro-2017-t3647101/post73181512
Click to expand...
Click to collapse
I think its only for GM variants...
Berong said:
I think its only for GM variants...
Click to expand...
Click to collapse
Yes, you are right. It does not work for SM-J730F and SM-J730G (tested). Stuck on samsung logo.
redymedan said:
Yes, you are right. It does not work for SM-J730F and SM-J730G (tested). Stuck on samsung logo.
Click to expand...
Click to collapse
After installing it reset phone
So it does work for G?
Berong said:
So it does work for G?
Click to expand...
Click to collapse
according to @redymedan yes.
ashyx said:
according to @redymedan yes.
Click to expand...
Click to collapse
I mean, will the TWRP work for G/DS?
I'm sorry for messing the thread...
I know the modified boot.img will work for G/DS.
But Oves said flashing TWRP and wipe data will make it work ( Correct me if I'm wrong)
Sent from my LG-H502 using XDA-Developers Legacy app
Berong said:
I mean, will the TWRP work for G/DS?
I'm sorry for messing the thread...
I know the modified boot.img will work for G/DS.
But Oves said flashing TWRP and wipe data will make it work ( Correct me if I'm wrong)
Click to expand...
Click to collapse
As long as the variants don't differ in CPU/SoC (Qualcomm/Exynos), with Samsung it never was a big deal to use twrp from a "brother" model. Always make a backup first before flashing critical system parts and keep the original odin flash file in handy.
Thanks. Now I know sir.
File not found
ashyx said:
◘ 1. Download the files below:
sm-j730gm_SR3-SuperSU-v2.79-SR3_root_boot_32
Click to expand...
Click to collapse
Hi. I read through this new thread, and the original thread by Oves (India) who was working on the root for the J730G/DS as well. @ashyx love the work, thank you very much. But when I click on the 32 bit root file on androidfilehost.com it gives me a 404 error, file not found.
I think the link is either broke, or the file has been removed. If people are reading the old thread, they may eventually make there way here to find the updated file.
Can you please repost the link for the proper file? Thanks again for all your hard work!
superkid333 said:
Hi. I read through this new thread, and the original thread by Oves (India) who was working on the root for the J730G/DS as well. @ashyx love the work, thank you very much. But when I click on the 32 bit root file on androidfilehost.com it gives me a 404 error, file not found.
I think the link is either broke, or the file has been removed. If people are reading the old thread, they may eventually make there way here to find the updated file.
Can you please repost the link for the proper file? Thanks again for all your hard work!
Click to expand...
Click to collapse
It hasn't been removed it's still working just checked.
Maybe try a different browser or disable any ad blockers.
That is strange, I still can't get it to work via Chrome or Firefox. I just tried it now on my mobile, same thing.
This is the link from the browser:
https://www.androidfilehost.com/?fid=673368273298979779"
Well, no worries, I'm sure somehow I will figure it out. I'm using the link on the first page of this thread for the 32 bit file.
Find someone who can do boot.img and recovery for xperiu L1
Custom recovery isn't required if you use Magisk to root, but custom kernel is no exception.
I tried to modify stock kernel with Magisk Manager but it failed.
Currently I don't have Linux PC so building custom kernel may be a problem.
mingkee said:
Custom recovery isn't required if you use Magisk to root, but custom kernel is no exception.
I tried to modify stock kernel with Magisk Manager but it failed.
Currently I don't have Linux PC so building custom kernel may be a problem.
Click to expand...
Click to collapse
Use Android Image Kitchen by @osm0sis to convert the boot.elf (boot.img) and fotakernel.elf (recovery.img) to standard aosp .img format then test using fastboot (Bootloader must be unlocked) Check out other "mediatek" xperia device threads also.
I tried before.
It didn't work as it cannot unpack the boot.img extracted using Flashtool sin converter
@bigrammy
Do you help a create boot.img And recovery.img
Bro please helping very very thanxxxxx
mingkee said:
I tried before.
It didn't work as it cannot unpack the boot.img extracted using Flashtool sin converter
Click to expand...
Click to collapse
HEKER510 said:
@bigrammy
Do you help a create boot.img And recovery.img
Bro please helping very very thanxxxxx
Click to expand...
Click to collapse
Upload the boot.sin and fotakernel.sin only to a NO spam file host like mega or G-drive and I will take a look when I get some time.
bigrammy said:
Upload the boot.sin and fotakernel.sin only to a NO spam file host like mega or G-drive and I will take a look when I get some time.
Click to expand...
Click to collapse
Actually, you can download full ROM using Flashtool with xperifirm, and extract boot and recovery using SIN extractor.
Currently I am at work and I will upload them to android file host later Monday
mingkee said:
Actually, you can download full ROM using Flashtool with xperifirm, and extract boot and recovery using SIN extractor.
Currently I am at work and I will upload them to android file host later Monday
Click to expand...
Click to collapse
Bro do you created boot.img and recovery.img
Very very thanxxxx bro
mingkee said:
Actually, you can download full ROM using Flashtool with xperifirm, and extract boot and recovery using SIN extractor.
Click to expand...
Click to collapse
Did you Really type that. :laugh: :laugh:
I have enough #***# on my PC without adding even more unnecessary Gig's for a device I don't even own.
As you will know there are many variants country to country single sim dual sim etc so I will need the boot from the testers variant and not just one I made guess at.
bigrammy said:
Did you Really type that. :laugh: :laugh:
I have enough #***# on my PC without adding even more unnecessary Gig's for a device I don't even own.
As you will know there are many variants country to country single sim dual sim etc so I will need the boot from the testers variant and not just one I made guess at.
Click to expand...
Click to collapse
G3313 (single SIM)
Kernel
https://androidfilehost.com/?fid=962021903579487242
MD5: af6470e932b1231cf207343a97eeee76
Recovery
https://androidfilehost.com/?fid=673791459329055867
MD5: 871ca7cc7c688b722f7fe38597ff18cb
mingkee said:
G3313 (single SIM)
Kernel
https://androidfilehost.com/?fid=962021903579487242
MD5: af6470e932b1231cf207343a97eeee76
Recovery
https://androidfilehost.com/?fid=673791459329055867
MD5: 871ca7cc7c688b722f7fe38597ff18cb
Click to expand...
Click to collapse
Here is the boot.img to test.
It has not been modified in anyway so encryption and verity are still enabled as they are in the stock .elf
IF it boots then we will move on.
Bootloader unlock is required just for clarity and anyone thinking of testing it.
I have successfully modified the kernel and mine is rooted.
The next one will be dual SIM version and it will come later.
Here is mine https://androidfilehost.com/?fid=673791459329055871
---------- Post added at 09:54 AM ---------- Previous post was at 09:40 AM ----------
bigrammy said:
Here is the boot.img to test.
It has not been modified in anyway so encryption and verity are still enabled as they are in the stock .elf
IF it boots then we will move on.
Bootloader unlock is required just for clarity and anyone thinking of testing it.
Click to expand...
Click to collapse
Use Notepad ++ to edit default.prop
ro.secure=0
ro.debuggable=1
Save and repack.
That's it.
mingkee said:
I have successfully modified the kernel and mine is rooted.
The next one will be dual SIM version and it will come later.
Click to expand...
Click to collapse
So I need not of wasted my time after all
I am well aware of how to root a kernel and do all things regarding sony and mediatek and I think you somehow got your wires crossed.
I suggested to you how to modify the kernel.elf but you said you tried and failed that's why I offered to HELP I don't even have the L1 hence the reason for not going for the full on modification of the kernel until it was fully tested.
Anyway now your underway I will leave you all to get on with it.
Good Luck :good:
Unfortunately, I am still unable to make TWRP for L1 at this time.
Moreover, it appears that modified stock image doesn't work for other L1 variations, and all I have is US version. I uploaded all three variations and see the results.
It looks like SIM cannot be read with modified image.
where is tutorial on XDA on how to twrp recovery create please link brothersss very thankx
HEKER510 said:
where is tutorial on XDA on how to twrp recovery create please link brothersss very thankx
Click to expand...
Click to collapse
I found there's a YouTube video to tell how to compile.
https://youtu.be/WkulPr_uUqI
Linux machine required.
mingkee said:
I found there's a YouTube video to tell how to compile.
https://youtu.be/WkulPr_uUqI
Linux machine required.
Click to expand...
Click to collapse
hm i windows machine (((((((((
i find this https://www.youtube.com/watch?v=799eopwzQYg
this is good tutorial How to make Cwm or Twrp recovery for any Android device
https://www.youtube.com/watch?v=rFnG7fso9HE
How backup stock recovery ?
I am install apk flashfire and open and click backup stock recovery but failed
How to stock recovery bro?
Where is it?
So like the title says i open here a discussion for TWRP on the S10/S10+.
I can say for have TWRP we needs someone that have experience in treble A/B devices and with vbmeta.img.
The S10/S10+ have the layout of a Treble A/B device with boot.img without ramdisk because is in root folder etc but he dont use it (like A/B treble is disabled)
I allready compiled a TWRP for the S10+ but he cant boot because of vbmeta.img that blocks the recovery with the error message Recovery: Verifing footer failed (6). Thats means Samsung added AVB checks for recovery partition in vbmeta.img.
Now on phones with fastboot is that disabled in 3 mins but on Samsung phones not because we dont have fastboot.
Now for boot TWRP on the S10/S10+ is there someone needed that knows how to edit vbmeta.img for allow the recovery to boot or we need to find out how to resign and add the footer back to custom recovery.
When someone have an idea how to edit vbmeta.img or resign and readd the footer back in custom recovery let me know that because for flash magisk this time is twrp needed and dont works anymore like on S9/N9 with patch boot.img and then flash it with odin because boot.img dont have any ramdisk inside.
What i found are the tools from Samsung byself in his firmware odin tar where in it is a signing key and some tools that i dont know how to use (for get the tools open the ap file from odin tar and in it is a meta-data folder with a zip. zip password ist fota12345)
Hey @geiti94...did you manage to figure it out?
rodrigofd said:
Hey @geiti94...did you manage to figure it out?
Click to expand...
Click to collapse
Yes allready booted on s10+
Awesome let me know if you need any help testing
geiti94 said:
Yes allready booted on s10+
Click to expand...
Click to collapse
Good man!
Great work @geiti94, now the testing begins, ......:good:
geiti94 said:
Yes allready booted on s10+
Click to expand...
Click to collapse
can't wait to see it for the masses.
This..
..is fantastic! Keep up the good work!
geiti94 said:
Yes allready booted on s10+
Click to expand...
Click to collapse
You did this for the Note 9 Too - thanks for all the hard work you put into this - looking forward to being able to flash root - thanks again!
So has root been tested with twrp?.....amazing that once again Gieti94 has got twrp booting, hope everything else is easy to get up and running, and no more surprises from Samsung :good:
That's awesome！We have Waited for your work for a long time.:victory:
Waiting for TWRP/root before pulling the trigger on an Exynos S10e - this is very encouraging. THANKS!
Typing from my new S10 Plus, missing root and twrp already, hope we'll get them soon ?
I lot of jibberish here but i'm STILL excited!
Wow. I cannot wait. Thanks in advance!
As Always Amazing job and Hard work Bro. Huge Thanks my bro.
That phone, rooted, will be a beast!
Will root be possible for the Exynos model or Snapdragon model?
MCube74 said:
Will root be possible for the Exynos model or Snapdragon model?
Click to expand...
Click to collapse
Always likely for exynos, possibly for the HK and Latin America snaps but highly unlikely (or at least will take a year or so) for the NA snaps.
Been this way for years so no surprise for most of us.
for all twrp works like normal. why he is not released? because root still dont works and magisk dev is working on it (he have my twrp).
at least i can show that gsi roms works on the s10+
im not saying im gonna root my a22 yet but is anyone gonna port twrp or nah
when you try to write twrp, you may need to unlock bootloader first. and i have the problem with param file, because it's compressed by lz4 with another methods. can't open it with 7zip anymore.
do you have it?
same. i thought i'd be able to flash a custom ROM but I'm stuck with my device not listed on TWRP
nptoonix said:
same. i thought i'd be able to flash a custom ROM but I'm stuck with my device not listed on TWRP
Click to expand...
Click to collapse
Yea but this is a device that's like 3 months old
Will this work? (https://odinforum.com/discussion/7/how-to-flash-custom-rom-on-samsung-devices-using-odin)
nptoonix said:
Will this work? (https://odinforum.com/discussion/7/how-to-flash-custom-rom-on-samsung-devices-using-odin)
Click to expand...
Click to collapse
Well firstly it's done on a old version of odin with the old layout of firmware files, which won't work. And if it did work there's a high chance there's no custom roms for A22.
BlueTower said:
Well firstly it's done on a old version of odin with the old layout of firmware files, which won't work. And if it did work there's a high chance there's no custom roms for A22.
Click to expand...
Click to collapse
Thank you for the response I'll wait then