my saga of ROOTING XIAOMI REDMI 3 / unlocking bootloader redmi 3 on MIUI8 - Xiaomi Redmi 3 Guides, News, & Discussion

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

Related

[HOW TO] Meizu M2 Mini | Root, adb, unlock bootloader, TWRP recovery and CM 12.1

{
"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"
}
**Intro**
Just a simple HOW TO to centralize everything I found on Russian, Italian, meizufans and xda forums.
M2 Mini has good hardware but very poor software, going to CM is a relief !
**Disclaimer**
I'm not responsible for bricked device.
You may loose warranty.
You need basic knowledge of using adb tools and rooting phones.
**Boot in Recovery and Fastboot**
Boot in recovery : power on holding Volume Up and Power
Boot in fastboot mode : power on holding Volume Down and Power
**Rooting**
King Root works well http://www.kingroot.net
**ADB Drivers**
Google drivers won't recognize M2 Mini, you have to edit the inf file.
You have to activate USB Debugging in the Developer Options for ADB to work.
1) Download drivers at: http://developer.android.com/sdk/win-usb.html
2) Edit android_winusb.inf
3) Go to [Google.NTamd64] section and add this to the end of the section :
;MEIZU M2
%CompositeAdbInterface% = USB_Install, USB\VID_0E8D&PID_201D&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_2A45&PID_0C02&MI_01
4) Reboot Windows without driver signature enforcement
HOW TO: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
5) Install modified driver
HOW TO : http://developer.android.com/tools/extras/oem-usb.html
**Unlock bootloader**
You have to be on *Flyme OS 4.5.4i* for bootloader unlocking to work.
DOWNLOAD LINK : https://forum.meizufans.eu/topic/3905/flyme-os-4-5-4-stable-m2
1) You need busybox on the phone
DOWNLOAD LINK : https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
2) You have to download the unlock_bootloader.sh
DOWNLOAD LINK: http://www37.zippyshare.com/v/fvm5edpr/file.html
2) Copy file to sdcard via MTP or ADB
adb push unlock_bootloader.sh /sdcard
3) Execute the file as root from ADB
adb shell
su
(accept warning on the phone)
sh /sdcard/unlock_bootloader.sh
4) Unlock
adb reboot bootloader
fastboot oem unlock
(wait for the phone to display confirmation)
"Volume Up" to accept
(wait for unlocking)
5) Reboot your phone into Flyme OS
It is very important to restart your phone and wait for Flyme OS to boot up completely before flashing a custom recovery.
**Custom recovery (TWRP)**
If you didn't boot into Flyme OS at the previous step, you might be stuck in boot loop in recovery and need to go back to the stock recovery (Uploaded on XDA by @murtaza1326)
DOWNLOAD LINK: https://drive.google.com/file/d/0B6kCPdWyvl3xa1RDWVRDRHlfS2c/view
XDA LINK: http://forum.xda-developers.com/showpost.php?p=66476298&postcount=574
1) Download last TWRP 3
DOWNLOAD LINK: https://mega.nz/#!PVcihSST!0yHN3p6dsKqAgW2-2krUSvvzRA-bFQmPR16wUbC7aKs
FOUND ON: http://www.movilesdualsim.com/tema/twrp-3-0-2_modnat-ltt-multilanguage.132746/
2) Flash recovery
fastboot flash recovery_3.0.0.3NAT&LTT.img
**CyanogenMod 12.1**
Last version seems to be 0.9 from April,16th 2016 on Russian forums.
1) Download Cyanogen
FORUM LINK: http://4pda.ru/forum/index.php?showtopic=715935
DOWNLOAD LINK: https://drive.google.com/file/d/0Bwzrxcf3P6N6S1hzaUYtNGFwMDA/view
2) Download Google Apps
GITHUB LINK: https://github.com/AlexLartsev19/cgapps/releases
DOWNLOAD LINK: https://github.com/AlexLartsev19/cgapps/releases/download/20160423/cgapps-arm-5.1.1-201604241754.zip
3) Boot into recovery
Hold "Volume Up" and Power
4) Copy everything to sdcard via MTP
5) Full wipe
Go to Wipe > Advanced wipe > check Dalvik, System, Cache, Data > Wipe
6) Flash CM and Gapps
Go to Install, select your CM zip file and install.
Do the same with Gapps.
7) Restart your phone
**Enjoy !**
**Screenshots**
Phone is in French,...but all languages available
Reserved @madcorp
any screnshots for cm12.1
Sent from my m2 using XDA Premium 4 mobile app
abhishekbhosale7399 said:
any screnshots for cm12.1
Sent from my m2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sure! I'll try to post some later today
thank you ?
Sent from my m2 using XDA Premium 4 mobile app
@abhishekbhosale7399 screenshots added in the main post
Is it better than flyme 4.5.4i ? Are there any bugs? Is battery better? Are you happy with cm?
Nice work!! Permission to port CM12.1? I already have a CM12.1 for MT6735 in the works, but there are a few bugs. Can you do a bug report?
Regards
Nothing for Meizu m2 note ?
is it supports OTG ?
Sent from my m2 using XDA Premium 4 mobile app
It will be really helpful if you could post a video tutorial
update link please i am not able to install by going to about phone
Sent from my M2 Mini using XDA Premium 4 mobile app
i hope @madcorp build for Meizu M2 NOte too, thanks.
Not sure how close this is but looks genuine to debrick meizu phones. This is displaying it on the meizu m2 note but surely should work on the mini.
https://youtu.be/twgynLFAczc
Phone cannot see SIM
Yep, ive been using CM for few months, everything was good. But today i had to wipe /data, and couldn't. Recovery says, that it cannot mount /data. I thinks, that's because of encryption. I played around, tried wipe system from Settings, but it didn't work too. I and did
wipe data
in the phone's terminal. Saw lots of errors from apps, of course. Then rebooted and, oh my, phone was asking me for password to unencrypt the storage. Huh.
I enetered password, loaded into system, and, everything is pretty cool (ive got clean firmware, system apps only), except two things:
Phone is still encrypted, hence, i cant change firmware or do anything else
Second, and most terrible, is that phone can't see SIM card. No SIM at all. I changed SIM's position, but it does not work, yeah. Actually, SD card is working, i can see it from file manager, read/write files. Wi-Fi is working too.
I have backups for all partitions, except Internal Storage and /data. /data was backuped using Titanium Backup, files from Internal Storge moved to SD card. So, i do not care about files, i just want my phone up and running. Any help?
Do we have to unlock bootloader for flashing custom recovery
How downgrade from flyme 5.1 to 4 for bootloader unlock?
meizu m2
guys my mobile meizu m2 stack in bootloop
i am try to recovery but recovery lose
and mobile also not unlock bootloader
any one help me
to install recovery and stock rom
---------- Post added at 07:04 AM ---------- Previous post was at 07:01 AM ----------
murtaza1326 said:
Reserved @madcorp
Click to expand...
Click to collapse
guys my mobile meizu m2 stack in bootloop
i am try to recovery but recovery lose
and mobile also not unlock bootloader
any one help me to unlock bootloader and
install recovery and stock rom
Good Work!
Thank you very much. I needed something like this because I had a lot of problems with Flyme 5.x.x. Now with Root, Flyme 4.x.x,...everything is much better.
Thanks a lot!:good:
jcarlos.trillo said:
Good Work!
Thank you very much. I needed something like this because I had a lot of problems with Flyme 5.x.x. Now with Root, Flyme 4.x.x,...everything is much better.
Thanks a lot!:good:
Click to expand...
Click to collapse
Houw did you downgrade???

