{
"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
Related
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.
[Kernel] Stock Rootable Kernel Galaxy Note7 N930F/FD/S/L/K Without TWRP (08/20/2016)
TWRP 3.0.2-0 Galaxy Note 7 All Exynos Model Only: N930F/FD/S/L/K
Install TWRP
Consider before flash anything (Knox tripped), all you risk !!!
Stock firmware for full restore:
http://samfirm.net/forums/samsung-galaxy-note7.86/
Click to expand...
Click to collapse
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Note7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
DOWNLOAD
Official: http://teamw.in/devices/samsunggalaxynote7exynos.html
Beta: http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047
- Download Odin 3.12.3 & Samsung Android USB Driver for Windows
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
{
"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"
}
Extract Odin 3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for herolte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 11 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Thank & Credit @jcadduono - S7/S7e TWRP install instructions
Source: @Manh_IT http://choimobile.vn/threads/huong-dan-cai-twrp-galaxy-note-7-all-exynos-model-n930f-s-l-k-w8.67874/
W8 is the Snapdragon variant. Do not flash this on that.
This TWRP could not have been built from OSRC as it hasn't been released yet, so is likely using a stock kernel leak and missing support for ADB, MTP, UMS, F2FS, NTFS etc. (unlike the post copypaste from my threads says )
As is usual of Manh_IT and outside Vietnam forums, the sources are unavailable and you're pretty much on your own flashing this.
Once OSRC is out (August 19th for Snapdragon, anywhere between August 19th and September 2nd for Exynos), then official TWRP will be out soon after with all the other features supported.
PS. Would be nice to know if no-verity-opt-encrypt zip works on this device, it isn't working on the new 7870 devices due to forced encryption in vold (encrypts even when encryption disabled in boot image)
great , good news for new user note7 exynos model
Wow, first recovery for the epic note7!!:good:
Wow thank you
Sent from my SM-N930F using Tapatalk
jcadduono said:
W8 is the Snapdragon variant. Do not flash this on that.
This TWRP could not have been built from OSRC as it hasn't been released yet, so is likely using a stock kernel leak and missing support for ADB, MTP, UMS, F2FS, NTFS etc. (unlike the post copypaste from my threads says )
As is usual of Manh_IT and outside Vietnam forums, the sources are unavailable and you're pretty much on your own flashing this.
Once OSRC is out (August 19th for Snapdragon, anywhere between August 19th and September 2nd for Exynos), then official TWRP will be out soon after with all the other features supported.
PS. Would be nice to know if no-verity-opt-encrypt zip works on this device, it isn't working on the new 7870 devices due to forced encryption in vold (encrypts even when encryption disabled in boot image)
Click to expand...
Click to collapse
Look who's been lurking around the n7 thread.
Nice to see you here man!????
Hopefully later your team will release the official TWRP, for both model exynos and snapdragon.
And also your idleKernel. It's been an amazing kernel for my note3 up until now. Bravo. . .and bravo too OP.
It does not work for me. Flash is ok, but cannot boot into recovery. Stuck at Samsung screen.
Normal boot works.
SM-N930FD
I did a factory reset, now it does not boot at all anymore. Any help please?
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
bill340 said:
It does not work for me. Flash is ok, but cannot boot into recovery. Stuck at Samsung screen.
Normal boot works.
SM-N930FD
Click to expand...
Click to collapse
Me too no work stuck at Samsung screen boot
Sent from my SM-N930F using Tapatalk
I cannot go into recovery. Only download mode works. But when trying to flash something in odin, I get this error as mentioned.
Is there any way to get back on the device?
MSH2000FF said:
Me too no work stuck at Samsung screen boot
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
bill340 said:
I did a factory reset, now it does not boot at all anymore. Any help please?
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Click to expand...
Click to collapse
bill340 said:
It does not work for me. Flash is ok, but cannot boot into recovery. Stuck at Samsung screen.
Normal boot works.
SM-N930FD
Click to expand...
Click to collapse
bill340 said:
I cannot go into recovery. Only download mode works. But when trying to flash something in odin, I get this error as mentioned.
Is there any way to get back on the device?
Click to expand...
Click to collapse
Your devices model and build number ?
Worried to try as it's not working for many above - and still the Stock Firmware TAR is not available to re-flash if something goes wrong.
WolfW said:
Your devices model and build number ?
Click to expand...
Click to collapse
SM-N930F
bill340 said:
SM-N930F
Click to expand...
Click to collapse
Flash N930FXXU1APG7 firmware and try again !
http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/
JazonX said:
Worried to try as it's not working for many above - and still the Stock Firmware TAR is not available to re-flash if something goes wrong.
Click to expand...
Click to collapse
If your device model is SM-N930F or N930FD, use this firmware: http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/
WolfW said:
If your device model is SM-N930F or N930FD, use this firmware: http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/
Click to expand...
Click to collapse
Thanks, Downloading now. Hope you'll rebuild the recovery sans the issues others faced.
I still have the issue, that I cannot flash in Odin, due to the mentioned error... Any idea?
bill340 said:
I still have the issue, that I cannot flash in Odin, due to the mentioned error... Any idea?
Click to expand...
Click to collapse
Take error screenshots on Odin and Download screen on your phone !
Here are the screenshots....
bill340 said:
Here are the screenshots....
Click to expand...
Click to collapse
You should ad tar only to AP and press start. Read the OP very carefully.
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?
Unofficial release -TWRP recovery for the Samsung Galaxy J2 PRO 2018 - Qualcom msm8917
{
"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"
}
THIS FOR FIRMWARE BASED ON "ARD3" OR "ARD*" . SO PLEASE MAKE SURE YOUR FIRMWARE IS "ARD3 OR "ARD*" :
Current status: BETA
Features:
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
efs backup support
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
(Note: failure to follow these instructions implicitly will cause TWRP to be replaced by stock recovery at boot!)
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
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.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Download:
recovery.tar.md5 For J250f
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest magisk with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
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 magisk (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt-5.1
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, Omnirom, my tester ilmiawan budi utomo @FBGroup
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
Reserved
readme
this for firmware base on "ard3" please make sure your firmware "ard3"
andii_nr said:
readme
this for firmware base on "ard3" please make sure your firmware "ard3"
Click to expand...
Click to collapse
help me please J250FDXU1ARA2
Khang140401 said:
help me please J250FDXU1ARA2
Click to expand...
Click to collapse
First update to ARD3
andii_nr said:
First update to ARD3
Click to expand...
Click to collapse
I updated and flash this with odin but it not work ☹☹ my board msm8937 ? Work? Please reply me.
---------- Post added at 06:10 AM ---------- Previous post was at 06:04 AM ----------
[/PHP]
andii_nr said:
First update to ARD3
Click to expand...
Click to collapse
Khang140401 said:
I updated and flash this with odin but it not work ☹☹ my board msm8937 ? Work? Please reply me.
---------- Post added at 06:10 AM ---------- Previous post was at 06:04 AM ----------
[/PHP]
Click to expand...
Click to collapse
Are you sure your phone sm-j250f and firmware ARD3 ?
If yes that recovery work fine , am also test with 3friend and work ..
andii_nr said:
Are you sure your phone sm-j250f and firmware ARD3 ?
If yes that recovery work fine , am also test with 3friend and work ..
Click to expand...
Click to collapse
see it ??
andii_nr said:
Are you sure your phone sm-j250f and firmware ARD3 ?
If yes that recovery work fine , am also test with 3friend and work ..
Click to expand...
Click to collapse
My devices _J250FDXU2ARD3
problem
team win worked with me but when i want to open my phone it reboot himself and i should install rom
Khang140401 said:
see it ??
Click to expand...
Click to collapse
Read all instruction ..
This phone has deencrypt .. so you must FORMAT DATA -> flash magisk -> flash boot-patcher ..
Costum ROM s8 for j250f
andii_nr said:
Unofficial release -TWRP recovery for the Samsung Galaxy J2 PRO 2018 - Qualcom msm8917
THIS FOR FIRMWARE BASED ON "ARD3" OR "ARD*" . SO PLEASE MAKE SURE YOUR FIRMWARE IS "ARD3 OR "ARD*" :
Current status: BETA
Features:
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
efs backup support
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
(Note: failure to follow these instructions implicitly will cause TWRP to be replaced by stock recovery at boot!)
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
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.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Download:
recovery.tar.md5 For J250f
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest magisk with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
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 magisk (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt-5.1
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, Omnirom, my tester ilmiawan budi utomo @FBGroup
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
Click to expand...
Click to collapse
Thanks bro for twrp
ARD3 doesn't support current root. Why? Only restart... Phone is not opening.
TWRP => all directory 0 mb. There is a problem.
Thanks for your hard work. The recovery works really fine with our device if instructions were followed carefully.
Now all we need is a custom kernel with selinux set to permissive. I appreciate any help.
Help me
I have a problem with my mobile device that shows me this message when running
"Set warranty bit: kernel"
What is the solution?
i can't use camera when rooted!
pls help me!
timtini said:
i can't use camera when rooted!
pls help me!
Click to expand...
Click to collapse
Latest version of SuperSU or Magisk.
ashyx said:
Latest version of SuperSU or Magisk.
Click to expand...
Click to collapse
of course!
i was try to root with Super SU and Magisk but it still bug!
So I thought of twrp caused!
Nice kang ?
Hello All
Its a never used LEX 727. Decided to flash a custom rom. Installed latest TWRP, but when i go to flash the rom got error 7.
Tried with diffrent roms but still error 7.
Then updated firmware to 30S by @codeworkx from here and again tried different roms but am still getting the error.
Following the suggestions given by various posters, I have tried doing full wipes, rebooting to recovery, using the ALL IN ONE tool but nothing is working.
I've also tried many older versions of TWRP as well as roms but nothing, the error is still there.
Any more suggestions on how to fix this? Thank you.
This is a typical error when TWRP is old or does not fit the model.
First, stay at 20s firmware:
Downloads for : LeEco Le Pro3 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
You have to keep an eye on this:
- LEX720 (ZL1_CN)
- LEX722 (ZL0_CN)
- LEX727 (ZL1_NA)
Error 7 says the ROM’s updater script says the phone model of your phone is incompatible. A quick search for LineageOS give me this compatible on:
[ROM][OFFICIAL][TREBLE][X72X][11.0.X] LineageOS 18.1 for LeEco Le Pro3
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from...
forum.xda-developers.com
Make sure you have the latest TWRP installed for the X727:
Download TWRP for zl1
Download TWRP Open Recovery for zl1
eu.dl.twrp.me
Importand: If LineageOS aks to install it's own recovery, don't do it.
Important:
Install recovery, then reboot directly into recovery and install the rom. Original Firmware will revert back to stock recovery while boot! The you have to start over again.
Hello @Neppomuk_
Thanks.
1- I installed the 20S firmware
2- Installed the latest TWRP version 3.6.2_9-0-zl1 , and, rebooted to recovery.
3- Downloaded both the latest official LOS as well as the unofficial one by the poster whose link you have posted above. First tried installing the official rom and it gave error 1. Then tried flashing the unofficial one and same error. i.e.: "E1001: failed to update system image", Error 1.
4- I also tried installing the Mokee rom and it is also giving the same error. I downloaded the rom from their official site here
4- I am attaching screenshots of the errors. The first one is from the lineage "unoffical" after the "offical" had failed to install. The second one is from the failed Mokee rom.
{
"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"
}
Hopefully this is progress.
Error 1 is corrupted boot. You have the flash the stock boot.img with bootloader. I own a x720 so I can not provide you my one. It is possible to extract it from stock rom.
Check if you can find one here:
Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s
Return to Un-modded Stock: Bootloader unlocked and TWRP and Root included The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download. Be Advised Do your research before flashing...
forum.xda-developers.com
Neppomuk_ said:
Hopefully this is progress.
Error 1 is corrupted boot. You have the flash the stock boot.img with bootloader. I own a x720 so I can not provide you my one. It is possible to extract it from stock rom.
Check if you can find one here:
Click to expand...
Click to collapse
Actually i have had that error before while experimenting, so i'm afraid there has been no progress.
Are you asking to flash the stock boot image? And then what? Will appreciate if you outline the steps.
@Neppomuk_
1- Extracted stock boot image from the file you provided. Flashed it to boot successfully. Rebooted to recovery.
2- Went through the process of flashing the rom again. Still error 1.
OK, the E1001 from your screenshots is interesting. System image is (marked as) encrypted.
Do Following from twrp, all steps without reboot:
wipe/advanced wipe, tick 'Dalvilk/Art', 'Cache', 'Data' and 'System'
then go wipe/format data, confirm with yes, now the encryptiono (state) should be gone.
Now reboot straight back into recovery and flash the, this was mokee rom?, again.
Neppomuk_ said:
OK, the E1001 from your screenshots is interesting. System image is (marked as) encrypted.
Do Following from twrp, all steps without reboot:
wipe/advanced wipe, tick 'Dalvilk/Art', 'Cache', 'Data' and 'System'
then go wipe/format data, confirm with yes, now the encryptiono (state) should be gone.
Now reboot straight back into recovery and flash the, this was mokee rom?, again.
Click to expand...
Click to collapse
Did it. Still error 1.
The first picture is LOS. The second one is Mokee.
Let's try following:
In TWRP go to Advanced, select File Manager, select the System folder from the list and the push the checkmark on the bottom right corner. No push the chmod 755 button the give full access to system partition.
Try to install custom rom.
A second try:
Go to wipe / Advanced wipe
select the system partition
now select 'repair or change file system' and then 'repair file system'.
Try to install custom rom.
I had problems with the 2nd try on some devices they do not allow repair of system partition.
Did the 1st option. Still error 1.
Did the 2nd option and the process was aborted or failed with error 4.
Did the 1st option. Still error 1.
Did the 2nd option and the process was aborted or failed with error 4.
Did you had any problem to flash TWRP on the device earlier?
With error 4 we have a second option:
In TWRP go to Wipe / Advance Wipe, select 'System' partition and select 'Repair or Change File System'.
Select 'Change File System', select EXT2 and proceed.
Then do the same to go back to EXT4.
Do the same with the Data partition.
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
OK, something special:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Neppomuk_ said:
Did you had any problem to flash TWRP on the device earlier?
Click to expand...
Click to collapse
No.
Neppomuk_ said:
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
Click to expand...
Click to collapse
Not sure how to do this. As far as i know one can only flash images in boot loader mode. How does one flash a zip file in that mode?
Neppomuk_ said:
OK, something special:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Click to expand...
Click to collapse
Are you asking to flash the lineage boot.img in bootloader mode and then flash the entire rom by TWRP?
Do partial flash in bootloader mode, if not already happen, use Minimal ADB and Fastboot:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Command to flash boot image in console:
fastboot flash boot [boot.img]
Then stay in bootloader mode. The mobild should mount a drive to the system. Copy the ROM imge to the internal storage on that drive. You can copy the rom in TWRP mode also. Then install the rom throug TWRP.
I never sideloaded data. I like to check the transfer is successfully finished. I had some faulty sd cards, wich do no give an error while sideloading stuff.
As an alternative you can use an OTG USb Stick and putt the stuff on this one. Would do the same and could be faster.
If you need drivers for Windows:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
and the device specified one:
LeEco Le Pro3 USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
-> I did not verify if this driver downloads are still valid, please check them first.
I do have the latest drivers and ADB installed. Everything i have been telling you has been done via ADB as well as from the internal storage of the phone.
But my question was, when you say :
Neppomuk_ said:
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
Click to expand...
Click to collapse
What are you exactly asking me to do? How can one flash a zip file using bootloader, assiming that's what you are saying?
And, when you are saying:
Neppomuk_ said:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Click to expand...
Click to collapse
Are you asking me to flash the boot.img using bootloader and then flash the rom from TWRP?
My question is i can flash the boot.img from TWRP, can't I? Anything wrong with that approach?
I think understand you now. Do a partial flash using boot loader and the do the rest using TWRP.
Thank you for clarifying. One needs confirmation so we do not do anything we aren't supposed to.
Sorry, I mixed up another case where I'm tring to remove forced data encryption.
There are flashable boot.img in zip files wich you can flash from TWRP, but this is not your one.
I still believe, that something is wrong with your boot partition.
The whole procedure:
- Extract boot.img from Lineagos and install it in bootloader mode: fastboot flash boot [boot.img]
- Boot into TWRP while holding Power and volume up.
- If not done, wipe cache and system, format data.
- Copy LineageOS to the drive / internal storage
- Use TWRP to install the rom
veda1 said:
I think understand you now. Do a partial flash using boot loader and the do the rest using TWRP.
Thank you for clarifying. One needs confirmation so we do not do anything we aren't supposed to.
Click to expand...
Click to collapse
Yes, better one question to much than new problems...
Did as suggested. Still error 1.
I have another question while we continue to look at this. If worse comes to worse i've no choice but to use EUI. Is it possible to patch the latest android security patches to it? That is, rom will be EUI , but updated with all security patches?