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...
Related
Latest TWRP v3.0.2-1 for the Samsung Galaxy SM-A510
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Flash with Odin 3.10.7 using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
twrp_3.0.2-1_sm-a510
TO ROOT
Flash the file below in twrp.
DO NOT LET TWRP ROOT YOUR DEVICE WHEN IT ASKS. USE ONLY THE FILE BELOW:
https://download.chainfire.eu/921/SuperSU
NOTE: ON SOME ANDROID 5.1.1 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.
Device Tree: Coming soon
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
root for Samsung Galaxy SM-A510FD
murtada_1989a said:
root for Samsung Galaxy SM-A510FD
Click to expand...
Click to collapse
Post #22
http://forum.xda-developers.com/showthread.php?p=65301392
Please guys can I have some feedback on this? I don't own this device.
A710F/FD already confirmed working.
I will try this but can i when it fails just use odin to go back to stock rom?
franzerelli said:
I will try this but can i when it fails just use odin to go back to stock rom?
Click to expand...
Click to collapse
Yep just odin back the stock firmware or you can wait until later and I will post the stock recovery.
It's highly likely you will have no issues however.
confirmed working. Thanx ashyx. You are the greatest.
franzerelli said:
confirmed working. Thanx ashyx. You are the greatest.
Click to expand...
Click to collapse
No worries thanks for the confirmation.
failed
flashed #twrp but failed with an error
"Custom Binary(Recovery) Blocked By Frp Lock"
You need to enable OEM unlock in developer settings.
Sent from my HTC One_M8 using XDA Free mobile app
Will this work on a510y?
Sent from my SM-A510Y using Tapatalk
ashyx said:
You to enable OEM unlock in developer settings.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
thanks for the reply.
but the device is already locked [FRP]
i tried OTG method.
it's not working out.
and i need twrp to perform FRP unlock.
please let me know if you know any other method to unlock FRP.
ZaaherAnsari said:
thanks for the reply.
but the device is already locked [FRP]
i tried OTG method.
it's not working out.
and i need twrp to perform FRP unlock.
please let me know if you know any other method to unlock FRP.
Click to expand...
Click to collapse
Flash the stock firmware that will get rid of the FRP Lock.
Then make sure you disable it in developer settings.
Is it possible to have TWRP 3.0.0-0 for GALAXY A7(2016) SM-A710Y? Thanks.
Samtinker said:
Is it possible to have TWRP 3.0.0-0 for GALAXY A7(2016) SM-A710Y? Thanks.
Click to expand...
Click to collapse
You're device has the same specs as the sm-a710f.
All the 710 models use the same device code a7xelte.
It highly likely that TWRP will work for any a710.
I only append the model number with F/FD as they are the only ones to have been tested.
If your worried then download the stock firmware first as a backup. However I'm quite confident you won't need it.
If you do go ahead post back with your results.
ashyx said:
You're device has the same specs as the sm-t710f.
All the 710 models use the same device code a7xelte.
It highly likely that TWRP will work for any T710.
I only append the model number with F/FD as they are the only ones to have been tested.
If your worried then download the stock firmware first as a backup. However I'm quite confident you won't need it.
If you do go ahead post back with your results.
Click to expand...
Click to collapse
Hi ashyx,
I succeeded to flash twrp_2.8.7.1_LL_5.1.1_t710.tar with Odin, but can't enter TWRP recovery. I got message "Recovery is not Seandroid Enforcing". Any other versions I can try? Thanks.
My firmware is A710YZTU1AOL8 Android 5.1.1.
---------- Post added at 03:41 PM ---------- Previous post was at 03:12 PM ----------
Samtinker said:
Hi ashyx,
I succeeded to flash twrp_2.8.7.1_LL_5.1.1_t710.tar with Odin, but can't enter TWRP recovery. I got message "Recovery is not Seandroid Enforcing". Any other versions I can try? Thanks.
My firmware is A710YZTU1AOL8 Android 5.1.1.
Click to expand...
Click to collapse
Hi ashyx,
I made the mistake. I flashed the wrong TWRP. Now it's no problem to enter TWRP 3.0.0-0 for sm-a710f. Thanks.
Everybody try this? I fear it's not working :'(
Samtinker said:
Hi ashyx,
I succeeded to flash twrp_2.8.7.1_LL_5.1.1_t710.tar with Odin, but can't enter TWRP recovery. I got message "Recovery is not Seandroid Enforcing". Any other versions I can try? Thanks.
My firmware is A710YZTU1AOL8 Android 5.1.1.
---------- Post added at 03:41 PM ---------- Previous post was at 03:12 PM ----------
Hi ashyx,
I made the mistake. I flashed the wrong TWRP. Now it's no problem to enter TWRP 3.0.0-0 for sm-a710f. Thanks.
Click to expand...
Click to collapse
You do realise you've posted in the sm-a510 thread and not sm-t710?
Can you post your success here:
http://forum.xda-developers.com/showthread.php?t=3314403
ashyx said:
You do realise you've posted in the sm-a510 thread and not sm-t710?
Can you post your success here:
http://forum.xda-developers.com/showthread.php?t=3314403
Click to expand...
Click to collapse
My device is A510FD and i flash TWRP 3.0.0 successed. But go to recovery it's show the fault Recovery is not Seandroid Enforcing
Tuanrangsut1 said:
My device is A510FD and i flash TWRP 3.0.0 successed. But go to recovery it's show the fault Recovery is not Seandroid Enforcing
Click to expand...
Click to collapse
That's not a fault it's normal.
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
34.3.A.0.244 - 7.1.1 - 09 NOV 2017 update
F5122 IS AT https://mega.nz/#F!DEQykYjL!Vux2m1_Rug9hg9B4_q0ifw
F5121 .. https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ (THANKs @eagleeyetom )
both f5121/5122 folders have 1 kernel image,
FLASH THE ROM
FLASH THE KERNEL,
FLASH TWRP,
BOOT IN TO TWRP .
FLASH MAGISK or SUPERSU, VIA FLASHABLE ZIP
BOOT THE DEVICE
IF YOU HAVE FLASHED MAGIK THEN INSTALL MAGIS MANAGER
MAGISK POST https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
CHAINFIRE SUPERSU ZIPs LATEST AT https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
PREVIOUS KERNELS
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
https://forum.xda-developers.com/xperia-x/development/rooted-kernels-f5121-f5122-34-3-0-238-t3683968
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
https://forum.xda-developers.com/xp...ted-kernels-f5121-f5122-34-3-0-224-8-t3669793
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5121-f5122-34-3-0-217-7-t3654368
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
siggi77 said:
Hi,
Thx for this new update but i dont found the kernel in the package.
I found the img.clean, twrp, fsc, sr5 and magisk but no kernel..
So what can i do for F5121!?
Siggi
Click to expand...
Click to collapse
on https://mega.nz/#F!CBhRyR7Z!L5uo_GWiCzXcNWQaZGJ9bQ
the F5121_34.3.A.0.244_su.img is the kernel
just flash and your device will wakup ROOTED.
twrp 3.1.1 problem
on my 64 GB xperia X F5122
1. after flashing ROM if
2. I flash twrp 3.1.1 it will
3. make my system partition 40GB and i get only 20gb workable
I tried many things but flashing recovery via adb always create this problem and if i BOOT the device before going in to the partition , sony stockrom makes internal storage encrypted which then twrp3.1.1 is unable to read
plz help
@serajr @shoey63 @munjeni
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
siggi77 said:
Hi,
Ok thx this package is complete...
Great
Siggi
---------- Post added at 09:37 PM ---------- Previous post was at 09:33 PM ----------
Hi,
OK this file is not a .img:
F5121_34.3.A.0.244_su is the kernel but isn´t a .img
Please make a new package
Siggi
---------- Post added at 10:22 PM ---------- Previous post was at 09:37 PM ----------
In the package for F5122 is the corret .img, but for F5121 not or is the same?
Click to expand...
Click to collapse
i am sorry,
i have fixed it
please check again
thank you
Hi, great
thx for the new package
Siggi
clean kernel image is drm fixed??
kloroform said:
clean kernel image is drm fixed??
Click to expand...
Click to collapse
yes sir, it is,
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
xxarigattoxx said:
That is little bit complicated we need a good guide
---------- Post added at 02:56 PM ---------- Previous post was at 02:31 PM ----------
I flashed rom>kernel with su then flashed twrp.
Later I flashed the magisk.zip and reboot the system but everytime its entering the twrp screen.
Wont going bootanimation and starts the phone. Just twrp screen.
OH GOD I SOLVED THIS. HERE MY SOLUTION:
First things first, I WANT TO FLASH MAGISK AND NO MORE USE SUPERSU, THATS I WANT. IF YOU WANT TO USE MAGISK HERE IS MY SOLUTION.
1. Flash the stock rom on the post. (up)
2. When flash finished, boot the phone and close the phone.
3. Flash the clean kernel with flashtool.
4. Boot the phone, is everything okay, close again.
5.a So there is little bit strange, open adb on windows (yes really. dont use flashtool this time)
5.b Flash the twrp-3.1.1-suzu-2017.07.16.img from this address: https://androidfilehost.com/?w=files&flid=197369 (on the middle)
5.c the command is here "fastboot flash recovery twrp-blablabla.img"
6. and type "fastboot reboot" will boot up your phone.
7. If its really open, -not stuck at the sony logo or everytime goin in twrp- you did! congrats!
I hope it help you
Click to expand...
Click to collapse
the guide is here
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
also twrp3.1.1 works best at 32gb variant by giving 20gb workable and putting systemparittion to 12gb
however it does the SAME with 46gb variant and give only 20gb workable and put system partition 40 gb
thats why for 64gb variants i don't recomend using twrp3.1.1
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Jomoteck said:
Hi, when you say flash the rom you mean in Flashtool ? There is no twrp flashable rom here ?
Click to expand...
Click to collapse
once you flash the modified kernel with supersu then there is no need for twrp, simply boot your device and it will wakeup rooted.
however if you wana use magisk and your device is 64gb then i highly recommend you to do this
1. flash rom
2. flash the modified kernel
3. boot the device and go thru sony setup , give google account and let it sync
4. switch off mobile after 15 or so mins
5. flash twrp3.1.1 suzu (given in the mega link, in the OT)
6. HOLD power and VOLUME DOWN BUTTON till PINK led comes on sonylogo and you are taken to twrp, keep system readonly and flash magisk ( via otg or if you had it in your sd card prior) ( at this point you may flash other zips also, if there are any)
7. twrp may give you error such as... cannot mount internal storage etc, just ignore.
8. after flashing, switchoff mobile, and boot it into system.
9. for safty purposes, you can erase twrp by connecting device in fastboot mode and executing following command
Code:
fastboot erase recovery
now you can ask me why i let you boot your device first. normally its unprecedented.
the reason i explain here
https://forum.xda-developers.com/showpost.php?p=74573987&postcount=121
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
nova001 said:
hello
i have 34.3.A.0.217 rom with root. how can i update 34.3.A.0.244 ? can you help me anyone ?
Click to expand...
Click to collapse
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
YasuHamed said:
1. download 34.3.A.0.244 using xperifirm under flashtool
2. flash it using flashtool (please google the tutorial ) (wipe everything while flashing
**** TAKE BACKUP of EVERYTHING (DATA) ****
Click to expand...
Click to collapse
thats oke, but we cant dowload anywhere? only xperifirm ?
nova001 said:
thats oke, but we cant dowload anywhere? only xperifirm ?
Click to expand...
Click to collapse
Xperifirm is the best
Other servers i cant guarantee
I was able to flash rom, flash kernel, flash root and boot the phone and was able to use it.
PROBLEM:
- It heats up during use.(FIXED) constant mobile data was the cause..
- Everytime I lock the screen my mobile data turns on when I unlock the SCREEN. (FIXED) disable find my device as administrator.
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
cyanides13 said:
HI question does FCS_thermal_Xperia_X_v1.3.zip work for Nougat?
Click to expand...
Click to collapse
Yes it works I use it actually.
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 ?
Custom TWRP Recovery for Nokia 4.2 codename Panther
Firmware : 136
For September Security patch
Link: https://drive.google.com/drive/folders/1tqQVK_IAQLSq2RDHhPD_p3v7IEXkAwbI?usp=sharing
Request: Unlocked bootloader
How to install:
Go to bootloader/fastboot mode:
fastboot flash boot "path to twrp.img"
Control volume to "reboot recovery mode"
Done
It no support decrypt data at the moment. So,you need format data
fix slot on sep twrp
Added a/b slot. You can flash system,boot to a or b if you want
Update link tomorrow
Good news: Tree ready for build rom
Bad news: doesnt boot???
Hello, the TWRP link above is no longer available. Can you send it to my mailbox? Thank you! Email account: [email protected]
clurs said:
Hello, the TWRP link above is no longer available. Can you send it to my mailbox? Thank you! Email account: [email protected]
Click to expand...
Click to collapse
I sended a friend request in qq,check it
Is there a way to use this on october patch?
thegamingcat13 said:
Is there a way to use this on october patch?
Click to expand...
Click to collapse
I cant test it. My computer cant backup oct patch. I think you need ask calyx for it
thinhx2 said:
I cant test it. My computer cant backup oct patch. I think you need ask calyx for it
Click to expand...
Click to collapse
Ok thank you
Hello,
I want to port TWRP to my Nokia 3.2. how did you port it? Or what's the procedure?
Thanks
s3tupw1zard said:
Hello,
I want to port TWRP to my Nokia 3.2. how did you port it? Or what's the procedure?
Thanks
Click to expand...
Click to collapse
send me boot.img of 4.2
Hi, I've uploaded the firmware here:
https://drive.google.com/file/d/1jJkDi807fagKFJ1ggzFY1Lc4TGY-llEB/view
If you don't want to download the whole firmware I'll upload the boot.img file when I'm at home on my computer.
Thanks
---------- Post added at 10:07 AM ---------- Previous post was at 09:57 AM ----------
Btw. Could you write a guide on how to Port TeamWin for Android One devices? I think it would be interesting for other people who don't have TeamWin for their Android One devices.
---------- Post added at 10:42 AM ---------- Previous post was at 10:07 AM ----------
I got the boot img from my system using dd. I packed boot_a and boot_b into a rat file
https://drive.google.com/file/d/1-DRQ_LRdEMez-Qpj2jboJsDysG5awl_b/view?usp=drivesdk
Hi,
how did you port TWRP to Nokia 4.2 ? Is there a guide on how to do this ?
bro can u please how to use the files??!!
Any news on this
Which variants of the 4.2 will this work on?
doesnt work just stuck on twrp loading
Hi everyone. I am trying to install twrp but stuck at fastboot menu.
I have unlocked bootloader, because it says device state: unlocked. Then i am trying to fastboot flash but get error. I am trying flash:raw and set_active a and b. I try boot recovery.img. no matter what I do the phone restarts, shows android logo and then go back to fastboot. Fastboot devices shows the phone. What am I missing? Wrong files, wrong order, any better guide or files to test? I am not sure what I have done also flashed a vbmedia file
Android 10 was released today for Galaxy M30 (INS) ,
Here i am posting 2 links
1. For users Who Just Want Stock Rom as it is
2. For Users Who Need rooted stock rom
Steps :
1. Download Zip and Extract
2. For without root users just flashing via odin would be enough
3. Progress if you wana root
4. when your done with setting up your stock rom , go into Software info and activate developer option
5. Turn on OEM unlock and turn off Auto Update System
6. Boot into download mode again
7. open odin and turn off auto reboot
8. Choose the magisk patched zip and extract
9. In Odin under AP choose this tar and flashed
10. now be careful and press volume down and power till your device boots and quickly press volume up and power to boot into recovery mode
11. Wipe Data in stock recovery and reboot and your good to go
So Here's a Grive Link
Both Firmwares need to be extracted and flashed via odin
Unrooted Stock Firmware
Stock Unrooted
Magisk Rooted
Magisk Rooted
XDAevDB Information
ANDROID 10 (ONEUI 2) Stock Firmware and Rooted (M305FDDU3CSL4), ROM for the Samsung Galaxy M30
Contributors
Er. Aditya
ROM OS Version: Android 10
Thanks to ,
Samsung For Firmware
topjohnwu for magisk
reserved just in case
last one
Sorry for ignorance, but... how do I flash the stock unrooted firmware using Odin?
shrmp said:
Sorry for ignorance, but... how do I flash the stock unrooted firmware using Odin?
Click to expand...
Click to collapse
unzip the zip file and there u will find these files
AP_M305FDDU3CSL4_CL17406009_QB27774088_REV00_user_low_ship_meta_RKEY_OS10.tar.md5
BL_M305FDDU3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
CP_M305FDDU3CSL1_CP14521597_CL17406009_QB27626610_REV00_user_low_ship.tar.md5
CSC_OMC_ODM_M305FODM3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
HOME_CSC_OMC_ODM_M305FODM3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
in odin on your right you will find slots to select files
under BL choose BL_M305FDDU3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
under AP choose AP_M305FDDU3CSL4_CL17406009_QB27774088_REV00_user_low_ship_meta_RKEY_OS10.tar.md5
under CP choose CP_M305FDDU3CSL1_CP14521597_CL17406009_QB27626610_REV00_user_low_ship.tar.md5
under CSC choose HOME_CSC_OMC_ODM_M305FODM3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
make sure ur phone is in download mode and you have your drivers installed
I see, does updating with Odin erase userdata?
---------- Post added at 22:05 ---------- Previous post was at 21:08 ----------
Nevermind, I just tried flashing the update but it does not work with the SM-M305M variant. Back to waiting...
Er. Aditya said:
7. open odin and turn off auto reboot
8. Choose the magisk patched zip and extract
9. In Odin under AP choose this tar and flashed
Click to expand...
Click to collapse
But, in Magisk here, it states:
Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Will it be any issues, if we just flash the AP?
Thanks. Flashed Magisk now.
Can i simply falsh it with twrp??
i did everything correctly i'm stuck on Samsung Boot Logo
help
zer0C00L...... said:
i did everything correctly i'm stuck on Samsung Boot Logo
help
Click to expand...
Click to collapse
these steps have been tested alot of times so make sure you dont miss any
Prxtek said:
Can i simply falsh it with twrp??
Click to expand...
Click to collapse
Nope. Plus this phone does not have a TWRP for Q as of now. Moreover, please do not try any TWRP as of now.
Use ODIN only.
---------- Post added at 00:48 ---------- Previous post was at 00:46 ----------
Er. Aditya said:
these steps have been tested alot of times so make sure you dont miss any
Click to expand...
Click to collapse
By any chance you have a list of bloatwares to remove?
vdbhb59 said:
Nope. Plus this phone does not have a TWRP for Q as of now. Moreover, please do not try any TWRP as of now.
Use ODIN only.
---------- Post added at 00:48 ---------- Previous post was at 00:46 ----------
By any chance you have a list of bloatwares to remove?
Click to expand...
Click to collapse
with root you can simply use titanium backuo and remove according to you
Er. Aditya said:
with root you can simply use titanium backuo and remove according to you
Click to expand...
Click to collapse
I tried, and I end up in bootloop, millions of times..
Trouble is, some inbuilt apps are bound with /system, and unable to get through. Moreover, you cannot imagine, I have been into bootloop 11 times since last evening.
So, if a list is present, I would be happy.
Last thing, did you notice, even if you have not logged into google account, it still keeps installing those 5 bloody recommended apps.
vdbhb59 said:
I tried, and I end up in bootloop, millions of times..
Trouble is, some inbuilt apps are bound with /system, and unable to get through. Moreover, you cannot imagine, I have been into bootloop 11 times since last evening.
So, if a list is present, I would be happy.
Last thing, did you notice, even if you have not logged into google account, it still keeps installing those 5 bloody recommended apps.
Click to expand...
Click to collapse
thats google preload stuff but happens just once , i havent faced this issue yet between make a list of apps your removing il take a look
and il work on a debloated version once i get some time
Please upload to one of the alternative sites (google quota block)
Whats the deal with U3, U4, U5 and greater version of bootloaders with Exynos chipset?
I know Samsung has locked bootloaders of USA snapdragon variants, but can all exynos chip-set ones be unlocked?
Or till U2 bootloader can be unlocked and can have root but above U3 cannot be rooted?
It's so confusing, Please someone Help me
Posted for the latest Patched Magisk here: https://forum.xda-developers.com/ga...d-firmware-t4026819/post81336955#post81336955
---------- Post added at 01:52 ---------- Previous post was at 01:52 ----------
For guides: https://forum.xda-developers.com/galaxy-m30/how-to/guide-galaxy-m30-recovery-edl-modes-t4020231
The M305M variant firmware with Android 10 can be found on sammobile. Can it be flashed without regard for the country it was made for or it has to be the same as the original firmware?
kesleyf said:
The M305M variant firmware with Android 10 can be found on sammobile. Can it be flashed without regard for the country it was made for or it has to be the same as the original firmware?
Click to expand...
Click to collapse
Can be used. However ensure you have mounted system.
You may lose data due to that. So ensure to have a backup.