[GUIDE] [ ROM] Step by step guide before you flash the cm13 build with M bootloader

How to flash cm13 with fp scanner version (both official/unofficial)
Requirements:
- TWRP Alka (Download here, just extract the .img and flash it via your current TWRP )
1. BACKUP!BACKUP!BACKUP!!
Before Flashing anything to your device, we need to backup our full ROM. This can be done by using the TWRP Alka i gave you. steps are in the following:
- Boot Into TWRP
- Go to Backup
- check all the partitions you have (see below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- backup all and wait until its finished (approx 5-10 mins)
For safety purpose store the backup in sdcard or have a copy of it in your PC
2. FLASHING
CAUTION! THIS WILL RELOCK YOUR BOOTLOADER ( Irrespective of if you unlocked officially or unofficially in stock ROM it will get locked and flashing this ROM won't brick your phone or cause bootloops) TWRP will still continue to function normally with all its functions
okay now that we have already backed up all our partitions, we can flash the rom.
- go back to TWRP Main screen (suggesting that you didnt reboot after backing up) and chose Wipe
- Wipe system, Dalvik, Cache, Data
- after its done, go back to TWRP main screen.
- Install the ROM
- Install GAPPS (6.0.1 arm64)
- Reboot.
First boot takes around 5 minutes and it'll initially welcome you in the setup screen.
3. RE-UNLOCKING
Now you know that your Bootloader got relocked. But that's fine, even at a LOCKED state, your TWRP is still functioning as it should be (flashing, restoring, backup, wipe).
So its up to you if you want to unlock or not. Both options are fine and wont affect you in any way.
To unlock your bootloader you have to:
- Boot into Fastboot
- Reunlock Using MiUnlockTool
- reboot.
4. RESTORING to MIUI lollipop or older cm13 builds
if you encounter problems with the rom (stuffs doesnt work, something FC, not a daily use worthy) you can easily go back to where you were before flashing this build.
- Boot into TWRP
- Tap Restore
- check all the partitions and restore
- wait until it finished and reboot.
you should now be in your previous rom (whether its MIUI or AOSP or CM) and the bootloader should've stayed unlock.
Reserved
reserved
Thanks for the tuto. Can we flash miui roms without flashing patched boot.img or else with this recovery ?
the next updates of CM lock bootloader or one-time?
Enviado desde mi XRN3P.
Great tutorial!
One question, I converted my SD to be internal (big mistake). Is there a way for twrp to see the SD and back stuff there?
Or otherwise revert back to external without losing all the data?
Sent from my Redmi Note 3 using Tapatalk
Great! I wanna install this asap!!!
Enviado desde mi Redmi Note 3 mediante Tapatalk
ASAP, for sure! Thanks for your work, Santosh!
There's no emmc-backup in the list in twrp, I flashed the twrp mentioned in op, what's wrong?
Edit: Here's a screenshot, there are a lot things to backup, but no emmc
https://app.box.com/s/mitdohqzvyfql6yf6s3ma8ig24um7ecq
Thank's for guide, working perfect, after full restore I have unlocked bootloader. I had go back to MIUI, there still is no sim card bug for me if in slots is only one SIM and is no trigger to turn off one of them, also camera is working really bad, even colours are bad yelow/black when trying to do a shot.
Sent from my Redmi Note 3 using Tapatalk
Great Job!
Enviado desde mi Redmi Note 3 mediante Tapatalk
Try it or die said:
There's no emmc-backup in the list in twrp, I flashed the twrp mentioned in op, what's wrong?
Edit: Here's a screenshot, there are a lot things to backup, but no emmc
https://app.box.com/s/mitdohqzvyfql6yf6s3ma8ig24um7ecq
Click to expand...
Click to collapse
Facing the same problem. There are a ton of things to backup, yet no EMMC backup. Not sure what's wrong here. Flashed your TWRP via the one I already had and now getting this.
Cristal clear. Eating release to flash. Thanks to dev
Enviado desde mi Redmi Note 3 mediante Tapatalk
nadavar said:
Great tutorial!
One question, I converted my SD to be internal (big mistake). Is there a way for twrp to see the SD and back stuff there?
Or otherwise revert back to external without losing all the data?
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
just go to internal stor-3 dots- migrate data.that would help you.
Sent from my Redmi Note 3 using XDA-Developers mobile app
I am ready to move onto MM. Those who cannot will ask for fix that wont come. So decide. Our dev already gave a detailed instruction. Thanks dev.
Sent from my Redmi Note 3 using XDA-Developers mobile app
same issue[or not an issue],but no emmc ..maybe it is for miui stock and i am on AOSP,..btw flashed twrp and waiting for new update
M.Carter said:
Thanks for the tuto. Can we flash miui roms without flashing patched boot.img or else with this recovery ?
Click to expand...
Click to collapse
I don't know about that but you can't flash any miui lollipop rom after you flash this cm13 and lock your bootloader. You will first have to restore to cm13(older) or aosp with unlocked bootloader and only then you can flash miui.
Or you can also unlock bootloader on the new rom and the flash miui. Correct me if I'm wrong about the last part, Santosh.
Sorry for the messed up (the ss isnt twrp alka, but another recovery) in twrp Alka the emmc backup is aboot and aboot.bak (it has different names for other partitions, but if you backup them all it wont have any problems) ill edit the post rightaway with the proper twrp
Windslash31 said:
Sorry for the messed up (the ss isnt twrp alka, but another recovery) in twrp Alka the emmc backup is aboot and aboot.bak (it has different names for other partitions, but if you backup them all it wont have any problems) ill edit the post rightaway with the proper twrp
Click to expand...
Click to collapse
I flashed mokee ROM (which I know will lock my bootloader) but before that I backup everything using the TWRP alka. And as expected , upon restoring the backup everything is working as they were working before. Bootloader is still unlocked.
the right screenshots are added on the other thread, sorry for the ****ed up
Got understand all steps except 4. How to reunlock the bootloader with mi flash tool. I before unlock bootloader via mi flash tool by flashing full 7.1.8 rom with replace emcc file and then give fastboot command. So now how to reunlock it.
Sent from my kenzo using XDA-Developers mobile app

[GUIDE][KENZO/KATE] Install LineageOS with locked bootloader

{
"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..

[RECOVERY][ROOT]TWRP 3.1.0-1 Samsung Galaxy J3 Emerge SM-J327P

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"

[RECOVERY][UNOFFICIAL]TWRP 3.4.0-0 Touch Recovery [m30lte]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.

Categories

Resources