[Unofficial] TWRP 2.8.7.0 for HTC m9+ (m9pw, m9 plus, htc_hiau_ml_tuhl) English version
Credit:
TWRP / @Dees_Troy
Theme: Materialised Play @z31s1g topic
Xiaolu: this version is based on xiaolu's repositories and original compilation and device tree https://github.com/xiaolu?tab=repositories
Repositories: https://github.com/tbalden/android_device_htc_htc_hiau_ml_tuhl https://github.com/tbalden/android_bootable_recovery-twrp
Hit the Thanks button if you like the work being done, or donate to the dev:
DONATION HEREhttp://forum.xda-developers.com/donatetome.php?u=3088420http://forum.xda-developers.com/donatetome.php?u=3088420http://forum.xda-developers.com/donatetome.php?u=3088420
Default theme (please download the primary recovery image below):
{
"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"
}
Materialised Theme (please download the second recovery image below):
Tested on a Chinese M9+
Issues:
- ADB doesn't work. You need to copy flashable files to the device while phone is in normal mode over MTP, not in the recovery.
- external sd card: doesn't work properly, DON'T try flashing from it, I had to restore a backup when I tried
- in Materialised Theme mode, on theme/splash creation screen: creation and flashing of own theme/recovery image fails
WARNING: As usual, use it at your own risk! This comes without any warranties, by downloading and using it you are taking all responsibilities on yourself.
STOCK RECOVERIES: if you want to go back to your Stock recovery some Carriers (regions) some recovery versions for different official firmware versions are available in this thread: http://forum.xda-developers.com/one-m9/one-m9-general/firmware-stock-recoveries-regions-t3120826
ALSO BE AWARE: for some regions the Stock Recovery Image of the phone is not available. So basically, if you flash the recovery as long as there's no official image to extract the original, you won't be able to flash back to stock recovery, meaning that you might have problem with flashing official updates!
SO AGAIN: YOU WON'T BE ABLE TO FLASH BACK TO STOCK RECOVERY, meaning you most probably won't be able to upgrade on the official OTA updates till someone gets an official RUU for your device's carrier from which the stock recovery can be extracted Some carriers some firmware versions are already covered in the thread mentioned above (STOCK RECOVERIES)
You'll need:
- Unlocked bootloader (e.g. proceed as detailed here: http://www.htcdev.com/bootloader)
- Fastboot tool
- Better use a USB 2.0 port, might work to flash with USB 3, but there were reports of issues with that
INSTALLATION:
Code:
- Unlock bootloader
- Boot your device into Download mode: POWER OFF, then long press [Volume Down + Power]
- Hook up USB with PC and the phone
- with fastboot:
fastboot flash recovery recovery-twrp-2.8.7.0-htc_m9pw-english.img
Example:
Code:
c:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery-twrp-2.8.7.0-htc_m9pw-english.img
target reported max download size of 800000000 bytes
sending 'recovery' (13996 KB)...
OKAY [ 1.454s]
writing 'recovery'...
(bootloader) HOSD CL#534001
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.272s]
finished. total time: 2.728s
DOWNLOAD:
TWRP (unmodified, Default Theme):
2.8.7.0: http://d-h.st/BEYh (Use Download Now button on the site)
TWRP with Materialised Light Play theme and light blue material splash precompiled:
2.8.7.0 - material_play: http://d-h.st/16Ec
Unlock tutorial for materialised twrp version:
2.8.6.0 v2: http://d-h.st/OXFu (Use Download Now button on the site)
2.8.6.0 v1: http://d-h.st/MZh6
ACCESS RECOVERY
Power off. Long press Power + Vol Down. In Download mode with volume buttons navigate to reboot to bootloader, press power.
In bootloader navigate with volume buttons to BOOT TO RECOVERY MODE, press Power.
Rooting guide thread: http://forum.xda-developers.com/one-m9/one-m9-general/howto-rooting-m9-m9pw-htchiaumltuhl-t3116327
reserved for versioning post
VERSIONS
2.8.7.0 - 2015-07-18 - Changes from official TWRP release bump (like the option of keeping System partition readonly, for stock backups)
2.8.6.0 v2 - 2015-07-11 - Removed unnecessary touch logging which slowed down recovery and spammed log window
2.8.6.0 v1 - 2015-05-23 - Initial English version
==========
Also I'll try to get root access on the device now with this recovery. Will post it in a separate thread when it's done.
UPDATE:
Root access flashing from TWRP:
Yes it works.
With TWRP recovery flash the SuperSU update zip from here https://download.chainfire.eu/735/SuperSU
Code:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]_hiau_ml_tuhl:/ $ su
su
[email protected]_hiau_ml_tuhl:/ #
Rooting guide thread: http://forum.xda-developers.com/one-m9/one-m9-general/howto-rooting-m9-m9pw-htchiaumltuhl-t3116327
Thanks for the great work you've been doing so far! I really appreciate dev's like you who manage to do so much with little resources or help available. Cheers!
thanks for this recovery
Thanks for this it was a life saver. I was getting nowhere trying to use TWRP 2.8.7.*
I found that when it runs, there are a lot of red warning messages - E: touch-drag and E: touch-hold. Dont get these message with other versions of TWRP, or is it just something with my M9Plus?
joe97113 said:
Thanks for this it was a life saver. I was getting nowhere trying to use TWRP 2.8.7.*
I found that when it runs, there are a lot of red warning messages - E: touch-drag and E: touch-hold. Dont get these message with other versions of TWRP, or is it just something with my M9Plus?
Click to expand...
Click to collapse
I want to compile a new one without that, also of 2.8.7.0 but I cannot seem to have it booted. If I succeed I'll get back with it.
2.8.6.0 updated with v2 for m9+, it's just cosmetic changes, but makes the navigation faster. Check original post for new download link.
2.8.6.0 v2 - 2015-07-11 - Removed unnecessary touch logging which slowed down recovery and spammed log window
I still have issues with booting my new compilation for 2.8.7.0, so for now this is just a minor update for 2.8.6.0 specifically for the m9+ unofficial english twrp recovery
tbalden said:
2.8.6.0 updated with v2 for m9+, it's just cosmetic changes, but makes the navigation faster. Check original post for new download link.
2.8.6.0 v2 - 2015-07-11 - Removed unnecessary touch logging which slowed down recovery and spammed log window
I still have issues with booting my new compilation for 2.8.7.0, so for now this is just a minor update for 2.8.6.0 specifically for the m9+ unofficial english twrp recovery
Click to expand...
Click to collapse
Many Thanks tbalden. I will give the new version a go.
Hi tbalden,
I have run into a bit of a problem with your latest recovery and wondering if you or anyone else may have an idea what's causing this problem which is, the bootloader unlocked fine and I flashed v2.img via fastboot and all went fine also then booted into recovery and I am getting the error E:Unable to mount '/system' when trying to flash CleanSlate which actually seems to flash fine, I went into Mount and tried to mount the system partition but it won't check and the same error come up in the dialogue.
I now can't reboot into the system and it hangs at the splash screen so I'm guessing this error is the problem with the ROM being flashed correctly and everything is messed up now.
It may be a simple fix but if you or anyone else knows what may be causing this I would appreciate some help please, thanks.
Update: Everything is installed correctly and working now.
@Sojourner353 Are you by chance installing the rom from external sdcard ? That doesn't work, and caused me same issue (I've it in the first post of this thread as known issue). Do you have a back up? Restore, boot, and move the zip to internal storage and try that.
If you don't have a backup, you might need a RUU zip for your CID, and as I see that is Hong Kong (CID 708 based on your post in the rom thread). I don't have a HK RUU zip base 1.09, maybe @xiaolongzi?
tbalden said:
@Sojourner353 Are you by chance installing the rom from external sdcard ? That doesn't work, and caused me same issue (I've it in the first post of this thread as known issue). Do you have a back up? Restore, boot, and move the zip to internal storage and try that.
If you don't have a backup, you might need a RUU zip for your CID, and as I see that is Hong Kong (CID 708 based on your post in the rom thread). I don't have a HK RUU zip base 1.09, maybe @xiaolongzi?
Click to expand...
Click to collapse
Thanks for the reply, I do have a nandroid but it's giving me the same result after restoring it, I am also installing from the internal memory, there is no external SD in the unit at all.
The only thing I can think of is there is some sort of corruption in the recovery caused by the PC I flashed it from (Surface Pro 3 USB3), never used this PC on previous devices so today I will use my Server that has USB2 and has done many devices in the past without issue.
If I still have a problem I will just have to wait for a RUU to become available I guess.
Sent from my HTC One M8x using Tapatalk.
UPDATE: I've done some thorough testing, multiple flashing of full ROM and backup / restore, v2 seems to be OK on my side, so adding back link.
===
I didnt have the time to properly invevstigate, but the V2 might have some instability issues, sorry guys, removed for now till I investigate the issue.
Please revert back to V1 !
Finally did a test with v2, much better than the previous version - did not find any issues. Thanks.
2.8.7.0+ m9+ english version soon to upload. Testing it some more.
Those who wish to backup intact System.img (remount Read/Write issue circumvention when going back to stock recoveries and trying OTAs failed with remounted System partitions) should be able to use Read-Only system mode with this:
With 2.8.7.0 TWRP i'll soon release, I've tested 2.8.7.0 theme from this thread: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 Nicely working. (Through 1440x2560 Themes Folder, Material Light theme, name 287x-v1-1440_play)
Tho I had a hard time with Swipe right to unlock, before I found out that i need to swipe the lower screen part, and there's no actual graphical slider, just colored text (you'll understand it if you try installing it yourself )
new update
2.8.7.0 - 2015-07-18 - Changes from official TWRP release bump (like the option of keeping System partition readonly, for stock backups)
new addition:
TWRP with Materialised Light Play theme and light blue material splash precompiled recovery image version.
Check first post for download in Downloads section
i repacked 286 with system read only to backup unmodified system image before. If i could rename the name system.emmc.win to system_image.emmc.win to restore with your new version 287, i will test it. Thank your new versin 287 and this make M9+ perfect if someone still want to keep OTA.
Sent from my HTC_M9pw using XDA Free mobile app
Help.
"Swipe right to Unlock" does not work for me, any suggestions. Tried to volume down+ power button with no luck. Occasionally the screen goes black then the text comes back.
---------- Post added at 08:39 PM ---------- Previous post was at 08:23 PM ----------
joe97113 said:
Help.
"Swipe right to Unlock" does not work for me, any suggestions. Tried to volume down+ power button with no luck. Occasionally the screen goes black then the text comes back.
Click to expand...
Click to collapse
Managed to reboot. Might go back to previous version at least the unlock works.
joe97113 said:
Help.
"Swipe right to Unlock" does not work for me, any suggestions. Tried to volume down+ power button with no luck. Occasionally the screen goes black then the text comes back.
---------- Post added at 08:39 PM ---------- Previous post was at 08:23 PM ----------
Managed to reboot. Might go back to previous version at least the unlock works.
Click to expand...
Click to collapse
Which version? material Themed or the default?
In Material themed you either need to swipe over the low area of the screen (the text will go gray as you progress), or in settings set alternative lock screen to make it more visible
In default theme version very occasionally it happened to me, I had to try unlock it and wait about ten seconds till it unlocked in the end. But this happened on 2.8.6.0 not the new version
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.
Hey guys! Here is how to get recovery for your Z3 Compact without losing any files or flashing any kernels, as this could usually be a pain in the butt if you need a kernel for a custom rom...
I do not take credit for any of the resources in this guide and neither do i take any responsibility for bricked phones,dead SD cards or death
Click to expand...
Click to collapse
Prerequisites
1. Unlocked Bootloader (Its fairly easy to do, a simple google would suffice)
2. TWRP image- Get it Here
3. Flashtool installed with all required drivers
4. ADB and Fastboot (Here)
5. Patience
How to Install
1. Make sure you have an unlocked bootloader or this will, and shall not work.
2. Make sure you are running the latest firmware (.291). If not, use flashtool to update to the latest firmware.
3. Copy the downloaded TWRP image to your adb/fastboot folder and rename it recovery.img for ease.
4. Click shift+right click in any empty space in your adb/fastboot folder and click open command window here.
5. switch off your z3c. press the vol up button and insert USB cable to boot into fastboot mode
6. Make sure everything is working by typing
Code:
fastboot devices
in the cmd window. If all is well, then it should show your device's serial along with fastboot written beside it.
7. Time to flash the recovery:
Type in this command
Code:
fastboot flash recovery recovery.img
Congrats! You now have a recovery
8. To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.
You can now flash any rom or zips you want with this recovery, for root, flash the latest SuperSu Zip from chainfire.
I would also recommend flashing DRM fix zip.
If you want a better version of the stock rom, i will recommend installing SliMM Rom by Wajk
Note: This TWRP can get uninstalled in some cases, for example flashing a rom with twrp built in. But repeat the same process to get TWRP back without losing any data!
Thanks!
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
dansan691 said:
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
Click to expand...
Click to collapse
No, you can install SliMM directly. To get root, you should be using armv23 version... Try this. Also, you should use a DRM restore zip to get back camera quality
Clarification
Should I have to flash DRM Fix every time I flash TWRP?
andry360 said:
Should I have to flash DRM Fix every time I flash TWRP?
Click to expand...
Click to collapse
No need. But if you change reflash ROM, you might need to
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
epiii_nephrine said:
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
Click to expand...
Click to collapse
Can you please give me the error you get?
panzerox123 said:
Can you please give me the error you get?
Click to expand...
Click to collapse
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
epiii_nephrine said:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
Click to expand...
Click to collapse
Alright... I know what's up. If you can wait till 9PM IST today, I will create another guide. Thanks!
To Get Root
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
panzerox123 said:
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
Click to expand...
Click to collapse
Thank you so much sir! will be testing this version.. i'll let you know :good:
epiii_nephrine said:
Thank you so much sir! will be testing this version.. i'll let you know :good:
Click to expand...
Click to collapse
Sure! If this does not work, I have another method.
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
smahio said:
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
Click to expand...
Click to collapse
Doesn't make any sense... It would so that only if you flashed to boot partition. Download EliteKernel V3 , extract the zip, keep the boot.img in your minimal adb folder and do
Fastboot flash boot boot.img
Then try again
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please 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"
}
ewjy said:
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
Click to expand...
Click to collapse
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
panzerox123 said:
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
Click to expand...
Click to collapse
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
ewjy said:
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
Click to expand...
Click to collapse
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
panzerox123 said:
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
Click to expand...
Click to collapse
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
ewjy said:
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
Click to expand...
Click to collapse
Funny... It works very well for me... In fact it's much more stable than previous versions
Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"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.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
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.
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:
Flash with ODIN 3.12.7 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 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:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(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 SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, 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
.
.
Reserved
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app
rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?
Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.
Everything went smooth! Thank you so much!
rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.
No problems at all... Everything went perfect!
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.
need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921
ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"
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 Kernel + ROOT + TWRP + DRM Fix
Code:
** Your warranty is now void.
**
** I am not responsible for bricked devices, dead SD cards,
** thermonuclear war, or you getting fired because the alarm app failed. Please
** do some research if you have any concerns about features included in this MOD
** before flashing it! You are choosing to make these modifications, and if
** you point the finger at me for messing up your device, I will laugh at you.
**
Requirements
If you haven't unlocked bootloader yet check this guide
Good News ! For advanced users If you have TA.img backup of your device I highly suggest using this tool to patch stock kernel using your own TA image to have drm working with latest Magisk 16.3. Follow TA_POC METHOD instructions below .
- Kernel (boot.img) + Magisk + DRM fix patch : Here
- Latest TWRP from here[/B]
And obviously :
- ADB and FASTBOOT : https://forum.xda-developers.com/showthread.php?t=2317790
- Xperia X PERFORMANCE drivers : https://developer.sonymobile.com/downloads/drivers/xperia-x-performance-driver/
- FlashTool : http://www.flashtool.net/downloads.php
What are DRM Keys ?
If you unlocked the bootloader on a Sony Xperia device, you probably know that the potential loss of warranty is not the only disadvantage you have to accept. Another fairly hidden issue is related to various proprietary features such as the X-Reality color mangement, BIONZ image processor and the active noise cancelling techniques. Once you decide to unlock your bootloader, the process also removes a piece of data referred to as the DRM keys. These are tied to various services (such as streaming video and the like) offered by Sony but are also required for the features mentioned above to work properly. Put simply, once the keys are gone, you’ll face issues such as decreased low light camera image quality and the lack of the X-Reality mode.
Click to expand...
Click to collapse
Kernel features
this is pure stock kernel of the mentioned above firmware with
- RIC disabled
- added DRM patch support
Instructions
Before proceed backup all you important data like pictures, files to another device.. !
Make sure you follow all steps carefully with caution .. !
01- Flash Oreo FTF via Flashtool (Full wipe is recommened exclude nothing except TA files if there's any)
02- When done flashing unplug device ..
03- Enter fastboot mode and flash TWRP (hold vol up + plug usb)
Code:
fastboot flash recovery twrp-3.2.1-0-dora.img
then flash kernel
Code:
fastboot flash boot boot.img
04- Unplug and enter TWRP (Hold vol down + power button)
05- In TWRP Flash drmfix.zip + SafetyNet Cleaning Tools.zip then Magisk v16.3.zip
06- OPTIONAL Flash ROM Ptach to clean system and remove all bloat apps
07- Reboot and enjoy
Click to expand...
Click to collapse
TWRP asking for decryption code / Internal Storage showing 32GB only for DUAL Model
Turn off the phone (from TWRP if you can or hold vol up and power button till the phone vibrates 3 times)
Enter Fastboot and format user data partitions using this code
Code:
fastboot format userdata
If you are getting error try from TWRP recovery > WIPE > Swipe to format data
Now start your phone and set it up the issue should be resolved.
If still storage is not showing do clean installation in Flashtool wiping everything and exclude nothing then follow then instructions above .. I also noticed that flashing the correct XZ DUAL boot.img the first time before first boot fix this
To check drm keys type *#*#7378423#*#* on your phone and go to Service Test > Security
If you have all [Key OK] they are OK! like the pictures I attached below
Extras (Recommended)
- LXT (Battery Life | Speed Tweaks)
- [MOD][THERMAL FIX] FSC™ 4.0 Improve performance & Eliminate heat
- [XZ/XZs/XP]V1 Dontbelive XPERIA XZ1 StereoMOD
- [Magisk][Module] SELinux Manager by Jman420 (Set to permissive)
- [Magisk][Module] Unified Hosts Adblocker
- [Magisk][Module] Youtube Vanced [Official]
Must have apps
- Gboard - the Google Keyboard
- Brevent
- Kiwi Browser - Fast & Quiet
Credits @serjar for unofficial rootkernel update
Old DRM restore by @tobias.waldvogel
Magisk by @topjohnwu
SafetyNet Cleaner by @sceryavuz
TWRP by TeamWin
Doesn't work. When I did all, phone get infinite bootloading. And why TWRP shows F8131? My phone is F8132
---------- Post added at 08:23 AM ---------- Previous post was at 07:39 AM ----------
OP, before publishing, check it! Tried 2 method, still stuck on boot.
Finally, got it!
{
"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"
}
ramirrat said:
Finally, got it!
Click to expand...
Click to collapse
Great!! Did you do anything other than the OP instructions?
Hi,
I also managed to apply the procedure.
Links in requirement are not pointing to newsest TWRP and Magisk. They are pointign to TWRP 3.0.0 and Magisk 14.3. Now available are TWRP 3.1.1 and Magisk 14.5.
Generallt method one worked with full total wipe while flashing Oreo with flashtool.
serajr said:
Great!! Did you do anything other than the OP instructions?
Click to expand...
Click to collapse
Used method 2, but flashed this TWRP
YES ... the Problem was TWRP and MAGIKS. Thank You. I used Method 1 - ok
but "SHAME ON SONY" - still no RAW Format for Camera with Oreo. I will go back to Oreo AOSP - so i can use Google Camera with RAW.
thnx
gordon
Is it possible to root with SuperSU instead of Magisk? I had a lot of camera problems when I used Magisk. It's up to 2.82 now, I think that' a general Oreo compatible thing.
ok i got it all to work,
steps i performed, on my laptop windows 7 ult x64
downloaded and installed the following
ADB and FASTBOOT extracted it on my c:/adb
Xperia X Performance drivers extracted it on c:/
FlashTool installed it and it's drivers located in the install folder of flashboot
downloaded the folowing files
Oreo Kernel Image copy to c:/adb
https://mega.nz/#!OA5BBJDY!lQ9Xojv5DN45QPbUQt-iQGhI409B7l7WoWvo0GTqYlY]DRM fix patch copy to to phone memory
TWRP 3.1.1.0 have not tried latest yet but 3.1.1.0 works fine, copy to c:/adb
Magisks 14.5 Beta copy to phone memory
folowed the guide methode 1 with slightly changes
01- Flash Oreo FTF via Flashtool ([color=redFull wipe in TWRP since i don't quite know how to use flashtool[/color], exclude FOTAKERNEL !! )
02- When done flashing unplug device .. (Do not boot yet !!)
03- Enter fastboot mode and flash the given kernel image (hold vol up + plug usb)
Code: fastboot flash boot boot_oreo.img
04- Flash TWRP 3.1.1.0 have not tried latest yet but 3.1.1.0 works fine
Code: fastboot flash recovery twrp.img
05- Unplug and enter TWRP (Hold vol down + power button) and did full wipe except system and micro sd
06- Flash drmfix.zip
07- Flash Magisks 14.5 Beta
08- Reboot and enjoy
everything works fine
ramirrat said:
Used method 2, but flashed this TWRP
Click to expand...
Click to collapse
Got it working now, thanks!
Used Method 1 with given twrp.
@korom42 great job mate! :good:
HI, i'm just doing this guide. i've download the firmware from xperifirm, and i got 3 files withount extension. I've googled and i read a guide to converto these 3 files into a ftf via flashtool. At certain point, i have to select all files except all the .ta files, and create the zip. I'm right?
The files are:
auto-boot.ta
cust-reset-ta
fota-reset.ta
master-reset.ta
osv-restriction.ta
reset-kernel-cmd-debug.ta
reset-non-secure-adb.ta
reset-wipe-reason.ta
simlock.ta
thanks... method 1 [email protected] AndroPlus TWRP 3.1.1.0 used.
Up and running with method 1. Unfortunately I had to use Magisk, but so far it seems to behave. SuperSu does NOT work. It will install, but the device does not show root.
Installed and running with method 1 but got a lot of issue using Windows 10. So i do all the work on a Windows 7 laptop without any problem.
Just 1 thing not working: magisk.
I followed the guide step by step with success, but magisk says me to update, and when i hit yes, nothing happen.
See attachment.
And another thing. I've wiped all except fotakernel, so why when I've boot up the Phone, i find all my apps, my settings and wallpaper Like how i leave them?
Sorry for my English.....
Edit: can't use netflix anymore
Edit2: magisk problem solved. I've download The apk from The site, then installed and when i hit yes to install magisk, it download a flashable via twrp zip, flashed it and magisk work, but now I've Lost safetynet for no reason.....
But i can use netflix now.
Safetynet is a important thing?
I forgot to say that I used Windows 10, as always. Regular command prompt (writing cmd in the start menu will give that, nothing else). But problems with that is usually because of wrong drivers for the phone, nothing else.
After 2 days of usage, i noticed a lot of lag, so i've done a factory reset from the android menu, not twrp, and is all working fine withount any kind of lag (except at powe off, the circle stop running, then after 20 seconds, power off, but it's not important, maybe a sony bug).
Now can i reflash from twrp in order drmfix.zip, SafetyNet Cleaning Tools.zip then Magisk v14.5.zip, or i will do any mistake?
I've noticed sone remote play, netflix, sony news and sony lounge are not working, i think cause DRM
Hello korom42
Are you creating a kernel & root for a new release of sony? There are new updates & I'm eager for this new thing
Flashed 41.3.A.2.24 with wipes
Flashed oreo.img
Flashed twrp.img
Get bootloop
Time to update kernel
there is some problem with that kernel, my phone will reboot unexpectly.I'm sure i flash it the right way
---------- Post added at 12:17 PM ---------- Previous post was at 12:11 PM ----------
ramirrat said:
Flashed 41.3.A.2.24 with wipes
Flashed oreo.img
Flashed twrp.img
Get bootloop
Time to update kernel
Click to expand...
Click to collapse
try twrp 3.2 or 3.0
completed the steps, if i wanted to go back to 7 where do i find those files?