Hi,
Could anybody extract boot.img from OTA experience 8.0 (Pie) before installing it, so patched boot could be generated by Magisk?
I'm using SATV 2015.
Thanks!
Hi,
attached the (unpatched) boot.img that was in my update.
Shield 2015 16GB
Already patched mine, but did not dare to flash yet, because I am waiting for the backup...
Regards
Chaos
hardwarechaos said:
Hi,
attached the (unpatched) boot.img that was in my update.
Shield 2015 16GB
Already patched mine, but did not dare to flash yet, because I am waiting for the backup...
Regards
Chaos
Click to expand...
Click to collapse
Thanks!
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Hi
sash11 said:
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Click to expand...
Click to collapse
Just hit the same problem with my 2015 :-/
Regards
Chaos
hardwarechaos said:
Hi
Just hit the same problem with my 2015 :-/
Regards
Chaos
Click to expand...
Click to collapse
nVidia did something to protect against rooting. After I flashed stock boot.img and booted into the OS, magisk manager was gone.
https://forums.geforce.com/default/topic/1158216/shield-tv/shield-experience-upgrade-8-0/
Adds rooting feature preventing incorrect images from being flashed to SHIELD
Hi
sash11 said:
nVidia did something to protect against rooting. After I flashed stock boot.img and booted into the OS, magisk manager was gone.
Click to expand...
Click to collapse
can't confirm that. Did basically the same, but the manager is still here.
Edit: Wonder if that is the reason Quote from Nvidia:
... once you get to 8.0 and flash to a new release, we'll verify the image being flashed is compatible with the unit being flashed.
Regards
Chaos
hardwarechaos said:
Hi
can't confirm that. Did basically the same, but the manager is still here.
Edit: Wonder if that is the reason Quote from Nvidia:
... once you get to 8.0 and flash to a new release, we'll verify the image being flashed is compatible with the unit being flashed.
Regards
Chaos
Click to expand...
Click to collapse
It is a system application now. That's why I could not find it in the list of regular apps. Very weird. nVidia must classify it as such and put in into that category.
hardwarechaos said:
Hi
Just hit the same problem with my 2015 :-/
Regards
Chaos
Click to expand...
Click to collapse
Same to me, if I boot with magisk_patched, it keeps stuck at nvidia Logo
Guess we have to wait.
Maybe the boot.img of the developer image, once it is released, might work. Or hopefully someone finds a way too root again.
Regards
Chaos
Hi, just a question
Since Nvidia will release an unlocked Full 8.9 developper OTA (hope it'll be soon) , isn't it better to root that than trying on the official "locked" one ?
As for me, since i started rooting my shield, i always did it that way without problems.
Btw i was thinking of trying the same trick as you did but since i hadn't much time ... Anyway you saved my day, thanks
One last thing for those of you who are dev or android enthousiast, i make use of a fantastic Magisk script called xXx No Limits wich i find very neat.
My questions are
* Could such a script be usefull in case of the Shield ?
[Depending, i guess on wich Magisk modules are compatible with the Shield. Is there a list for compatible modules ?
* If worth it Could someone make such a script for the Shield ?
Thanks in advance for giving me clues, have all a great day !
Has anyone, by chance, backed up the 8.0 ota zip file for the shield 2015 16gb version? I updated by accident before saving it.
Hi
TAM1m said:
Has anyone, by chance, backed up the 8.0 ota zip file for the shield 2015 16gb version? I updated by accident before saving it.
Click to expand...
Click to collapse
yes I have it here. Uploading to my gdrive.
Just drop me a PM and i will send you the link.
Regards
Chaos
sash11 said:
I have 2017 model. Got full OTA image, extracted boot.img and patched with 19.3 magisk. After flashing and rebooting system is stuck at NVIDIA logo.
So something is going on... Flashed back stock boot.img and was able to boot into the OS.
Click to expand...
Click to collapse
nvm.. i found it
yea.. they did something.. no matter what i do i cant get patched boot.img to load.. it just hangs on nvidia logo like others..
i was not able to get the full firmware however and only pulled the ota.zip which has a boot.img and then other patch files
elliwigy said:
yea.. they did something.. no matter what i do i cant get patched boot.img to load.. it just hangs on nvidia logo like others..
i was not able to get the full firmware however and only pulled the ota.zip which has a boot.img and then other patch files
Click to expand...
Click to collapse
The question is if it's the same with boot.img from the dev. rom...that would be bad.
trohn_javolta said:
The question is if it's the same with boot.img from the dev. rom...that would be bad.
Click to expand...
Click to collapse
Compared CRC of both boot img from normal and dev version. It's the same. So better ask topjohnwu for looking into magisk to support this shield tv update.
oldpoem said:
Compared CRC of both boot img from normal and dev version. It's the same. So better ask topjohnwu for looking into magisk to support this shield tv update.
Click to expand...
Click to collapse
Hmm.. yeah. I now think it's because of android pie not necessarily because of changes from nvidia.
Full recovery images are available for download for Shield Experience 8.0.0
https://developer.nvidia.com/gameworksdownload
Would you mind to share the best solution when you succeed?
Related
Repacked Stock ROM for SWR50 Version LWX48P
I made a twrp flashable stock ROM ZIP of the LWX48P version firmware. You can download it at SWR50-LWX48P-repacked-signed.zip. Don't flash it with the stock recovery, it is for twrp. The ZIP contains the unmodified files, this means it is NOT rooted, busyboxed or something else. Use it to go back to stock, if you mess up with your system. You can also use the Sony PC Companion to go back to stock.
It includes also the u-boot/bootloader partition images like and from the OTA. If you don't want to reflash them, feel free to modify the zip.
Use it on your own risk.
If you need the stock recovery, too, then you can download a dump of it at SWR50-LWX48P-stock-recovery.img. Flash it with fastboot.
How did you make this? I want to do a repacked ROM with the new 5.1 update.
phib3rrr said:
How did you make this? I want to do a repacked ROM with the new 5.1 update.
Click to expand...
Click to collapse
Please tell, I want to as well! I also really need this!!!!
newb question, what adb command would i use to flash the SWR50-LWX48P-stock-recovery.img
thanks
zr1 said:
newb question, what adb command would i use to flash the SWR50-LWX48P-stock-recovery.img
thanks
Click to expand...
Click to collapse
You can't do it necessarily with an adb command but you can with fastboot
Code:
adb reboot bootloader
[wait for phone to reboot to bootloader]
fastboot flash recovery SWR50-LWX48P-stock-recovery.img
thanks Syphen 5 thats what i needed
hello, i'm on MEC24H. No risk to downgrade bootloader ?
murigny64 said:
hello, i'm on MEC24H. No risk to downgrade bootloader ?
Click to expand...
Click to collapse
Just tried it. Looks all good here. :good:
perpe said:
Repacked Stock ROM for SWR50 Version LWX48P
I made a twrp flashable stock ROM ZIP of the LWX48P version firmware. You can download it at SWR50-LWX48P-repacked-signed.zip. Don't flash it with the stock recovery, it is for twrp. The ZIP contains the unmodified files, this means it is NOT rooted, busyboxed or something else. Use it to go back to stock, if you mess up with your system. You can also use the Sony PC Companion to go back to stock.
It includes also the u-boot/bootloader partition images like and from the OTA. If you don't want to reflash them, feel free to modify the zip.
Use it on your own risk.
If you need the stock recovery, too, then you can download a dump of it at SWR50-LWX48P-stock-recovery.img. Flash it with fastboot.
Click to expand...
Click to collapse
I just wanted to say thanks for this post. My sw3 was stuck on the 4 dot symbols in MM booting. I tried several different ROMs and XC would not work either. Your pack worked and allowed my watch to live again. Although it is LP, that is fine. At least I can now use it.
Does this version support updates?
Thank you for the post!
Do you know maybe why this version can't get updates correctly? Seems like I get an update or two and then it stuck. Can I fix it somehow?
d-h.st isn't usable anymore. Can someone mirror the file to mega or dev host?
Thx in advance
tron1 said:
d-h.st isn't usable anymore. Can someone mirror the file to mega or dev host?
Thx in advance
Click to expand...
Click to collapse
There is a newer ROM here: https://forum.xda-developers.com/sm...sony-smartwatch-3-marshmallow-mec24h-t3382450
crunchybutternut said:
There is a newer ROM here: https://forum.xda-developers.com/sm...sony-smartwatch-3-marshmallow-mec24h-t3382450
Click to expand...
Click to collapse
Yes, I know. And it's installed on my watch since yesterday. But I would like to revert it to stock. Unfortunately Xperia companion isn't able to recover my watch to stock state. Companion already managed it to nearly kill my watch.
tron1 said:
Yes, I know. And it's installed on my watch since yesterday. But I would like to revert it to stock. Unfortunately Xperia companion isn't able to recover my watch to stock state. Companion already managed it to nearly kill my watch.
Click to expand...
Click to collapse
I see. I believe the stock firmware you are looking for is here as well:
https://forum.xda-developers.com/wiki/Sony_Smartwatch_3#Official
There is a link to it on Google's servers.
Hope that helps.
crunchybutternut said:
I see. I believe the stock firmware you are looking for is here as well:
https://forum.xda-developers.com/wiki/Sony_Smartwatch_3#Official
There is a link to it on Google's servers.
Hope that helps.
Click to expand...
Click to collapse
This is just an incremental update file. You need a unmodified system on the watch to apply this update.
tron1 said:
d-h.st isn't usable anymore. Can someone mirror the file to mega or dev host?
Thx in advance
Click to expand...
Click to collapse
If you are looking for SWR50-LWX48P-repacked-signed.zip file, you can contact me to get it.
I can't post outside links, since I am a new user...
ushastikin said:
If you are looking for SWR50-LWX48P-repacked-signed.zip file, you can contact me to get it.
I can't post outside links, since I am a new user...
Click to expand...
Click to collapse
Thx a lot. I'm very interested in.
Thx to ushastikin I reupped the file.
share url: https://www.androidfilehost.com/?fid=673368273298930755
md5: c05d241fd95e356650abb68a7bddb0be
Hello! I have LWX48P version on SW3. After I repacked that file by flash it with twrp (I did it and it went successfully) what should I do now to get the LWX49K version? I want the LCA43 version. Thank you
Catarina Pina said:
Hello! I have LWX48P version on SW3. After I repacked that file by flash it with twrp (I did it and it went successfully) what should I do now to get the LWX49K version? I want the LCA43 version. Thank you
Click to expand...
Click to collapse
Hi,
Just try to update from Android menu (Settings->About->System Updates). Sometimes it takes several hours or a day to get the update, but it should happen.
Pay attention to stop updating after LCA43 - the update to MEC24H didn't work and I had to flash again the LWX48P.
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
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+
Hi
i may be been messing with my phone a bit to much. The phone always boots into the bootloader.
Every time i try to normal boot, reboot or power off, the device instantly reboots into bootloader.
This happend when i tried to flash an image onto the phone. using boot_b and boot_a. it can also have been flash_a and flash_b. can't remember which one.
Does anyone on you know to fix this?
ManLikeNewMark said:
Hi
i may be been messing with my phone a bit to much. The phone always boots into the bootloader.
Every time i try to normal boot, reboot or power off, the device instantly reboots into bootloader.
This happend when i tried to flash an image onto the phone. using boot_b and boot_a. it can also have been flash_a and flash_b. can't remember which one.
Does anyone on you know to fix this?
Click to expand...
Click to collapse
reflash stock rom
dat7476 said:
reflash stock rom
Click to expand...
Click to collapse
I've tried to find a stock ROM online, and I just can't find one :/
ManLikeNewMark said:
I've tried to find a stock ROM online, and I just can't find one :/
Click to expand...
Click to collapse
Did you ever solve this or find the stock rom?
currently oneplus hasn't published any N100 stock ROM. (DE downloads)
If someone wants to root their device with magisk, they could get a boot image extracted.
Here is how i did it for N10. Otherwise i guess you must wait for an official download
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
here you finally have stock n100 !
The extracted file is a payload.bin, you can get the boot image for example with this script
Any idea how can I get an image for MSMDownload tool as the phone is stuck on Qualcomm EDL mode due to me messing around with it...
Thanks guys
Hello guys,
This is a boot.img of the latest stock rom from OnePlus site for NORD N100 BE2013
96 MB file on MEGA
mega.nz
OnePlusN100Oxygen_14.E.08_OTA_008_all_2012151227_edf41bd540d840f2
I hope it helps.
motovnet said:
Hello guys,
This is a boot.img of the latest stock rom from OnePlus site for NORD N100 BE2013
96 MB file on MEGA
mega.nz
OnePlusN100Oxygen_14.E.08_OTA_008_all_2012151227_edf41bd540d840f2
I hope it helps.
Click to expand...
Click to collapse
how can i flash if i dont have recovery
ManLikeNewMark said:
Hi
i may be been messing with my phone a bit to much. The phone always boots into the bootloader.
Every time i try to normal boot, reboot or power off, the device instantly reboots into bootloader.
This happend when i tried to flash an image onto the phone. using boot_b and boot_a. it can also have been flash_a and flash_b. can't remember which one.
Does anyone on you know to fix this?
Click to expand...
Click to collapse
You bricked your phone.
MSM flash it back to the original stock firmware.
ManLikeNewMark said:
I've tried to find a stock ROM online, and I just can't find one :/
Click to expand...
Click to collapse
Do not, your phone is most likely OxygenOS 11.0.2 and the recent update on the website is 11.0.3.
motovnet said:
Hello guys,
This is a boot.img of the latest stock rom from OnePlus site for NORD N100 BE2013
96 MB file on MEGA
mega.nz
OnePlusN100Oxygen_14.E.08_OTA_008_all_2012151227_edf41bd540d840f2
I hope it helps.
Click to expand...
Click to collapse
andreas__ said:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
here you finally have stock n100 !
The extracted file is a payload.bin, you can get the boot image for example with this script
Click to expand...
Click to collapse
Those are the 11.0.3 version, most if not all phones are on 11.0.2 which makes the boot files incompatible, you have to upgrade to 11.0.3 first, i got my phone rooted after i updated my phone to 11.0.3 and then extracted the boot and patched it with magisk.
TL;DR: This method will most likely not work on your phone unless your phone is running OxygenOS 11.0.3 which isn't pushed to phones yet.
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