Related
Latest Android 6.0 Build No. MPSH24.49.18-4 for Moto X Style
Scenario:
While experimenting various stock roms for my Indian Version Moto X Style 1572, I flashed 1575 on my phone. Network did not work. But without trying to fix all the issues , I stepped back and flashed back to Indian Retail Version of Stock Rom XT1572_CLARK_RETASIA_DS_6.0_MPH24.49-18_cid7_subsidy-DEFAULT_CFC.xml.zip from this page. Everything worked but my Bluetooth stopped working. Then tried almost all custom roms and even cyanogen but BT never worked.
So now I was left for few days with BlueTooth issues in phone. Then after taking hints from various threads I managed to unbrick my phone to get latest stock build and May 2016 Android Secutity Patch Level
In short this guide unbricks Indian Moto X Style perfectly to resolve BlueTooth issues / IMEI Loss / other network related issues by flashing latest stock to Android 6.0
Advantages:
1) An important thing to remember, that above Indian stock rom, you will get Android Security Patch Level dated 1-February-2016. But I with files linked by me in this guide (Brazil Rom) so you will get Android Security Patch dated 1-May-2016 with more security
2) The rom is 3 months latest than Indian Stock and build is MPSH24.49.18-4.
3) Initial free space of usable internal memory is upto 75% out of 10GB, which is much higher than Indian Stock which gives only 50% usable space.
Resolution:
Taking idea from this EU (European) Single Sim version I decided to try BRAZIL's latest Dual Sim stock rom and then flash modem+baseband, and VOILA!! Everything Worked perfectly! No network and bluetooth issue anymore.
UNBRICKING STEPS:
So I thought to put these steps here following easy steps.
1) Download BRAZIL's latest official Dual Sim MM 6.0 firmware - MPHS 24.49-18-4 - RETLA-DS-Brazil (May) from here. Extract all files from rar file into new folder on desktop of pc.
2) Also Download Indian Baseband or Modem file called fsg.mbn (DOWNLOAD and extract "fsg.mbn" file in above new folder on your desktop by replacing over brazillian version of fsg.mbn
3) Start phone in Bootloader Mode (power off phone. Then press VolumeDown Key and Power Key both together to start phone in bootloader mode)
and then connect phone to pc with usb cable.
4) Now open command prompt windows on your pc and from the new folder, execute batch file named "Instalador.bat" at command prompt. Wait until all commands are executed which flashes all partition image files one by one. Press any key when prompted on screen to go ahead and wait until it finishes. When done phone will automatically restart. Now you can disconnect USB cable from phone.
Phone will start normally but WITH FULL NETWORK, Wifi and BLUETOOTH all working just fine.
5) Optional (rooting): First enable debugging mode in Settings >> Developer Mode. Restart phone in bootloader mode and connect to pc and from windows command prompt execute following commands to flash latest TWRP recovery file. (DOWNLOAD TWRP).
mfastboot flash recovery twrp-3.0.2-0-clark.img
Click to expand...
Click to collapse
Now start phone in TWRP RECOVERY mode and flash SuperSU flashable zip (DOWNLOAD)
You are done! Network will start showing properly and strongly in both sims Bluetooth also works fine as it should work.
===================================
*Note: 5th step is optional if you do not want to ROOT your phone.
THANKS TO
1) Luiz Augusto Cisneiros Christofoletti from facebook for exact Brazil Stock Link and European unbrick thread.
Reserved
Will I be able to get Ota updates in this rom in India.
[email protected] said:
Will I be able to get Ota updates in this rom in India.
Click to expand...
Click to collapse
No! You will not get OTA automatically but you can still flash new one manually over this rom. No need to worry when everything is possible with xda
In any case if you are rooting phone with last step then you will not get ota.
Can u post the process to flash the 6.0.1 build for the Moto X Style Indian Version. It is much more fast and stable than 6.0. It has already been provided for Moto X Pure so would I be able to flash it by changing modem ,if yes then please show the process, becasue no ROM has the stability which stock has and I didnt take the backup the day I rooted the phone.
Deleted
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Code:
chintandavda said:
Can u post the process to flash the 6.0.1 build for the Moto X Style Indian Version. It is much more fast and stable than 6.0. It has already been provided for Moto X Pure so would I be able to flash it by changing modem ,if yes then please show the process, becasue no ROM has the stability which stock has and I didnt take the backup the day I rooted the phone.
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/Moto X Style/Stock/
Check the phone version/ retail version and then u can flash it
Ps. There is no flashable stock rom available yet
U can follow the steps by
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
Thankyou
Sagar_1401 said:
https://firmware.center/firmware/Motorola/Moto X Style/Stock/
Check the phone version/ retail version and then u can flash it
Ps. There is no flashable stock rom available yet
U can follow the steps by
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
Thankyou
Click to expand...
Click to collapse
Can you please help me to locate Indian version as my baseband is retasia - MPHS24.49-18-4 but i cant find the same in the list provided. It'll be really greatfull if you can help me out here.
rockinsnake said:
Can you please help me to locate Indian version as my baseband is retasia - MPHS24.49-18-4 but i cant find the same in the list provided. It'll be really greatfull if you can help me out here.
Click to expand...
Click to collapse
bro why need
MPHS24.49-18-4 build where as u can flash latest 6.0.1
trust me
flash this https://firmware.center/firmware/Mo...HS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
refer this thread
Sagar_1401 said:
bro why need
MPHS24.49-18-4 build where as u can flash latest 6.0.1
trust me
flash this https://firmware.center/firmware/Mo...HS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
refer this thread
Click to expand...
Click to collapse
Is this more stable than the one installed?
Hope this will not messup any modem part. One guy on the mentioned thread faced issue while flashing:
http://forum.xda-developers.com//mo...moto-x-style-pure-stock-t3272486/post68936541
Instalador.bat?
Where is the Instalador.bat? it is not in the zip file.
If anyone have Moto x style August update india rom then please give me my IMEI is not working and I have to flash it with stock ROM please give me
[email protected] said:
If anyone have Moto x style August update india rom then please give me my IMEI is not working and I have to flash it with stock ROM please give me
Click to expand...
Click to collapse
I use this for my Indian Style
https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
unfortunately its not working with me please help me out i cant install any custom ROM too
im stuck in stock mm without WiFi,network
MIUI 8 GLOBAL BETA 6.8.11 reported for DOOGEE DG700
Requirements:
Stock 4.4 KK firmware installed on the phone
Custom recovery
A working brain ... and some patience!
Credits:
All credits go to team ARGN for crossporting MTK6592 to MTK6582 and updating their ported rom here
Me for porting from Gionee M2 to DG700
Feautures:
Cross ported from the latest MIUI8 xiaomi.eu release for Redmi Note. (credits go to team ARGN)
DG700 rom uses as base TEAM ARGN crossports from MTK6592 to MTK6582.
Working: dual sim 3g (using dual sim control apk), wifi, bluetooth, gps, camara, sdcard, and everything else.
No chiness apps
All gapps preinstalled as system apps.
Enhanced camera pics quality (must be enabled in camera settings).
Repartitioned internal storage to 6G, custom carliv touch recovery (using stock kk firmware in the downloads at the end of the post).
Xposed and xposed modules working.
Many more ...
Known bugs:
Theme apk SOMETIMES FC's, but themes are working.
NVRAMWARNING wifi bug, easilly fixable (search xda or google for fix), wifi works just ok even with the NVRAMWARINING bug.
Battery capacity will be shown only at 3100mah, even so battery life is far more superior than the actual R25 lollipop firmware for DG700. (I get about 3 days with wifi / data on, moderate usage of the phone on the current MIUI8 based on kk rom)
Custom recovery CTR touch NOT WORKING. USE HARDWARE KEYS!
Installing
Download DG700_MIUI8_beta_global_6.8.11.zip (link at the end of the post), copy it on the sd card.
Download Stock R14 firmware linked at the end of the post (the attached build INCLUDES CTR custom recovery and repartitioned internal storage to 6G), unzip the archive and flash it with sp flash tools.
After flashing R14 go directly to recovery, DO NOT BOOT into android.
Once in recovery take the following steps:
1. Wipe and Format Options > Clean to Install a new rom ... wait for the recovery to wipe system, data, go back to the main menu
2. Install zip > Choose zip from storage/sdcard1 > browse for DG700_MIUI8_beta_global_6.8.11.zip and select it, install and wait for the installer to finish, go back to the main menu
3. Reboot system now, when asked to install su / root phone, select NO! (if you want to root the phone later you can install Chainfire SU binaries from the recovery, and than SU app from the market)
Wait for the rom to load, for the first time it will take some time ... be patient.
If you are not on stock KK THIS WILL NOT WORK! After flashing R14 firmware you will loose the IMEI's. Follow the guide frome here to restore the IMEI's:IMEI REPAIR / RESTORE /BACKUP
Customizing ... well ... the sky is the limit ... I use Plak to remove titles from the hotseat / launcher icons (as you cans see in the attached screenshots) and MIUI Tweaks for status bar (notification bar) customization ...
IF ALL GOES WELL or IF YOU ENCOUNTER ANY PROBELMS PLEASE POST BACK!
If this post helped you hit the Thanks button!
ENJOY!
Downloads:
DG700 R14 Stock KK with CTR and repartitioned internal memory: DOWNLOAD LINK
DG700 MIUI8 xiaomi.eu global beta v6.8.11: DOWNLOAD LINK
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
simchaleh said:
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
Click to expand...
Click to collapse
You will need to use spflash tool and the stock rom attached in my first post in order to install (flash) kitkat. Search google or xda for a tutorial on how to use spflash tool.
Have in mind that this is an advanced process and many things might go wrong if you don't have experience with flashing the whole android on your phone.
I think that at some point even doogee had a tutorial at their site showing how to upgrade from kitkat to lollipop (see here: http://www.doogee.cc/download.php?ProId=41). It is the same process only you need to format the whole phone before flashing and instead of flashing lp use kk images and scatter attached by me. If you're not sure what you are doing do some research first ... there are lots of great tutorials on the net for spflashtools and mtk6582 phone. Also have in mind that for some newer DG700 models it is impossible to flash kitkat because of some drivers issues ... or so it was stated on the 4pda.ru dg700 thread.
Hey @tvladan,
thanks a lot for this thread!!!
My experience and feedback:
All went smooth until I booted with the Miui installed. Because the IMEI problem I was not able to log into android (use than play store) nor Miui and the system would not let me go any further until I could by magic.
IMEI
I could not log in (system need unique phone ID such IMEI) so I needed to get the apks and move/save on the sdcard to be installed.
I could not restore the IMEI with MTK which was suggesting a reset in order to fix it and I had no clue how to reset (not reboot).
Mobile uncle. I made a IMEI backup but even if the app was restoring without problem, it really did not do anything also after rebooting
Chameleon: the only app that did something although not permanent. I'm working to fix it
Nvram error: fixed with no issue as on this thread
MIUI: it is definitively a nice designed UI although the one I personally do not prefer. It is flexible if you want to do things as developers allow you which is on my opinion sometime to strick if we consider we all are looking for a rooted phone and than we are bond by the UI. For sure there are some features that are useful as were some I really appreciate from the stock ROM. One example: I agree that moving app to the SD card might slow down the system and use more battery but now that I've achieved a 6GB rom I'm using all of it for the app and just marginal cache/data will be saved on the SD....
@tvladan: If I'd like to try only the KK rom without the MIUI and avoid the IMEI problem, are the following steps correct:
1) restore LP with TWRP
2) install stock R14 KK
3) install your KK with 6gb partition
If this is correct, in all this writing and overwriting, is there any chance I'll flash the recovery TWRP?
In case it will happen, can I use the one as by this thread by @NaturalBornCamper
thanks and enjoy your DG700
ciao
gipsea said:
Hey @tvladan,
thanks a lot for this thread!!!
If I'd like to try only the KK rom without the MIUI and avoid the IMEI problem, are the following steps correct:
1) restore LP with TWRP
2) install stock R14 KK
3) install your KK with 6gb partition
If this is correct, in all this writing and overwriting, is there any chance I'll flash the recovery TWRP?
In case it will happen, can I use the one as by this thread by @NaturalBornCamper
thanks and enjoy your DG700
ciao
Click to expand...
Click to collapse
Yes you can install stock kk but not using the steps you posted. You can not restore it via twrp, you must flash it with spflash tools (using format mode, kk or lp, as you please) BUT you will still loose imei's. This happens because of the format method used by spflash tools, in most MTK phones, that erases all the internal partitions of the phone.
Regarding LP, there is a latest firmware (official) by dooge - R25 that has the internal memory repartitioned to 5.5Gb. I would recommand installing that and than rooting (if needed) via twrp using chainfire binaries. You can download the R25 from here: https://docs.google.com/uc?id=0B_UWiyCZx5s1Z2xxZTRYTE9OcGc&export=download. The thread by NaturalBornCamper is old, deprecated and useless now. That was in the beggining when we did not have a custom recovery or the knowledge on how to root / repartition the DG700 phone.
Regarding lost IMEIS i RECOMMAND the MAUI 3G METHOD to restore them for our phone presented here: http://forum.xda-developers.com/unite-2/general/guide-repair-imei-invalid-micromax-t3048984 It needs a little more work, but once the correct drivers are installed it should work no matter what! (It also has a video tutorial, with some patience and little knowledge you should succeed in properly restoring the IMEI's). In your situation, whatever rom / firmware you will flash now using spflsh tools it will NOT restore the imei's because the nvram was formated.
Good Luck!
LE: To sum it up, to have the latest LP, repartitioned and rooted you will have to follow these steps (and have some knowledge on how to use spflash tools)
1. Flash R25 using spflashtools in format mode.
2. Start up the phone, wait to boot into android (just wait, it will take a while because it will encrypt the data partition). Setup the phone, fix imei's using maui 3g tool methond posted above. At this point you should have a "re-partitioned", unrooted, on stock recovery phone with the proper IMEI's
3. Download the latest chainfire su binaries from here: https://download.chainfire.eu/696/supersu/ and copy the zip to sd card. (UPDATE-supersu-v...... link)
4. Flash TWRP using spflashtools in download mode.
5. DO NOT START ANDROID, Reboot the phone in recovery mode witch should be now twrp that you just flashed before. If you start up android it is possible and very likely that it will restore the stock recovery, but if restarting in twrp first it will override the restoring of the stock recovery forever.
6. Flash the update-supersu-file via twrp
7. Reboot the phone in andorid (if asked by twrp to root, select NO), go to the market, instal chainfire supersu apk, and voila you are now on the latest LP (witch is repartitioned), custom twrp recovery and rooted.
if you need the link to twrp only pls post back I'll upload it somewhere for you!
ciao @tvladan,
thanks for your reply.
Quick question: as I did back up the LP with TWRP including NVRAM, if I restore it will it be permanent? I read the thread you suggested about IMEI/NVRAM but if this work it is a straight shot
I'd like to try the R25 LP and KK. Did you tried both? KK apparently was better compared to the LP up to R24.
Thanks
gipsea said:
ciao @tvladan,
thanks for your reply.
Quick question: as I did back up the LP with TWRP including NVRAM, if I restore it will it be permanent? I read the thread you suggested about IMEI/NVRAM but if this work it is a straight shot
I'd like to try the R25 LP and KK. Did you tried both? KK apparently was better compared to the LP up to R24.
Thanks
Click to expand...
Click to collapse
LP moves a little slower than kk. Nothing to worry about. Regarding battery life there is a 12 -24 hours difference from lp to kk, kk lasting longer. If you install xposed framework on lp it will move a LOT slower. If you do not need xposed I recommend R25 LP. Also I have no knowledge of TWRP being able to backup nvarm. I might be wrong. All you can do is try different methods until you succeed. It is a devious and annoying process but when you get it right you'll be satisfied. Also after lots of hours fking around with this phone I really stand by the steps posted in my previous post as to how to repartition / root / repair imeis the fastest way!
simchaleh said:
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
Click to expand...
Click to collapse
tvladan said:
Yes you can install stock kk but not using the steps you posted. You can not restore it via twrp, you must flash it with spflash tools (using format mode, kk or lp, as you please) BUT you will still loose imei's. This happens because of the format method used by spflash tools, in most MTK phones, that erases all the internal partitions of the phone.
Regarding LP, there is a latest firmware (official) by dooge - R25 that has the internal memory repartitioned to 5.5Gb. I would recommand installing that and than rooting (if needed) via twrp using chainfire binaries. You can download the R25 from here: https://docs.google.com/uc?id=0B_UWiyCZx5s1Z2xxZTRYTE9OcGc&export=download. The thread by NaturalBornCamper is old, deprecated and useless now. That was in the beggining when we did not have a custom recovery or the knowledge on how to root / repartition the DG700 phone.
Regarding lost IMEIS i RECOMMAND the MAUI 3G METHOD to restore them for our phone presented here: http://forum.xda-developers.com/unite-2/general/guide-repair-imei-invalid-micromax-t3048984 It needs a little more work, but once the correct drivers are installed it should work no matter what! (It also has a video tutorial, with some patience and little knowledge you should succeed in properly restoring the IMEI's). In your situation, whatever rom / firmware you will flash now using spflsh tools it will NOT restore the imei's because the nvram was formated.
Good Luck!
LE: To sum it up, to have the latest LP, repartitioned and rooted you will have to follow these steps (and have some knowledge on how to use spflash tools)
1. Flash R25 using spflashtools in format mode.
2. Start up the phone, wait to boot into android (just wait, it will take a while because it will encrypt the data partition). Setup the phone, fix imei's using maui 3g tool methond posted above. At this point you should have a "re-partitioned", unrooted, on stock recovery phone with the proper IMEI's
3. Download the latest chainfire su binaries from here: https://download.chainfire.eu/696/supersu/ and copy the zip to sd card. (UPDATE-supersu-v...... link)
4. Flash TWRP using spflashtools in download mode.
5. DO NOT START ANDROID, Reboot the phone in recovery mode witch should be now twrp that you just flashed before. If you start up android it is possible and very likely that it will restore the stock recovery, but if restarting in twrp first it will override the restoring of the stock recovery forever.
6. Flash the update-supersu-file via twrp
7. Reboot the phone in andorid (if asked by twrp to root, select NO), go to the market, instal chainfire supersu apk, and voila you are now on the latest LP (witch is repartitioned), custom twrp recovery and rooted.
if you need the link to twrp only pls post back I'll upload it somewhere for you!
Click to expand...
Click to collapse
About #4), flash TWRP. I have used the one posted by @NaturalBornCamper on his thread on step 11
If the TWRP for KK is different please post
I'm working on R25
Next fun step, R14
Thanks
It is the same twrp, works on kk and lp. You have the right one. For r25 it does not matter on what you are now, the spflashtool needs to format all the phone in order to install r25.
Thanks and good to know.
Now I'm getting curious about NVRAM/IMEI and TWRP...
TWRP can make backup of NVRAM and I did before installing the KK with MIUI8.
If I understood correctly IMEI information is stored in the NVRAM so, theoretically, if I restore the first back up of the NVRAM I should restore also the IMEI?!?!?!
how can I check the difference between a temporary IMEI installation like with chamelephone from a permanent solution?
ciao
gipsea said:
Thanks and good to know.
Now I'm getting curious about NVRAM/IMEI and TWRP...
TWRP can make backup of NVRAM and I did before installing the KK with MIUI8.
If I understood correctly IMEI information is stored in the NVRAM so, theoretically, if I restore the first back up of the NVRAM I should restore also the IMEI?!?!?!
how can I check the difference between a temporary IMEI installation like with chamelephone from a permanent solution?
ciao
Click to expand...
Click to collapse
All you can do is try to restore via twrp ... temp imei restore should be erased at reboot.
Thank you for this very Good rom. it's better than the stock KitKat
Do you have any resurrection remix for this device or any marshmallow based on KitKat kernel..please
Unfortunately no, i moved to a mi5 last year and placed my old doogee in a drawer for safe keeping. This is the last port i made.
tvladan said:
Unfortunately no, i moved to a mi5 last year and placed my old doogee in a drawer for safe keeping. This is the last port i made.
Click to expand...
Click to collapse
Sorry for bothering you again . I just wanted to know if it is possible to restore lollipopTWRP backup without flashing stock lollipop with flashing tool . When I'm on KitKat..is it possible to just flash The kernel .
Thank you
zidane01 said:
Sorry for bothering you again . I just wanted to know if it is possible to restore lollipopTWRP backup without flashing stock lollipop with flashing tool . When I'm on KitKat..is it possible to just flash The kernel .
Thank you
Click to expand...
Click to collapse
Unfortunately it is not possible to restore lolipop over kitkat or opposite because of the big differences in partition tables used by each of them. So the only way to restore a nandroid image is to flash stock with spflash tools with format, install the custom recovery and than restore the recovery backup.
tvladan said:
Unfortunately it is not possible to restore lolipop over kitkat or opposite because of the big differences in partition tables used by each of them. So the only way to restore a nandroid image is to flash stock with spflash tools with format, install the custom recovery and than restore the recovery backup.
Click to expand...
Click to collapse
Ok thank you...then I better stick with kitkat even do some applications stopped supporting it.
You can move to doogee s60, it's on sale on gearbest and it is way better than titans s2. Also comes with android n from factory.
tvladan said:
You can move to doogee s60, it's on sale on gearbest and it is way better than titans s2. Also comes with android n from factory.
Click to expand...
Click to collapse
Thank you for the tip but I will stick with my beloved dg700 until it dies or I die.. Lol
Hi guys,
I tried to update my Bln-l21 from emui 5 (nougat) to emui 8 (oreo) using the guide https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
It worked so I went on to install TWRP from https://forum.xda-developers.com/honor-6x/development/rom-emui-8-0-0-honor-6x-dual-sim-t3794079, as suggested in a comment on the guide.
Only then I realized that in order to install Gapps I needed GSM installer, so I downloaded it, but it didn't work because it loaded TWRP instead of the stock erecovery.
I started to panic real bad
I tried reinstalling the firmware using hwota8 (since i had upgraded i figured i had to use that), but it completely destroyed my phone.
Now it wont boot, recovery wont boot and neither erecovery. I can only get it to enter fastboot.
I know, I am a total noob, but PLEASE help me out on this, i'm desperate.
Thank you so much
If you can enter into fastboot, just install twrp, boot into twrp and flash the ROM using HuRUpdater. Use your external storage for the HuRUpdater and the ROM files. The instructions are here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Before flashing through Hurupdater wipe system Cache Data Internal and Dalvik/ART Cache.
galapagos said:
If you can enter into fastboot, just install twrp, boot into twrp and flash the ROM using HuRUpdater. Use your external storage for the HuRUpdater and the ROM files. The instructions are here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank you for the answer, I was able to boot in TWRP (the one in the original post) and I downloaded Huru, but I'm unsure of which firmware to use. I want to downgrade back to nougat and rebrand back to europe (since the guide in the original post made me change to china).
Thank you again
Just use China and then install a custom ROM
Mannan Qamar said:
Just use China and then install a custom ROM
Click to expand...
Click to collapse
which one should I choose from firmware finder?
Which rom do you recommend?
Bonny96 said:
which one should I choose from firmware finder?
Which rom do you recommend?
Click to expand...
Click to collapse
Just use the original files you used in the first place. The ones you downloaded from the thread. In terms of a custom ROM there is a thread in Custom ROMS section for Pixys OS. Just search stable Pie ROM for Honor 6x and install it. It's very smooth, etc.
This is a EMUI 8 ROM. If you want to go back to EMUI 5 don't use this. This will only restore EMUI 8. After that flash Custom ROM Don't go back to EMUI 5
Mannan Qamar said:
Just use the original files you used in the first place. The ones you downloaded from the thread. In terms of a custom ROM there is a thread in Custom ROMS section for Pixys OS. Just search stable Pie ROM for Honor 6x and install it. It's very smooth, etc.
This is a EMUI 8 ROM. If you want to go back to EMUI 5 don't use this. This will only restore EMUI 8. After that flash Custom ROM Don't go back to EMUI 5
Click to expand...
Click to collapse
Hi, I successfully flashed with Hurupdater and I'm going trough the installation of the pixys rom. The guide says that i need to flash the stock recovery for my device, where can I find it?
Can I pull it from the firmware I used for Huru? If that's the case, how?
Thank you again
I do have instructions over there but cause you asked I will tell.
Extract the Update.zip the large file. In it you will have an Update.app. Now serach for Huawei Update Extractor on XDA and Download it. Run the application and navigate to Update.app. Select it and in settings of Extractor uncheck the first option. Now extract Recovery_Ramdis.img and flash it. Luck.
Mannan Qamar said:
I do have instructions over there but cause you asked I will tell.
Extract the Update.zip the large file. In it you will have an Update.app. Now serach for Huawei Update Extractor on XDA and Download it. Run the application and navigate to Update.app. Select it and in settings of Extractor uncheck the first option. Now extract Recovery_Ramdis.img and flash it. Luck.
Click to expand...
Click to collapse
Thank you so much! Now the phone is working again, I'm only having trouble flashing magisk (it doesn't show up among the apps) but i guess i can live without it for now...
Have you got a paypal or something? I wanna buy you a coffe, it seems the least I can do to repay your kindness and patience!
Bonny96 said:
Thank you so much! Now the phone is working again, I'm only having trouble flashing magisk (it doesn't show up among the apps) but i guess i can live without it for now...
Have you got a paypal or something? I wanna buy you a coffe, it seems the least I can do to repay your kindness and patience!
Click to expand...
Click to collapse
Really there is no need for that. I did what anyone would do. Your thanks is enough.
Can you tell me what version you flashed. What TWRP did you use and what was the message after flashing.Now regarding Magisk, I am gonna assume you flashed the ZIP and the Magisk Manager app didn't show up, correct? To solve that just download Magisk Manager v6.0.1 and install the apk.
If that's not the issue then download any Root Checker app to see if device is rooted. Although I guess you need Magisk Manager to validate Root access. So just install Magisk Manager and let me know what it says. If it says device is unrooted then you probably need to flash Magisk again.
P.S: I don't have a PayPal. Not yet available in my country.
Mannan Qamar said:
Really there is no need for that. I did what anyone would do. Your thanks is enough.
Can you tell me what version you flashed. What TWRP did you use and what was the message after flashing.Now regarding Magisk, I am gonna assume you flashed the ZIP and the Magisk Manager app didn't show up, correct? To solve that just download Magisk Manager v6.0.1 and install the apk.
If that's not the issue then download any Root Checker app to see if device is rooted. Although I guess you need Magisk Manager to validate Root access. So just install Magisk Manager and let me know what it says. If it says device is unrooted then you probably need to flash Magisk again.
P.S: I don't have a PayPal. Not yet available in my country.
Click to expand...
Click to collapse
I really appreciate your kindness,
I flashed the latest version of magisk available from the official thread using the same TWRP from before (king of mezi TWRP from elemental rom thread) and it looked fine... Yes, the app didn't show up, I will try with the manager and I'll let you know.
[edit] I installed the manager and turns out it actually worked the first time and I'm already rooted!
Thank you again, you've been wonderful!
Glad to help.
If you tried flashing Pixel Experience or any other custom ROM and lost your mobile network then flash this stock ROM.
Downloads:
ROM
FLASH ALL COMMAND
Instructions:
1. Download both files
2. Extract them in the Minimum ADB folder
3. Run the Flash-All.bat file.
4. Wait till its all done and reboot.
It should be working now :highfive:
**NOTE: This is for the Indian Version Only, don't flash this on any other device**
**Also i'm not responsible for anything, flash it on your own risk**
Had this issue since October last year. Didn't try to fix it because i upgraded. Trying it now. Will share feedback shortly.
Also if anyone is confused about the instructions, Read below.
1. Download both files,
2. Copy the "Flash-All.bat" file to C:\Program Files (x86)\Minimal ADB and Fastboot (Or your default installation directory for ADB)
3. Extract the ZIP file directly to the same folder.
4. Reboot the phone into the bootloader and plug it in.
5. Double click and run "Flash-All.bat"
6. Reboot after done.
[Update] - It works! Thank you!
So, does this mean - Indian Moto X4 (XT1900-2) does not support any custom ROM? As missing SIM functionality is a huge disappointment.
This must be flashed before flashing custom roms. This updates the firmware to the latest stock firmware so that phone becomes custom rom compatible.
Ok, got it
ROM Link is not working, can you please re upload it?
Manish54 said:
If you tried flashing Pixel Experience or any other custom ROM and lost your mobile network then flash this stock ROM.
Downloads:
ROM
FLASH ALL COMMAND
Instructions:
1. Download both files
2. Extract them in the Minimum ADB folder
3. Run the Flash-All.bat file.
4. Wait till its all done and reboot.
It should be working now :highfive:
**NOTE: This is for the Indian Version Only, don't flash this on any other device**
**Also i'm not responsible for anything, flash it on your own risk**
Click to expand...
Click to collapse
Instead of this, Can I flash firmware of second post in Official Lineage OS thread?
pbu80 said:
ROM Link is not working, can you please re upload it?
Click to expand...
Click to collapse
Working for me.
pothaiahgari omkar said:
Instead of this, Can I flash firmware of second post in Official Lineage OS thread?
Click to expand...
Click to collapse
No idea
pothaiahgari omkar said:
Instead of this, Can I flash firmware of second post in Official Lineage OS thread?
Click to expand...
Click to collapse
That looks like a old firmware. You can flash the firmware in this thread.
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??
nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11
walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64
Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.
Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.
Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash