[RECOVERY]TWRP 3.0.3-1 unofficial [SM-T700/T705/800/805/807] - UPDATE 10/02/2017 - Galaxy Tab S Android Development

UPDATE 10/02/2016- New version of TWRP has been released v3.0.3-0. See below:
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
I have updated versions SM-T800/805 with new builds. TWRP is now v3.0.3-1
TWRP OFFICIAL APP RELEASED: https://twrp.me/app/
Fixes:
Download mode now available in REBOOT options.
Root Shell now available in ADB.
Radio and Recovery backup.
System image backup/restore
Factory image flashing.
Supersu root option removed. This is to pre-empt the upgrade to MM which would cause a bootloop.
MTP fix - MTP now finally working in recovery.
Note: On my PC MTP works perfect in windows 7, but on Windows 8.1 was a little quirky. If you get a USB DEVICE NOT RECOGNISED error after enabling MTP, disable then quickly re-enable MTP and this should fix it.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
UPDATE 5/3/16:
Have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore. As far as I know the Tab S is the only device supporting this at the moment.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP_3.0.2-1-T700
TWRP-3.0.2-1-T705
TWRP-3.0.2-1-T800
NOTE: Certain models of the T800 version have a bug at the moment where the screen will be blank when booting to TWRP recovery until the screen timeout kicks in. After that pressing any button will show the screen. As a work around setting the timeout to 15 secs will shorten the wait.
TWRP-3.0.2-1-T805/T807(ATT or Verizon not supported)
twrp_3.0.3-1_sm-t800_10217
twrp_3.0.3-1_sm-t805_10217
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.

gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
As long the bootloader is unlocked, and if someone has an stock recovery pulled from it, then he could be twrp for it

Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.

gcappa said:
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
Click to expand...
Click to collapse
If you have the firmware downloaded just right click on the md5 and open it with 7zip or Winrar, then simply just drag the recover IMG to your desktop and send it here(or link to download). I'm not going to go to much in depth as I don't want this thread to be filled with non related to twrp stuff. I'm also unsure if he has time but ash is one good recovery builder

Ok, I'll do all that when I get home and upload a link.

gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
Should be possible as long as the right files are available. This is a snapdragon 805 device?
Seeing as I don't have this device you would have to test the builds and I would need some info from the device. Might take a few builds to get a proper working one.
I take it you are currently rooted? Also could you send me a link to the version of cwm you are using?

gcappa said:
Ok, I'll do all that when I get home and upload a link.
Click to expand...
Click to collapse
Is the sm-n9100 the Chinese version Note 4 Duos?
The TWRP recovery below is for this version, please test:
twrp-2860-n1900
Stock Recovery:
Stock-recovery-n1900
Note: You take responsibility for testing this.

Failed to flash on my T-800.

dwarfer66 said:
Failed to flash on my T-800.
Click to expand...
Click to collapse
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?

ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
Click to expand...
Click to collapse
Thank again ashy this is awesome, keep up the good work.
Confirmed its working T800 5.0.2

ashyx said:
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
Click to expand...
Click to collapse
This unofficial TWRP fails to flash, just says failed when trying to install.

dwarfer66 said:
This unofficial TWRP fails to flash, just says failed when trying to install.
Click to expand...
Click to collapse
Again, you need to confirm what your exact model is and build number. As you can see from the post above it flashes fine on a T800.
Post a screenshot of the issue with Odin.

It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking

RDDraco said:
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
Click to expand...
Click to collapse
Did you update the supersu app as requested? You need to post a screenshot of root validator so I can see the status of root.
You may just need to select full unroot from settings in the supersu app then boot into twrp and run the root process again or flash the supersu2.46 zip.
Also regarding wiping cache, it can sometimes take longer depending on what's in cache at the time. It may seem like it's hung but eventually completes. On occasion I've seen it take up to a few minutes to wipe.

Just saying that root is broken on custom roms such as iron rom. It's an known issue with touchwiz lollipop roms.
-DUHA

So it's a Rom issue?
What's the actual problem?
Isn't the Rom already rooted, unusual for a custom Rom to not be prerooted?

Guess that explains why it wasn't working. (Tkkg1994 managed to get IronRom working with root in v2.0.5) so its fine for me now.

RDDraco said:
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
Click to expand...
Click to collapse
Looked into this issue and have fixed it. Wipe Cache should work now.

ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
NOTE: If after using TWRP to root you don't see the notification to update Supersu, just install the latest Supersu app from Play. Check root status with Root Validator
Supersu
Root validator
Click to expand...
Click to collapse
Just today, I rooted my new Tab S (SM-T800) AFTER allowing it to OTA update to Android 5.0.2. After that, I used Odin to flash the latest version of CWM I could find for this device, and that trashed recovery altogether. Couldn't get into recovery at all. So I used Odin again to flash TWRP 2.8.6.0 and had recovery back, BUT I kept getting notifications that SuperSU needed to be updated. What I did then was flash "BETA-SuperSU-v2.48.zip", and that resolved the "update needed" problem, and all seems to be working smoothly now. :good:
I'm running stock Touchwiz Lollipop 5.0.2 . Haven't tried changing ROM's, but don't really have a desire to do that just yet.

Related

[PSA][HOW-TO] Recover from BootLoops caused by SuperSU

