New method to flash Twrp recovery !! without unlocking bootloader, safe method ... !
easy
boot in EDL mode, then flash fastboot Dev rom (the right DEV Rom for your Phone !) but before delete recovery..img from dev rom folder then put recoveryAlkaUpdate.img (or any TWRP u want..) and rename it to recovery..img
then flash with miflashtools !
confirmed working ! tested on my new Kate version received this moring form China !
original credit (french)
Allready flashed cm13 with this method without unlocking bootloader .. nice
Envoyé de mon X900+ en utilisant Tapatalk
supercowz said:
New method to flash Twrp recovery !! without unlocking bootloader, safe method ... !
easy
boot in EDL mode, then flash fastboot Dev rom (the right DEV Rom for your Phone !) but before delete recovery..img from dev rom folder then put recoveryAlkaUpdate.img (or any TWRP u want..) and rename it to recovery..img
then flash with miflashtools !
confirmed working ! tested on my new Kate version received this moring form China !
original credit (french)
Click to expand...
Click to collapse
Man I already did it many weeks back.
You know I have gone tired of telling this simple fact to everyone, but no one understands that this is the easiest way to installa custom recovery. Even a modified boot image or any modded file can be flashed before flashing the ROM. Only that for APK's, the MD5 checksum is mandate.
So,looks like no need to unlock officially or unofficially then lol.
Spread this post like virus bro,people are trying so hard to unlock their phones officially and at the end of process unlocks unoffiially and gets so much problems because of xiaomi's worst policy of unlocking.
this is really easy and intelligent stuff!
Good post bro. +99 post :good:
supercowz said:
New method to flash Twrp recovery !! without unlocking bootloader, safe method ... !
easy
boot in EDL mode, then flash fastboot Dev rom (the right DEV Rom for your Phone !) but before delete recovery..img from dev rom folder then put recoveryAlkaUpdate.img (or any TWRP u want..) and rename it to recovery..img
then flash with miflashtools !
confirmed working ! tested on my new Kate version received this moring form China !
original credit (french)
Click to expand...
Click to collapse
BTW, he has also just copy pasted from different forums. lol
---------- Post added at 01:19 ---------- Previous post was at 01:15 ----------
NVDX11 said:
So,looks like no need to unlock officially or unofficially then lol.
Spread this post like virus bro,people are trying so hard to unlock their phones officially and at the end of process unlocks unoffiially and gets so much problems because of xiaomi's worst policy of unlocking.
this is really easy and intelligent stuff!
Good post bro. +99 post :good:
Click to expand...
Click to collapse
Btw, unlocking does not matter at all, tbh. It does not matter the worst if you are on LBL or ULBL.
Check this post:
http://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-7-simple-steps-t3457086 (This is for unlocking bootloader unofficially)
http://forum.xda-developers.com/redmi-3/development/share-twrp-3-0-2-developed-cofface-t3471201 (this is for Redmi 3S / Redmi 3X / Redmi 3S Prime/Pro TWRP).
does it have to be done with a dev rom?
can't we just flash roms like cm13 etc straight from miflash with custom recovery included, as the guy on second post says? any more details on how to do this?
Is it compulsory to use developer ROM wht can't Ido with stable
Hi, is there any downside with this method compared to officially unlocking bootloader?
Which recovery is better for kate?
Thanks for the great info!
meangreenie said:
does it have to be done with a dev rom?
can't we just flash roms like cm13 etc straight from miflash with custom recovery included, as the guy on second post says? any more details on how to do this?
Click to expand...
Click to collapse
You can flash ONLY official MIUI Stable/Dev ROM using Mi Flash Tool
Has anyone confirmed this?
based on http://forum.xda-developers.com/wiki/Bootloader you need to unlock bootloader since the bootloader will verify (and boot) kernel and recovery.
If this does work, can anyone provide an explanation why?
Wow. Can I use this method for flashing this recovery on Snapdragon device? http://forum.xda-developers.com/red...wrp-install-twrp-flash-supersu-t3462448/page1
Everything I need is a stable MIUI with root access and Xposed
Sent from my Xiaomi Redmi Note 3 using XDA Labs
Wow! That's awesome! After this can I flash superSU? If so, which version works best with global dev?
PS: What about OTAs? I supose this will break it, so how can I get MIUI g dev updates?
Sry for this bunch of questions.
supercowz said:
New method to flash Twrp recovery !! without unlocking bootloader, safe method ... !
easy
boot in EDL mode, then flash fastboot Dev rom (the right DEV Rom for your Phone !) but before delete recovery..img from dev rom folder then put recoveryAlkaUpdate.img (or any TWRP u want..) and rename it to recovery..img
then flash with miflashtools !
confirmed working ! tested on my new Kate version received this moring form China !
original credit (french)
Click to expand...
Click to collapse
can i use global stable rom instead dev rom
Great stuff. Will give it a try once I am home.
My bootloader has never been unlocked. I am waiting for the unlock permission. Now, if I install TWRP using this method, will I be able to flash CM 13 or other kernels?
Worked perfect for me.
Installed zcx twrp + SuperSu with this method
Still at Miui 8 but maybe i switch to CM or another Custom Rom
hi,
is anyone have tried to flash custom rom with this method?
thanks.
supercowz said:
New method to flash Twrp recovery !! without unlocking bootloader, safe method ... !
easy
boot in EDL mode, then flash fastboot Dev rom (the right DEV Rom for your Phone !) but before delete recovery..img from dev rom folder then put recoveryAlkaUpdate.img (or any TWRP u want..) and rename it to recovery..img
then flash with miflashtools !
confirmed working ! tested on my new Kate version received this moring form China !
original credit (french)
Click to expand...
Click to collapse
Hi @supercowz, could you please edit the original post?
I don't think official TWRP will work. From the guide, ZCX TWRP was used and you recommended Alka TWRP, which is cofface TWRP based. The common factor between these TWRP is that they are able to bypass dm-verity (built in in settings of ZCX TWRP, cofface based TWRP's flash cracked boot.img automatically). Also, it is important to boot to recovery after flashing the modified fastboot dev else it might cause bootloop. Also official TWRP might cause bootloop.
To all:
I'm still looking for the reason why this method might work. Based on concept, bootloader starts first before recovery so the bootloader will verify if correct recovery is installed before it boots the recovery. Only explanation I can think of is that MiFlash tool and/or fastboot DEV rom is able to fool bootloader that the flashed recovery is acceptable.
To those that have tried this, can you check if your bootloader is still locked? Thanks!
---------- Post added at 10:52 AM ---------- Previous post was at 10:50 AM ----------
karkand said:
hi,
is anyone have tried to flash custom rom with this method?
thanks.
Click to expand...
Click to collapse
OP said he was able to flash CM after having flashed custom recovery by this method. Also you might want to check the source of this guide in the OP. It's in French so google translate is your friend!
I used this method on 2 Kate phone and success installing cm13...
Envoyé de mon Redmi Note 3 en utilisant Tapatalk
Which CM rom did you install as I dont see any for Kate version.
Everything works?
Related
[INDEX] REDMI NOTE 3 PRO (Snapdragon 650) ==> LIST of ROMs -=- [#UPDATES thread 2]
Hi All,
Note: In most of the cases, I will try to post the forum links only and not direct links.
Thank the developers, who have contributed their valuable time for our fun and entertainment ...
Click to expand...
Click to collapse
This thread will be having the list of all custom ROMs and any other Mods required for RN3 (SD Version).
**VIP KERNEL SOURCE is here: CLICK HERE
Below are the list of Custom ROMS...
STOCK ROMs:
Developers ROM (Version 6.3.18): Click here
Stable ROM - GLOBAL (Version: V7.2.3.LHOMICL) : Click here
Stable ROM - CHINA (Version: 7.2) : Click here
CUSTOM ROMs:
Qualcomm FACTORY ROM - AOSP (Leaked with Dev Apps): Click here
CM12 - Cynogenmod: Click here
CM13 - Cynogenmod: Click here
OTAs:
Version 7.2.3 (190+MB): Click Here
NOTE: Help me guys to update this thread regularly and Post any missing information to add it here...
OFFICIAL TWRP:
Latest TWRP link: Click here
Haa haa...
Waiting for New Kernels to be placed in this section...
TOOLKIT (TWRP and others):
If u want to be with MIUI and want TWRP, please install TWRP boot image specific to your version. If want custom rom, I dont think, it matters. Anyway, Install this app and follow the steps. Link is : https://drive.google.com/file/d/0B0pkb-PnDIp8Rk1TdzhmUnZGdnc/view
Make FLASHABLE OTA via TWRP:
Here is the link for the Guide: Click Here
TWRP Repository: Click here
Modded MBN file (Responsbile for Locking Bootloader): Click here
Mislenious
Bootloader Unlocking - 100% PERFECT:
100% Working Bootloader unlocking solution for Xiaomi Redmi Note 3 Pro. You dont even need confirmation from Xiomi. You can UNLOCK / RE-LOCK Bootloader at any time...
Trust me, I have personally tested and unlocked my device. Follow steps mentioned over here : Click here
Conclusion : Dont wait for Xiamo to get the permission to unlock ur device. Follow above method. Altough u get permission, at least 95% chances that Mi Unlock application fails. I was trying with Mi unlock app for days and even following up in mi forums, with no working solution. They simply said, try it after a week... So, I dont want some one to waste their valuable time like me...
Reserved
Qualcom factory rom aren't an Custom. Modify your thread
Inviato dal mio kenzo utilizzando Tapatalk
We Really REALLY !!! need a Separate section for this device
https://github.com/kenzo-dev
now the source is released, this repo needs to be updated.
Add this ROM please
http://forum.xda-developers.com/red...cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656
Updated Working Bootloader Unlock process ie without Mi permission... I have done it and it works pretty fine..
Sorry but,just for info,how can I relock my bootloader?
GiovanniArpino said:
Sorry but,just for info,how can I relock my bootloader?
Click to expand...
Click to collapse
There are two ways,
1. Flashing Fastboot rom from mi forum will relock your Boot loader.
2. From the above mentioned tutorial, backup the original "fastboot flash aboot emmc_appsboot.mbn" file and it will relock the bootlader. optionally, you can try "fastboot oem lock" command as well.
srihari210 said:
There are two ways,
1. Flashing Fastboot rom from mi forum will relock your Boot loader.
2. From the above mentioned tutorial, backup the original "fastboot flash aboot emmc_appsboot.mbn" file and it will relock the bootlader. optionally, you can try "fastboot oem lock" command as well.
Click to expand...
Click to collapse
Thanks!
Sent from my Redmi Note 3 using XDA-Developers mobile app
srihari210 said:
Updated Working Bootloader Unlock process ie without Mi permission... I have done it and it works pretty fine..
Click to expand...
Click to collapse
Hi Can you please share the perfect process to unlock bootloader there are many unlock process threads are here..Share Process and Link
Anands3 said:
Hi Can you please share the perfect process to unlock bootloader there are many unlock process threads are here..Share Process and Link
Click to expand...
Click to collapse
On POST 3, I have given the link to the complete process and it works perfectly.
So, barely, its like, flashing 7.1.7 or 7.1.8 version with CHANGED MBN file. (MBN file is the main file which will allow unlocking from Fastboot command)
After flashing with changed MBN file, run the FASTBOOK OEM UNLOCK_GO command to unlock the file.
Then, u can check FASTBOOT OEM DEVICE-INFO to check the status. Then, flash other OS like CM12/13 or Qualcommn rom.
If u want MIUI os then, use FASTBOOT command to flash TWRP and reboot to TWRP. Then, download RECOVERY ZIP file and with WINZIP replace MBN and Changed BOOTLOADER (TWRP) file and then flash that file in TWRP. These steps are like an overview of the process, if u want more info, u can google it or check, MI forum
Hey guys I'm thinking of buying this phone the 32gb/3gb SD650 version to be specific and it's nice it's getting a custom roms just like the mtk version. How's the CM12/13 roms as for now overall? Stability, battery you know.. are these roms suitable for daily use? Btw now I have a K3 Note.
Custom ROMs are at very early stage and are not suitable for daily usage. As the kernel drivers are already out, we hope stable version will come soon... Qualcomm factory ROM is stable but feels slow...
Subbed and rated. Thanks for updating ^^
Direct Link to OTA for 7.2.3 is updated in first post. If anyone didnot get the OTA, download 190+MB zip file and put zip file in folder: /internalstorage/downloaded_rom/ Then, updater to update to new version of stock.
srihari210 said:
Dont wait for Xiamo to get the permission to unlock ur device. Follow above method. Altough u get permission, at least 95% chances that Mi Unlock application fails. I was trying with Mi unlock app for days and even following up in mi forums, with no working solution. They simply said, try it after a week... So, I dont want some one to waste their valuable time like me... [/HIDE]
Click to expand...
Click to collapse
I thought if you use this method and then Flash any MIUI ROM you get Brick ?
syl0n said:
I thought if you use this method and then Flash any MIUI ROM you get Brick ?
Click to expand...
Click to collapse
Nope, u ll not brick your phone. I have done that and it works flawlessly... I have unlocked bootloader and installed Qualcomm and CM12 roms and again flashed stock OTA via MI updater app. I didnt have any problem.
Although its not for novice users, in most of the cases, hardware bricking a phone is almost not possible, unless, u try to play directly with hardware. And, softbrick will easily be recoverable(Well u need a PC and drivers for sure)... its just like, when u r not able to run the OS in your phone, then, repair shop guy will just flash the stock rom and will give it back to you.... Just, thats what we are doing with MI updater. As mentioned earlier, this may not be for normal user...
Anyway, Thread 2 updated with new tutorial on How to flash OTAs without relocking your phone...
Hey guys, I have adapted my work on custom boot images to cover the Redmi Note 3.
I don't want to manage another thread so wander over to the RN2 thread where I will host work on the RN3 also.
A functional version is now available based on 7.2.50 boot.img. It will be slimmed down further to match the RN2 version but I need to be guided by feedback on what works as I do not have your device.
http://forum.xda-developers.com/redmi-note-2/development/b-skinny-pro-t3347906
Thanks you . i will test
https://drive.google.com/file/d/0BwdRTuyj12_ydFl0VGM4YWpZMWM/view?pref=2&pli=1
It is link?
---------- Post added at 04:42 PM ---------- Previous post was at 04:29 PM ----------
It is working on rom dev 6.4.28 Testing more. What more can i do to improve battery life. Sr my english so bad
@phunghai110 All of the tweaks that apply to the Redmi Note 2 also apply to the Redmi Note 3.
The boot.img enables you to create an init.d script which is the main tool for managing performance / battery life.
Start by making sure your Busybox installation is up to date. Link to my BB 1.24-2 updater here:
https://drive.google.com/file/d/0BwdRTuyj12_yY01jZGFTZi14X3c/view?usp=sharing
Next, update SuperSu to any recent full version (don't rely upon the stock MIUI included versions)
Now do everything in the first post here except for deleting fingerprint related files of course:
http://forum.xda-developers.com/redmi-note-2/development/b-skinny-pro-t3347906
Leave the zram lines disabled at the moment until I release a boot.img that successfully disables mcd service (waiting on feedback from Test3 version)
This should be enough to see an improvement. More to come.
Does it work on "unofficial" Miui Roms too ? Like this one lhttp://en.miui.com/thread-277452-1-1.html ? It's a 6.5.5 Global Rom
Cameo164 said:
Does it work on "unofficial" Miui Roms too ? Like this one lhttp://en.miui.com/thread-277452-1-1.html ? It's a 6.5.5 Global Rom
Click to expand...
Click to collapse
not sure, but if you have an unlocked bootloader & custom recovery there is not much of a risk to just try it out - just be sure to safe the original boot.img first!
i, for one, can confirm that it work's well on this modified rom by quakze: http://en.miui.com/thread-236615-1-1.html
schmanto said:
not sure, but if you have an unlocked bootloader & custom recovery there is not much of a risk to just try it out - just be sure to safe the original boot.img first!
i, for one, can confirm that it work's well on this modified rom by quakze: http://en.miui.com/thread-236615-1-1.html
Click to expand...
Click to collapse
Okay, thanks. I will try. I had the fear that it could hard brick my phone.
Every MTK based (advanced) phone user should familiarize themselves with using SP Flash tools - a hard brick is virtually impossible since the MTK chip is hard-coded to power on and be flashed via USB when it receives the special code sequence from such software. One piece of advice: Never-ever do a format using this tool unless you want to loose your nvram partition and hence IMEI.
Skinny_Pro_RN3_MIUI_7250-5_boot.img is looking stable (thanks to @schmanto for testing)
I cannot say whether it will be compatible with 6.5.5 yet but someone will tell me soon enough - there is no risk of anything disastrous happening and you will always have a good backup to recover too if it messes up
Tell me please 8020 v8 will work with RN3?
Okay, I read everything, but couldn't understand much (sorry )
Still I'm a go for experiments and testing, always ...
So what exactly is SkinnyPro, and why should I flash it? P.S. I hate Xiaomi, too! *high five* xD
Hi guys! I found a way to unlock your bootloader unofficially in Marshmallow ROMs in seconds without the Mi Unlocking Tool and even without the Approval from XiaoMi and I want to share with all users here. This works fine with Redmi Note 3 Pro Snapdragon and Special Edition versions under Marshmallow ROM.
Link for tutorial: http://en.miui.com/thread-345728-1-1.html
Not working for my Redmi Note 3 Special Edition (Kate). Wich ROM did you use for your Special Edition?
im0nKeY said:
Not working for my Redmi Note 3 Special Edition (Kate). Wich ROM did you use for your Special Edition?
Click to expand...
Click to collapse
Latest Special Edition Global Stable. Works 100%.
I tried it 3 days ago with the Global Stable MIUI 7 and if I flash the modified bootloader my Kate does not boot anymore.
andersonaragao said:
Hi guys! I found a way to unlock your bootloader unofficially in Marshmallow ROMs in seconds without the Mi Unlocking Tool and even without the Approval from XiaoMi and I want to share with all users here. This works fine with Redmi Note 3 Pro Snapdragon and Special Edition versions under Marshmallow ROM.
Link for tutorial: http://en.miui.com/thread-345728-1-1.html
Click to expand...
Click to collapse
Are you sure it will work for redmi note 3 pro snapdragon (kenzo)? Since there is no official marshmallow rom for Kenzo. Or could you direct me to the marshmallow rom for Kenzo.
This is the same as the old method on Lollipop MIUI, replacing emmc_appsboot.mbn with a hacked copy and flashing. I wouldn't call it a new method.
andersonaragao said:
Latest Special Edition Global Stable. Works 100%.
Click to expand...
Click to collapse
Is it really a Kate you got it to work on?
im0nKeY said:
Is it really a Kate you got it to work on?
Click to expand...
Click to collapse
SURELY friend! I post things only after test it. I have some devices here including 3 Kenzos and 2 Kates devices. Works great and some users already used it and works. Look:
http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=344469&pid=6293255
http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=345728&pid=6332982
Guys just follow the instructions, it works for 100%. I have done this already like three times with my "kate" device with global beta rom installed.
Can you all post the exactly version ROM version, with wich you archived this?
im0nKeY said:
Can you all post the exactly version ROM version, with wich you archived this?
Click to expand...
Click to collapse
You can use latest Stable (V7.5.2.0.MHRMIDE) fastboot or latest Beta (6.9.1) fastboot ROMs.
Is it possible to just flash the modified bootloader via:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
Greetings
im0nKeY
Can I use this emmc_appsboot.mbn file from that MM thread to install miui_6.9.9 recovery zip in safe_twrp recovery (I know,I'll have to flash SuperSu and lazy flasher after I flashed the MM recovery rom and after first boot) ?
Hi @andersonaragao,
Can you please update your tutorial on the miui forum? I'm stuck in the middle.
First, the latest MI Flash Tool from the link you provided does not have an Advanced button. Also, it can't find the device after reboot edl; one has to boot the phone into fastboot manually for it to be recognized.
I downloaded the one you used from http://obigota.d.miui.com/tools/MiPhone20151028.exe, which works as described.
Further, the ROMs provided by on http://en.miui.com/download-301.html#449 are zip files in which I can't find the .bat, .mdn and .xml files needed to configure MiFlash. Please explain or provide a link where a proper ROM can be downloaded.
Hope you can help me out here!
heinhuiz said:
Hi @andersonaragao,
Please explain or provide a link where a proper ROM can be downloaded.
Click to expand...
Click to collapse
To answer my own question: Fastboot ROM can be found here: http://en.miui.com/thread-328019-1-1.html
when I tried to flash, it got stuck on patching system image unconditionally. and nothing happens. any idea how to solve this? I have tried flashing with TWRP, ALKA, Cofface, still no luck
I've tried this guide loads of times now and I'm always stuck with "FAILED (remote: oem unlock is not allowed)".
All the info regarding the problem mention to boot into the system and turn on oem unlock in the developer options. But I can't boot with the modified emmc_appsboot.mbn I only get the Mi logo flashing. I didn't enabled before, as written in the guide.
Any ideas?
Tantin said:
I've tried this guide loads of times now and I'm always stuck with "FAILED (remote: oem unlock is not allowed)".
All the info regarding the problem mention to boot into the system and turn on oem unlock in the developer options. But I can't boot with the modified emmc_appsboot.mbn I only get the Mi logo flashing. I didn't enabled before, as written in the guide.
Any ideas?
Click to expand...
Click to collapse
If you are using a newer version than DEV 6.11.3 It's not going to work as the bootloader lock control has changed,
downgread first and than procced with the unlocking proccess
All you need is here hxxps://drive.google.com/file/d/0B1cyJDH0uIykTGpOMUY1N2pENVE/view
not works for me i have redmi note 3
---------- Post added at 07:18 AM ---------- Previous post was at 07:17 AM ----------
is redmi note 3 addition is different from it then please provide appsboot file for redmi note 3 also
blackpac said:
If you are using a newer version than DEV 6.11.3 It's not going to work as the bootloader lock control has changed,
downgread first and than procced with the unlocking proccess
All you need is here hxxps://drive.google.com/file/d/0B1cyJDH0uIykTGpOMUY1N2pENVE/view
Click to expand...
Click to collapse
Nice suggestion. But, will the bootloader stay unlocked if we update to the latest dev rom via twrp, once it is unlocked unofficially with dev 6.11.3 or an older version?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Can you provide instruction on how to disassemble the phone. Also where to order spares from. The digitiser on my Storm is cracked and Wileyfox want to charge me the price of a new phone to replace it.
JonnyTech said:
Can you provide instruction on how to disassemble the phone. Also where to order spares from. The digitiser on my Storm is cracked and Wileyfox want to charge me the price of a new phone to replace it.
Click to expand...
Click to collapse
Eh, sorry mate, I don't know how to disassemble the device and no one else sure as hell knows how to do it (at least on other websites). There are only reviews and unboxing experiences of the Wileyfox Storm and guides on how to flash ROMs, root and recoveries, etc. But some member will help you out, surely! If nobody seems to be knowing the issue, pm a forum moderator so that he/she can guide you to some links/methods. :fingers-crossed: Best of Luck!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Downgrade from Nougat to COS 13.1.5-ZNH2KAS7EC-kipper
Hello everybody
I need some help with my Wileyfox Storm. Yesterday it become an OTA update and my old Original COS13 is away and i have now Android Nougat 7.1.1. Stock Rom.
I will undo this, and i don't know how to start. I need a noob friendly Thread to do this.
I hope somebody can help me.
Grettings from Germany
Sorry for the poor English
Downgrade to android 6.0 marshmallow
Hello everyone, well recently my phone updated to android 7.1.1 and I didn´t like very much, so could help me and tell me if is there a way to go back to android marshmallow 6.0, just like it came when I bought it. Is it possible and does anyone know how to do it?
Okay so im trying to get lineage Os on my phone, this OS isn't working at all i get in bootloops etc. So i tried AOSP extended and i managed to get this working. But when i try to install gapps or try to flash Super su or magisk it returns error 1. The problem is in the recovery probably. So i tried to flash / boot a different TWRP version but all of the other versions give me this error: FAILED (remote: dtb not found). I would appreciate any help i can get i am hardstuck because i cant get a proper working TWRP recovery working and the only rom i am able to flash is AOX but without gapps that isnt worth much.
Thanks in advance.
Infiniterum said:
Okay so im trying to get lineage Os on my phone, this OS isn't working at all i get in bootloops etc.
Click to expand...
Click to collapse
First of all, what build of LineageOS are you trying to install??? If it is dated 12.07.2017 or 05.07.2017 - it won't work at all. That builds are broken. Use 28.06 or 21.06 build.
Secondly, what TWRP version do you use? I installed LOS via TWRP 3.1.0.0.
Newer version is available now.
And what bootloader version do you have on your Storm. I mean what stock ROM was installed before installing TWRP.
Infiniterum said:
So i tried AOSP extended and i managed to get this working. But when i try to install gapps or try to flash Super su or magisk it returns error 1.
Click to expand...
Click to collapse
It seems to me, AEX is pre-rooted and comes with magisk pre-installed. When I installed that - only gapps were necessary.
Gapps need to be installed immediately after installing ROM, without any reboot.
~FNWL~ said:
First of all, what build of LineageOS are you trying to install??? If it is dated 12.07.2017 or 05.07.2017 - it won't work at all. That builds are broken. Use 28.06 or 21.06 build.
Secondly, what TWRP version do you use? I installed LOS via TWRP 3.1.0.0.
Newer version is available now.
And what bootloader version do you have on your Storm. I mean what stock ROM was installed before installing TWRP.
It seems to me, AEX is pre-rooted and comes with magisk pre-installed. When I installed that - only gapps were necessary.
Gapps need to be installed immediately after installing ROM, without any reboot.
Click to expand...
Click to collapse
I was using 05/07 build so that explains that. Im using TWRP 3.0.3.0 Kipper, but i can't find newe TWRP builds for the wileyfox storm, if you could give me some links that would be great. Stock rom was android 7.1 i believe and bootloader version is 'kipper-N-g2253387'. When i installed AEX via my (probably corrupt) TWRP recovery it says it also flashed Magisk but once the phone starts and i go to the magisk app it says im unrooted and so does rootchecker say. I think my biggest problem is with the TWRP recovery. If you could get me the download links of the versions your using that would be great.
Here you can get TWRP
https://www.androidfilehost.com/?w=files&flid=189519
Thanks to kligli from 4pda
Maybe the bootloader from 7.1-wileyfox is not compatible with Lineage OS.
Before flashing TWRP and LOS, I rolled back to COS 13.1.5 official Wileyfox ROM via fastboot. So I don't really know whether it is compatible or not.
~FNWL~ said:
Here you can get TWRP
https://www.androidfilehost.com/?w=files&flid=189519
Thanks to kligli from 4pda
Maybe the bootloader from 7.1-wileyfox is not compatible with Lineage OS.
Before flashing TWRP and LOS, I rolled back to COS 13.1.5 official Wileyfox ROM via fastboot. So I don't really know whether it is compatible or not.
Click to expand...
Click to collapse
So i flashed the twrp 3.1 and that works, it installs gapps now and no error with lineage OS, im gonna boot phone soon hopefully lineage will start to, i didnt know what gapps to flash but i tried the arm64 because i read it somewhere. But isn't the Storm ARM?
Use ARM64 - 7.1 - nano or pico GApps. Lineage official site said it works even without any GApps, but I have not tried that.
So I just bought a wileyfox storm few days ago and am on 7.1.1 what is the rooting method thanks.
---------- Post added at 02:46 AM ---------- Previous post was at 02:26 AM ----------
Also a just went into the bootloader and status is unlocked but I never unlocked the bootloader yet any ideas on this??
Hi Guys
Someone of you have audio problems on whatsapp ( with integrated and bt mic ) when recording audio? ( noise and metallic audio recording )
I'm on Lineage 7.1.2 - 14.1-20180110-nightly but have same problems with previous rom
Hello XDA,
I have been using Samsung phones all my life , Rooted (odin) a lotta phones installed countless custom roms and finally i thought its time for pure android experience . I bought a moto g4 plus from a friend of mine and have been going through the g4 + forum for 2 days now . I have not got the slightest of idea how you root / install custom rom on this device . Its so different from how you do it on a Samsung device so finally I have decided to ask for your help .
Info I would like to share :
1.The boot loader is locked
2.The device is a XT1643
3. 3 GB / 32 GB
4. December 1 , 2017 security patch
5. NPJS25.93-14-13
6. There was a OTA update when I received the phone which I didn't update
As mentioned earlier It looks like I am a complete noob when it comes to this device and I would need all the possible help I can get .
If anybody would be kind enough to guide me through this initial learning phase I will be very grateful and would even share my whisky ( which I usually don't do )
If you need any more information please ask
Thanks and Regards
DW
Drunken-warlord said:
Hello XDA,
I have been using Samsung phones all my life , Rooted (odin) a lotta phones installed countless custom roms and finally i thought its time for pure android experience . I bought a moto g4 plus from a friend of mine and have been going through the g4 + forum for 2 days now . I have not got the slightest of idea how you root / install custom rom on this device . Its so different from how you do it on a Samsung device so finally I have decided to ask for your help .
Info I would like to share :
1.The boot loader is locked
2.The device is a XT1643
3. 3 GB / 32 GB
4. December 1 , 2017 security patch
5. NPJS25.93-14-13
6. There was a OTA update when I received the phone which I didn't update
As mentioned earlier It looks like I am a complete noob when it comes to this device and I would need all the possible help I can get .
If anybody would be kind enough to guide me through this initial learning phase I will be very grateful and would even share my whisky ( which I usually don't do )
If you need any more information please ask
Thanks and Regards
DW
Click to expand...
Click to collapse
I'm sorry to reprimand you, but you really need to follow the rules here. It took me all of a few moments to find exactly what you're looking for simply by searching.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Don't hesitate to ask questions in the future, but only if you've exhausted all other avenues.
Ragarianok said:
I'm sorry to reprimand you, but you really need to follow the rules here. It took me all of a few moments to find exactly what you're looking for simply by searching.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Don't hesitate to ask questions in the future, but only if you've exhausted all other avenues.
Click to expand...
Click to collapse
Hello Mate
As mentioned above I have been searching the forum for almost 2 days before I thought of asking for help . I did go through the thread( that you have mentioned ) earlier today but it looks a bit old to me . The link on how to flash twrp comes back with a 404 error . The last few posts are helpful (as it deals with the same build) but again as am new to the particular device It would be helpful if someone could give me a noob friendly procedure . I am not here to break the rules just trying to learn without bricking my device
Thanks and Regards
DW
yeshwanthvshenoy said:
Flashing TWRP:
>>> Flashing TWRP or Rooting will void your warranty. Please ask anything before doing, if your not fully confident on what to be done. <<<
Get the TWRP image file from http://forum.xda-developers.com/mot...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Next, get the adb and mfastboot from https://drive.google.com/file/d/0B5jlU9JnLAZGbVU0UzJ3N3p4X2M/view?usp=sharing
Unzip the file and place the image file inside the extracted folder.
Reboot to Bootloader (power off, then press the power and volume down buttons simultaneously).
Open a new command prompt or terminal window and do the following:
Code:
mfastboot flash recovery twrp_*version*_athene.img
Rooting Device:
>>> The old guide is outdated. Will be updated shortly. <<<
Click to expand...
Click to collapse
Drunken-warlord said:
Hello Mate
As mentioned above I have been searching the forum for almost 2 days before I thought of asking for help . I did go through the thread( that you have mentioned ) earlier today but it looks a bit old to me . The link on how to flash twrp comes back with a 404 error . The last few posts are helpful (as it deals with the same build) but again as am new to the particular device It would be helpful if someone could give me a noob friendly procedure . I am not here to break the rules just trying to learn without bricking my device
Thanks and Regards
DW
Click to expand...
Click to collapse
Sorry for being so short earlier. We have quite a few members here who constantly post issues without using the search function.
You can try to post I quoted above to flash TWRP. It's fairly straight forward.
Are you planning on flashing a Nougat ROM or are you going the adventurous route and flashing an Oreo ROM? The TWRP version mentioned in the quoted post should be fine for flashing Nougat and 32-bit based Oreo ROMs, but you'll need 64-bit TWRP for 64-bit Oreo ROMs.
Use this as a reference for 32-bit and 64-bit Oreo ROMs: https://forum.xda-developers.com/moto-g4-plus/how-to/oreo-roms-table-t3717226
64-bit TWRP: https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206
Once you've flashed TWRP, you can either flash different versions through TWRP itself or through the Play Store app.
As far as ROMs, I'd recommend Official Lineage OS 14.1 for Nougat: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101
And I'd recommend Official AICP 13.1 for Oreo: https://forum.xda-developers.com/mo...om-aicp-13-1-o-8-1-0-official-weekly-t3731269 (You'll need to download the 20180212 build since most recent builds either have a broken camera or won't boot.)
Any other questions, don't hesitate to ask.
Drunken-warlord said:
Hello Mate
As mentioned above I have been searching the forum for almost 2 days before I thought of asking for help . I did go through the thread( that you have mentioned ) earlier today but it looks a bit old to me . The link on how to flash twrp comes back with a 404 error . The last few posts are helpful (as it deals with the same build) but again as am new to the particular device It would be helpful if someone could give me a noob friendly procedure . I am not here to break the rules just trying to learn without bricking my device
Thanks and Regards
DW
Click to expand...
Click to collapse
Hello and welcome, Please have a look in each device forum for a newbie help thread https://forum.xda-developers.com/moto-g4-plus/help/help-thread-question-noob-friendly-t3526598 where you can ask questions that are repeatedly asked and where you'll be guided to the right threads to help you further :good:
This keeps the forum clean and everything at a glance so you'll be find easily topics
@Ragarianok
I am going to try the Oreo builds as I have never got a chance to try it on my previous devices so I guess I will be using a 64bit version of twrp.
This is what am planning to do :
1. Unlock the bootloader
2. Flash an official version of TWRP
2.a Take a backup
3. Flash a custom kernel through twrp
4. Flash Super Su / Magisk
5. Flash a 64 bit version of twrp using TWRP
6. Flash a custom ROM
Please correct me if I am wrong
Thanks a lot for the detailed guide
Thanks and Regards
DW
Drunken-warlord said:
@Ragarianok
I am going to try the Oreo builds as I have never got a chance to try it on my previous devices so I guess I will be using a 64bit version of twrp.
This is what am planning to do :
1. Unlock the bootloader
2. Flash an official version of TWRP
2.a Take a backup
3. Flash a custom kernel through twrp
4. Flash Super Su / Magisk
5. Flash a 64 bit version of twrp using TWRP
6. Flash a custom ROM
Please correct me if I am wrong
Thanks a lot for the detailed guide
Thanks and Regards
DW
Click to expand...
Click to collapse
If you want 64bit Oreo roms it's a little bit different
1. Unlock the bootloader
2. Flash a 64 bit version of twrp
2.a Take a backup and safe it off your phone
3. Flash a Oreo 64bit custom ROM
3.a flash gapps package arm64 (8.0 or 8.1 depending on rom version)
4. Flash magisk 15.3
If you want to root the stock nougat rom steps 1-4 of your list are correct.
Drunken-warlord said:
@Ragarianok
I am going to try the Oreo builds as I have never got a chance to try it on my previous devices so I guess I will be using a 64bit version of twrp.
This is what am planning to do :
1. Unlock the bootloader
2. Flash an official version of TWRP
2.a Take a backup
3. Flash a custom kernel through twrp
4. Flash Super Su / Magisk
5. Flash a 64 bit version of twrp using TWRP
6. Flash a custom ROM
Please correct me if I am wrong
Thanks a lot for the detailed guide
Thanks and Regards
DW
Click to expand...
Click to collapse
Not quite. You'll want to go in this order:
1. Unlock bootloader
2. Flash TWRP
3. Backup
4. Wipe (Wipe/Advanced Wipe; ART/Dalvik, System, Data, Cache)
5. Flash ROM
6. Flash Gapps
7. Reboot
8. Go through setup wizard and let everything settle for ~10 minutes
9. Boot into TWRP and flash SuperSU or Magisk (I would suggest Magisk), then flash kernel and reboot
You'll need to flash the unofficial 64-bit TWRP mentioned in my previous post to flash a 64-bit Oreo ROM, otherwise you'll get an error message when flashing ROM.
You'll also need to use unofficial Gapps since there aren't any official Gapps for 8.1 just yet. I'd recommend either mini or micro here: https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/20180225/
You should be able to flash the most recent Magisk located here: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
If you do flash a custom kernel, I'd highly suggest Frostbitten: https://forum.xda-developers.com/mo...s-frostbitten-kernel-moto-g4-g4-plus-t3649155
@strongst
Just noticed that you posted a similar set of instructions and now I feel like a goober.
Ragarianok said:
Just noticed that you posted a similar set of instructions and now I feel like a goober.
Click to expand...
Click to collapse
What's a goober there are every time different ways users must decide which one to choose :laugh:
strongst said:
What's a goober there are every time different ways users must decide which one to choose :laugh:
Click to expand...
Click to collapse
In this context, it basically means I did something silly.
Ragarianok said:
In this context, it basically means I did something silly.
Click to expand...
Click to collapse
Nope you didn't
@strongst @Ragarianok
I am glad that I got the G4+. With amazing people like you on the forum it's guaranteed to be fun-filled learning experience
Thanks again for the support
Regards
DW
Drunken-warlord said:
@[email protected]
I am glad that I got the G4+. With amazing people like you on the forum it's guaranteed to be fun-filled learning experience
Thanks again for the support
Regards
DW
Click to expand...
Click to collapse
Thanks, you're welcome :good:
Ota ? ..... Was it jan security patch update ?
pang12345 said:
Ota ? ..... Was it jan security patch update ?
Click to expand...
Click to collapse
If it was an OTA update, it looks likely to be more the February 2018 security patch rather than the January 2018 patch.
Credit https://forum.xda-developers.com/moto-g4-plus/how-to/athene-security-patch-usa-february-t3745147
echo92 said:
If it was an OTA update, it looks likely to be more the February 2018 security patch rather than the January 2018 patch.
Credit https://forum.xda-developers.com/moto-g4-plus/how-to/athene-security-patch-usa-february-t3745147
Click to expand...
Click to collapse
The op was talking about xt1643 ,and this model is for india. And the link that you mentioned is for us model .
pang12345 said:
The op was talking about xt1643 ,and this model is for india. And the link that you mentioned is for us model .
Click to expand...
Click to collapse
That is true, however for our devices we have generally been issued the same security patch level regardless of region. It may be different builds for particular regions (e.g NPJS25.93-14-13 for India, Brazil and EU, and NPJ25.93-14.7-3 for US) but they are both the December 2017 security patch.
Regardless, we've still yet to see an OTA newer than December.
@strongst @Ragarianok @echo92
Evening ,
Thanks For all the support i finally rooted MY phone
But
I ran into a bit of a problem " Sim Cards Not Detecting "
This is What i did
1. Unlocked My bootloader
2. flashed twrp-3.1.1-athene_shreps
3. Took a backup of everything
4. flashed ElementalX-G4-2.00.zip
5. flashed Magisk 16.0
reboot : No sim cards detected
After which I flashed lineage-14.1-20180219-nightly-athene-signed.zip and the gapps provided
experienced the same error again .
uninstalled magisk and flashed the latest Super Su (V2.82) with no positive results
not sure what went wrong ...is there any way out of it ?
Drunken-warlord said:
@strongst @Ragarianok @echo92
Evening ,
Thanks For all the support i finally rooted MY phone
But
I ran into a bit of a problem " Sim Cards Not Detecting "
This is What i did
1. Unlocked My bootloader
2. flashed twrp-3.1.1-athene_shreps
3. Took a backup of everything
4. flashed ElementalX-G4-2.00.zip
5. flashed Magisk 16.0
reboot : No sim cards detected
After which I flashed lineage-14.1-20180219-nightly-athene-signed.zip and the gapps provided
experienced the same error again .
uninstalled magisk and flashed the latest Super Su (V2.82) with no positive results
not sure what went wrong ...is there any way out of it ?
Click to expand...
Click to collapse
First, I'm a little confused about the fact that you flashed that version of TWRP instead of the one located here: https://dl.twrp.me/athene/
Second, I've never had that happen when flashing, so I'm not really sure what to recommend. If I had to guess, I would say the best route would be to restore your backup and see if the SIM is detected.
I have found at least one thread with a similar issue; might be worth a look: https://forum.xda-developers.com/moto-g4-plus/how-to/fix-sim-card-issue-t3751679
Let us know what happens.
Ragarianok said:
First, I'm a little confused about the fact that you flashed that version of TWRP instead of the one located here: https://dl.twrp.me/athene/
Second, I've never had that happen when flashing, so I'm not really sure what to recommend. If I had to guess, I would say the best route would be to restore your backup and see if the SIM is detected.
I have found at least one thread with a similar issue; might be worth a look: https://forum.xda-developers.com/moto-g4-plus/how-to/fix-sim-card-issue-t3751679
Let us know what happens.
Click to expand...
Click to collapse
I went through that before posting my question .. the paper does not help .
Is it okey if I flash the twrp that you have mentioned over the existing twrp?
Thanks and regards
DW
Edit : I have restored my backup but still the same issue.
Edit : flashed the official TWRP . still the same results
EDIT : After 3 hours + Countless reboots the issue solved on its own ... I am not sure what really happened.. lol
Thanks for the Support
DW