DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
Hello everyone, in this guide i'll be showing you how to install TWRP with Andy Yan's LinageOS, or any other ROM you want.
Make sure to follow this guide if you haven't allready unlocked the bootloader and rooted your phone
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
INSTALLING TWRP
# Make sure you are on android 11 and that you have followed the guide mentioned for unlocking the bootloader and rooting
1. Go in settings app
2. Go in to developer options (they should already be enbled if you folowed the guide mentioned)
3. Enable usb debuging if they aren't allready
4. Reboot to download mode, you can do it with the HW keys or send it from the Android Debuging Bridge (ADB)
For the HW key method power off the phone and conect it to the PC, then hold VOL UP and VOL DOWN at the same time. After that you should get two options, you want the first one which is just press VOL UP.
For the ADB method, install the most up to date SDK platform-tools version and open CMD or TERMINAl in the install folder and type adb reboot download.
A usb debuging request should pop up on the phone, you want to click allow, and it should reboot in to download mode.
5. Open odin, click on AP or PDA and select the twrp file you have downloaded and uncheck auto reboot in options then you can click start
6. After the flashing process hold VOL DOWN and POWER at the same time and immediately after the phone exits the download mode hold VOL UP and POWER at the same time
7. If you failed to boot in to TWRP the instalation process will have to be repeated again.
INSTALING LINAGEOS OR ANY OTHER CUSTOM ROMDownload a AB rom, TREBLE CHECK is wrong.
# You will need an a external Sd_card if you are doing the method 1
Method 1.1. Transfer the linageos .img file you have downloaded to your sd_card.
2. Boot in to TWRP, VOL UP + POWER while booting or adb reboot recovery.
3. Once in TWRP select wipe, click advanced wipe and select data, system, internal storage, cache, dalvik, optional(efs, and thoes other stuff, not going to name them.)
4. After successful wipeing go in to install and select storage, click Micro Sd card and click ok.
5. Click install image and find your LinageOs.img file and select it.
6. Now you should be in a install image screen, select System Image and swipe to FLASH.
7. Reboot and enoy.
Method 2.1. Boot in to TWRP and go in to WIPE, selcect advanced wipe and check data, system, internal storage, cache, dalvik, optional(efs, and thoes other stuff, not going to name them.)
2. Go in to advanced options and select ADB sideload.
3. From the TERMINAL or CMD window type "adb devices" to check if your device is beeing recognized.
4. If the conections is confirmed type "adb sideload LineageOS.zip"
5. After flashing reboot and enoy.
If by any chance you get issues with flashing roms in TWRP because of problems with dynamic partitions flash DynaPatch to allow flashing to dynamic_partitions in recovery, you don't necesery need to use DynaPatch. You can use unviresal system rv disable enable, etc and etc. This is a problem in TWRP it self which soon should be fixed.
Another thing is if you rooted your phone the way in my guide, the patched boot_image might still stick to the new rom.
Knowng bugs:
LinageOs screen touch stop after putting the phone to sleep.
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp
@AndyYan LinageOs
After installing TWRP I can't boot into my system. It's always boot on TWRP. What should I do?
T4mim said:
After installing TWRP I can't boot into my system. It's always boot on TWRP. What should I do?
Click to expand...
Click to collapse
Go in to reboot and reboot to system, but if you installed linageos you mightev installed a rom not ment to be installed. find a A/B rom and install it, and disable dm-verify before installing.
LAST_krypton said:
Go in to reboot and reboot to system, but if you installed linageos you mightev installed a rom not ment to be installed. find a A/B rom and install it, and disable dm-verify before installing.
Click to expand...
Click to collapse
Not working boot up in the TWRP
T4mim said:
Not working boot up in the TWRP
Click to expand...
Click to collapse
Is that after installing linageos? or you haven't rooted the stock rom so you can't boot to it?
Rooted stock rom. I wasn't able to install lineageoS. That's why flashed stock rom again
T4mim said:
Rooted stock rom. I wasn't able to install lineageoS. That's why flashed stock rom again
Click to expand...
Click to collapse
please give me a stock rom file?
Jayke770 said:
please give me a stock rom file?
Click to expand...
Click to collapse
Download Samsung Galaxy A12 SM-A125F firmware
Download the latest Samsung firmware for Galaxy A12 with model code SM-A125F. Check out our free download or super fast premium options.
www.sammobile.com
T4mim said:
Rooted stock rom. I wasn't able to install lineageoS. That's why flashed stock rom again
Click to expand...
Click to collapse
I don't quite undrstand, so you weren't able to boot to rooted stock rom after installing twrp?
LAST_krypton said:
I don't quite undrstand, so you weren't able to boot to rooted stock rom after installing twrp?
Click to expand...
Click to collapse
Yes. I don't understand also.
T4mim said:
Yes. I don't understand also.
Click to expand...
Click to collapse
Have you patched just the boot.img or the whole AP file when selcting a file for patching in magisk?
Covering some misleading theories and issues with our A12
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread. Please don't comment or chat here if it isn't releated with something I said. If you need further help with...
forum.xda-developers.com
just boot.img
T4mim said:
just boot.img
Click to expand...
Click to collapse
Well, thats why. I mentioned that in my rooting guide allready. Shouldev followed it before doing this one. And said here https://forum.xda-developers.com/t/unlocking-the-bootloader-and-rooting.4331859/
https://forum.xda-developers.com/t/...ing-theories-and-issues-with-our-a12.4336999/
LAST_krypton said:
6. Now you should be in a install image screen, select System Image and swipe to FLASH.
7. Reboot and enoy.
Click to expand...
Click to collapse
Everything works (root/twrp) until the last 2 steps. Installing Lineage and enjoying it. I have downloaded the appropriate archive, unpacked and copied it to sdcard alonside with disable dm verity.
When I try to flash the rom, I get an error that sounds like this: couldn't find partition as system_image. What should I do.
RaresCelTare said:
Everything works (root/twrp) until the last 2 steps. Installing Lineage and enjoying it. I have downloaded the appropriate archive, unpacked and copied it to sdcard alonside with disable dm verity.
When I try to flash the rom, I get an error that sounds like this: couldn't find partition as system_image. What should I do.
Click to expand...
Click to collapse
Download the apropriate .img file for device. A/B. If that doesn't fix the problem then it is something with the TWRP, I'v been getting does error too. You are not the only one.
@LAST_krypton
Already tried the A/B version, but let's verify that I got the right version:
lineage-18.1-20210914-UNOFFICIAL-treble_arm64_bvS.img.xz 563.8 MB
Could you also point me to a link for disable-dm-verity?
I reinstalled the magisk patched version since I need a working phone. Should I try again with the TWRP+Lineage? Maybe second time's the charm?
RaresCelTare said:
@LAST_krypton
Already tried the A/B version, but let's verify that I got the right version:
lineage-18.1-20210914-UNOFFICIAL-treble_arm64_bvS.img.xz 563.8 MB
Could you also point me to a link for disable-dm-verity?
I reinstalled the magisk patched version since I need a working phone. Should I try again with the TWRP+Lineage? Maybe second time's the charm?
Click to expand...
Click to collapse
That is the right treble version, If you pre rooted your phone mentioned in my rooting guide dm-verify is disabled. Try following both of my guides mentioned. Use this for dm-verify if you haven't followed my guide for rooting https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
LAST_krypton said:
Knowng bugs:
LinageOs screen touch stop after putting the phone to sleep.
Click to expand...
Click to collapse
I have a question. If even the automatic screen sleep after 15 seconds makes the screen touch unresponsive, how is this rom usable? You never turn off the screen?
RaresCelTare said:
I have a question. If even the automatic screen sleep after 15 seconds makes the screen touch unresponsive, how is this rom usable? You never turn off the screen?
Click to expand...
Click to collapse
By editng the kerenl and disabeling deep sleep features. I haven't tried doing that but mentioned it in some older posts.
@LAST_krypton With the latest TWRP I installed Lineage. How do I manually edit the kernel?
Related
Hi. I'm here for help you
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Click to expand...
Click to collapse
1) How to install? If you have stock zenui go to 1C, if you have a custom ROM go to 1A
If you don't backup all your data you lost all.
1A) First do a TWRP backup on sdcard (if you don't have sdcard just do in internal storage and save the backup on pc. Select system, data, recovery and boot. Then go to wipe - advanced wipe, select dalvik, system, data, cache and Swype.
Then reboot in fastboot.
Now your phone don't have any OS installed so don't boot. We are going to install the stock and unmodified firmware and recovery on the phone.
1B) Download Asus flashtool:
https://drive.google.com/file/d/0B9rp3AJHKJXjNmRuRUJMWmtOT3c/view
and android 7 raw firmware for
ZE552KL:
http://www.mediafire.com/file/o12vo...14.2020.1703.28_M3.10.47.3_Phone-user.raw.zip
ZE520KL: http://www.mediafire.com/file/5qrp2...14.2020.1703.28_M3.10.47.3_Phone-user.raw.zip
Now boot your phone in fastboot, connect to pc, install and open Asus flash tool, select raw file and device model and flash the firmware. If the pc don't detect your phone install the drivers.
1C) Download from Asus site the latest nougat update:
WARNING: IF YOU OPEN THE ZIP FILE THE RECOVERY FAIL TO UPDATE
And you must delete this zip and download another
ZE552KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-14.2020.1712.85-user.zip
ZE520KL:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-14.2020.1712.85-user.zip
Put in device storage and wait the device to detect the update. Tap on notification and install. If fail try in order:
-put in sdcard and update via STOCK recovery
-sideload the file from your PC via adb
-download the file with another browser and delete the previous
After that, so the same with Android 8.0 update
ZE552KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1712.31-user.zip
ZE520KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1712.31-user.zip
2) Flash recovery
I know there are another method to flash a recovery but this method is simply:
2A) Download twrp from this thread:
https://forum.xda-developers.com/zenfone-3/development/recovery-twrp-3-2-1-ze520kl-ze552kl-t3742765
Download Zenfone 3 toolkit from this thread:
https://forum.xda-developers.com/zenfone-3/how-to/tool-zenfone-3-one-click-tool-t3507417
2B) Unpack and go to zenfone3_clictool/twrp folder. Delete both recoveries and put the 3.2.1 twrp in folder. If you have ZE552KL rename with " twrp-3.0.2-Z012D ", if you have ZE520KL rename with " twrp-3.0.2-Z017D ". Now boot your phone in fastboot, connect to pc and open the Zenfone 3 click tool, follow the instructions and select flash twrp for your device. Reboot your phone in recovery and see if can read internal storage. If read 0B try another time.
3) Rooting is so simple. Just download Magisk
boot in twrp and flash
Xposed work well, I tested only gravitybox
Substratum works... Meh
Reserved
ExperienceTesla said:
2) Flash recovery
I know there are another method to flash a recovery but this method is simply:
2A) Download twrp: https://www.dropbox.com/s/r9o4a3elbgvg6rj/twrp-3.2.1-0-Z012-20171220-oreotest.img?dl=1
Download Zenfone 3 toolkit from this thread:
https://forum.xda-developers.com/zenfone-3/how-to/tool-zenfone-3-one-click-tool-t3507417
2B) Unpack and go to zenfone3_clictool/twrp folder. Delete both recoveries and put the 3.2.1 twrp in folder. If you have ZE552KL rename with " twrp-3.0.2-Z012D ", if you have ZE520KL rename with " twrp-3.0.2-Z017D ". Now boot your phone in fastboot, connect to pc and open the Zenfone 3 click tool, follow the instructions and select flash twrp for your device. Reboot your phone in recovery and see if can read internal storage. If read 0B try another time.
Click to expand...
Click to collapse
Great job!
However, I have a question. TWRP you mention to in 2A's version is 3.0.2 or 3.2.1?
I'm sorry that my English is bad.
So, just to be sure, I'm currently on ViperOS, I need to follow from 1A step, right? Or anything before that I have to do first?
nyanntaryou said:
Great job!
However, I have a question. TWRP you mention to in 2A's version is 3.0.2 or 3.2.1?
I'm sorry that my English is bad.
Click to expand...
Click to collapse
Is 3.2.1 . It's a beta TWRP so may have some bug. But basic functions works
tkhquang said:
So, just to be sure, I'm currently on ViperOS, I need to follow from 1A step, right? Or anything before that I have to do first?
Click to expand...
Click to collapse
Yes. You need to follow whole thread: first start with backup, save backup to pc, flash stock ecc ecc
ExperienceTesla said:
Is 3.2.1 . It's a beta TWRP so may have some bug. But basic functions works
Click to expand...
Click to collapse
Can it work on both ze520kl and ze552kl?
Thank you in advance for your kind cooperation.
nyanntaryou said:
Can it work on both ze520kl and ze552kl?
Thank you in advance for your kind cooperation.
Click to expand...
Click to collapse
No, it doesn't work on the ZE520KL.
As oreo is finally available on this phone I'll also build a new twrp version for it
(If anyone is wondering: I posted OP's twrp some time ago in the oreo beta leak thread here)
Stay tuned...
planet9 said:
No, it doesn't work on the ZE520KL.
As oreo is finally available on this phone I'll also build a new twrp version for it
(If anyone is wondering: I posted OP's twrp some time ago in the oreo beta leak thread here)
Stay tuned...
Click to expand...
Click to collapse
Thank you for the great work!
The ZE552KL TWRP works fine for flashing the Magisk at my ZE520KL but not much else
I can't wait to get a proper TWRP for my ZE520KL
Will this also work for Z012DC (Canadian 5.5" Zenfone3)? I'm running WW_14.2020.1709.68 with TWRP and rooted, would I start from 1A or 1C?
rdmozero said:
Thank you for the great work!
The ZE552KL TWRP works fine for flashing the Magisk at my ZE520KL but not much else
I can't wait to get a proper TWRP for my ZE520KL
Click to expand...
Click to collapse
Is there any issues when you flashed twrp on your phone ze520kl?
rdmozero said:
Thank you for the great work!
The ZE552KL TWRP works fine for flashing the Magisk at my ZE520KL but not much else
I can't wait to get a proper TWRP for my ZE520KL
Click to expand...
Click to collapse
I really didn't expect this to work - there's always something new to learn
mecoromeo said:
Is there any issues when you flashed twrp on your phone ze520kl?
Click to expand...
Click to collapse
You can find the proper twrp version for your devices here:
https://forum.xda-developers.com/zenfone-3/development/recovery-twrp-3-2-1-ze520kl-ze552kl-t3742765
Ok, so I flash TWRP recovery and everything is OK, but, When I start the phone, it goes to bootloop...What should I do? Am I missing a step?
@Kevinxdfun29
Flash magisk, supersu binary or the no verify file if you don't want root. Then wipe cache and dalvik .
ExperienceTesla said:
Hi. I'm here for help you
1) How to install? If you have stock zenui go to 1C, if you have a custom ROM go to 1A
If you don't backup all your data you lost all.
1A) First do a TWRP backup on sdcard (if you don't have sdcard just do in internal storage and save the backup on pc. Select system, data, recovery and boot. Then go to wipe - advanced wipe, select dalvik, system, data, cache and Swype.
Then reboot in fastboot.
Now your phone don't have any OS installed so don't boot. We are going to install the stock and unmodified firmware and recovery on the phone.
1B) Download Asus flashtool:
https://drive.google.com/file/d/0B9rp3AJHKJXjNmRuRUJMWmtOT3c/view
and android 7 raw firmware for
ZE552KL:
http://www.mediafire.com/file/o12vo...14.2020.1703.28_M3.10.47.3_Phone-user.raw.zip
ZE520KL: http://www.mediafire.com/file/5qrp2...14.2020.1703.28_M3.10.47.3_Phone-user.raw.zip
Now boot your phone in fastboot, connect to pc, install and open Asus flash tool, select raw file and device model and flash the firmware. If the pc don't detect your phone install the drivers.
1C) Download from Asus site the latest nougat update:
WARNING: IF YOU OPEN THE ZIP FILE THE RECOVERY FAIL TO UPDATE
And you must delete this zip and download another
ZE552KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-14.2020.1712.85-user.zip
ZE520KL:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-14.2020.1712.85-user.zip
Put in device storage and wait the device to detect the update. Tap on notification and install. If fail try in order:
-put in sdcard and update via STOCK recovery
-sideload the file from your PC via adb
-download the file with another browser and delete the previous
After that, so the same with Android 8.0 update
ZE552KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1712.31-user.zip
ZE520KL: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1712.31-user.zip
2) Flash recovery
I know there are another method to flash a recovery but this method is simply:
2A) Download twrp: https://www.dropbox.com/s/r9o4a3elbgvg6rj/twrp-3.2.1-0-Z012-20171220-oreotest.img?dl=1
Download Zenfone 3 toolkit from this thread:
https://forum.xda-developers.com/zenfone-3/how-to/tool-zenfone-3-one-click-tool-t3507417
2B) Unpack and go to zenfone3_clictool/twrp folder. Delete both recoveries and put the 3.2.1 twrp in folder. If you have ZE552KL rename with " twrp-3.0.2-Z012D ", if you have ZE520KL rename with " twrp-3.0.2-Z017D ". Now boot your phone in fastboot, connect to pc and open the Zenfone 3 click tool, follow the instructions and select flash twrp for your device. Reboot your phone in recovery and see if can read internal storage. If read 0B try another time.
3) Rooting is so simple. Just download Magisk
boot in twrp and flash
Xposed work well, I tested only gravitybox
Substratum works... Meh
Click to expand...
Click to collapse
My phone is now WW-15.0410.1712.31
I cant sure that my phone will boot or not after flashed twrp. So I go to fastboot mode, and boot into twrp by command:
fastboot boot twrp-3.2.1-0-Z012-20171220-oreotest.img
downloading 'boot.img'...
OKAY [ 0.786s]
booting...
But nothing happens, my phone still in fastboot mode.
I can boot into twrp with beta oreo previously released.
I think that twrp is not compatible with official oreo now.
sontranngoc said:
My phone is now WW-15.0410.1712.31
I cant sure that my phone will boot or not after flashed twrp. So I go to fastboot mode, and boot into twrp by command:
fastboot boot twrp-3.2.1-0-Z012-20171220-oreotest.img
downloading 'boot.img'...
OKAY [ 0.786s]
booting...
But nothing happens, my phone still in fastboot mode.
I can boot into twrp with beta oreo previously released.
I think that twrp is not compatible with official oreo now.
Click to expand...
Click to collapse
Try install recovery following the instructions in first post. Worked for me
If the "zenfone3 clicktool" method not work try
fastboot flash recovery twrp-3.2.1-0-Z012-20171220-oreotest.img
So reboot in recovery and give me a feedback
ExperienceTesla said:
Try install recovery following the instructions in first post. Worked for me
If the "zenfone3 clicktool" method not work try
fastboot flash recovery twrp-3.2.1-0-Z012-20171220-oreotest.img
So reboot in recovery and give me a feedback
Click to expand...
Click to collapse
Yes. I flashed the twrp successfully. But I cant boot into twrp without flashed it. I need to backup the latest stock recovery, in order to flash a new stock rom in future.
i got bootloop after trying to reboot my phone from twrp recovery. wtf
Flat Bar Indicator
w1040 said:
i got bootloop after trying to reboot my phone from twrp recovery. wtf
Click to expand...
Click to collapse
When does Android 8.0 support the Flat Bar Indicator module?
dzunghooca said:
When does Android 8.0 support the Flat Bar Indicator module?
Click to expand...
Click to collapse
Wrong thread bro
Hello, I was searching for a root for my "new" Samsung J3 Prime (SM-J327W) that I got from my sister. I did the OEM Unlock and in ODIN Mode, it says that it's also "FRP LOCK : OFF". So far, CF-Auto-Root didn't work and all TWRP images, that I found, wouldn't even download on the device . I tried images for the "T", "P" and "U" variants also. The "P" one, lead to bootloop (I recovered stock rom since I got it). So is there any root for this device? It's on the latest versions of firmware and Android available for it.
Did you find anything for the J327W yet? I can only find ROMs for the 320, 327P and 330. I've been having very erratic battery life for over a year. It started after a factory android update. Sometimes my battery life will drop from 70% down to less than 5% in a minute. I've done a factory reset, cleared the cache and replaced the battery but nothing has helped. Trying to put a new ROM OS on this POS is my last hope.
shane_c said:
Did you find anything for the J327W yet? I can only find ROMs for the 320, 327P and 330. I've been having very erratic battery life for over a year. It started after a factory android update. Sometimes my battery life will drop from 70% down to less than 5% in a minute. I've done a factory reset, cleared the cache and replaced the battery but nothing has helped. Trying to put a new ROM OS on this POS is my last hope.
Click to expand...
Click to collapse
I think you'll need a battery replacement at this point... I did build a TWRP ROM myself for my popeltecan (code name of J327W in Canada apparently) but, according to a TWRP Builder Developer, my device might have some kernel issues with TWRP so I can share my ROM but I am not sure it will work on your device. Do you have your stock ROM in case?
Here is a GDrive link to my recoveries, there's the stock and the twrp one but be aware that you need all the ROM if there is a problem with the twrp (that means stock : BL, AP, CP and CSC). But you can use the stock recovery to build a device tree.
https://drive.google.com/open?id=1dNZGaNvCtd5kinHNfnr8MV5Z6o2_GOj4
MikasuX14 said:
I think you'll need a battery replacement at this point... I did build a TWRP ROM myself for my popeltecan (code name of J327W in Canada apparently) but, according to a TWRP Builder Developer, my device might have some kernel issues with TWRP so I can share my ROM but I am not sure it will work on your device. Do you have your stock ROM in case?
Click to expand...
Click to collapse
Replaced the battery about 3 months ago but it made no difference. I have some vacation time coming up so will have a little more free time to look into things.
shane_c said:
Replaced the battery about 3 months ago but it made no difference. I have some vacation time coming up so will have a little more free time to look into things.
Click to expand...
Click to collapse
Maybe a factory reset would be a good idea to try. If you want to try my twrp recovery build, you'll be wiping your data anyway. I highly suggest you to get the full stock rom since even just getting back the stock recovery could end up with a weird sort of corruption (like duplicated or unknown options inside the Settings app, or at least I experienced that). I am not responsible if it breaks anything, you were warned to get your precautions such as getting the stock rom.
MikasuX14 said:
Hello, I was searching for a root for my "new" Samsung J3 Prime (SM-J327W) that I got from my sister. I did the OEM Unlock and in ODIN Mode, it says that it's also "FRP LOCK : OFF". So far, CF-Auto-Root didn't work and all TWRP images, that I found, wouldn't even download on the device . I tried images for the "T", "P" and "U" variants also. The "P" one, lead to bootloop (I recovered stock rom since I got it). So is there any root for this device? It's on the latest versions of firmware and Android available for it.
Click to expand...
Click to collapse
hi if your still looking. i looked into it and the j327u twrp does work on j327w. i had the same problem trying to gain SU access with the other image files for j327w i had to use magisk zip and install it from twrp menu. had to format data and mount system in twrp.
twrp j327u does work but i could not get supersu or magisk to work, my build is J327WVLS4BSK1 with 8.1.0 oreo. i'm not sure there's a way to get past dm-verity using the boot patch by asphyx in the TWRP threads or the universal dm-verity workaround by zackptg5.
i first flashed twrp j327u using odin, ran up against dm-verity when running supersu. both MikasuX14 and another twrp j327w version i found would also flash and load, but the touchscreen wouldn't register my input. cfar didn't work either
sfirmware (website) has workable firmware for rev 4 j327w builds in case you need to recover your phone from soft brick - i could get my build's firmware to flash using the patched odin 13.3.3 version found on this site
bytwigorlimerick said:
twrp j327u does work but i could not get supersu or magisk to work, my build is J327WVLS4BSK1 with 8.1.0 oreo. i'm not sure there's a way to get past dm-verity using the boot patch by asphyx in the TWRP threads or the universal dm-verity workaround by zackptg5.
i first flashed twrp j327u using odin, ran up against dm-verity when running supersu. both MikasuX14 and another twrp j327w version i found would also flash and load, but the touchscreen wouldn't register my input. cfar didn't work either
sfirmware (website) has workable firmware for rev 4 j327w builds in case you need to recover your phone from soft brick - i could get my build's firmware to flash using the patched odin 13.3.3 version found on this site
Click to expand...
Click to collapse
heres what i did. i soft bricked, bootlooped and had to flash firmware from sfirmware a few times to get it to work
i used a twrp for j327u i found on a another similar thread on this topic. i flashed it with odin.
once inside twrp menu i went to wipe menu, i hit format, then back to mount menu, checked boxes data/system (previously data or system wouldnt check off before formatting data).once data and system were mounted i then
plugged phone back into computer while in twrp menu. the phone showed up as J327u cut/paste the latest magisk .exe into the internal storage of j327u (on computer) . i then on twrp menu found and installed magisk exe finally got it to properly install magisk i then in reboot menu hit system and reboot.
the phone restarted after awhile like it was factory reset but once i set up the phone magisk apk was already installed and root access was available. hope this helps.
so i've been busy for a long while before looking back into this. I will try again with the J327U rom. Right now, i struggle to find stock roms of the J327W because i flashed a not working twrp apparently and it locks my boot.
The J327U TWRP didn't work for me. Though, twrp itself works but i cannot get the system to boot and i cannot get to root it, no matter what i tried, i ended up in boot loop.
I managed to root this phone without TWRP. I used Linux tools to do this so I'm not sure if it could work on Windows.
Requirements:
Stock ROM for your phone (I used samfirm.js to pull it from the Samsung servers but downloading from sammobile.com works too)
A way to extract zip files
A way to extract tar files
Heimdall flasher (https://www.glassechidna.com.au/heimdall/)
Magisk Manager APK
An Internet connection on your phone
A compatible USB connector for your phone
Of course, a SM-J327W running the stock Android firmware
Obligatory warning: This WILL void the warranty of your phone and permanently trigger the warranty void flag. It also WILL cause a factory reset, so back up all your data first.
Bear with me, because there are a lot of steps. This will take around 15 to 30 minutes.
You will need to download and extract a stock ROM for your phone. Make sure that you download a ROM for the SM-J327W and not another model. Also make sure to download the latest version available.
Stock ROMs usually come in a zip file containing a few tar.md5 files. You will only need to extract the one that starts with "AP" for this procedure.
Step 1: Extract the tar.md5 file that starts with "AP" from your stock rom.
Step 2: Open the tar.md5 file in an archive manager. You may need to remove ".md5" from the end of the file.
Step 3: Extract the boot image (boot.img) from the AP file.
Step 4: Upload the boot image and the Magisk Manager APK to your phone. You can use ADB to transfer the files. For example:
adb push boot.img /storage/emulated/0
adb push Magisk-v22.0.apk /storage/emulated/0
Step 5: Open the files app on your phone. Navigate to the internal storage and tap on the Magisk APK file to install it. You may be prompted to allow installation from unknown sources.
Step 6: Open the Magisk app. It should say that Magisk isn't installed and it shoulld say "Yes" beside "Ramdisk". Tap the cogwheel icon in the top-right corner.
Step 7: Due to a bug in Magisk, you need to install version 21 instead of the latest version (v22). Set the update channel to "Custom Channel".
Step 8: When prompted, enter the following URL: "https://raw.githubusercontent.com/t...d863d3a15c6a2276b1061a280ece80ed7/stable.json" (Without the quotes.)
Step 9: Now it's time to patch the boot.img file. Tap the button to install Magisk and select the option to patch a file. When prompted, navigate to the internal storage and select the boot.img file that you transferred previously.
Step 10: Magisk will patch the file and tell you where it saved the patched file. Transfer the patched file to your computer. You can use ADB for this, for example:
adb pull /storage/emulated/0/Download/magisk_patched_XXXXX.img
Remember to replace the Xs with the the random characters that Magisk added to the file name.
Step 11: Reboot your phone into Download mode. You can shut it down and then hold the power, home, and volume down buttons at the same time to enter Download mode or use ADB: "adb reboot bootloader"
Step 12: A warning may show about the dangers of installing a custom OS. Press the volume up key to continue.
Step 13: The screen should now show "Downloading... Do not turn off target." If your phone isn't already plugged into your computer, plug it in now.
Step 14: Use Heimdall flasher to flash the patched boot image. For example:
heimdall flash --BOOT magisk_patched_XXXXX.img
Again, replace the Xs with the random characters that Magisk added to the file name.
Step 15: After a few seconds, Heimdall should report that the flash succeeded and your phone will reboot. It may take longer than usual. Leave it to do its thing and DO NOT pull out the battery.
Step 16: Your phone will show a notice that unauthorized changes have been detected and will prompt you to factory reset it. Press the button to perform the factory reset.
Step 17: Set up your phone as if it was new. It's not rooted yet, but you're really close if you got so far.
Step 18: Once you reach the home screen, upload the Magisk Manager APK to your phone again and install it like before.
Step 19: Open Magisk Manager. It will show that Magisk is installed and may prompt you to reboot to complete installation. Do not update Magisk to v22 or you will lose root access and you will have to flash the patched image again.
In the (very unlikely) case that your phone doesn't boot after flashing the patched boot.img, you can simply flash the original boot image and it should be fixed.
CONGRATULATIONS! You just rooted your SM-J327W successfully.
I also managed to port TWRP to this phone with the touchscreen working using the kernel from a recovery image for the SM-J327P found here: https://forum.xda-developers.com/t/...-1-samsung-galaxy-j3-emerge-sm-j327p.3573607/. All the partitions are mapped correctly. Due to a bug (presumably with the kernel), the data partition can unfortunately only be mounted read-only. However, this shouldn't affect being able to flash zips on your phone and you can insert an SD card to write backups onto. In the future, I may port CWM recovery to this phone using the stock kernel to be able to mount the data partition read-write.
You can find my custom recovery attached to this reply.
Follow up: It seems that the bug that causes Magisk to fail is fixed in the latest version (v22.1.) As a result, steps 6-8 in my previous post are unnecessary.
MikasuX14 said:
Here is a GDrive link to my recoveries, there's the stock and the twrp one but be aware that you need all the ROM if there is a problem with the twrp (that means stock : BL, AP, CP and CSC). But you can use the stock recovery to build a device tree.
https://drive.google.com/open?id=1dNZGaNvCtd5kinHNfnr8MV5Z6o2_GOj4
Click to expand...
Click to collapse
link is dead do you have twrp for j327w?
This TWRP recovery is compiled from source & not official yet
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Official TWRP Website : https://twrp.me/umidigi/onemax.html
GitHub Release : Here (release name : TWRP-UMIDIGI-One_Max)
Version Information
ROM OS Version: 8.1.x Oreo
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Are there any decent ROMs yet for this phone? LineageOS would be fantastic.
@kgoerbig not to my knowledge. Maybe I'll try porting a 9.0 GSI soon.
I'm not sure if this is helpful or not, but Umidigi posts stock ROM on there forum. Can ROMs be ported based on there code? Or is it more complicated then that?
https://community.umidigi.com/m/?a=viewthread&tid=18692
_cab13_ said:
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Click to expand...
Click to collapse
I have tested LineageOS 16.0 GSI Android 9.0 (and many others ...) and it works well, even GSM and Camera.
The only thing I cannot have is a complete root : I install Magisk 19.3 correctly, but applications cannot get root permission (Titanium Backup cannot have su permission)
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
silviuss82 said:
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
Click to expand...
Click to collapse
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
dreambo said:
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
Click to expand...
Click to collapse
kgoerbig said:
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
Click to expand...
Click to collapse
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
dreambo said:
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Click to expand...
Click to collapse
kgoerbig said:
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
Click to expand...
Click to collapse
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
dreambo said:
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
Click to expand...
Click to collapse
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
kgoerbig said:
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
Click to expand...
Click to collapse
I have used the European one, UMIDIGI One Max E V1.0
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
"Couldn't wait, ended up formatting with encryption disabled via a zip + magisk"
How did you format without encryption? I try to format from TWRP, type 'yes' , to verify, and encryption is still active. I'd like to disable encryption, so that I can properly backup everything from TWRP.
kgoerbig said:
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
Click to expand...
Click to collapse
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
dreambo said:
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
Click to expand...
Click to collapse
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
kgoerbig said:
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
Click to expand...
Click to collapse
Which AOSP ? where do you found it ?
dreambo said:
Which AOSP ? where do you found it ?
Click to expand...
Click to collapse
This thread:
https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521
This Rom
https://github.com/phhusson/treble_experimentations/releases
Do a complete backup of stock from TWRP onto microsd or USB first! System, data, modem, nvram partitions etc. That way you can restore from TWRP, and not lose os, data, or nvram (IMEI).
Specifically, system-arm64-aonly-gapps-su.img.xz
1. Download and extract file you downloaded, onto your phone.
2. Do a format (type yes)
3. Install from TWRP as "image".
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery
3. Latest adb & fastboot files
4. Stock ROM ZIP files
5. Stock Recovery [OPTIONAL]
Custom Recovery Method:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_*.zip /sdcard or MTP
3. Wipe data, cache & dalvik (format data if stuck at boot animation)
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip. Your device will have Stock Recovery with Stock ROM. Finally Reboot.
Fastboot Method:
Note: Following process formats internal storage, so backup the internal storage files. If your device is in Stock ROM & somehow system partition is messed up just flash only system.
1. Download required Fastboot files
2. If downloaded 7z files, extract system.img file.
3. Enter
Code:
fastboot -w && fastboot erase system && fastboot flash recovery recovery.img && fastboot flash boot boot.img && fastboot flash vbmeta vbmeta.img && fastboot flash dtbo dtbo.img && fastboot flash system system.img && fastboot reboot
4. It takes a while to flash System partition, have patience.
5. Device reboots to system if everything is flashed successfully.
Stock Recovery Method:
1. Download Stock ROM OZIP Files & Stock Recovery
2. Copy *.ozip to sdcard or internal storage.
2. Goto fastboot & enter fastboot flash recovery recovery.img
3. Reboot to recovery, wipe (1st option). Then go back to main menu Install from storage locate the *.ozip file & install.
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
ceesiama said:
I'm sorry, but this doesn't work for me..stuck with the rooted but uninstalled magisk OS.. :'(
Click to expand...
Click to collapse
zip isn't installed successfully? can you also send screenshot, so I can help you.
4j17h said:
zip isn't installed successfully? can you also send screenshot, so I can help you.
Click to expand...
Click to collapse
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Yes, since device is decrypted lock screen doesn't work. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
4j17h said:
ok no problem, so what do you want to know about? Clear data, cache, dalvik after or before flashing stock zip it won't bootloop. Coming to Magisk, yes that method is not reliable. I have figured out 100% working way which works for everyone & doesn't fail anytime. Maybe I will make a new guide soon or ...Mod edit: Link to Telegram removed
Click to expand...
Click to collapse
I'm sorry I mistyped in the above comment, when i followed your method, zip installed successfully but it bootlooped into stock recovery everytime. I hope that clarifies a bit. I''ll be very grateful if you can help me..
ceesiama said:
https://forum.xda-developers.com/realme-3-pro/how-to/guide-unlock-bootloader-install-twrp-t3938845
I followed this guide, everything went smooth, magisk was also installed and rooted. But I tried setting fingerprint and set lock pin, But it says wrong pin everytime, so i had to reset the phone again. I used the same method above. But this time magisk won't install no matter how many times I reset my phone using the above method. So I thought if I could revert back to stock, maybe I can root and install magisk again. So i followed your guide.
After installing the stock zip and reboot to system, it stuck on bootloop(realme logo), then I flash back using the above method again, I can log in to the phone, and red notification says root has been detected, but magisk is not installed, ive tried many things but still i cannot install magisk. I've tried your guide 2/3 bootloop everytime. What could be the problem? I am not very much of a tech genus :'(
Click to expand...
Click to collapse
Try install magisk manager, maybe ur device still rooted
haditriw said:
Try install magisk manager, maybe ur device still rooted
Click to expand...
Click to collapse
no that's not how magisk works in Realme 3 Pro, if device is restarted there will be no magisk. You need to goto fastboot then goto recovery, it boots to system. We have magisk. Yes this method tricky. I am going to publish new guide, it will be simple & straight forward.
Bricked/ Bootlooping
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
4j17h said:
Prerequisite
1. Unlocked Bootloader
2. OrangeFox Recovery or TWRP Recovery or Pitch Black Recovery
3. Latest adb & fastboot files
4. Stock ROM zip files: RMX1851_A15
5. Stock Recovery [OPTIONAL]
Follow the below steps:
1. Enable USB-Debugging: adb reboot recovery or hold the volume up while rebooting or hold the volume down to enter bootloader & choose Reboot to Recovery by volume buttons, power key to enter.
2. Copy the Stock ROM zip to your device via adb push RMX1851_flashable_A15.zip /sdcard or MTP
3. Wipe data, cache & dalvik
4. Locate the zip file & Install
5. Flashing all the partitions with stock files takes time. Hold for a while.
6. After successful install of the zip, Reboot to System. You get the stock Recovery & stock ROM.
Previous Firmware: RMX1851_A14 Google Drive || AndroidFileHost || Mega Cloud storage
Note: This guide will be updated in coming days with fastboot flash files & custom recovery flashable files with latest versions.
Click to expand...
Click to collapse
pls help me, im stuck on bootloop :'(
malakaz27 said:
pls help me, im stuck on bootlooop :'(
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
pls help me, im stuck on bootloop :'(
Click to expand...
Click to collapse
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
this method worked perfectly fine for me. i tried both lineage os roms available and both of them caused bootloop or end up destroying boot. so thanks to developer for making this zip file.
4j17h said:
I have seen you have started a new thread of bootloop. Is this because you flashed one of these stock zip? you were going back to stock from los?
Click to expand...
Click to collapse
hi i am stuck in bootloop after flashing all stuff in fastboot guide
leo77g said:
hi i am stuck in bootloop after flashing all stuff in fastboot guide
Click to expand...
Click to collapse
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
4j17h said:
bootloop to recovery? have you tried fastboot -w usually this should boot to system or else flash stock recovery, wipe full. This should definitely get back the device to system.
Click to expand...
Click to collapse
formatting worked and thanx for help )
Moderators' Announcement: I've removed the links to Telegram and references to it. This is not a development thread, and support is to be provided through XDA. Many posts proved this has not been the case!
You may be asking, "Why was my Telegram or Whatsapp thread closed?"
Well, it's just becoming too much.
Going forward, we will only allow one Telegram chat link on a development thread by the ROM's developer and only if thorough support is still provided in the ROM thread on XDA.
All discussion channels, photography channels, whatnot channels will be strongly discouraged and removed with immediate effect. Please reference the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Also, we now have an official XDA Discord Server. We would encourage you to try it out.
Announcing the Official XDA-Developers Discord Server
FYI
Thanks,
The Moderation Team
Click to expand...
Click to collapse
Need Help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
ResSetOk said:
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
Click to expand...
Click to collapse
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
4j17h said:
since your bootloader is locked, all you can do is wipe full data or flash back P2Q then format & then flash Q2P.
Click to expand...
Click to collapse
I did Wipe before and after firmware, on P2Q is stitched without problems, but under firmware in Q2P in recovery writes, that not managed wipe userdata. The data was not encrypted, the password is not asked.
do you have video for Fastboot Method ?
[No message]
KINDLY CHECK THE LATEST POST. I HAVE AN UPDATE REGARDING THIS ROM.------------------------------------------------------------------THIS IS NOT A CUSTOM ROM! IS A MODIFIED VERSION OF THE ORIGINAL ROM!
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 ROM 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.
FLASHING PROCEDURE
Download the latest build
Reboot to recovery
Take Backup (Not Necessary)
Wipe System, Data, Cache , Dalvik
Flash the latest build
Reboot
Done!
DOWNLOAD LINK:V1.0
IMPROVED
Faster scroll
Deleted bloatware apps (More space)
More coming in the future!
Firstly, thanks for taking the time to make this, it's appreciated.
I have followed your instructions to the best of my abilities:
*Reboot to recovery (TWRP)
*Wipe System, Data, Cache , Dalvik
*Flash the latest build
*Reboot
but now TWRP is telling me there is no OS? WTF? Help!!
I can still boot into TWRP recovery and fastboot if needed but would prefer to maintain root if at all possible.
iFink said:
Firstly, thanks for taking the time to make this, it's appreciated.
I have followed your instructions to the best of my abilities:
*Reboot to recovery (TWRP)
*Wipe System, Data, Cache , Dalvik
*Flash the latest build
*Reboot
but now TWRP is telling me there is no OS? WTF? Help!!
I can still boot into TWRP recovery and fastboot if needed but would prefer to maintain root if at all possible.
Click to expand...
Click to collapse
If you reboot, it boots? And if you want root, you can use magisk
When i reboot it boots straight to Huawei eRecovery not normal system
If you or someone can help me, because this is my first rom.
I don't knwow why is booting in Huawei eRecovery...
But, if you extract, try to repack system.img and flash with fastboot the file "system.img" (the repacked file)
AndroTwrpid said:
If you or someone can help me, because this is my first rom.
I don't knwow why is booting in Huawei eRecovery...
But, if you extract, try to repack system.img and flash with fastboot the file "system.img" (the repacked file)
Click to expand...
Click to collapse
Hi
On my huawei mediapad t3 tablet, I wanted to do a factory reset on TWRP and by mistake I selected "system". By trying the custom installation goes well but when I reboot the tablet hangs on "your device booting now ..."
Can someone help me
I found solution , i posted it to help anyone : #Poste318
Hmm good to see people using this device still!!
Hi,
Many thanks for creating this ROM.
I am wondering if you can help me, I am fairly new to flashing.
I managed to unlock the bootloader and flash TWRP no problem.
In TWRP, I have tried to flash this rom using your instructions, with the exception of flashing Magisk 21.2 immediately after (before reboot). I did also do a format aswell as advanced wipe on the partitions you mentioned, was this my mistake?
Now i just get "Your device is booting now" which never happens.
I went back into TWRP and repeated the process, also flashed a Magisk uninstaller script just incase, then repeated the process again. Still getting the same problem after about 4 attempts.
Do I need to go back to stock and start again?
If so, any help on that would also be appreciated!
Thanks
A better solution is to extract the zip, then boot in twrp mode, then move the system.img to internal storage, click install, select the img file, then choose "system" and done.
Someone here has managed to install this successfully?
twolitrepinto said:
Hi,
Many thanks for creating this ROM.
I am wondering if you can help me, I am fairly new to flashing.
I managed to unlock the bootloader and flash TWRP no problem.
In TWRP, I have tried to flash this rom using your instructions, with the exception of flashing Magisk 21.2 immediately after (before reboot). I did also do a format aswell as advanced wipe on the partitions you mentioned, was this my mistake?
Now i just get "Your device is booting now" which never happens.
I went back into TWRP and repeated the process, also flashed a Magisk uninstaller script just incase, then repeated the process again. Still getting the same problem after about 4 attempts.
Do I need to go back to stock and start again?
If so, any help on that would also be appreciated!
Thanks
Click to expand...
Click to collapse
Hello,
Sorry, this is a bit of off topic, can you tell me how you rooted your device? i can't seem to root mine.
I am totally a noob.
Does this rom fully work?
Thanks for your answer.
gr981888 said:
Hello,
Sorry, this is a bit of off topic, can you tell me how you rooted your device? i can't seem to root mine.
I am totally a noob.
Click to expand...
Click to collapse
You need to first go to dc-unlocker.com, then buy 4 credits, download the software and login in your account in the software. Then enable on the tablet usb debugging and click the magnifying glass and you will get the bootloader code. Then insert the usb cable in the tablet, then go in fastboot mode then open cmd and type: "fastboot oem unlock code" (replace code with the code obtained in dc unlocker) then on the tablet click yes and your tablet will format. done.
Chris_wafer said:
Does this rom fully work?
Thanks for your answer.
Click to expand...
Click to collapse
I don't tested.
Does sanyone have an updated download link? The one on the original post is broken
Lane-boy21 said:
Does sanyone have an updated download link? The one on the original post is broken
Click to expand...
Click to collapse
hey, i lost the files sorry, i'm trying to find it.
I will put the same does anyone can update the download link please ?
Lane-boy21 said:
Does sanyone have an updated download link? The one on the original post is broken
Click to expand...
Click to collapse
Did you get that link in the end ?
Me too