Hey there,
Since Lollipop is out and most of you are Rooting it, There's a chance you might run into a BootLoop after flashing the SuperSU through TWRP/CWM. And when this happens, New users mostly flash their Stock Firmware and Restart the process all over again. This is not necessary and can be avoided by following these steps:
RECOVER FROM BOOTLOOP CAUSED BY SUPERSU:
Re-Boot into Recovery mode (TWRP/PhilZ) by Holding the Power and Volume Down button
Select Wipe > Advanced Wipe > Check only Dalvik Cache & Cache
Swipe to Clear the Dalvik Cache and Cache
Re-Boot! (Can take ~6-7mins)
Done!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
CREDITS:
Tip @ joel-n1 posted here.
Click to expand...
Click to collapse
Hope this helps! Thanks
KrishnaSagar said:
Hey there,
Since Lollipop is out and most of you are Rooting it, There's a chance you might run into a BootLoop after flashing the SuperSU through TWRP/CWM. And when this happens, New users mostly flash their Stock Firmware and Restart the process all over again. This is not necessary and can be avoided by following these steps:
RECOVER FROM BOOTLOOP CAUSED BY SUPERSU:
CREDITS:
Hope this helps! Thanks
Click to expand...
Click to collapse
Excellent PSA! I followed your instructions and this seems to have solved my bootloop problems. XT1063 with 5.0 22.21.16.
Thanks man! I rooted it before and had to restore the backup. I'll try now that I'm armed with this info
UPDATE: Can confirm that the method is working. I rooted the phone and the phone went into a boot loop. Cleared dalvik and cache, and voila! the phone booted up.
mahendru1992 said:
Thanks man! I rooted it before and had to restore the backup. I'll try now that I'm armed with this info
UPDATE: Can confirm that the method is working. I rooted the phone and the phone went into a boot loop. Cleared dalvik and cache, and voila! the phone booted up.
Click to expand...
Click to collapse
Glad to help I had my fair share of Bootloops and dont want them to happen again. I can now confidently flash any supersu beta without fear.
Yes..to erase cache, saves alot of flashing..lol
Anytime the device is "stuck" in a bootloop, or stalls on the "unlocked bootloader" screen, power down, boot to recovery, then erase cache..saves me 90% of the time..
sent by my:
Lollipop 5.0_22.11.6 (w/Root)
TWRP v2.8.0.1-titan
UPDATE-SuperSU-v2.16
XT1064 Moto G (2nd Gen.)
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Will doing this delete my data in my phone?
wiping cache&dalvikCache is not working, my phone will boot, optimize apps and works fro like 5 seconds and then it reboots and its stuck back on logo bootloop
help?
ZeroGoCZ said:
wiping cache&dalvikCache is not working, my phone will boot, optimize apps and works fro like 5 seconds and then it reboots and its stuck back on logo bootloop
help?
Click to expand...
Click to collapse
In this case you should flash the firmware again.
Wolfcity said:
In this case you should flash the firmware again.
Click to expand...
Click to collapse
Okay, but how do I root my phone then? What is causing the bootloops?
ZeroGoCZ said:
Okay, but how do I root my phone then? What is causing the bootloops?
Click to expand...
Click to collapse
I suspect you've used the wrong superSU version. What firmware are you on and how did you root the first time? Did you use systemless root? What's the number of the superSU version?
Sent from my Moto G 2014 using XDA-Developers mobile app
Wolfcity said:
I suspect you've used the wrong superSU version. What firmware are you on and how did you root the first time? Did you use systemless root? What's the number of the superSU version?
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
My phone is Leagoo Alfa 1 running lollipop 5.1, stock rom and kernel, twrp v3.0, unlocked bootloader. Tried to flash supersu 2.46, then beta 2.62 and then 2.66. I did not forget to wipe cache+dalvik cache. None of these work. I do not know what systemless root it. (Going to look on it) My last root was on android 4.4.2, so I am new with lollipop.
Edit: This was was never rooted before, I just got it a few days ago.
ZeroGoCZ said:
My phone is Leagoo Alfa 1 running lollipop 5.1, stock rom and kernel, twrp v3.0, unlocked bootloader. Tried to flash supersu 2.46, then beta 2.62 and then 2.66. I did not forget to wipe cache+dalvik cache. None of these work. I do not know what systemless root it. (Going to look on it) My last root was on android 4.4.2, so I am new with lollipop.
Edit: This was was never rooted before, I just got it a few days ago.
Click to expand...
Click to collapse
You know that this is the Motorola Moto G 2014 forum here?
So I dont´t really know what´s the best for your device. Maybe you should have a look in your devices forum (if there is one) or ask in the superSU thread:
http://forum.xda-developers.com/showthread.php?t=1538053
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I had good experience with the BETA-SuperSU-v2.62-3-20151211162651.zip but I´m running a 6.0.1 custom rom.
yeah, I am aware of the fact, that this is moto g 2014, sorry for bothering :|
Anyway, looking at the systemless root - it works on lollipop 5.1.1 and up. Unfortunately my thingy is 5.1 so, no luck there~ *****me*
Thank you for your time and your answer. My posts are mostly ignored...
mali_ said:
Hey! My moto g2 2014 is stuck in logo screen after rooting with supersu 2.78 stable. Which version should I use? I'm unable to root it. Please help.
Click to expand...
Click to collapse
Some more info please. Which revovery? What kind of ROM?
I had sucess on my ROMs flashing BETA-SuperSU-v2.62-3-20151211162651.zip. After flashing you can upgrade it via playstore to 2.78.
Depending on the ROM you´re using you can boot into recovery and reflash it to fix the bootloop.
help bootloop htc one m7
i have an htc one m7,android 5.0.2 and rooted it (CWM-SuperSU-v1.30).then i flash it with BETA-SuperSU-v2.30.
now it cause a bootloop.so i wipe cashe and delvik.but has no effect.
thanks for any help.
I wiped the cache and it's still stuck in the boot loop,I used the latest supersu version and also the latest of twrp
Just use the SuperSU Uninstaller ZIP, wipe your dalvic cache and reboot.^^
Transfer it in TWRP on your internal storage via ADB.
ZIP Download: http://forum.xda-developers.com/attachment.php?attachmentid=3528363&d=1446472307
Hi,,Plz help me.. i am a beginner in rooting.. i have unlocked bootloaded for moto g3, flashed logo.bin to remove warning message,installed twrp , after that i have tried to root using supersu.zip ..Now my phone is stuck in bootloop...What should i do..Plz give suggestion..
i have used below files
twrp-osprey-3.0.2-r1_2
UPDATE-SuperSU-v2.65-20151226141550
logo.bin
all are downloaded from XDa forum itself
i installed Mokee rom60.1 release one on my redmi 2. I enabled root access in developer options but when checked with root checker, it showed not rooted. So, i flashed supersu zip v2.46 thrpugh twrp and wiped cache and dalvik cache.
now i reboot the system but nothing is going on except mokee logo. it is showing more than half an hour. please help me
Reflash everything, before flashing supersu, do it by these steps (taken from here)
1. Don't use the zip method. Download the backup instead and restore it (don't forget to backup your main rom).
2. Download the latest SuperSU zip here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
It must be 2.67+ or higher.
3. In TWRP, go to Advanced>Terminal Command, don't select any folder and type the following commads (you have to clean the textbox in order to type another one):
touch /data/.supersu
echo SYSTEMLESS=true > /data/.supersu
To verify that you made it correctly type
cat /data/.supersu
If you have at hand a desk with adb you can do this quicker using twrp's adb:
touch /data/.supersu && echo SYSTEMLESS=true > /data/.supersu && cat /data/.supersu
If the above commands return
SYSTEMLESS=true
Then it's okay, you can proceed.
3. After that, install the SuperSU zip. It must be the 2.67 version (or higher).
4. Reboot system, if TWRP asks to install root, don't let it and press Reboot System.

