{
"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"
}
Hello guys,
This is my first guide and it is focused on people who just bought their Redmi Note 3 (KENZO/KATE) and having problems with officially unlocking their bootloader. (stuck @ 50% like me)
If you don't want to wait on stock MiUi until you can officially unlock your bootloader (because you need to wait additional ~2 weeks after you received permission from Xiaomi until their servers updated) or you want that extra security layer with locked bootloader this guide is made for you!
Since official LineageOS 14.1 just released, i thought some of you guys are interested in this awesome, easy and safe method.
To save you time searching hours and hours through this forum i made this quick summery.
Downloads :
MiUi 8 Global Developer ROM 6.11.3: KENZO or KATE
ZCX TWRP (direct downloadlink: click here)
Mi Flash 6.8.30
Latest firmware (choose correct device)
[ROM][OFFICIAL][7.1.1][kenzo] LineageOS 14.1 by The_strix
Open GApps - ARM64 - Android 7.1
Instructions : (follow them carefully!)
Extract MiUi 8 Global Developer ROM and replace recovery.img (in images folder) with ZCX TWRP's recovery.img
Flash using Mi Flash (in EDL mode) and check clean_all
After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP (change TWRP language from chinese to english: click here)
Reboot to system (if you get prompt: "Disable stock recovery replace now" > just swipe to allow disable)
Boot to MIUI and complete initial setup (important step - don't skip! first boot will take around 10 minutes)
-----------------------------------------------
Shutdown device and boot to TWRP again
(optinal) Backup every partition and safe this backup on an external device
Wipe > Advanced Wipe > check Dalvik / ART Cache, System, Data, Internal Storage, Cache > Swipe to Wipe
Flash Latest firmware, LineageOS 14.1 and GApps (ARM64, Android 7.1)
Reboot to system and you're DONE!!
updated method (works with newest MIUI version) :
There is a new updated method by kuan improved by @N.G. and @razr_96. Thanks for mentioning.
Advantages:
no need to download full MIUI fastboot rom
much faster method, only takes seconds to flash (instead of 4 minutes and you don't have to complete initial MIUI setup which also takes around 5 minutes)
this method is better if you want to stay on MIUI and just want to root
you can stay on your current MIUI version (even 7.1.19 which is currently the latest) and don't have to wipe your data
Disadvantages:
this doesn't clean everything, i would recommend to clean everything if you want to install a custom rom
you have to download a file i can not verify
Instructions : (follow them carefully!)
(optinal) Backup your current MIUI data (Settings > Additional settings > Backup & reset > Local backups > Back up) and copy it to an external media
Download and extract: Kenzo or Kate
(optinal) Replace included ZCX TWRP recovery.img (in images folder) with your preferred TWRP recovery.img
Flash using Mi Flash 20160401 (in EDL mode) and check flash all except data and storage (not clean_all like in the method mentioned above)
BE AWARE: This MiFlash version is different to the MiFlash version mentioned above! This version does only support 64 bit systems and you need atleast Windows 7!
After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP (change TWRP language from chinese to english: click here)
Reboot to system
Video tutorial: https://www.youtube.com/watch?v=rCONN1_IPuU
Troubleshooting :
[APP][ROOT][7.1.1]QuickSettings Flashlight fix for all nougat roms
If something goes wrong, start over again and follow my guide step by step.
This guide only works with MiUi 8 Global Developer ROM 6.11.3 or lower.
Put MIUI 8 Global Developer ROM in "C:\ROM" - MiFlash tends to have problems if there are any spaces in folder names.
If you flashed something wrong and have no simcard signal anymore or no IMEI look here for help: EFS Recovery Guide
If you didn't remove your passcode before you did a backuprestore using TWRP:
TWRP > Advanced > Filemanager > /data/system > delete locksettings.db
Issues with locked bootloader :
none
(advanced technique) Higher security with locked bootloader:
Thanks @LeoYL !
A little addition: If you want a even higher level of security, which is nobody except you can flash packages in recovery, you can create a recovery with limited functions and forced signature verification, with your own keys embedded in that recovery.
This is just like the original status of nearly all Android devices when they are shipped: only signed OTA update packages can be applied via recovery. Normally, the packages are signed by OEMs; however, you can become the "OEM" by creating your own private key, which is used during package signing.
Just follow these guides to create a recovery with your own keys. I use CM 13.0 recovery, since it only has basic recovery features, including installing a ZIP file, factory reset, and it has mandatory ZIP signature verification.
http://mjg59.dreamwidth.org/31765.html
https://forum.xda-developers.com/showpost.php?p=62796459&postcount=2
The reason why I don't use TWRP is that it allows update packages with any signature. Although you can enforce signature verification, it can also be switched off in TWRP settings.
Now you get a recovery which only accepts ZIP packages that are signed with your own private key. The only downside is you need to sign every package you want to flash each time. But this also means that if a stranger picks your lost phone up, they can't tamper your phone's OS. If the "reset protection" feature works with locked bootloader on our Redmi Note 3, the only distance between our phones' security and Google devices' is edl mode and encryption.
Wanna try other custom roms?
Just follow this guide and you can flash every other nougat customrom as well like:
[ROM]AOSIP 5.5 for Redmi Note 3(Kenzo)[OFFICIAL BUILDS]
[ROM][Nightlies][android-7.1.1_r6]ResurrectionRemix 5.8.0[OFFICIAL][VoLTE]
[ROM][OFFICIAL][Weekly][7.1.1_R13][Slim 7 For Kenzo]
[ROM] ► [7.1.1 ► N4F26M] ► [OTA][OMS][Goodix] ► Nitrogen OS
credits :
@The_strix: For his development work
@Psy_man: For extracting nougat firmware
@kuan: For creating this method (french forum)
@Tobsucht TM: For answering my questions
If this guide was helpful to you, don't forget to press the Thanks! button :good:
Enjoy your new custom rom!
khajiit
This method also works with Kenzo, obviously using the Kenzo miui rom and firmware instead.
razr96 said:
This method also works with Kenzo, obviously using the Kenzo miui rom instead as well as not flashing the kate firmware.
Click to expand...
Click to collapse
That's right! Thanks for pointing it out.
Redmi Note 3 SE _ Kate
Thanks bro worked on my Kate :good:
How to successfully unlock bootloader(official way) worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
Just use that Miflash : rootjunkysdl.com/files/Redmi%20Note%203%20Pro%20Kenzo/Firmware%20Unbrick/MiFlash.zip
Because that one in thread not working properly.
armo1111 said:
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
Just use that Miflash : rootjunkysdl.com/files/Redmi%20Note%203%20Pro%20Kenzo/Firmware%20Unbrick/MiFlash.zip
Because that one in thread not working properly.
Click to expand...
Click to collapse
The guide you linked is not working for me, thats why i made this guide which works 100%.
I tried this with the Global developer ROM for my kenzo.
When I try to get into TWRP, the Mi logo flashes but nothing else happens.
When I let the MIUI ROM start up and try to get into the recovery again,
it only shows me to connect my device to the Mi PC Manager.
What am I doing wrong?
blitzpeace said:
I tried this with the Global developer ROM for my kenzo.
When I try to get into TWRP, the Mi logo flashes but nothing else happens.
When I let the MIUI ROM start up and try to get into the recovery again,
it only shows me to connect my device to the Mi PC Manager.
What am I doing wrong?
Click to expand...
Click to collapse
Did you follow my instructions correctly?
- replaced recovery.img with ZCX TWRP recovery.img - check?
- EDL mode - check?
- remove usb cable after flash and press volume up+power button until mi logo shows up and then release buttons - check?
- are you sure you have kenzo version? did you download rom for kenzo? - check?
!! caution: the rom linked in this guide is only for kate version!!
thank you ! I've been trying the official route for 6 weeks, getting absolutely nowhere (even though I finally do have unlock permission).
this method worked like a charm, finally I'm off MIUI and running LineageOS
khajiit said:
Did you follow my instructions correctly?
- replaced recovery.img with ZCX TWRP recovery.img - check?
- EDL mode - check?
- remove usb cable after flash and press volume up+power button until mi logo shows up and then release buttons - check?
- are you sure you have kenzo version? did you download rom for kenzo? - check?
!! caution: the rom linked in this guide is only for kate version!!
Click to expand...
Click to collapse
1. I guess, do I have to replace only the recovery.img or more? If only recovery.img, then yes!
2. Yes, otherwise MiFlash would give me an error instead of flashing the ROM
3. Yes, but it appears only for an blink of an eye and then disappears again, the phone screen then stays dark
4. Yes, the newest one. Maybe that's the problem?
blitzpeace said:
4. Yes, the newest one. Maybe that's the problem?
Click to expand...
Click to collapse
Yes, that's the problem! This method only works until version 6.11.3.
You have to flash 6.11.3 (or earlier) to get TWRP and then you can flash what you want.
Good luck!
Excellent :good:
To boot into EDL
If you are lost with chinese language in TWRP, look at the first screenshot
And for Gapps take 64bits
Hi, I just got this ROM but when I plug the device in my computer it keeps connecting/disconnecting rapidly. Did I do something wrong?
Very helpful, but i would like to suggest people to use miunlocktool from windows 7-32 bit operating system. Miunlocktool perfectly works in windows 7 & don't stuck at 50%. Before unlock process, just "add oem unlocking device" from MIUI developer setting then start unlocking process..... Its really works for me & also others who followed these steps.
Skex506 said:
Hi, I just got this ROM but when I plug the device in my computer it keeps connecting/disconnecting rapidly. Did I do something wrong?
Click to expand...
Click to collapse
Yes, you did something wrong
Are you sure you have a "KATE" device not "KENZO"?
Follow my guide carefully and try again. It works 100%!
Rifatspir said:
Very helpful, but i would like to suggest people to use miunlocktool from windows 7-32 bit operating system. Miunlocktool perfectly works in windows 7 & don't stuck at 50%. Before unlock process, just "add oem unlocking device" from MIUI developer setting then start unlocking process..... Its really works for me & also others who followed these steps.
Click to expand...
Click to collapse
You don't think i've/we've tried everything? Official unlock works for you? Great! But it doesn't work for everyone... trust me.
Can we please stop to suggest to unlock officially with different guides? This guide is for people who don't want to or can't unlock officially.
khajiit said:
You don't think i've/we've tried everything? Official unlock works for you? Great! But it doesn't work for everyone... trust me.
Can we please stop to suggest to unlock officially with different guides? This guide is for people who don't want to or can't unlock officially.
Click to expand...
Click to collapse
I also said that million times to other people who suggest me different types of official method. When i success after trying couple of methods then i realized it is possible to unlock kate. I'm not saying that your post is not helpful, i saw many post like that, mostly in whirlpool forum. BTW, good luck with your tips :good:
Sure it is possible to unlock Kate officially but you have to wait for Xiaomi to get permission and wait for their servers to syncronize.
You have to wait up to 1 month (depending on your location and other things) until their servers confirms that you have permission to unlock (unable to verify thing). All these guides outside are working but it's a matter of time until they start working. That's why they didn't work for you in first place. :good:
hi @khajiit
They say not enough storage when I want to flash it. Could you please help me with this?
Spoiler: not enough
actuallyaka said:
hi @khajiit
They say not enough storage when I want to flash it. Could you please help me with this?
Click to expand...
Click to collapse
You are using a really old MiFlash version, try updating to the version mentioned in this guide.
And rename your folder "Redmi note 3 pro" to "Redmi.note.3.pro" or "Redmi_note_3_pro".
MiFlash tends to have problem with spaces.
khajiit said:
You are using a really old MiFlash version, try updating to the version mentioned in this guide.
And rename your folder "Redmi note 3 pro" to "Redmi.note.3.pro" or "Redmi_note_3_pro".
MiFlash tends to have problem with spaces.
Click to expand...
Click to collapse
Thank you khajiit..
it works know with using 2016 version..
Related
UPDATE 27 DEC2016
-I received SYSTEM UPDATED NOTIFICATION ON 27 DEC2016 FOR MIUI8 on 5.1.1 (1.2GB), while my device was bootunlocked and ROOTED.
- after updating, twrp + root was gone
- so i flashed twrp IDO and flash supersu + lazyflasher and rebooted my device
---------------------
Recently I did something wild by buying Redmi3. For a die hard Sony Xperia fan over last many years it was something wild for me.
Immediately I felt the boundaries within MIUI8 where
- no app can be disabled
- no application dock / all app icons landing on launcher
- MIUI mediocre music with no equalizers
- bundled google and other duplicate apps (Miui galary + google photos) which and cannot be removed
however the features i enjoyed the most in MIUI8 particularly
- Dual APPs
- detailed dual sim control and renaming status bar icons/shape
- detailed control of memory optimization in developer options
- better memory optimization ( atleast for facebook and messenger which take gb/s of place to run )
i started my investigation immediately about rooting the Xiaomi Redmi devices running on MIUI8 (android5x) and the short and sweet version says
1. Unlocking Bootloader
2. flashing TWRP
3. flashing SuperSU
4. Flashing LazyFlasher
BOOTING in to SYSTEM.
however the above missing all the bleeding saga of work around you have to perform in order to reach the point where u actually install twrp.
UNLOCKING REDMI3 (REDMI DEVICES)
prerequisite~~~
MAKE BACKUP OF YOUR DEVICE!!!!!!!!!!!!
DO IT ON YOUR OWN RISK
I AM SHARING MY OWN EXPERIENCE HERE!
ONLY ONE DEVICE SHOULD BE LINKED WITH ONE MI ACCOUNT ( what i have read ov
1. once you start using REDMI, you must create MIUI account in your device- verified by your Mobile Sim Career / valid email and having legitimate details about you. the more valid details you give to your MI Account, the chances of unlocking bootloader are more. I even had to connect it with my only facebook account!
https://drive.google.com/open?id=0B31ivZaiUAGMWTYxX3ZXLUxrb2c
2. for REDMI3 download the DEVELOPER ROM from http://en.miui.com/download-298.html and put it in the mobile's SD card or internal memory.
on Redmi3 goto UPDATER APP (in folder TOOLS) and click the 3 dots top/right and click CHOOSE UPDATE PACKAGE and install the DEVELOPER GLOBAL or DEVELOPER CHINESE ROM MIUI8 over stableROM
https://drive.google.com/open?id=0B31ivZaiUAGMa3lPUWVnWnVXdXc
https://drive.google.com/open?id=0B31ivZaiUAGMNXBCLWdnWHpYbXc
it may give you warning like its older version and all data will be wiped. Proceed anyways. the device will BOOT an install DEVELOPER ROM. This process took 1 hour and i had Developer ROM in my REDMI3. after booting i logged in to my MI ACCOUNT. (DATA WIFI enabled)
3. NOW~~~~ goto http://en.miui.com/unlock/ and fill the form , asking your MI account details and VALID reason why you want to unlock your redmi device. Once done you will be asked to wait for SMS by XIAOMI. it may take 10 to 12 days. at this point if anything about you account is fake or you change your SIM CARD/number in you REDMI3 / Redmi. your bootloader request will be denied. I recieved my SMS on day5
https://drive.google.com/open?id=0B31ivZaiUAGMVnMzb3RKSEtTdkU
3. once you get the sms, download MIunlock TOOL from
http://en.miui.com/forum.php?mod=at...kMjVifDE0Nzk5MDA2OTJ8NTQyOTQ4MzM5fDQxODQyOQ==
4. now here is the Tricky part! which i found after so many FAIL TO UNLOCK device errors is that you must be in CHINA/ TAIWAN / SINGAPORE inorder to run you MIUNLOCK TOOL. for this purpose i used https://www.tunnelbear.com/ application and location SINGAPORE
5. unzip miunlock tool and run the exe file. LOGIN using your MI ACCOUNT
{
"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"
}
account will be validated for unlocking permission
since you recieved SMS, MIUNLOCK will ask you to CONNECT YOUR DEVICE FASTBOOT MODE / remember redmi goes to fastboot mode when POWER and volume down keys pressed and hold simultaneously for few second with jerk.
if everything goes right , the SMS + SINGAPORE LOCATION by TunnelBear; Miunlock tool will finally UNLOCK your device (WHEW)!!!!!!!!
INSTALLING TWRP / SUPERSU / LAZYFLASHER (ROOTING REDMI)
YOU HAVE NOW UNLOCKED device RUNNING ON global or chinese DEVELOPER ROM MIUI8, (you can check the unlock status from about device section)
now
1. Download the stable MIUI8 from http://en.miui.com/download-298.html, and flash it with UPDATER TOOL the way you installed developer rom (as explained above)
2. once stable rom is flashed, boot your device and started using it by logging in to MI Account, google accounts etc. (again whole process takes 1 hr)
3. download TWRP IDO https://drive.google.com/open?id=0B31ivZaiUAGMVjZ6ekU4TEVveTA
4. download lazy flasher and supersu (as attached) and put it in the sdcard or internal memory!
5. switch-off device (REDMI3) and boot it in FASTBOOT mode by holding VOLdown+power keys.
FLASH TWRP by adb commands. please see this video! its EXTREMELY HELPFUL!! follow it by heart!
https://www.youtube.com/watch?v=G_P7Qd3kpAI
6. once you boot twrp as system readonly! make BACKUP in sdcard or internal memory!
7. mount system! and flash both zipfiles in sequence (A) superSU & (B) LAZYFLASHER ( lazyflasher disables dm-varity and prevent you from bootloops)
8. REBOOT in to SYSTEM! the first boot may take some time!
CONGRATULATIONS you have ROOTED REDMI3 / XIAOMI
warning
1. you will no receive any updates since system is modified by twrp hence you have to FLASH any updates in fastboot mode by downloading fastboot version of MIUI in future using MIFLASH TOOL / or XDA FLASHER
https://drive.google.com/open?id=0B31ivZaiUAGMdFBSYWhoMnJzakk
---any future flashing will void rooting and twrp, so you have to install twrp/supersu/lazyflasher after every update.
2. I skipped the EDL mode part! XIAOMI devices are highly unstable and you can brick them VERY EASLY!!!!
3. I skipped the part where you can replace twrp.img with kernel.img by naming it kernel.img in FASTBOOT ROM version using 7-zip. again you can brick your device very easly!
HOWEVER
4. if your boot locking request has been denied by MIUI team,,,, EDL is your LAST OPTION
First of all, you're in wrong forum. This kind of thread should be on General section.
Second,
Unlocking process could be done in any region (I don't receive my SMS verification but my request is accepted). I'm in Indonesia and I don't use VPN and unlocking works. :good:
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
First of all, you're in wrong forum. This kind of thread should be on General section.
Second,
Unlocking process could be done in any region (I don't receive my SMS verification but my request is accepted). I'm in Indonesia and I don't use VPN and unlocking works. :good:
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
sorry for posting in the wrong section
admins, please move the post to the right one
I am in kuwait, and i constantly got failure unless i tried region Singapore! My guess malaysia would also be acceptable ! however in my region its not getting unlocked
YasuHamed said:
I am in kuwait, and i constantly got failure unless i tried region Singapore! My guess malaysia would also be acceptable ! however in my region its not getting unlocked
Click to expand...
Click to collapse
If I remember: Xiaomi phones in Asia (excluding China) are mostly released in India, Indonesia, Singapore, Malaysia, and Taiwan.
That's why the unlocking process always fails on your case.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
If I remember: Xiaomi phones in Asia (excluding China) are mostly released in India, Indonesia, Singapore, Malaysia, and Taiwan.
That's why the unlocking process always fails on your case.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
true!
i have read, people from other countries and locations cannot unlock Xiaomi
This worked for me. The twrp rooting part.
Flashed twrp, left it read only, then flashed the newest superSU (2.79) and then lazy flasher zip.
All good here! And I already had dm-verity issues and had to flash stock rom again. (30 minutes after I got the phone. Didn't read well enough first time around. Lol)
Thanks! :good:
Whoa, Darth is here! xD
Congrats on having your (new) device rooted. Hope you could enjoy the phone...
Sent from my Redmi 3 using XDA Labs
Darth said:
This worked for me. The twrp rooting part.
Flashed twrp, left it read only, then flashed the newest superSU (2.79) and then lazy flasher zip.
All good here! And I already had dm-verity issues and had to flash stock rom again. (30 minutes after I got the phone. Didn't read well enough first time around. Lol)
Thanks! :good:
Click to expand...
Click to collapse
oh you are welcome sir
i am glad to be help
2. for REDMI3 download the DEVELOPER ROM from http://en.miui.com/download-298.html and put it in the mobile's SD card or internal memory.
on Redmi3 goto UPDATER APP (in folder TOOLS) and click the 3 dots top/right and click CHOOSE UPDATE PACKAGE and install the DEVELOPER GLOBAL or DEVELOPER CHINESE ROM MIUI8 over stableROM
https://drive.google.com/open?id=0B3...3lPUWVnWnVXdXc
https://drive.google.com/open?id=0B3...XBCLWdnWHpYbXc
Click to expand...
Click to collapse
Hi op, i tap on the link and it brings me to the rom download page but it was for redmi 3 prime and i'm using redmi 3 (snapdragon version) Can this guide still work on my phone? or i just need to simply download dev rom for my phone's version? And i heard that Global rom doesn't allow for root activation so which rom should i dowload? i prefer global though
LoliIsMe said:
Hi op, i tap on the link and it brings me to the rom download page but it was for redmi 3 prime and i'm using redmi 3 (snapdragon version) Can this guide still work on my phone? or i just need to simply download dev rom for my phone's version? And i heard that Global rom doesn't allow for root activation so which rom should i dowload? i prefer global though
Click to expand...
Click to collapse
1) All Redmi 3 variants are Snapdragon, with difference in RAM, eMMC, and fingerprint sensor availability.
2) Who knows?
3) You can just flash SuperSU or Magisk.
Sent from my Redmi 3 using XDA Labs
krasCGQ said:
1) All Redmi 3 variants are Snapdragon, with difference in RAM, eMMC, and fingerprint sensor availability.
2) Who knows?
3) You can just flash SuperSU or Magisk.
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
So I can just flash SU from the stock recovery to gain root access?
Sorry for my ignorance though:crying:
LoliIsMe said:
So I can just flash SU from the stock recovery to gain root access?
Sorry for my ignorance though:crying:
Click to expand...
Click to collapse
With custom recovery of course.
Sent from my Redmi 3 using XDA Labs
krasCGQ said:
With custom recovery of course.
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
Now i'm stuck at flashing twrp part,
1. "adb reboot bootoader" the result was "bootloader is disabled"
so i entered into fastboot manually, plug in the cable and check with "fastboot devices" and it was connected.
2. i ran "fastboot flash recovery (and the file here)" it failed "data transfer failure (or something like that)<unknown>"
and i'm sure my bootloader is unlocked correctly. do i need the fastboot mode enabled in the developer option?
LoliIsMe said:
2. i ran "fastboot flash recovery (and the file here)" it failed "data transfer failure (or something like that)<unknown>"
and i'm sure my bootloader is unlocked correctly. do i need the fastboot mode enabled in the developer option?
Click to expand...
Click to collapse
Yeah, try to enable that.
Sent from my Redmi 3 using XDA Labs
krasCGQ said:
Yeah, try to enable that.
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
result still the same, no luck, but i found something
the daemon keeps shutdown like every 8 seconds, after waiting for a while and enter "adb devices" it's going to say daemon not running...
update:
i restarted my pc and now everything works fine silly pc thx man
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"
{
"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"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei P10.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 3 ROMs in total as of now - LineageOS (Unofficial), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei P10
Contributors
OldDroid, XePeleato, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-27
do you know anyway in which i could unlock my bootloader?
JohnnyMwanza said:
do you know anyway in which i could unlock my bootloader?
Click to expand...
Click to collapse
DC Unlocker is the only way to go as Huawei stopped releasing bootloader unlock codes since July 22, 2018.
I installed the Resurrection Remix and Lineage rom on my P10+ (VKY L29) device and both got me the same problem:
When i boot (the boot is successful), Google starts the first configuration. It asks me the language and the visual properties and then i press "next". The screen remains on "Just a second..." for about forever.
I tried format data before and after, tried to install several Treble roms... Everything took me to the same problem.
I tried also to re-install Gapps, but this took me to another problem: the Google First Configuration is totally black.
What should i do?
McEyes said:
I installed the Resurrection Remix and Lineage rom on my P10+ (VKY L29) device and both got me the same problem:
When i boot (the boot is successful), Google starts the first configuration. It asks me the language and the visual properties and then i press "next". The screen remains on "Just a second..." for about forever.
I tried format data before and after, tried to install several Treble roms... Everything took me to the same problem.
I tried also to re-install Gapps, but this took me to another problem: the Google First Configuration is totally black.
What should i do?
Click to expand...
Click to collapse
Its a know glitch, just reboot and try again.
netmaniack said:
Its a know glitch, just reboot and try again.
Click to expand...
Click to collapse
I tried rebooting about 10 times and he always did the same.
Fortunately I figured out how to resolve this hell:
The Google first configuration setup checks the integrity of the ramdisk Partition. I had a custom recovery so obviously the check was not satisfied.
The solution is to flash the stock recovery ramdisk partition (in my case i download The Official update of Huawei p10 Plus and extracted only the ramdisk image).
When i finished the configuration I completed every setup and then I reinstalled the custom recovery again.
McEyes said:
Fortunately I figured out how to resolve this hell:
The Google first configuration setup checks the integrity of the ramdisk Partition. I had a custom recovery so obviously the check was not satisfied.
The solution is to flash the stock recovery ramdisk partition (in my case i download The Official update of Huawei p10 Plus and extracted only the ramdisk image).
When i finished the configuration I completed every setup and then I reinstalled the custom recovery again.
Click to expand...
Click to collapse
If you have properly read the instructions in OpenKirin website, it was clearly stated there that all these ROMs must be installed wirh stock recovery to avoid other issues.
ej8989 said:
If you have properly read the instructions in OpenKirin website, it was clearly stated there that all these ROMs must be installed wirh stock recovery to avoid other issues.
Click to expand...
Click to collapse
True, I've read the disclaimer, but if someone, like me, used to install ROMs with the same warning without any problem (like an AOSP rom on my previous phone, which I installed having the TWRP), maybe he/she would think that there is not so much to worry about.
However, I noticed that there isn't a real "guide" on internet about a workaround of the "Just a sec" problem, so I wrote that message also for who needs a help and does not know about the partition check.
I found a bug on the "display" menu.
When i select a theme (light, dark, or the black switch), the system theme doesn't change at all. Tried to reboot, clear cache and data of SystemUI, nothing changed.
I bypassed this theme issue with Substratum. Didn't get any bug/problem with Substratum.
Device: P10 plus VKY-L29
Rom: Resurrection Remix 6.1.0 - Oreo - 2018.08.18
McEyes said:
I found a bug on the "display" menu.
When i select a theme (light, dark, or the black switch), the system theme doesn't change at all. Tried to reboot, clear cache and data of SystemUI, nothing changed.
I bypassed this theme issue with Substratum. Didn't get any bug/problem with Substratum.
Device: P10 plus VKY-L29
Rom: Resurrection Remix 6.1.0 - Oreo - 2018.08.18
Click to expand...
Click to collapse
for me working normal
how to root ? can i flash normal magisk or need special for huawei device?
doktor29 said:
for me working normal
how to root ? can i flash normal magisk or need special for huawei device?
Click to expand...
Click to collapse
If you use a normal Huawei EMUI system, there is a special treatment which use a special SuperSu zip file.
Also, you can use a Magisk version, always optimized for Huawei. I found the zip variant in a thread in the P10+ section.
If you have the Treble ROM, which is the main topic of the thread, I did this:
Ensured that there were no setups to do;
Re-flashed TWRP;
Installed the normal Magisk zip from TWRP.
Because is not a EMUI system anymore, you can easily install every mod or patch you wish.
Personal note: I tried install SuperSu with the zip, but the app said "binary occupied". Since it did like that before, with the EMUI system, I gave up and I installed Magisk.
Now it works like a charm.
McEyes said:
If you use a normal Huawei EMUI system, there is a special treatment which use a special SuperSu zip file.
Also, you can use a Magisk version, always optimized for Huawei. I found the zip variant in a thread in the P10+ section.
If you have the Treble ROM, which is the main topic of the thread, I did this:
Ensured that there were no setups to do;
Re-flashed TWRP;
Installed the normal Magisk zip from TWRP.
Because is not a EMUI system anymore, you can easily install every mod or patch you wish.
Personal note: I tried install SuperSu with the zip, but the app said "binary occupied". Since it did like that before, with the EMUI system, I gave up and I installed Magisk.
Now it works like a charm.
Click to expand...
Click to collapse
can you link magisk version?
i try many official but i get info "unable to detect boot image"
doktor29 said:
can you link magisk version?
i try many official but i get info "unable to detect boot image"
Click to expand...
Click to collapse
This is the thread:
https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
It says is good even for P10.
you must flash it with TWRP
McEyes said:
This is the thread:
https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482
It says is good even for P10.
you must flash it with TWRP
Click to expand...
Click to collapse
what version of recovery You use ? because still wont work, i have 3.1.1 for oreo
you have dencrypted or encrypted data ? i try to decrypt but still in recovery i dont see anything in data partition
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
any chance to get rid of this annoying notification of SDCARD after reboot ?
rom ressurection remix
---------- Post added at 09:52 PM ---------- Previous post was at 09:33 PM ----------
antiratar said:
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
Click to expand...
Click to collapse
so how i can flash magisk without twrp ?
for me it works only data partition is not vivible due to encryption
can someone test fingerprint after reboot ?
i have strange issue, after reboot my fingerprint is not recognized anymore :/
if i add new one is ok till next reboot, then again my FP is not recognizing.
and no i dont mean it wont work berofre i put PIN/Passoword after reboot it wont work at all after reboot till i add next one :/
it happen in RR and Carbon, other roms i dont test
doktor29 said:
can someone test fingerprint after reboot ?
i have strange issue, after reboot my fingerprint is not recognized anymore :/
if i add new one is ok till next reboot, then again my FP is not recognizing.
and no i dont mean it wont work berofre i put PIN/Passoword after reboot it wont work at all after reboot till i add next one :/
it happen in RR and Carbon, other roms i dont test
Click to expand...
Click to collapse
Are you on stock kernel? Does this happen ALL the time or just random?
doktor29 said:
so how i can flash magisk without twrp ?
Click to expand...
Click to collapse
Instructions here: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
You only need to use fastboot.
ej8989 said:
Are you on stock kernel? Does this happen ALL the time or just random?
Instructions here: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
You only need to use fastboot.
Click to expand...
Click to collapse
it happen to me every reboot :/
i have only magisk with stock recovery, from instruction above
doktor29 said:
what version of recovery You use ? because still wont work, i have 3.1.1 for oreo
you have dencrypted or encrypted data ? i try to decrypt but still in recovery i dont see anything in data partition
Click to expand...
Click to collapse
I use the FromFutureRom version that is in the thread I linked before. I think is made especially for Huawei P10/P10+
My data partition is still encrypted.
In order to decrypt data you should format the so called "user data", which is the combination of /data and /sdcard. Don't have to say that you will lose everything on your internal archive, so be sure to backup everything. The external SD card will NOT be affected.
In the TWRP you can to this on the menu "format" -> "format data" -> write "yes" and format everything.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
antiratar said:
Don't use twrp with openkirin rom's. Join the telegram openkirin group and u will get there all the help u need. U need magisk 16.7 or newer. I don't understand why people still use twrp when is stated so many times that using twrp with openkirin rom's usually leed's to bootlop.
Click to expand...
Click to collapse
You are absolutely right, but I said that you can install TWRP or any custom rom AFTER the Treble Rom installation. I am now on Resurrection Remix Treble rom, with a TWRP recovery installed after the rom flash and everything is fine since the first boot.
{
"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 is an open-source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Code:
[SIZE="4"]#include <std_disclaimer.h>
/*
* 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 doing this to your device
* 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.[/SIZE]
Downloads
TWRP - View
ODIN Tool - View
Device tree - View
Installation
Read this before attempting to proceed with this guide.
Make sure you've backed up your personal data and have Samsung USB drivers installed.
Samsung implemented something call RMM Lock since 2017.
@corsicanu and @BlackMesa123 found out about this and gave us insight into what's happening.
This feature is meant as extra security to prevent theft.
As of latest update from Samsung, the RMM is reimplemented as KG Lock, known as KnoxGuard Lock.
However this new implementation made it more friendly and simple for devs.
You will need to update to latest Android 10 firmware with May 2020 security patch
AP Version:M305FDDU5CTF2
CSC VERSION: M305FODM5CTF2
Find the firmware over here https://samfw.com/
After flashing, boot back into Android and go to Developer Options by tapping Build Number under Software Information seven times.
Go into Developer options and enable OEM unlock.
It will ask for PIN/PASSWORD enter and device will reboot and wipe everything, unlocking the bootloader.
After rebooting back into Android you should find that it says "Bootloader already unlocked" under OEM Unlock
Switch off device.
Press Volume+ & Volume- key simultaneously and plug in USB CABLE connected to your computer.
There will be a warning screen. Press Volume+ to continue to Odin Download Mode
Observe the screen, there will be a flag saying "KG STATE: checking..." and "OEM LOCK: OFF"
If this is there for some time that means your bootloader accepts unofficial images. Thanks to @corsicanu for this insight.
Proceed to flash TWRP.
Open up Odin Downloader and uncheck Auto Reboot.
Select downloaded recovery.tar in AP field
Connect device and then click start.
Once done, press Volume- and Power button for 7 seconds to reboot, IMMEDIATELY PRESS VOLUME + AND PWR BUTTON SIMULTANEOUSLY TO BOOT INTO TWRP.
Thanks a lot to @Akhil99 for helping me figure out xD
XDA:DevDB Information
TeamWin Recovery, Tool/Utility for the Samsung Galaxy M30
Contributors
Sahil_Sonar
Akhil99
Version Information
Status: Stable
Current Stable Version: v3.4.0-0
Stable Release Date: 2020-06-27
Created 2019-06-23
Last Updated 2020-06-27
Changelog:
Build 2019-06-23
Updated on latest omni sources
Fix notch cutout overlay
Build 2020-06-27
Synced with latest TWRP sources
Updated kernel image with SM-M305F_SWA_QQ_Opensource
Build 2020-06-29
Fixed MTP
Sync ramdisk with stock Android 10
Join our new Telegram community
[OLD]Video guide: https://www.youtube.com/watch?v=NIUhuEc5WVA&feature=youtu.be
--- blank two ---
Sahil_Sonar said:
Edit: I did flash it via ODIN said "sucess" but still goes to stock recovery will surely fix up!
Edit 2: I am currently testing v1.1 will be up soon! Stay tuned (Yea... those links deleted don't want to keep users trying it because that just doesn't work!)
Click to expand...
Click to collapse
nice, i just bought it, I can test new versions if you want.
maybe we need to apply those "dm-verity" stuff right after flashing recovery for twrp to stick after boot?
thalesbraga said:
nice, i just bought it, I can test new versions if you want.
maybe we need to apply those "dm-verity" stuff right after flashing recovery for twrp to stick after boot?
Click to expand...
Click to collapse
I can help too , i flashed it but still boots to stock recovery and i have the dm verity thingy ,tried installig a zip to bypass it ,didnt work ,let me know if you have any new versions you need to test
You tested that on pie updataed M30 bro
StarkTonyXUV said:
You tested that on pie updataed M30 bro
Click to expand...
Click to collapse
No ,on a 8.1 one , i cant update it because the phone detected that i tried to flash it
???
pankspoo said:
Can some one tell me is it genuine?
http://www.droidthunder.com/root-samsung-galaxy-m30/
Click to expand...
Click to collapse
I am working on it there is no reason of being non geninue :good:
Sahil_Sonar said:
I am working on it there is no reason of being non geninue :good:
Click to expand...
Click to collapse
Genuine means its working or not?
pankspoo said:
Genuine means its working or not?
Click to expand...
Click to collapse
Tried installing TWRP ...unable to boot in to recovery mode
Sahil_Sonar said:
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Note: This recovery is un-tested I cannot assure if works or not. Please proceed at your own. I am not responsible for any damage caused to your device nor xda-developers. If you are unaware how stuffs work please search on google:fingers-crossed:
Downloads
TWRP - View
ODIN Tool - View
Device tree - View(Coming soon! :victory
Installation
Unlock bootloader (Hint: Developer options OEM Unlock :angel: )
Turn off your device and go to download mode, connect via USB to PC(Hint: adb reboot bootloader)
Kick ODIN and flash the recovery
Boot into TWRP and format data (or else face encryption issues)
You are good to go! :laugh:
XDA:DevDB Information
TeamWin Recovery, Tool/Utility for the Samsung Galaxy M30
Contributors
Sahil_Sonar
Version Information
Status: Testing
Current Beta Version: v0.1
Beta Release Date: 2019-05-19
Created 2019-05-19
Last Updated 2019-05-19
Click to expand...
Click to collapse
I dont know how to reply cuz a lot of things are complicated in this site ,but when will it be ready ?
Well it's ready! Download links will be available in a short time!
more147 said:
Tried installing TWRP ...unable to boot in to recovery mode
Click to expand...
Click to collapse
Because RRM Lock is enabled please check op and download latest files! I have sucessfully booted and flashed AOSP GSI on my phone
pankspoo said:
Genuine means its working or not?
Click to expand...
Click to collapse
Yep it is!
Nonneed to type commands to unlock oem.
Like fastboot oem unlock before doing everything. Just enabling oem umlock in developer option works??
pankspoo said:
Nonneed to type commands to unlock oem.
Like fastboot oem unlock before doing everything. Just enabling oem umlock in developer option works??
Click to expand...
Click to collapse
No need Samsung bootloader are easy to unlock just make sure it isn't RMM locked. However it will simply wipe your data so make sure you have a backup
---------- Post added at 09:12 AM ---------- Previous post was at 09:09 AM ----------
[/COLOR]
Sahil_Sonar said:
Well it's ready! Download links will be available in a short time!
Click to expand...
Click to collapse
i tried posting a reply multiple times but couldnt for some reason ...
anyway , i got an md5 error , binary invalid , removed md5. from the file's name , odin says its a success but my phone is stuck on the loading bar under downloading word , note : i have auto reboot disabled and my phoen isnt rmm or frp or locked in any other way and i flashed it using AP
edit :i reseted the file to its original (.tar.md5) and it worked like there was no error (this didnt work when i tried it on other files i had the same problem with ) i enabled force reboot , i couldnt boot to twrp and my phone was working like nothing happend , no verity check , nothing
---------- Post added at 09:30 AM ---------- Previous post was at 09:12 AM ----------
Sahil_Sonar said:
Here's an important note for those you got stock recovery instead of TWRP
--> Make sure auto-reboot is disabled in Odin
--> You will have to reboot into TWRP for the first time after flashing it [/url]
No more thanks :laugh: custom ROM's coming!
Click to expand...
Click to collapse
how do i reboot to twrp if im dtck on stock reboot after flashing ?
Urgent help.
Dm Variety zip is not flashing its showing updater sript error.
Except that everything is ok still i booted in os.
But now my phone showing sim card changed restart u r phone everytime i cant able to use phone
pankspoo said:
Urgent help.
Dm Variety zip is not flashing its showing updater sript error.
Except that everything is ok still i booted in os.
But now my phone showing sim card changed restart u r phone everytime i cant able to use phone
Click to expand...
Click to collapse
So this process of twrp is highly unsafe. Please mention possible solutions in your thread.
When you flash custom binary on your phone(i. E: twrp and root) Samsung automatically trigger it even after flashing RRM bypass file, so it unregister the device thats why sim errors strats evoking after doing this all.
To solve this i flashed stock firmware (how big and slow is that?) ruined whole night and now no sim Error(sim changed restart your phone) this is possibly CSC error. But still my over the air updates not working its showing device is modified.
So please do all this at risk and thread owner please give possible solution to this before giving customs roms or GSI stuff.
Hello All
Its a never used LEX 727. Decided to flash a custom rom. Installed latest TWRP, but when i go to flash the rom got error 7.
Tried with diffrent roms but still error 7.
Then updated firmware to 30S by @codeworkx from here and again tried different roms but am still getting the error.
Following the suggestions given by various posters, I have tried doing full wipes, rebooting to recovery, using the ALL IN ONE tool but nothing is working.
I've also tried many older versions of TWRP as well as roms but nothing, the error is still there.
Any more suggestions on how to fix this? Thank you.
This is a typical error when TWRP is old or does not fit the model.
First, stay at 20s firmware:
Downloads for : LeEco Le Pro3 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
You have to keep an eye on this:
- LEX720 (ZL1_CN)
- LEX722 (ZL0_CN)
- LEX727 (ZL1_NA)
Error 7 says the ROM’s updater script says the phone model of your phone is incompatible. A quick search for LineageOS give me this compatible on:
[ROM][OFFICIAL][TREBLE][X72X][11.0.X] LineageOS 18.1 for LeEco Le Pro3
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from...
forum.xda-developers.com
Make sure you have the latest TWRP installed for the X727:
Download TWRP for zl1
Download TWRP Open Recovery for zl1
eu.dl.twrp.me
Importand: If LineageOS aks to install it's own recovery, don't do it.
Important:
Install recovery, then reboot directly into recovery and install the rom. Original Firmware will revert back to stock recovery while boot! The you have to start over again.
Hello @Neppomuk_
Thanks.
1- I installed the 20S firmware
2- Installed the latest TWRP version 3.6.2_9-0-zl1 , and, rebooted to recovery.
3- Downloaded both the latest official LOS as well as the unofficial one by the poster whose link you have posted above. First tried installing the official rom and it gave error 1. Then tried flashing the unofficial one and same error. i.e.: "E1001: failed to update system image", Error 1.
4- I also tried installing the Mokee rom and it is also giving the same error. I downloaded the rom from their official site here
4- I am attaching screenshots of the errors. The first one is from the lineage "unoffical" after the "offical" had failed to install. The second one is from the failed Mokee rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hopefully this is progress.
Error 1 is corrupted boot. You have the flash the stock boot.img with bootloader. I own a x720 so I can not provide you my one. It is possible to extract it from stock rom.
Check if you can find one here:
Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s
Return to Un-modded Stock: Bootloader unlocked and TWRP and Root included The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download. Be Advised Do your research before flashing...
forum.xda-developers.com
Neppomuk_ said:
Hopefully this is progress.
Error 1 is corrupted boot. You have the flash the stock boot.img with bootloader. I own a x720 so I can not provide you my one. It is possible to extract it from stock rom.
Check if you can find one here:
Click to expand...
Click to collapse
Actually i have had that error before while experimenting, so i'm afraid there has been no progress.
Are you asking to flash the stock boot image? And then what? Will appreciate if you outline the steps.
@Neppomuk_
1- Extracted stock boot image from the file you provided. Flashed it to boot successfully. Rebooted to recovery.
2- Went through the process of flashing the rom again. Still error 1.
OK, the E1001 from your screenshots is interesting. System image is (marked as) encrypted.
Do Following from twrp, all steps without reboot:
wipe/advanced wipe, tick 'Dalvilk/Art', 'Cache', 'Data' and 'System'
then go wipe/format data, confirm with yes, now the encryptiono (state) should be gone.
Now reboot straight back into recovery and flash the, this was mokee rom?, again.
Neppomuk_ said:
OK, the E1001 from your screenshots is interesting. System image is (marked as) encrypted.
Do Following from twrp, all steps without reboot:
wipe/advanced wipe, tick 'Dalvilk/Art', 'Cache', 'Data' and 'System'
then go wipe/format data, confirm with yes, now the encryptiono (state) should be gone.
Now reboot straight back into recovery and flash the, this was mokee rom?, again.
Click to expand...
Click to collapse
Did it. Still error 1.
The first picture is LOS. The second one is Mokee.
Let's try following:
In TWRP go to Advanced, select File Manager, select the System folder from the list and the push the checkmark on the bottom right corner. No push the chmod 755 button the give full access to system partition.
Try to install custom rom.
A second try:
Go to wipe / Advanced wipe
select the system partition
now select 'repair or change file system' and then 'repair file system'.
Try to install custom rom.
I had problems with the 2nd try on some devices they do not allow repair of system partition.
Did the 1st option. Still error 1.
Did the 2nd option and the process was aborted or failed with error 4.
Did the 1st option. Still error 1.
Did the 2nd option and the process was aborted or failed with error 4.
Did you had any problem to flash TWRP on the device earlier?
With error 4 we have a second option:
In TWRP go to Wipe / Advance Wipe, select 'System' partition and select 'Repair or Change File System'.
Select 'Change File System', select EXT2 and proceed.
Then do the same to go back to EXT4.
Do the same with the Data partition.
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
OK, something special:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Neppomuk_ said:
Did you had any problem to flash TWRP on the device earlier?
Click to expand...
Click to collapse
No.
Neppomuk_ said:
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
Click to expand...
Click to collapse
Not sure how to do this. As far as i know one can only flash images in boot loader mode. How does one flash a zip file in that mode?
Neppomuk_ said:
OK, something special:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Click to expand...
Click to collapse
Are you asking to flash the lineage boot.img in bootloader mode and then flash the entire rom by TWRP?
Do partial flash in bootloader mode, if not already happen, use Minimal ADB and Fastboot:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Command to flash boot image in console:
fastboot flash boot [boot.img]
Then stay in bootloader mode. The mobild should mount a drive to the system. Copy the ROM imge to the internal storage on that drive. You can copy the rom in TWRP mode also. Then install the rom throug TWRP.
I never sideloaded data. I like to check the transfer is successfully finished. I had some faulty sd cards, wich do no give an error while sideloading stuff.
As an alternative you can use an OTG USb Stick and putt the stuff on this one. Would do the same and could be faster.
If you need drivers for Windows:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
and the device specified one:
LeEco Le Pro3 USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
-> I did not verify if this driver downloads are still valid, please check them first.
I do have the latest drivers and ADB installed. Everything i have been telling you has been done via ADB as well as from the internal storage of the phone.
But my question was, when you say :
Neppomuk_ said:
Now, you have to transfer the custom rom to your phone again. But do it in bootloader mode this time.
Click to expand...
Click to collapse
What are you exactly asking me to do? How can one flash a zip file using bootloader, assiming that's what you are saying?
And, when you are saying:
Neppomuk_ said:
The LineageOS ROM has it's own boot.img inside. You can use this one as well, flash it in bootloader.
Click to expand...
Click to collapse
Are you asking me to flash the boot.img using bootloader and then flash the rom from TWRP?
My question is i can flash the boot.img from TWRP, can't I? Anything wrong with that approach?
I think understand you now. Do a partial flash using boot loader and the do the rest using TWRP.
Thank you for clarifying. One needs confirmation so we do not do anything we aren't supposed to.
Sorry, I mixed up another case where I'm tring to remove forced data encryption.
There are flashable boot.img in zip files wich you can flash from TWRP, but this is not your one.
I still believe, that something is wrong with your boot partition.
The whole procedure:
- Extract boot.img from Lineagos and install it in bootloader mode: fastboot flash boot [boot.img]
- Boot into TWRP while holding Power and volume up.
- If not done, wipe cache and system, format data.
- Copy LineageOS to the drive / internal storage
- Use TWRP to install the rom
veda1 said:
I think understand you now. Do a partial flash using boot loader and the do the rest using TWRP.
Thank you for clarifying. One needs confirmation so we do not do anything we aren't supposed to.
Click to expand...
Click to collapse
Yes, better one question to much than new problems...
Did as suggested. Still error 1.
I have another question while we continue to look at this. If worse comes to worse i've no choice but to use EUI. Is it possible to patch the latest android security patches to it? That is, rom will be EUI , but updated with all security patches?