CWM Recovery 6.0.2.8
Build from source
abandoned
Tnx and Credits go out to: koush & cyanogenmod
Without them this all would not be possible
Tnx to Angel_666 for thinking with me
For your information
My source files: cwm-P5210-santos10wifi
Code:
# mount point fstype device [device2]
/efs ext4 /dev/block/mmcblk0p2
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
/recovery emmc /dev/block/mmcblk0p11
/modem emmc /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/boot emmc /dev/block/mmcblk0p10
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
If you want to build your own rom, you need a specific file in the Kitchen.
Put the attached file in: kitchen/tools/edify_defs
Then the kitchen supports this device as well
Thanks you !
Old beta:
Unfortunately, It stuck at bootlogo when go to Recovery
I need 3 files to make the recovery.
The device trees are not know yet as well
So those who gain root, get these files for me please:
recovery.fstab (got this)
graphics.c
postrecoveryboot.sh
DutchDanny said:
I need 3 files to make the recovery.
The device trees are not know yet as well
So those who gain root, get these files for me please:
recovery.fstab (got this)
graphics.c
postrecoveryboot.sh
Click to expand...
Click to collapse
Hi! There is no graphics.c and postrecoveryboot.sh script in our device. Only recovery.fstab.
Test 2 is posted in the OP
Test two comes up with
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> modded.cwm.recovery2.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
in odin
confyzone said:
Test two comes up with
in odin
Click to expand...
Click to collapse
MD5 sum was incorrect. I resign IMG adn flash, but still no success - if we try to go in recovery mod, device freezes on "Samsung Galaxy Tab" logo.
I think we must dig in devices that have x86 platform (like we have).
What did you use to resign the IMG?
Send via my BinDroided HTC ONE
DutchDanny said:
Test 2 is posted in the OP
Click to expand...
Click to collapse
Still not work ! It`s stuck at bootlogo like first test 1
Test 3 is in the OP
DutchDanny said:
What did you use to resign the IMG?
Send via my BinDroided HTC ONE
Click to expand...
Click to collapse
Standart tools of linux - tar IMG, then calculate MD5 summ for tar, then rename .tar in .MD5
After that Odin will accept any image to flash.
for Linux console:
Code:
tar -H ustar -c recovery.img > yourrecoveryname.tar
md5sum -t yourrecoveryname.tar >> yourrecoveryname.tar
mv yourrecoveryname.tar yourrecoveryname.tar.md5
P.S. Test3 not working - freezes on logo.
I think you can calculate MD5 in Windows by TotalCommander or another advanced filemanager.
test 4 is in the OP
DutchDanny said:
test 4 is in the OP
Click to expand...
Click to collapse
And again incorrect MD5.
Well, use this tool to create correct md5 images for odin:
https://mega.co.nz/#!2gQlkYCC!CQNmLi0O9Up4qaOOgYaBOiYqqGImjEdyW9rxKo58_ps
USAGE:
Unpack attachment in any place.
Place your recovery.img in "Odin_tarmaker" folder, then run "CreateOdin_tar.bat".
After some sec, new signed MD5 image appear in folder.
P.S. I think we must find any device on x86 platform with already working CWM. Then we can port recovery to our tab.
I'm a HTC guy, not so used to Odin....
I have it for my galaxy tab 1...
But I work more with recovery then Odin
Send via my BinDroided HTC ONE
Test 5 is in the OP
I have HIGH hopes for this one....
DutchDanny said:
Test 5 is in the OP
I have HIGH hopes for this one....
Click to expand...
Click to collapse
I'll download now and give it a try
Sent from my GT-P5210 using xda app-developers app
---------- Post added at 09:00 PM ---------- Previous post was at 08:51 PM ----------
Update: Flashed fine, tablet rebooted into OS perfectly, now testing to see if recovery took
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
Update 2: I now can not boot into recovery, using all different methods to get into recovery, it does not show, it only continues with boot.
confyzone said:
I'll download now and give it a try
Sent from my GT-P5210 using xda app-developers app
---------- Post added at 09:00 PM ---------- Previous post was at 08:51 PM ----------
Update: Flashed fine, tablet rebooted into OS perfectly, now testing to see if recovery took
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
Update 2: I now can not boot into recovery, using all different methods to get into recovery, it does not show, it only continues with boot.
Click to expand...
Click to collapse
So it boots up Android, instead of recovery?
Send via my BinDroided HTC ONE
DutchDanny said:
So it boots up Android, instead of recovery?
Send via my BinDroided HTC ONE
Click to expand...
Click to collapse
Flash succeeds, boots into android/touchwiz OS, I can boot into download mode, how ever when I try the power + vol up + home, it doesn't boot into recovery, it just continues to boot into Android/touchwiz
Sent from my GT-P5210 using xda app-developers app
Related
^^This
Probably NO its an old device but i still like it so there is still a change of it and maybe CM13.0 too it just need time.
Working on Lineage OS 13.0 Rom for this device with TWRP 3.0.2.0 but new CM 12.1 got already new version so maybe i can try to grab 3.1.1 twrp source and compile for our device but dont know if it will work
Tried not possible our devices have too much modified TWRP that the branch don't wanna to merge.
I would greatly recommend checking galaxy nexus TWRP thread, where they also had a lot of problems with 3.1.0.0.
Situation is remarkably kind of similar to ours: they are stuck to 3.0 kernel, and they haven't QCOM hardware (they have support for nougat though)
I had ported it to our device but it doesn't compile because of sdk it showed errors always about sdk i have it on my GitHub branch 7.1 I may create new branch and try again because you are not the only one who want latest stuff if there were moreeeeeee time and more people we might be able to Port android 7.1 but this device is not much used anymore there is lot less devs. But if anybody wants to try download android 6.0 source add our vendors and all our device stuff and add my TWRP and try to build only TWRP without android you might get successful build
Sent from my nypon using XDA Labs
---------- Post added at 07:19 PM ---------- Previous post was at 07:16 PM ----------
In few days i will create new thread In p general and will post there stuff about my porting diary maybe more devs will add and will be help me
Sent from my nypon using XDA Labs
---------- Post added at 07:30 PM ---------- Previous post was at 07:19 PM ----------
And I don't think sdk problems are releated to my porting since android 6.0 don't compile on 5.1.1 but it does on 6.0 so I don't know guys about that
Sent from my nypon using XDA Labs
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
mirhl said:
I would greatly recommend checking galaxy nexus TWRP thread, where they also had a lot of problems with 3.1.0.0.
Situation is remarkably kind of similar to ours: they are stuck to 3.0 kernel, and they haven't QCOM hardware (they have support for nougat though)
Click to expand...
Click to collapse
Also would you help me post some stuff if you have this device ?
Sent from my nypon using XDA Labs
Sorry, I don't.
mirhl said:
Sorry, I don't.
Click to expand...
Click to collapse
Oh ok Then i will try to port it on my own. But thanks still.
I have done it i build TWRP 3.1.1 for xperia P its on my LineageOS thread but its build from omni tree so it will not boot CM roms yet im going to build on CM tree somehow(CM doesnt support TWRP officialy omni do so thats why i build it first in omni).
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
It wasn't booting because it was built using omni tree now I compiled using cm tree and its working and yes I'm writing with adrianDC about FOTAkernel I want to do that one mainly now and then official support.
---------- Post added at 11:01 PM ---------- Previous post was at 10:55 PM ----------
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
But idk if we don't need to make the fota partition or does Nypon have it already ?
---------- Post added at 11:07 PM ---------- Previous post was at 11:01 PM ----------
mirhl said:
It's kindish confusing to say that "recovery cannot boot rom", for as much as yes, kernel and recovery are physically the same atm.
Wouldn't be a problem if we had FOTA as I was talking about (or an universal kernel like they have on gnex.. but I'm digressing)
Click to expand...
Click to collapse
And I meant kernel cannot boot the ROM because it was built for omni ROM.
Haxk20 said:
But idk if we don't need to make the fota partition or does Nypon have it already ?
Click to expand...
Click to collapse
Every sony phone should have it.
That was exactly the secret of the smart idea.
Supposedly, I think at least on XU that should correspond to /dev/block/mmcblk0p13
mirhl said:
Every sony phone should have it.
That was exactly the secret of the smart idea.
Supposedly, I think at least on XU that should correspond to /dev/block/mmcblk0p13
Click to expand...
Click to collapse
And how can we check which one it is on XP ?
After I know which partition it is I can start working on it.
First add it to TWRP as FOTA (just to addone line )
Then well edit few files in device tree and then well we would have fota partition used by recovery yayyy.
It shouldn't be too hard to do .
I just need to know what files should I edit from adrianDC I will write him.
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Garcia98 said:
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Click to expand...
Click to collapse
Yes I know all of this but still thanks and the benefit here is that with the new method I can request official support for xperia P from twrp team.
Cause if I must build a boot.IMG still when new commit comes in twrp I would have a ton of boot.IMG and users will not use them cause they would have to flash every new version. And also if users use omni and I build cm boot.IMG they cannot boot to system.
If we add fota then users could update twrp just from twrp app ifimwrong about this please correct me.
Also why is not our FOTA recognized as recovery then ?
---------- Post added at 10:00 PM ---------- Previous post was at 09:53 PM ----------
Garcia98 said:
Sony devices can't boot into FOTA partition once the bootloader is unlocked, what newer devices do is just load the recovery ramdisk from the FOTA partition (which can still store data and be accessed) into the boot partition, it's not a real recovery partition, what our devices do is just the same but the recovery ramdisk is stored in the boot.img.
The only benefit of using the FOTA partition to store the recovery is that it can be updated more easily, in newer Sony devices you can just use fastboot to flash the image, but our devices can't use fastboot to flash the FOTA partition so you would have to use the dd command, which isn't as convenient as fastboot. Also AGONTUK already made a script that replaces the recovery ramdisk in a boot.img, so updating the recovery is not a big hassle.
That's why we didn't bother porting the method newer Sony devices use to boot into the recovery, the benefits are non-existent (because our FOTA partition is not recognised as a recovery partition by fastboot).
Click to expand...
Click to collapse
And also which partition is FOTA on xperia P ?
Haxk20 said:
Yes I know all of this but still thanks and the benefit here is that with the new method I can request official support for xperia P from twrp team.
Cause if I must build a boot.IMG still when new commit comes in twrp I would have a ton of boot.IMG and users will not use them cause they would have to flash every new version. And also if users use omni and I build cm boot.IMG they cannot boot to system.
If we add fota then users could update twrp just from twrp app ifimwrong about this please correct me.
Also why is not our FOTA recognized as recovery then ?
---------- Post added at 10:00 PM ---------- Previous post was at 09:53 PM ----------
And also which partition is FOTA on xperia P ?
Click to expand...
Click to collapse
The FOTA partition is the 13, the same as Xperia U, Go and Sola.
Our bootloader doesn't flag the FOTA partition as a recovery partition, that's why fastboot can't access to it, and only Sony could solve that through a firmware update.
I don't really know how the TWRP official app works, but if they accept devices with boot.img based recoveries the current method would be fine. If the recovery ramdisk has to be on a separate image then you would need to use the newer method, ask them about that.
Also it doesn't matter whether you're building TWRP on Omni or CM sources, the recovery ramdisk will be the same and that's everything that matters, you can then use that recovery ramdisk in a boot.img for CM, Omni or whatever ROM you want.
Garcia98 said:
The FOTA partition is the 13, the same as Xperia U, Go and Sola.
Our bootloader doesn't flag the FOTA partition as a recovery partition, that's why fastboot can't access to it, and only Sony could solve that through a firmware update.
I don't really know how the TWRP official app works, but if they accept devices with boot.img based recoveries the current method would be fine. If the recovery ramdisk has to be on a separate image then you would need to use the newer method, ask them about that.
Also it doesn't matter whether you're building TWRP on Omni or CM sources, the recovery ramdisk will be the same and that's everything that matters, you can then use that recovery ramdisk in a boot.img for CM, Omni or whatever ROM you want.
Click to expand...
Click to collapse
Yes recoveryramdisk is same of course but the boot.img itself isn't and tested it doesn't boot with omni one.
I will lookup if current method will work but I don't think so
Haxk20 said:
Yes recoveryramdisk is same of course but the boot.img itself isn't and tested it doesn't boot with omni one.
I will lookup if current method will work but I don't think so
Click to expand...
Click to collapse
You have to take only the recovery ramdisk you get after compiling the recovery and swap it with the old recovery ramdisk in the target boot.img, check AGONTUK script, you can throw the boot.img you get after compiling the recovery to the recycle bin.
Garcia98 said:
You have to take only the recovery ramdisk you get after compiling the recovery and swap it with the old recovery ramdisk in the target boot.img, check AGONTUK script, you can throw the boot.img you get after compiling the recovery to the recycle bin.
Click to expand...
Click to collapse
Hi well the link to download doesn't work and well now im going to makethefota working.
Haxk20 said:
Hi well the link to download doesn't work and well now im going to makethefota working.
Click to expand...
Click to collapse
Check the attached files of this post
Attached in this thread is TWRP-3.1.1-0 repackaged for the SM-T285 built by @_mone from his SM-T280 build. Basically I packaged the latest gtexslte kernel with the ramdisk build by @_mone. I don't have time to build twrp myself so a big thanks to him.
Update August 20, 2017
==================
- Remove persdata error message when wiping
- fix properties to correctly use gtexslte instead of gtexswifi
Issues:
- Seems to start slower than the 3.0.1 build
For GPL compliance:
https://github.com/jedld/kernel_samsung_gtexslte.git
Sources:
Omni TWRP device tree is the same as the one @_mone is using but use the gtexslte kernel and skip the DTB boot image header shenanigans that the SM-T280 uses.
See thread
INSTALLATION INSTRUCTIONS:
This installation instruction is only for the LTE enabled version of the Samsug galaxy tab A 7" 2016 (SM-T285). If you have a wifi-only version (SM-T280) go to this thread instead.
Disclaimer: I am not responsible for bricked devices and provide no warranty, make sure you made the proper backups and contingencies before you do this procedure. Make sure you have a stock firmware available as a contingency plan
Before going through this make sure your tablet is OEM Unlocked!. Make sure you have developer settings enable and there should be a setting there that says OEM unlock. That should be enabled, otherwise your SM-T285 will not accept firmware changes. Also make sure your tablet has sufficient charge and is not about to die.
1. Put your tablet in download mode (Turn off. holding POWER + HOME + VOL DOWN until download mode appears. There will be a warning that about custom firmware blah- blah-blah just hit volume up to proceed). Connect your tablet to your computer using the provided micro usb cable.
2. Flash with ODIN 3.10.7 in the AP slot. Uncheck Auto reboot. (If you are on Linux you can use Heimdall
3. Load the respective attached file (TWRP_3.1.1-0_SM-T285_20170501.zip) in this thread below into the AP slot and hit start.
4. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Root and SuperSU
==============
1. Download the latest available SuperSu Zip from chainfire. Install Zip using TWRP. Reboot phone.
2.Your phone might reboot a couple of times, however at the end of the process you should be rooted.
Credits:
@_mone and @ashyx
hi, i can't install with odin v3.10.7. "md5 error! Binnary is invalid"
help please
oNuRs7 said:
hi, i can't install with odin v3.10.7. "md5 error! Binnary is invalid"
help please
Click to expand...
Click to collapse
reuploaded. see if it fixes things, make sure you extract the zip first though.
jedld said:
reuploaded. see if it fixes things, make sure you extract the zip first though.
Click to expand...
Click to collapse
it's work thanks.
I am getting a `Failed to mount '/persdata' (Invalid argument)`. What does this mean? Is it harmful? My device is softbricked atm, but I am unsure if it's related.
EDIT: Whoops, my bad. Wrong topic. Can someone delete this?
Binero said:
I am getting a `Failed to mount '/persdata' (Invalid argument)`. What does this mean? Is it harmful? My device is softbricked atm, but I am unsure if it's related.
Click to expand...
Click to collapse
This should be fine.
TWRP-3.1.1-0 repackaged for the SM-T285 build
Hi
Does the TWRP-3.1.1-0 repackaged for the SM-T285 build kernel allow for USB OTG host and simultanious charging mode?
TWRP 3.2.3-0
twrp-3.2.3-0-gtexslte.img
twrp-3.2.3-0-gtexslte.tar
I used my device tree that I created from _mone's android-6.0 gtexswifi device tree and jedld's omni-6.0 gtexslte source.
Bootloader and modem
T285XXU0ARB1_T285XXU0AQD1.tar
You might as well update these while you're trying out the new TWRP Use Odin's "AP" button.
@acornkenya, @barani kumar, @User_99: you guys thanked my post above. Does that mean my twrp build works?
ripee said:
@acornkenya, @barani kumar, @User_99: you guys thanked my post above. Does that mean my twrp build works?
Click to expand...
Click to collapse
The bootloader and modem work perfectly, but the TWRP failed to boot. I apologize for not informing you sooner; I have been very busy.
---------- Post added at 11:03 PM ---------- Previous post was at 11:01 PM ----------
ripee said:
@acornkenya, @barani kumar, @User_99: you guys thanked my post above. Does that mean my twrp build works?
Click to expand...
Click to collapse
The bootloader and modem work perfectly, but the TWRP failed to boot. I apologize for not informing you sooner; I have been extremely busy.
acornkenya said:
The bootloader and modem work perfectly, but the TWRP failed to boot. I apologize for not informing you sooner; I have been very busy.
---------- Post added at 11:03 PM ---------- Previous post was at 11:01 PM ----------
The bootloader and modem work perfectly, but the TWRP failed to boot. I apologize for not informing you sooner; I have been extremely busy.
Click to expand...
Click to collapse
No problem at all, just curious. I'll take another look later.
ripee said:
@acornkenya, @barani kumar, @User_99: you guys thanked my post above. Does that mean my twrp build works?
Click to expand...
Click to collapse
Currently not. Need the device. No time for playing.
I have one will boot to tarp 3.1.1 but that's all cant get roms to load...
Code:
*** Disclamer * Your warranty is now void. * *
We are not responsible for bricked devices, dead SD cards, * thermonuclear war,
or you getting fired because the alarm app failed. Please * do some research if you
have any concerns about features included in this ROM * before flashing it! YOU are
choosing to make these modifications, and if * you point the finger at us for messing
up your device, we will laugh at you.
DISCONTINUED, MOVED TO BUILDING CRDROID AND AICP ANDROID PIE
Known Issues
No audio through speaker, currently trying to find a fix.
ROM ResurrectionRemix-O-v6.2.1-20181202
TWRP DOWNLOAD
INSTALLATION
I am assuming that most of you already know how to flash custom ROMS.
Boot into TWRP Recovery Flash TWRP 3.2.3-0 image
Wipe the System, Cache and Data.
Flash ROM Zipfile
Flash the GApps (optional, needed for Google Playstore to work).
(Optional) Flash root zipfile Majisk/SuperSU.
Wipe ART/Dalvik cache.
Reboot
Flashing the ROM itself the boot time is around 5 mins, if you flash Gapps + Majisk or SuperSU expect the first boot time to increase to about 7-8 mins
XDA:DevDB Information
SM-T350 ResurrectionRemix Oreo, ROM for the Samsung Galaxy Tab A series
Contributors
nubianprince
Source Code: https://github.com/Nubianprince/gt58wifi_rr
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Nougat
Version Information
Status: Beta
Beta Release Date: 2018-12-02
Created 2018-12-02
Last Updated 2019-03-23
Reserved
reserved
Did you guys just use the open source code of lineage 15.1 that didn't have working speaker. So is basically the same rom with different name. I'm still going to flash it for kicks but doesn't seem kinda pointless? Twrp should be better I'll let you know I'm assuming you forgot to mention gapps.
Funny cause the guy that built that took the source codes from someone else and that's why the speaker never got fixed because you don't know how to build or compile your just copying.
I got the rom up and running i was on marshmallow firmware and it worked fine. It takes awhile to boot up give it 10 minutes then when you start up it's really slow and lagging but after a couple reboots it works fine. I do say it's resremix tons of customization I haven't used any yet. I still think it's based off the lineage codes but it's different very different setup so it's worth installing if the damn speaker could get fixed it would be great. Bluetooth speaker or headphones work camera works I think the camera on this tablet is **** but works lol. Thanks for the rom guys. Twrp also seems to be working fine which is great because that's been a pain before.
Good job
Enviado desde mi SM-T320 mediante Tapatalk
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
joejunior253 said:
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
Click to expand...
Click to collapse
After you flashed the new twrp 3.2.3 did you reboot back into recovery? You can't just flash it then flash the rom you have to reboot in to recovery again to have it take effect. Also then follow all other instructions what instructions did you follow just a little more detail. Also what room or system were you on before?
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
Device?
Firmware?
TWRP version?
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
joejunior253 said:
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
Click to expand...
Click to collapse
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
nubianprince said:
Device?
Firmware?
TWRP version?
Click to expand...
Click to collapse
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
joejunior253 said:
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
Click to expand...
Click to collapse
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
joejunior253 said:
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
Click to expand...
Click to collapse
Are you not English speaking? I said you had a efs error that's what I thought. You should have flashed the last version of nougat you had working when the error happened boot into stock and turned on USB debugging. Then you flash twrp either t355 3.1.1 or 3.2.3 are the best. I guess flash 3.1.1 for 355 at first then when you flash twrp on stock nougat boot into twrp and flash magisk 17.1 I'm having trouble with magisk 18 on some devices so use 17.1. Those terminal codes are tricky type them perfect or they don't work I recommend a couple times until it works. They should reset your efs partition then you reboot and flash your firmware again I'd say flash nougat again. Cause I flash marshmallow and got drk error. The firmware doesn't touch efs partition so once you screw it up your ass is grass unless you have a efs backup that works not the one from 3.2.1 twrp that screws everyone up. This is why people should not put stuff out until they have tested it. After you fix efs and can reboot then use twrp to flash twrp 3.2.3 by install image find the twrp 3.2.3 image select recovery. Flash because you can't flash Oreo with twrp 3.1.1. Then you can flash this rom.
You need root so you have to flash magisk in twrp after you flash twrp.
Try this code that will list partition blocks. Your efs should be 13. If it's not you don't have smt350 lol. Those codes work it Should say writing inode or something
ls -l /dev/block/bootdevice/by-name enter
mke2fs /dev/block/mmcblk0p13 enter
mount -w -t ext4 /dev/block/mmcblk0p13
Edit try SuperSU 2..82 sr5 beta or 2.79 sr3 because SuperSU is better for Samsung it's made to disable dm verity I think. Only up to nougat SuperSU will not work on Oreo you'll have to use magisk. The most important thing is after you flash the working stock firmware one of them will work I had this problem to only nougat q1 would work the rest didn't boot. So after I got my tablet running I flashed twrp 355 3.1.1 and went into terminal inside advance in twrp. I typed this commands and it worked it reset my efs partition my Bluetooth worked again my tablet would flash custom roms again and even downgrade back to marshmallow but I'm not recommending that. You type the first one hit enter type the second one hit enter then reboot. The firmware needs to be the same one you had when it errors if it's q5 then q5. I'm trying to help man I don't think your tablet is done I think it'll work again but it'll take some time and effort. You got this man . I always flash root first I don't think you have to because twrp already has root but I would say flash SuperSU first .
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
Read everything i ve posted I said it was efs
Dude your all over the map man
1. Flash nougat firmware the last one you had boot up in the rom
2. Flash twrp 3.1.1
3. Flash SuperSU 2.7.9 or magisk 17.1 probably should go with SuperSU 2.82 SR5 beta.
4. Mack a back up
5. Reboot into rom
6. Reboot back into twrp and type that code it fixes your efs partition and resets it. Into terminal emulator inside twrp try it to it says writing inode or something like that. Both lines.
Reboot .
7. Go back into twrp flash image in install menu find twrp 3.2.3 I'm file make sure it's a image file.
Here's a section of my first post
Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
If you can't boot into nougat go into twrp and type that code into the terminal emulator then when you get it to say writing idone or something it's working if you can't see the screen is black you have to search xda on tab a forms there's a fix a don't remember anyone please if you had twrp black screen what did you do? I've never had it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:24 PM ----------
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
No you can't flash magisk before twrp that makes no sense.
Please let me know what firmware update your trying to flash it Should be a the last one you had when you got the efs error and was able to boot into rom. That firmware only that one. No others will work I had this problem and fixed it. Also what twrp were you using when you got the efs error? Please answer it will help others to not touch it. I noticed that twrp 3.2.1 was taking down so I'm wondering did twrp 3.2.3 cause the error?
---------- Post added at 03:34 PM ---------- Previous post was at 02:36 PM ----------
Everyone did I not explain the fix right? I'm trying to learn how to help people on xda and if you guys think I didn't explain things right please let me know. I am fine with criticism so I can learn how to better help people.
liking it so far (been using for a day), i like the customization options for the UI. it took a bit in the setup thingy... it took a couple tries to get passed the "checking for update" spot. but it runs nicely now
Hi Bro., Can I flash this Rom on t355y ?
Hello, I got my Umidigi F1 into a boot loop, USB debugging was not enabled and i'm having issues with Windows recognising the device so havent been able to use SP Flash.
I do have an SD card, and was hoping that with TWRP i could load the stock firmware to escape from my current dilemma.
TWRP shows no OS installed;
q: can i copy the stock ROM to the SD Card and recover from there?
Regards,
smckay12
sadly,with twrp you can only flash custom roms not md5 files :/.thats why before flashing anyhting in twrp or after installing twrp you have to make a nandroid backup unless you know what you are doing.so the only way is to make your phone be recognized by the comouter so you can flash stock.what file have you flashed?
paranoic(d) said:
sadly,with twrp you can only flash custom roms not md5 files :/.thats why before flashing anyhting in twrp or after installing twrp you have to make a nandroid backup unless you know what you are doing.so the only way is to make your phone be recognized by the comouter so you can flash stock.what file have you flashed?
Click to expand...
Click to collapse
I have twrp running but this fails to install the stock rom - UMIDIGI_F1_V1.0_20190125_20190528-1708_update.zip
I'll have to try and troubleshoot the failure for the Win PC to reconigse phone when its in recovery
can you elaborate the error?
paranoic(d) said:
can you elaborate the error?
Click to expand...
Click to collapse
I attempt to install the ZIP:
Verifying current system.....
E3006: Not enough free space on /cache to apply patches.
Updater process ended with ERROR: 7
If I run df from a terminal i see
tmpfs
/dev
tmpfs
/tmp
/dev/block/mcblk0p36
/data
/dev/block/mcblk0p36
/sdcard
0% used 115095068KB available
the error 7 is the error which says cant verify zip file?
---------- Post added at 08:55 PM ---------- Previous post was at 08:50 PM ----------
check tha guide here?
im not responsible if you brick your device!!
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This TWRP does not include Magisk..
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Installing TWRP may void warranty.
Downloads Update
TWRP and Disable_Dm-Verity_ForceEncrypt
twrp_A50sOS10MagiskPatched4GSIRom.tar for rooting GSI ROM, it does not work for Stock ROM
Installation
1. Make sure the bootloader is unlocked, OEM unlock option is grey out
2. Enter Download Mode : Turn Power Off. Press and hold Volume Up key + Power Key, When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears. Wipe data / factory reset.* Select Reboot to bootloader.
3. Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
4. Flashing twrp_A50s_OS10.tar as AP in ODIN,
5. Connect phone to computer then click start.
6. Magisk is now successfully flashed to your device! Several steps before you can properly use the device.
7. DO NOT SKIP THIS STEP! Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
8. Select Wipe -> Format data.
9. Copy Disable_Dm-Verity_ForceEncrypt_01.14.2020.zip to phone
10. Install Disable_Dm-Verity_ForceEncrypt_01.14.2020.zip
11. Select Reboot to System
12. Done!
Video Install Instructions https://youtu.be/b9czi6MpVeQ
Magisk root does not work right now, Boot loop issue
Contributors
halcyon441 and redymedan
Source Code: https://github.com/halcyon441-png/android-10
Created 2020-05-12
UPDATE: 2020-05-21
im proud of you. send me what you edit, i need for educational purpose.
do a reserved reply or two. you will need it for update and bugs.
halcyon441 said:
im proud of you. send me what you edit, i need for educational purpose.
Click to expand...
Click to collapse
1. Fix error message "unable to find partition for path /system_root" change recovery.fstab line
/system ext4 /dev/block/platform/13520000.ufs/by-name/system flags=display="System";backup=0 to
/system_root ext4 /dev/block/platform/13520000.ufs/by-name/system flags=display="System";backup=0
Code:
/boot emmc /dev/block/platform/13520000.ufs/by-name/boot
/cache ext4 /dev/block/platform/13520000.ufs/by-name/cache flags=backup=1;
/data f2fs /dev/block/platform/13520000.ufs/by-name/userdata
/efs ext4 /dev/block/platform/13520000.ufs/by-name/efs flags=backup=1;display="EFS"
/modem emmc /dev/block/platform/13520000.ufs/by-name/radio flags=backup=1;display="Modem Firmware"
/product ext4 /dev/block/platform/13520000.ufs/by-name/product flags=backup=1;display="Product"
/product_image emmc /dev/block/platform/13520000.ufs/by-name/product flags=backup=1;flashimg;display="Product Image (CSC)"
/recovery emmc /dev/block/platform/13520000.ufs/by-name/recovery flags=backup=1;flashimg
/system_root ext4 /dev/block/platform/13520000.ufs/by-name/system flags=display="System";backup=0
/system_image emmc /dev/block/platform/13520000.ufs/by-name/system flags=backup=1;flashimg
/vendor ext4 /dev/block/platform/13520000.ufs/by-name/vendor flags=backup=0
/vendor_image emmc /dev/block/platform/13520000.ufs/by-name/vendor flags=backup=1;flashimg
/misc emmc /dev/block/platform/13520000.ufs/by-name/misc flags=backup=0;display="Misc"
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg vfat /dev/block/sdf1 /dev/block/sdf flags=display="USB-OTG";storage;wipeingui;removable
2. Fix Stuck on Boot logo ( Samsung Logo )
add mkshrc file to etc folder
Code:
# Copyright (c) 2010, 2012, 2013, 2014
# Thorsten Glaser <[email protected]>
# This file is provided under the same terms as mksh.
#-
# Minimal /system/etc/mkshrc for Android
#
# Support: https://launchpad.net/mksh
: ${HOSTNAME:=$(getprop ro.product.device)}
: ${HOSTNAME:=android}
: ${TMPDIR:=/tmp}
export HOSTNAME TMPDIR
if (( USER_ID )); then PS1='$'; else PS1='#'; fi
PS4='[$EPOCHREALTIME] '; PS1='${|
local e=$?
(( e )) && REPLY+="$e|"
return $e
}$HOSTNAME:${PWD:-?} '"$PS1 "
3. I use Disable_Dm-Verity_ForceEncrypt
make a pull request on my source. i will update it. please note that you may have to update your TWRP soon because i will fix some errors.
halcyon441 said:
make a pull request on my source. i will update it. please note that you may have to update your TWRP soon because i will fix some errors.
Click to expand...
Click to collapse
I don't have account on github, you can update it by your self. That is not my TWRP that is yours
good afternoon. you can do twrp on samsung a30s fn / ds. android 10? The site 4PDA is empty, no one can overcome this obstacle.
Sent from my SM-A307FN using XDA Labs
Android 9
Anyone have custom rom for android 9 and are disable dm verity force encrypt work on android 9
Thanks for your work sir, now we are in way of making custom rom and I can't wait to install custom rom for our a50s. By the way sir, is it ok to install magisk? There will be no issue??
kdotxallentheman said:
Thanks for your work sir, now we are in way of making custom rom and I can't wait to install custom rom for our a50s. By the way sir, is it ok to install magisk? There will be no issue??
Click to expand...
Click to collapse
Can you build custom rom?
Magisk is not working yet
Good job sir...
NikkoVn said:
Can you build custom rom?
Magisk is not working yet
Click to expand...
Click to collapse
You can flash tremble rom.
kdotxallentheman said:
Thanks for your work sir, now we are in way of making custom rom and I can't wait to install custom rom for our a50s. By the way sir, is it ok to install magisk? There will be no issue??
Click to expand...
Click to collapse
I have added TWRP with Magisk Patched and It's only work for gsi rom LineageOS etc
redymedan said:
I have added TWRP with Magisk Patched and It's only work for gsi rom LineageOS etc
Click to expand...
Click to collapse
Try another A50S twrp from telegroup @ULtimaTe_Pie2
gcam for samsung a50s i want camera use for night mod
nikkali25 said:
You can flash tremble rom.
Click to expand...
Click to collapse
I like customs rom bro
stuck
i cant flash stock firmware using odin...stuck in download mode..plz help
---------- Post added at 02:37 PM ---------- Previous post was at 02:34 PM ----------
Advarun said:
i cant flash stock firmware using odin...stuck in download mode..plz help
Click to expand...
Click to collapse
in download mode screen, it says.. "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4 , BINARY:3 pit_flash_binary - unsupported"
Advarun said:
i cant flash stock firmware using odin...stuck in download mode..plz help
---------- Post added at 02:37 PM ---------- Previous post was at 02:34 PM ----------
in download mode screen, it says.. "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4 , BINARY:3 pit_flash_binary - unsupported"
Click to expand...
Click to collapse
It fails because you are flashing a firmware older than what your phone had previously. Download the latest firmware and it will flash successfully. You can download from SamFirm it will give you latest one for your region
kamwash said:
It fails because you are flashing a firmware older than what your phone had previously. Download the latest firmware and it will flash successfully. You can download from SamFirm it will give you latest one for your region
Click to expand...
Click to collapse
:victory: worked...thanks a lot