[GUIDE] How to flash the COS 13 update. Even if you get the release keys error

Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.

[RECOVERY][ROOT]TWRP 3.3.1-1 Samsung Galaxy J3 2017 SM-J330F/J330FN/J330G/DS

Unofficial release -TWRP recovery for the Galaxy J3 2017 - SM-J330F/FN/FZ/G/DS EXYNOS 7570
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance
UPDATE 10/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status: Beta
Update 15/9/2018
TWRP 3.2.3-1 OO build released.
Current status: Stable
Update 27/1/2018
TWRP 3.2.1-1NN build released
Current status: Stable
Update 23/11/2017
TWRP 3.1.1-1 NN build released.
Current status: Stable
Features:
TOUCHSCREEN working
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.[/B]
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
NOTE: ON 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.
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1)
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports 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 POWER + HOME. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1, THE DEVICE WILL AUTO BOOT TO RECOVERY)
5. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
DOWNLOAD:
twrp_3.3.1-1_sm-j330x_13819
twrp_3.2.3-1_j330_13918
twrp_3.2.1-1_sm-j330f_270117
twrp_3.1.1-1_sm-j330f_231117
Nougat Root instructions:
Install latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, disable dmverity and mount internal storage:
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install the boot image patch.
Boot image patch
no-verity-no-encrypt_ashyx
5. Install Magisk(if root is required)
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Reboot
OREO ONLY ROOT INSTRUCTIONS:
1. Install the Root patch kernel with TWRP.
J330F-FN_root_no_sim_patch
NOTE:This is a custom Oreo J330F/FN XXU3BRG3 permissive/enforcing kernel and patch built from source. It makes changes to the system partition also.
What does it do?:
*It installs a custom kernel to fix the no SIM issue when rooting.
*Patches the system to fix WIFI and Bluetooth not turning on when using custom kernels.
*Patches DM-Verity.
*Removes forced encryption and patches /data not able to be mounted (after formatting).
*Removes the SecurityLogAgent nag when using a custom kernel.
2. If you wish to mount /DATA for access to internal storage then FORMAT the /DATA partition.
3. To root install the latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
PIE ONLY ROOT INSTRUCTIONS:
To root install latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable encryption (mount DATA in TWRP) install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
Finally FORMAT /DATA in TWRP.
Reboot.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @lemlis, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
UPDATE: Touchscreen fixed
.
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
Click to expand...
Click to collapse
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Click to expand...
Click to collapse
Probably the version of SuperSu you flashed.
ashyx said:
twrp_3.1.1-1_sm-j330f_231117
Click to expand...
Click to collapse
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
lemlis said:
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
View attachment 4340464View attachment 4340476
Click to expand...
Click to collapse
Seems I didn't include my updated FSTAB in the new build. Corrected, thanks for pointing it out.
ashyx said:
Probably the version of SuperSu you flashed.
Click to expand...
Click to collapse
Yeaa you right..i use super su which remain in my memory card almost 2 years ago ???
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
BlackDragonz said:
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
Click to expand...
Click to collapse
updato.com
i cant flash super su twrp didn't show the file to flash
File to flash have to be on sd card ?
Help Me
azhar960225 said:
Help Me
Click to expand...
Click to collapse
Police. Fire or ambulance?
I Want root j3 pro 2017..but how
azhar960225 said:
I Want root j3 pro 2017..but how
Click to expand...
Click to collapse
Flash SuperSU or Magisk.
How? To Flash How? Cannot root j3 How to Flash?
7.11 Android...
arabarabow said:
twrp didn't show the file to flash
Click to expand...
Click to collapse
put zip file inside any folder.File to flash have to be in folder
Just done flashing latest build and flashed magisk, all are running fine. Tysm @ashyx !
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
arabarabow said:
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
Click to expand...
Click to collapse
Boot to TWRP and flash Supersu or Magisk. Use the three button combo.
Can i just use cf auto root to root my phone without installing a recovery? Or it's better to root using this method?

[STOCK][N][ARB01] H830 20N ZIPs + KDZ (2017-12-01 Security Patch)

First off, a HUGE thank you to @autoprime (for paving the way) and @waylo (for his assistance on getting this going after I found the KDZ)
I am currently storing these in my google drive account, so please be gentle till I have a better host location:
Below are the downloads for the LG-H83020N firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020N-Flashable.COMPLETE-ARB01.zip
As always, COMPLETE is 100% stock
Flash COMPLETE zip -> wipe cache partition -> flash Magisk ZIP (or SuperSU if you insist) to root and keep TWRP
OPTIONAL: After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks
LG-H83020N-Flashable.Bootloader-ARB01
LG-H83020N-Flashable.Modem-ARB01.zip
LG-H83020N-Flashable.Boot.zip
H830N_00_1017.kdz (HUGE Thank you to @Azul Baseem for the upload)
For instructions, follow the same instructions as you would in any other KDZ/ZIP thread. For Example
Feel free to hit thanks.
Also feel free to hit up autoprime's All in One thread HERE
Thank you very much bedwa!
Kdz link updated!
Thank you @bedwa as always.
I fear my only true contribution here is MD5 confirmation of the files:
LG-H83020N-Flashable.COMPLETE-ARB01.zip 8a49733028bef23d775bf542eb62b726
LG-H83020N-Flashable.Boot.zip ddea9d814f66266de34a154f0c7f6b41
H830N_00_1017.kdz 732b717af8d77501342be445002c4fae
Edit: Also, since someone will definitely miss it in the title, this is confirmed to still be on Anti-Rollback 1. You're free to flash back and forth between 20A if you need to Dirtycow your phone again.
Keeping me honest, I swear I'll remember them next time.
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
shinji257 said:
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
Click to expand...
Click to collapse
Fixed. That's what I get for using the copypasta method. Missed the one. :silly:
help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i had this issues when i try to flash it i already use uppercut
solved
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
abced123 said:
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
Click to expand...
Click to collapse
That would be trickier. All of these are the partition images. To make a slim zip like that I'll have to either unpack and build or unpack and attempt to repack. I might, but not likely at this time.
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
fc3211 said:
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
Click to expand...
Click to collapse
Quite welcome... It's more time consuming than hard work, but the appreciation and thanks is greatly appreciated as well.
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
nizarp said:
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Click to expand...
Click to collapse
Backup is always good, shouldn't have to restore it as it's updating from a previous version and doesn't wipe data when upgrading. But that's the correct process with or without #6.
azizo07 said:
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
Click to expand...
Click to collapse
Shouldn't, but it would always be a good idea to backup beforehand. I would however only flash the bootloader, as the boot is the kernel and will be different than what LineageOS uses though.
I just boot into TWRP and flashed the complete zip and then flashed the latest SuperSU Zip. I pressed Reboot System after that, but, I am now stuck in a boot loop. Phone shows LG logo and reboots again and again.
I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?
Sounds like you will need to LGUP or Uppercut your phone back to stock 20A. Then dirtycow back TWRP. Then try flashing the new ZIP again. Skip Supersu this time and try Magisk instead.
Thanks. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?
No, rebooting into TWRP wouldn't do anything. There's a script you might need to get into and delete prior to rebooting. But that only ensures that TWRP stays.
"After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks"
That having been said, I've done this before and STILL not had TWRP stay. Some recommend wiping /cache as well.
OR, again, use Magisk instead and don't use SuperSU.
Even if TWRP didn't stick, you should have been booting into system fine. You wouldn't be rooted, TWRP would be gone, but system shouldn't have been messed up. So something got borked, I'd have to guess, because of SuperSU.
New security patch update alert

[RECOVERY][OFFICIAL]TWRP 3.4.0.0 Recovery [m30lte]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE : TWRP FOR M30 IS NOW OFFICIAL​
I would like to thank TeamWin for their amazing work!
After a long hiatus from Android Development, I am back to the dev scene.
As usual, I am not responsible for damage to your device, you, the user is choosing to make these modifications.
Your device's warranty is VOID if this procedure is followed, Proceed at your own caution!
With the new update of Android 10 for our device SM-M305[F] / M305[M], Samsung reimplemented RMM and called it KG(KnoxGuard), there is confusion in the device community on how to install TWRP and root device.
@vdbhb59 and myself @akhil99 are actively working together to bring support to this device.
Follow these updated instructions to get TWRP working with Latest Stock Firmware.
This thread will be updated regularly.
STRONGLY ADVICE TO BACKUP DATA.
Steps to get TWRP working with stock firmware
Reported to be working with firmware w/ following details
Device: Samsung Galaxy M30 SM-M305[F] / M305[M]
BL: M305FDDU5CTF2
AP: M305FDDU5CTF2
CP: M305FDDU5CTF1
CSC: HOME_CSC_OMC_ODM_M305FODM5CTF2
Patch: 1st May 2020
Android Version: 10
One UI Version : 2.0
First of all flash completely stock firmware, you can always root with Magisk later.
If you are rooted and have TWRP installed already and you are not on Latest Firmware mentioned above then flash latest firmware.
Select BL, AP, CP, CSC (Use HOME_CSC).
Never only flash AP, will cause your /data to shrink.
Once you're updated to latest firmware mentioned above, make sure you unlock your bootloader.
Go into Settings>Software Info>Tap build number seven times.
Go into Settings>Developer Options>OEM Unlock & enable it.
It will prompt you with password/pin confirming to unlock bootloader. Device will reboot and wipe itself.
Setup device once it reboots and again enable developer options and see OEM unlock to be enabled and togglable.
Next enable USB debugging in Settings>Developer Options>USB Debugging.
Open up ADB/FASTBOOT Utility on your computer and connect your device with USB C cable.
Type in following commands without the quotations.
1."adb reboot download" ; reboots your device into Download mode, can flash device via Odin Downloader(Windows) or Heimdall Utility(Linux)
2.Download the attached TWRP.tar if you're using Odin or TWRP.img if you're using Heimdall to flash.
3.Flash the TWRP recovery by
ODIN:-
Clicking AP in Odin and make sure the Repartition and Auto Reboot boxes are UNTICKED/NOT SELECTED.
Click Start at bottom.
Heimdall:-
Open up a terminal window in the directory where twrp.img is downloaded.
Type in heimdall flash --RECOVERY twrp.img --no-reboot
4.Once flash is complete, press Volume Down+Power Button to shutdown and as soon as screen is black IMMEDIATELY PRESS AND HOLD VOLUME UP+POWER Button and let go of Power button when you see samsung logo, continue holding Volume Up until device boots into TWRP.
5.Once device boots into TWRP, swipe to allow modifications and then Click Wipe>Format Data>type in "yes". This will format everything and reset the device.
6.Go into Wipe>Advanced Wipe>Tick only Cache and swipe to wipe it.
7.Reboot back into recovery by Reboot>Recovery>Do not Install.
8.Once rebooted back into TWRP, transfer the attached zip to phone Internal or SDcard, DO NOT RENAME THE ZIP.
9.Flash the zip by, Install > Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, swipe to flash it.
10.Wipe cache and dalvik cache, reboot into system by, Reboot > System > Do not install.
11.Device will boot into Android 10 One UI 2.0 wait patiently for about 15mins.
12.Once device boots, setup as usual, you will need internet.
13.Voila! You have successfully installed TWRP alongside Stock firmware on Android 10 M305FDDU5CTF2 firmware.
Thanks to @vdbhb59 for his persistent testing and timely directions that helped me to bring you this guide.
Thanks to @SahilSonar for bringing TWRP to our device initially
Thanks to @akhil99 (me) for fixing MTP/ADB in TWRP recovery and bringing you this guide.
HIT THANKS IF WE HELPED YOU.
Downloads:
Edit: TWRP for Odin fixed as some users reported problems.
Official: TWRP OFFICIAL
Disable DM_Verity_ForceEncrypt : https://androidfilehost.com/?fid=8889791610682882483
XDA:DevDB Information
[RECOVERY][OFFICIAL]TWRP 3.4.0.0 Recovery [m30lte], Tool/Utility for the Samsung Galaxy M30
Contributors
Akhil99
Source Code: https://github.com/akhil1999/twrp_device_samsung_m30lte
Version Information
Status: Stable
Stable Release Date: 2020-07-10
Created 2020-07-10
Last Updated 2020-08-25
Reserved
25/08/2020 : OFFICIAL STATUS!
12/07/2020 : Added extra steps clearly mentioning for those getting into modding for the first time
10/07/2020 : Unofficial Stable release!
Quick Question
Actually I read here on XDA before, that the only way to root One UI is to patch the whole firmware using magisk, then flash it via ODIN. Since I can't download a large (over 2 gigs of) firmware, I was looking for a substitute.
After flashing TWRP as per your post above, would I be able to flash magisk via it amd root my M30? Would it be fine? Have anyone rooted their M30 with TWRP?
BTW, thanks @Akhil99
Azamsm said:
Actually I read here on XDA before, that the only way to root One UI is to patch the whole firmware using magisk, then flash it via ODIN. Since I can't download a large (over 2 gigs of) firmware, I was looking for a substitute.
After flashing TWRP as per your post above, would I be able to flash magisk via it amd root my M30? Would it be fine? Have anyone rooted their M30 with TWRP?
BTW, thanks @Akhil99
Click to expand...
Click to collapse
I have already posted about it. I am rooted with TWRP
Snaps coming soon
Sir, will it erase the data ?
Vinnu777 said:
Sir, will it erase the data ?
Click to expand...
Click to collapse
Nope, it is just recovery, so it will not erase any data.https://forum.xda-developers.com/newreply.php?do=newreply&p=83039519
Vinnu777 said:
Sir, will it erase the data ?
Click to expand...
Click to collapse
You are choosing the "Format Data" option that wipes everything in the Internal Storage. I advise you to back up data!
TWRP Images
TWRP images posted.
Sir, whenever I try to flash the given TWRP zip , after pressing start it throwing "Odin downloader has stopped working" msg and stopped working. But when i try to flash old TWRP zip it giving success . I have flashed latest firmware from below site
samfrew.com/download/Galaxy__M30
Could you pls tell me what happening , why your TWRP file is not installing or is this related to FIRMWARE I have flashed ,plz Check it sir!
Vinnu777 said:
Sir, whenever I try to flash the given TWRP zip , after pressing start it throwing "Odin downloader has stopped working" msg and stopped working. But when i try to flash old TWRP zip it giving success . I have flashed latest firmware from below site
samfrew.com/download/Galaxy__M30
Could you pls tell me what happening , why your TWRP file is not installing or is this related to FIRMWARE I have flashed ,plz Check it sir!
Click to expand...
Click to collapse
You need to be on Stock ROM, and the latest June release. Check my thread for the stock ROM, and download from there..
[Rom][ANDROID 10-Q | Stock & Rooted Firmware | M305FDDU5CTF2] - https://forum.xda-developers.com/ga...m-android-10-q-stock-rooted-firmware-t4026819
I don't want anything to go wrong. So I have this latest build with may security patch. My question is- Which section in ODIN should I choose to pick twrp tar file?
Azamsm said:
I don't want anything to go wrong. So I have this latest build with may security patch. My question is- Which section in ODIN should I choose to pick twrp tar file?
Click to expand...
Click to collapse
AP Slot
Vinnu777 said:
Sir, whenever I try to flash the given TWRP zip , after pressing start it throwing "Odin downloader has stopped working" msg and stopped working. But when i try to flash old TWRP zip it giving success . I have flashed latest firmware from below site
samfrew.com/download/Galaxy__M30
Could you pls tell me what happening , why your TWRP file is not installing or is this related to FIRMWARE I have flashed ,plz Check it sir!
Click to expand...
Click to collapse
TWRP for Odin is now fixed. Kindly try again. It was a error on my part that has now been fixed!
Akhil99 said:
TWRP for Odin is now fixed. Kindly try again. It was a error on my part that has now been fixed!
Click to expand...
Click to collapse
I tried and twrp booted. Then I formatted data and wipe dalvik/ART cache & cache in Advanced wipe. Then I rebooted in twrp again. Then I flashed Disable Dm verity zip and wiped dalvik cache.
Now when I try to boot into system, it boots in download mode instead!!!!
Please help.
Has it something to do system unmounted? Please reply. My phone is still resting in TWRP!
Vinnu777 said:
Sir, whenever I try to flash the given TWRP zip , after pressing start it throwing "Odin downloader has stopped working" msg and stopped working. But when i try to flash old TWRP zip it giving success . I have flashed latest firmware from below site
samfrew.com/download/Galaxy__M30
Could you pls tell me what happening , why your TWRP file is not installing or is this related to FIRMWARE I have flashed ,plz Check it sir!
Click to expand...
Click to collapse
After flashing TWRP and rebooting to system, did your phone also go in download mode or it just successfully booted? Cuz my phone is in download mode after I tried to reboot to system post flashing TWRP.
Can you plz help me
Arshebareen said:
After flashing TWRP and rebooting to system, did your phone also go in download mode or it just successfully booted? Cuz my phone is in download mode after I tried to reboot to system post flashing TWRP.
Can you plz help me
Click to expand...
Click to collapse
Looks like you aren't on patched firmware as mentioned in the thread. Head over hereto get and install the magisk patched firmware. Remember this will trip knox as usual.
Akhil99 said:
Looks like you aren't on patched firmware as mentioned in the thread. Head over hereto get and install the magisk patched firmware. Remember this will trip knox as usual.
Click to expand...
Click to collapse
I fixed the MTP issue in WIndows. I had to turn off and then turn on MTP devices module. It looks like a windows issue.
vdbhb59 said:
I fixed the MTP issue in WIndows. I had to turn off and then turn on MTP devices module. It looks like a windows issue.
Click to expand...
Click to collapse
I have a solution for MTP but I don't have a way to send files to you.
Topser99 said:
I have a solution for MTP but I don't have a way to send files to you.
Click to expand...
Click to collapse
Attach the file here.
vdbhb59 said:
Attach the file here.
Click to expand...
Click to collapse
twrp that i edited for you
https://mega.nz/file/TlVXUaiD#X_87J_yzoHGX6PQvkMJ-jmhLbViDDocI1IXOTcB_MNI
This is the file that I edited.
https://mega.nz/file/rkUzgASY#GwiHdcQLcQduIMZvGHBxsXb1YrkSUSs3_41rhlTA8aQ

Categories

Resources