DISCLAIMER
Not taking responsibility if it goes wrong
Do not use this procedure if you have a higher bootloader version than Cx182, it will brick your device.
I made this because I didn't want to flash oreo -02 firmware only -03, and I know that both have the same bootloader and modem. I advice against this if you have -02, you should do it the proper way.
This guide works for both XT1635-02 and XT1635-03.
This was tested using XT1635-03 on a custom ROM.
Make sure you have adb enabled on your device.
You should not loose any data, and you will be able to boot back to the system without any problem.
This will update to the following:
Bootloader Version: Cx182
Modem Version: M8953_10238.63.04.83R
FSG Version: FSG-8953-04.118
Download Oreo stock signed image:
NOTE: This image is for XT1635-02, but for 2 times (from Marshmallow to Nougat, and from Nougat to Oreo I've used a XT1635-02 image on my XT1635-03 and it still works)
Link in this thread
[url]https://drive.google.com/file/d/1J3A1tXgYBt16-DLzbn1YnwboVHKq37D4/view[/URL]
[url]https://mega.nz/#!K8NznAYY!5iwmWn8_BmoQrQF8-LPPykffrpglp5VZWxS6_We-njk[/URL]
Unzip the downloaded zip into your adb folder.
Boot device into Bootloader/Fastboot Mode.
If you are not sure what are you doing, ask here or read fastboot documentation before flashing anything
Commands: Credits to @allrightlite
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
EDIT: OP says only use on -03. cool.
You are telling folks they can turn a 7 ROM into an 8 ROM.
1.82 bl is Oreo.
Ill advised if you flash to N ROM (?).
Ill advised to flash bl separate from ROM (?).
(EDIT - I really don't know to what extent you can mix them but may well be more than I know.)
KrisM22 said:
1.82 bl is Oreo. Ill advised if you flash to N ROM. Ill advised to flash bl separate from ROM.
Click to expand...
Click to collapse
You mean N stock right?
My suggestion is - don't mix bl and rom unless you really know what you are doing and are ready to deal with a brick situation. These are not legos. a different bl provides a different environment . A ROM expects/needs a certain environment to run correctly. The only okay mix I know of is Alberto97's 8.1AOSP which runs on a 7.x bl 0 but it was especially built to do so.
EDIT: I really don't know to what extent you can mix the contents of a 7 and 8 ROM.(stock and/or custom)
KrisM22 said:
My suggestion is - don't mix bl and rom unless you really know what you are doing and are ready to deal with a brick situation. These are not legos. a different bl provides a different environment . A ROM expects/needs a certain environment to run correctly. The only okay mix I know of is Alberto97's 8.1AOSP which runs on a 7.x bl 0 but it was especially built to do so.
Click to expand...
Click to collapse
You mean not to mix bl with stock ROMs, custom ones is fine right?
Fábio Ferreira said:
You mean not to mix bl with stock ROMs, custom ones is fine right?
Click to expand...
Click to collapse
nope. - you're mixing 7 and 8 ROM guts.
This will update to the following:
Bootloader Version: Cx182
Modem Version: M8953_10238.63.04.83R
FSG Version: FSG-8953-04.118
Click to expand...
Click to collapse
Okay! So if you look at the above posts you will see that twice I have taken the time to warn you against doing what you want to do. That's all I can do. The responsibility for what you do is yours alone. ANY ROM relies heavily on its support system/bl/environment. Change that and you will have an unknown situation. Stock ROMs, custom ROMs , soaktests, all need something to stand on that is designed for them.
Think physical building architecture for a minute. if I take a 100 story building off its foundation and drop it on another foundation, How likely do you think it would be to remain as strong as before? or just fall over?
going through re-editing this stuff and just saying again:
EDIT: I really don't know to what extent you can mix the contents of a 7 and 8 ROM.
Keep cool, that's working. Special thanks goes to Alberto97, who has tell us in his thread what we need. But thanks to TeamMax, too. He has confirmed, that we don't need OEM.img for custom ROMs (it's unused, so for treble/vendor). So, the 5 commands are working fine. Have tested here and no problems. Now on Android 9.0 thanks Treble
KrisM22 said:
Okay! So if you look at the above posts you will see that twice I have taken the time to warn you against doing what you want to do. That's all I can do. The responsibility for what you do is yours alone. ANY ROM relies heavily on its support system/bl/environment. Change that and you will have an unknown situation. Stock ROMs, custom ROMs , soaktests, all need something to stand on that is designed for them.
Think physical building architecture for a minute. if I take a 100 story building off its foundation and drop it on another foundation, How likely do you think it would be to remain as strong as before? or just fall over?
Click to expand...
Click to collapse
But I don't understand, the only thing I'm not flashing is system, which custom ROMs replace.
We already take a building and change foundations.
Fábio Ferreira said:
But I don't understand, the only thing I'm not flashing is system, which custom ROMs replace.
We already take a building and change foundations.
Click to expand...
Click to collapse
You are mixing the guts of N and O ROMs.
Fábio Ferreira said:
You mean not to mix bl with stock ROMs, custom ones is fine right?
Click to expand...
Click to collapse
No
stock or custom use the same bl etc. The difference is between 7 and 8. You are taking stuff from 8 and putting it into a ROM built around 7.
again, just:
EDIT: I really don't know to what extent you can mix the contents of a 7 and 8 ROM.
OP edited OP to say only use on -03 , so, cool. You can sum up my comments in this thread to say "if you're on -02, know what you're doing and be able to unbrick yourself" - ignore the rest.
I think OP knows what te is doing for -03 (and maybe for -02 as well...! )
Apparently you are able to mix 7 and 8 - I just don't want to go on record for having said it and have someone brick their phone. But that is the direction of treble. Enjoy.
Related
Hello Guys, i am here to share FF OS 1.4 build for ZTE Open
Much more stable than previous build.
Code:
[b]fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash cache ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img[/b]
Link(updated)(22-09-14)
Thank you, I build fos myself and use your boot.img to flash my phone and now it boots well.
Could you explain which changes you have made to boot.img (and from which version)?
sekun said:
Thank you, I build fos myself and use your boot.img to flash my phone and now it boots well.
Could you explain which changes you have made to boot.img (and from which version)?
Click to expand...
Click to collapse
Which version you have compiled?
I didn't modified any boot.img
It was modified by someone else.
One More Question:
Did you ZTE Open hangs most of the times?
LinuxHolic said:
Which version you have compiled?
I didn't modified any boot.img
It was modified by someone else.
One More Question:
Did you ZTE Open hangs most of the times?
Click to expand...
Click to collapse
First I built from 1.1B02 to 1.3 and modified boot image according to this method [1] and made these modifications [2].
Next, built from 1.3 to 1.4 and used your boot img.
I've just tested 1.4 a little for now, and my zte open never hangs on 1.3.
[1] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[2] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
sekun said:
First I built from 1.1B02 to 1.3 and modified boot image according to this method [1] and made these modifications [2].
Next, built from 1.3 to 1.4 and used your boot img.
I've just tested 1.4 a little for now, and my zte open never hangs on 1.3.
[1] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[2] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
Click to expand...
Click to collapse
How did you installed 1.3 on you phone?
An .img files?
I wasn't able to install it on my phone. Tried with 3 different boot.img files
Thanks
LinuxHolic said:
How did you installed 1.3 on you phone?
An .img files?
I wasn't able to install it on my phone. Tried with 3 different boot.img files
Thanks
Click to expand...
Click to collapse
I've followed this tutorial [1] (built from 1.1 to 1.3, set BRANCH=v1.3 instead of v1.2 in the script) and have modified boot.img according to the 2 links [2] and [3] mentioned before.
[1] rowehl.com/blog/2013/10/24/firefoxos-1-dot-2-on-zte-open
[2] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[3] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
sekun said:
I've followed this tutorial [1] (built from 1.1 to 1.3, set BRANCH=v1.3 instead of v1.2 in the script) and have modified boot.img according to the 2 links [2] and [3] mentioned before.
[1] rowehl.com/blog/2013/10/24/firefoxos-1-dot-2-on-zte-open
[2] pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/#comment-1749
[3] bugzilla.mozilla.org/show_bug.cgi?id=965180#c9
Click to expand...
Click to collapse
Can you give me the boot.img that you modified?
Thanks
LinuxHolic said:
Can you give me the boot.img that you modified?
Thanks
Click to expand...
Click to collapse
filebin.net/hfalt65z3o/boot-1.3.0.img
Works great!!!
LinuxHolic said:
Hello Guys, i am here to share FF OS 1.4 build for ZTE Open
This will work for all those who are having Bootloop issues while flashing Custom firmware
This build is compiled by someone so i take no credit for that. I'm just here to share that
Code:
[b]fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash cache ramdisk.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img[/b]
Click to expand...
Click to collapse
This image works great. At least as far as I have tested. Much snappier than 1.1, 1.2.
Could I ask (beg) you to compile a japanese version?
I'm giving a talk in Japan on JavaScript in about a month and I was hoping to show off this device.
I'd really appreciate it if you could do this for me.
I believe the information contained here may be helpful: ... 8 / I cannot post links as a newbie...
The comments at this bugzilla page explain how to add japanese text @ bugzilla mozilla org show_bug.cgi ? id=933252#c16
thank you so much!
asdf2a3 said:
This image works great. At least as far as I have tested. Much snappier than 1.1, 1.2.
Could I ask (beg) you to compile a japanese version?
I'm giving a talk in Japan on JavaScript in about a month and I was hoping to show off this device.
I'd really appreciate it if you could do this for me.
I believe the information contained here may be helpful: ... 8 / I cannot post links as a newbie...
The comments at this bugzilla page explain how to add japanese text @ bugzilla mozilla org show_bug.cgi ? id=933252#c16
thank you so much!
Click to expand...
Click to collapse
As i've already mentioned earlier that this build has been compiled by someone(not me)
Whoops
LinuxHolic said:
As i've already mentioned earlier that this build has been compiled by someone(not me)
Click to expand...
Click to collapse
:crying: My bad. I didn't read before I installed..
Could you point me in the right direction?
My own builds of b2g have been less than successful. The closest I've gotten was to get a unstable versions installed.
you may want to have a look at neuralassembly . blogspot . com (can't post links....) its in japanese and he explains how to build a japanese enabled version for Samsung Galaxy S3, you'll have to adapt that but i guess at least you will be able to read it without google translate
hope this is helpful to you.
linr76 said:
you may want to have a look at neuralassembly . blogspot . com (can't post links....) its in japanese and he explains how to build a japanese enabled version for Samsung Galaxy S3, you'll have to adapt that but i guess at least you will be able to read it without google translate
hope this is helpful to you.
Click to expand...
Click to collapse
Thanks, I can and have compiled for this device. The tricky parts are finding a version that is stable enough to use. And getting all of the right proprietary drivers. And there may be some other unknown(s) that I'm messing up. The version you've posted tells me the git version so that's 1 of the 2 major foreseeable obstacles.
Call me a conspiracy nut, but what's the big deal with closed source drivers on cell phones? So what if the public finds out how to write to a screen or send communication over the radio. Technically we can already write to small lcd screens with adrino parts and communicate over the air with shortwave. And yet every single phone out there is closed, even the Maemo was partially closed. I don't see any legitimate reason for this other than some giant conspiracy by large corporations. Either the ma bells don't want us using the air-waves for free or the governments of the world don't want us not being tracked. And I suppose it's a lot of both.
well, it was just an example on how to get japanese working on the device, not really a cookbook.
for the building i guess you should follow the instructions on Mozilla developer network.
they have a page dedicated to the ZTE Open.
mine will arrive maybe next week, so i cant really build yet, since the phone has to be connected for the build to proceed.
and i am fine with it being in english, even though my native language is german, but i always change the language to english (must be an IT thing with me)
linr76 said:
well, it was just an example on how to get japanese working on the device, not really a cookbook.
for the building i guess you should follow the instructions on Mozilla developer network.
they have a page dedicated to the ZTE Open.
mine will arrive maybe next week, so i cant really build yet, since the phone has to be connected for the build to proceed.
and i am fine with it being in english, even though my native language is german, but i always change the language to english (must be an IT thing with me)
Click to expand...
Click to collapse
There are some official ZTE versions out there with fastboot disabled. B06 is safe. But be careful to read about other user experiences before you upgrade.
asdf2a3 said:
There are some official ZTE versions out there with fastboot disabled. B06 is safe. But be careful to read about other user experiences before you upgrade.
Click to expand...
Click to collapse
As far as I am aware when ZTE first released the 1.1 Firefox OS update through their website it was released without fastboot enabled. This however was a mistake, so they took those files down and re-uploaded newly compiled versions of the same Firefox OS 1.1 but with fastboot enabled. :good:
thanks for the warnings, i have read about that and i think it is even stated on the MDN.
i think because of this there is also a lot of misunderstandings, as i do not think you need a hacked boot.img if your phone has fastboot enabled already.
well i guess i will find out when it arrives, as i want to upgrade at least to 1.3
this wont be my daily use device, i just want to see where FXOS stands and is developing to.
if i like it i guess i would go for a more mid-level device (like a Alcatel Fire E/S or the new not yet announced higher spec ZTE)
my only gripe here is that sony doesnt seem to move on and release their FXOS phone, and the support with Alcatel was a bit patchy so far from what you read.
it would be nice if all of the FXOS phones had the possibility to be used as Dev-devices.
Deleted
Hi,
Thanks for this release. Is all the device working ? I mean GPS, WiFi etc...
I'm new to Firefox OS, and I would like to install the latest fully functional release
Anyway thanks for your great work !
Nitroman70 said:
Hi,
Thanks for this release. Is all the device working ? I mean GPS, WiFi etc...
I'm new to Firefox OS, and I would like to install the latest fully functional release
Anyway thanks for your great work !
Click to expand...
Click to collapse
I am not the creator/uploader of this post but I have installed it multiple times and know a little bit about this kind of thing It is a pre-release version so it is far from being complete or "stable"... I would not suggest using this build for daily use as there is no guarentee everything will work correctly even if it does for someone else, but for testing and/or restoring a bricked (broken phone) it is perfect.
[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
Got my Mix yesterday - set it up last night.
I was apprehensive with everyone talking about different ROMs, unlock codes, rooting, throttling, etc etc.
Mine came with MIUI Global 8.0.7.0.0 with Google appstore already installed. The packaging was sealed.
Downloaded apps at about 3.5 megabytes per second (as shown by the notification bar connection speed widget).
SMS works fine.
Calling works fine.
I even get 4G on O2 (in the UK). I live in Leeds so it's one of those cities where O2 are using 1800 mhz for 4G as well as the usual 800 Mhz which Mix can't do.
All my banking apps work fine.
I've got Nova Prime on it. MIUI has some nice tweaks built in. There's no bloatware on it at all.
Also, compared to the Lumia 950XL I had for a year, it's about 2 mm wider and that's about it.
I've been using an S7 Edge for the last couple of months and set up wise, there's no difference. Everything just works out of the box. No flashing, tweaking, rooting etc.
Fingerprint reader is faster than S7. It can also wake the phone as well. Double tap to wake is there too.
If I didn't know better, I'd say this was just any other Android phone bought in the UK, instead of a China import where people have been talking about flashing EU ROM etc and having other issues.
Funniest thing about it is that once you get over the initial WOW factor of the screen, you just get used to it. It's only when you look at other phones you think, haha your phone looks like it's from the 1970s.
Only thing I haven't really tried is the camera. Pretty sure it won't be up to 950XL or S7 standards but I've installed Snap Camera so let's see if it's half decent.
Great phone so far.
Just depends if your happy with vendor rom and no updates as long as you own the phone, I removed vendor rom and have had 2 updates since with like yourself no issues.
Where did you get your Mix? Mine also had that ROM but I flashed the China ROM since it wasn't getting OTA updates. Your Mix might be fine for now but I hear the spyware/malware stuff works like a trojan horse, I'd recommend flashing now, your bootloader is probably already unlocked. Just install the China ROM and skip the EU ROM or rooting if you want.
slitz123 said:
Where did you get your Mix? Mine also had that ROM but I flashed the China ROM since it wasn't getting OTA updates. Your Mix might be fine for now but I hear the spyware/malware stuff works like a trojan horse, I'd recommend flashing now, your bootloader is probably already unlocked. Just install the China ROM and skip the EU ROM or rooting if you want.
Click to expand...
Click to collapse
Agreed and I skipped rooting and EU (for now)
jazz452 said:
Agreed and I skipped rooting and EU (for now)
Click to expand...
Click to collapse
I'm really confused now.
I thought my Global 8.0.7 ROM was the 'normal' China ROM.
Is it a VENDOR ROM? Is it obvious because it came with Gapps installed?
Also, how do you know this has malware on it? Kaspersky doesn't find anything on it.
Anyway, I better flash the official China ROM now - the EU one sounds more suitable (since I'm in the UK) but it's not official is it so ANYTHING might be in that.
Thanks.
Hid Sugiura said:
I'm really confused now.
I thought my Global 8.0.7 ROM was the 'normal' China ROM.
Is it a VENDOR ROM? Is it obvious because it came with Gapps installed?
Also, how do you know this has malware on it? Kaspersky doesn't find anything on it.
Anyway, I better flash the official China ROM now - the EU one sounds more suitable (since I'm in the UK) but it's not official is it so ANYTHING might be in that.
Thanks.
Click to expand...
Click to collapse
Don't think they do put spyware on never found anything, no updates is the killer for me, they probably aren't allowed to mess with official ROM and keep the same numbers plus updates would probably mess up Google apps.
I went with stable China as it has English language and didn't want to TWRP at the moment. OTA updates aren't available on EU ROM ATM although first custom ROM is out with OTA based on EU ROM see forum. I installed Google apps from the mi store with no issues once all permissions were granted.
jazz452 said:
Don't think they do put spyware on never found anything, no updates is the killer for me
I went with stable China as it has English language and didn't want to TWRP at the moment. OTA updates aren't available on EU ROM ATM although first custom ROM is out with OTA based on EU ROM see forum.
Click to expand...
Click to collapse
OK, so this ROM I have is some sort of weird ROM put on by Gearbest (where I got it from). Who developed it and has it been confirmed that there is malware on it?
Reading up on it, I can see how to install: China stable V8.0.12.0.MAHCNDI
Download ROM. Copy to root directory of phone.
Go into Settings/updates/reboot to recovery mode and install the Zip.
Is that right? Since it's not an update, do I have to wipe the phone in recovery?
I'm a bit loathed to do it cos:
a) This is a rather expensive phone from China which makes it a bit hairy. I've flashed ROMs on cheaper devices before but...
b) It's currently running dandy.. everything is fast and smooth and everything WORKS but this thing about spyware and malware I find worrying (even tho I can't seem to find any proof of this.) But yeah, lack of updates is a problem.
Does anyone have a link on an idiots guide on how to go from Vendor to China Stable Official?
There's a thread on this forum about this but it kinda says you need TWRP and Root etc.
If I put China Stable, do I need to root it to put on Gapps?
Will China ROM stop my banking apps to work?
jazz452 said:
Don't think they do put spyware on never found anything, no updates is the killer for me, they probably aren't allowed to mess with official ROM and keep the same numbers plus updates would probably mess up Google apps.
I went with stable China as it has English language and didn't want to TWRP at the moment. OTA updates aren't available on EU ROM ATM although first custom ROM is out with OTA based on EU ROM see forum. I installed Google apps from the mi store with no issues once all permissions were granted.
Click to expand...
Click to collapse
Another question... since I have the Vendor ROM on it, does it mean that my bootloader is unlocked already?
Hid Sugiura said:
Another question... since I have the Vendor ROM on it, does it mean that my bootloader is unlocked already?
Click to expand...
Click to collapse
The updater app has been disabled on this ROM, there is a guide (under guides) how to flash from vendor rom to China stable mine came from gearbest and was unlocked. No need TWRP or root. No rush your home won't set on fire with vendor rom just read a few times till you are sure of what you are doing. mi flash is used for flashing ROMs with xiaomi.
Hid Sugiura said:
I'm really confused now.
I thought my Global 8.0.7 ROM was the 'normal' China ROM.
Is it a VENDOR ROM? Is it obvious because it came with Gapps installed?
Also, how do you know this has malware on it? Kaspersky doesn't find anything on it.
Anyway, I better flash the official China ROM now - the EU one sounds more suitable (since I'm in the UK) but it's not official is it so ANYTHING might be in that.
Thanks.
Click to expand...
Click to collapse
If you use Malwarebytes on the Vendor ROM, it flags the MIUI Notes app as "Agent.downloader.Trojan". Check it out! I didn't even sign in on the phone until I could get the EU ROM flashed. Not saying that Vendors deliberately inject their ROMS with malware. Just saying there can always be that one hacker dude who is compiling these ROMS for the vendors.
From what it looks like, most vendors are given a flashable signed zip file that can be flashed using official recovery, the file is named MIUI Global 8.0.7.0 or 8.0.8.0 (Mine came with 8.0.8.0).
So when most vendors receive stock, guess they unbox it, flash this zip file most probably via the official MIUI recovery, run the diagnostic test and if everything passes, they box the item and ship it out. Most vendors may have staff who are trained to copy the flashable zip file via MTP, boot stock recovery and flash! It doesn't take a genius to do that and its done it 5 minutes.
I am on the EU ROM. Even though unofficial, these MIUI EU ROMS have been there since the beginning of MIUI and no one ever had any reliability issues with the EU ROM. The ROM has no bloatware and comes with GAPPS pre-installed.
---------- Post added at 02:37 AM ---------- Previous post was at 02:19 AM ----------
Hid Sugiura said:
Another question... since I have the Vendor ROM on it, does it mean that my bootloader is unlocked already?
Click to expand...
Click to collapse
Not necessarily! Mine came with a vendor ROM and bootloader locked. This is why I assume that Vendors are given a Signed ROM file which can be flashed using the official MI Recovery. I don' t think every vendor has the skills to unlock bootloader and flash a vendor ROM after installing a custom recovery. Its a time consuming process.
If they already have a Signed customized ROM file that can be flashed using the official recovery, its as easy as copying the ZIP file to the phone and flashing it via the recovery. Takes hardly 5-10minutes.
Thank you very much for your replies - much appreciated.
As soon as I read your post, I did Malwarebytes and that found nothing - apart from saying I should switch off NFC so that's a little more comforting. As I said, Kaspersky hasn't found anything.
So, the China Stable is the ONLY official ROM there is - the vendor and EU ones are equally unofficial and neither have OTA updates.
OK more questions:
Some people say China Stable is the way to go cos of the updates.
1) Is the bloatware that bad? Can't I just ignore it? haha
2) Does it need rooting to put Gapps on it? Rooting is a no no for me cos certain apps won't run with it.
If I go the EU ROM, cos of the built in Gapps, can it be updated without wiping every time?
Thanks for all your help.
Hid Sugiura said:
Thank you very much for your replies - much appreciated.
As soon as I read your post, I did Malwarebytes and that found nothing - apart from saying I should switch off NFC so that's a little more comforting. As I said, Kaspersky hasn't found anything.
So, the China Stable is the ONLY official ROM there is - the vendor and EU ones are equally unofficial and neither have OTA updates.
OK more questions:
Some people say China Stable is the way to go cos of the updates.
1) Is the bloatware that bad? Can't I just ignore it? haha
2) Does it need rooting to put Gapps on it? Rooting is a no no for me cos certain apps won't run with it.
If I go the EU ROM, cos of the built in Gapps, can it be updated without wiping every time?
Thanks for all your help.
Click to expand...
Click to collapse
You should go with EU rom, or custom rom which is starting to appear now. The worst rom to go for imo is the China one, and I find it a bit strange some people want to go for that due to OTA update. OTA update is not such a big deal, you get more update with EU or custom rom and no, you don't need to wipe data, it is so simple and easy to do manual update.
If you are totally beginner then maybe you find the OTA update easier, but at the same time if you are totally beginner you will find it hard to get china rom to become stable and usable. By the way the new custom rom also has OTA update, if you really want that.
So in short, I see almost no reason to stay in China rom, unless you find selecting zip file and flashing rom "too hard". But it's really quite easy to learn.
Mine from gearbest has unlocked bootloader but slightly different number than yours 8.0.8, it's easy to check from fastboot plenty of threads on here.
---------- Post added at 11:29 AM ---------- Previous post was at 11:22 AM ----------
satishp said:
If you use Malwarebytes on the Vendor ROM, it flags the MIUI Notes app as "Agent.downloader.Trojan". Check it out! I didn't even sign in on the phone until I could get the EU ROM flashed. Not saying that Vendors deliberately inject their ROMS with malware. Just saying there can always be that one hacker dude who is compiling these ROMS for the vendors.
From what it looks like, most vendors are given a flashable signed zip file that can be flashed using official recovery, the file is named MIUI Global 8.0.7.0 or 8.0.8.0 (Mine came with 8.0.8.0).
So when most vendors receive stock, guess they unbox it, flash this zip file most probably via the official MIUI recovery, run the diagnostic test and if everything passes, they box the item and ship it out. Most vendors may have staff who are trained to copy the flashable zip file via MTP, boot stock recovery and flash! It doesn't take a genius to do that and its done it 5 minutes.
I am on the EU ROM. Even though unofficial, these MIUI EU ROMS have been there since the beginning of MIUI and no one ever had any reliability issues with the EU ROM. The ROM has no bloatware and comes with GAPPS pre-installed.
---------- Post added at 02:37 AM ---------- Previous post was at 02:19 AM ----------
Not necessarily! Mine came with a vendor ROM and bootloader locked. This is why I assume that Vendors are given a Signed ROM file which can be flashed using the official MI Recovery. I don' t think every vendor has the skills to unlock bootloader and flash a vendor ROM after installing a custom recovery. Its a time consuming process.
If they already have a Signed customized ROM file that can be flashed using the official recovery, its as easy as copying the ZIP file to the phone and flashing it via the recovery. Takes hardly 5-10minutes.
Click to expand...
Click to collapse
Xiaomi hate vendor ROMs that's why they lock bootloader, no one wants a bad name with spyware installed on their phones.
RIGHT! Thank you again for all your replies and advice.
I'm gonna do:
1) Find out if it's unlocked and get that done if necessary.
2) Install the EU one knowing now that updates don't wipe the phone.
My fear is that somewhere in between having an unlocked bootloader (which I might have already) and having the EU ROM, I lose the ability to use my Barclays Banking apps. I definitely know that it won't work with root but I also know that unlocked bootloaders and custom ROMs aren't the same as being rooted.
However, the fear of this vendor ROM being a security hazard gives me the heebie jeebies so I'll follow the kind advice given and put on the EU ROM.
Thanks for now!
Hid Sugiura said:
RIGHT! Thank you again for all your replies and advice.
I'm gonna do:
1) Find out if it's unlocked and get that done if necessary.
2) Install the EU one knowing now that updates don't wipe the phone.
My fear is that somewhere in between having an unlocked bootloader (which I might have already) and having the EU ROM, I lose the ability to use my Barclays Banking apps. I definitely know that it won't work with root but I also know that unlocked bootloaders and custom ROMs aren't the same as being rooted.
However, the fear of this vendor ROM being a security hazard gives me the heebie jeebies so I'll follow the kind advice given and put on the EU ROM.
Thanks for now!
Click to expand...
Click to collapse
Good luck! Just to let you know i am on EU ROM with bootloader unlocked and rooted, i can still use Paypal and HSBC Banking apps. I don't use Barclays so can't comment on that.
OK I'm following the guide on XDA under Guides: Guide: Flash Global/China ROM.
I've checked that the bootloader is unlocked - which it is.
I've done point 7:
copy the latest xiaomi.eu rom zip to your device (which you can see in your computer's explorer as a device)
But when I use the command to get the phone into TWRP, the screen is unresponsive so I can't Swipe to Unlock.
I've waited for minutes as suggested on other sites but to no avail.
Any ideas?
Thanks in advance.
Hid Sugiura said:
OK I'm following the guide on XDA under Guides: Guide: Flash Global/China ROM.
I've checked that the bootloader is unlocked - which it is.
I've done point 7:
copy the latest xiaomi.eu rom zip to your device (which you can see in your computer's explorer as a device)
But when I use the command to get the phone into TWRP, the screen is unresponsive so I can't Swipe to Unlock.
I've waited for minutes as suggested on other sites but to no avail.
Any ideas?
Thanks in advance.
Click to expand...
Click to collapse
If you don't root remember to flash dm-verify before you boot phone or will boot loop. TWRP unresponsive is known have a search
Again, thanks for helping me.
So, found the right TWRP for my phone. For others having the same non-responsive screen, don't install the TWRP that has RC1 or RC2 EU in the file name.
Thanks to the guy above for telling me to install dm-verity before rebooting. I would never have known that.
It installed - but there was a slight strangeness.
I expected the phone to be totally wiped and set to default but everything was as I had set it.
I checked the About Phone and it is now MIUI 8.2 by xiaomi.eu 6.12.29 Beta.
Everything works and is set up as before when I was on Vendor Rom.
Am I safer now?
Hid Sugiura said:
Again, thanks for helping me.
So, found the right TWRP for my phone. For others having the same non-responsive screen, don't install the TWRP that has RC1 or RC2 EU in the file name.
Thanks to the guy above for telling me to install dm-verity before rebooting. I would never have known that.
It installed - but there was a slight strangeness.
I expected the phone to be totally wiped and set to default but everything was as I had set it.
I checked the About Phone and it is now MIUI 8.2 by xiaomi.eu 6.12.29 Beta.
Everything works and is set up as before when I was on Vendor Rom.
Am I safer now?
Click to expand...
Click to collapse
It was fate TWRP failed, could of been in a whole heap trouble, although not to the point of brick
Good stuff that you managed to get the EU ROM on. You didn't actually need to install TWRP if you just wanted to flash the China ROM though, EDL mode with the stock image on full clear would've been fine but don't worry about it. Gearbest get their stock from other suppliers who are the ones that put the vendor ROM on apparently, but I can't confirm that.
A good order to do things if you've identified you have a vendor ROM would be:
Flash the China ROM with EDL mode with the flash tool set to Flash all (using other options will keep your apps and settings on the vendor ROM but I have no idea if that means it'll keep any trojans or spyware installed)
Boot up the phone and set it up
If you're happy with the China ROM then call it a day then optionally use the Google Installer v2 from the Xiaomi forums if you need GApps (you may have to tinker with the GApps permissions if some things aren't syncing right).
If not then you could flash twrp-3.0.2-0-rc2-eu-lithium.img, flash on the EU ROM and optionally SuperSU for root and also optionally Xposed, then enjoy a preconfigured GApps with no Chinese apps that you aren't too likely to use plus extra languages!
If you are rooted then I'd recommend adding the following line in your build.prop to enable the Camera2 API:
Code:
persist.camera.HAL3.enabled=1
Personally, I'm still waiting on a CM port though, MIUI is too aggressive in killing my apps even though I have like 4.2 GB of RAM free even with all the relevant power settings, app settings, app locks, dev settings etc off. Android Wear functions better after disabling those power settings at least, I sat there scratching my head for a while wondering why the heck my watch wasn't showing any notifications.
Hi, I recently bought an used OnePlus 8 Pro and it was already updated to Android 11. After repairing it, I discovered that it's not possible to run TWRP on this firmware version.
Couldn't I just go ahead and downgrade the OS in order to run TWRP on it or is it basically impossible like on the latest Samsung Galaxy S-series devices?
Would be glad if someone could answer me that question. I kinda tried to boot into twrp because I was too quick to read the thread but it just caused my device to run into Qualcomm Emegency Mode.
What do you need twrp for? If it's just to root and almost everything else... It can be done via other means.
sensui123 said:
What do you need twrp for? If it's just to root and almost everything else... It can be done via other means.
Click to expand...
Click to collapse
I also counter the same problem, i just want to use twrp to flash another rom. Do you have any solution? I have search the forum but i didnot find something useful.
freeman1007 said:
I also counter the same problem, i just want to use twrp to flash another rom. Do you have any solution? I have search the forum but i didnot find something useful.
Click to expand...
Click to collapse
Hmmmm the way I've seen a lot of custom roms... They're installed/flashed partition by partition in bootloader via fastboot.....I guess if you have to use twrp to flash the entire rom you do need to downgrade to os 10.
sensui123 said:
Hmmmm the way I've seen a lot of custom roms... They're installed/flashed partition by partition in bootloader via fastboot.....I guess if you have to use twrp to flash the entire rom you do need to downgrade to os 10.
Click to expand...
Click to collapse
Thank you for your response. i think i just did not catch up the latest progress. Would you please help me find the instruction about how to flash rom in the new way you mentioned ? thank you so much.
And i still have the same question , is it necessary for us to downgrade to android 10 and then start flashing rom.
Look at the roms in the subforum here:
OnePlus 8 Pro ROMs, Kernels, Recoveries, & Other
Improve your OnePlus 8 Pro 's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
I just looked at some popular ones like Pixel experience and Lineage and they're both flashed in this way. Look at the opening post where the instructions are... Seems like Pixel Experience there's a batch file that flashes the partitions but it's essentially done this way without twrp.
sensui123 said:
Look at the roms in the subforum here:
OnePlus 8 Pro ROMs, Kernels, Recoveries, & Other
Improve your OnePlus 8 Pro 's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
I just looked at some popular ones like Pixel experience and Lineage and they're both flashed in this way. Look at the opening post where the instructions are... Seems like Pixel Experience there's a batch file that flashes the partitions but it's essentially done this way without twrp.
Click to expand...
Click to collapse
thank you for your reply, I already tried to flash pixel experience, i followed the install guide but failed to flash its recovery file.
Install PixelExperience on instantnoodlep - PixelExperience Wiki
Install PixelExperience on instantnoodlep - PixelExperience Wiki
wiki.pixelexperience.org
Because it requires installing rom from recovery, so I get stuck here.
The problem is the device enters crash dump mode when switched to recovery mode. I guess the reason is that my p8pro is in andriod 11 before i flash recovery. now the device can enter android 11 normally but the recovery don't function. So I am here to ask is it necessary for me to downgrade to android 10 to solve the problem.
sensui123 said:
Look at the roms in the subforum here:
OnePlus 8 Pro ROMs, Kernels, Recoveries, & Other
Improve your OnePlus 8 Pro 's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
I just looked at some popular ones like Pixel experience and Lineage and they're both flashed in this way. Look at the opening post where the instructions are... Seems like Pixel Experience there's a batch file that flashes the partitions but it's essentially done this way without twrp.
Click to expand...
Click to collapse
Thank you for your reply, it help me a lot. i have already flash my device lineage os . Regarding the problem i mentioned in my last reply, it seems the install guide is for android 10. As for android 11 , i think it needs a payload dumper to extract all files and flash them one by one.
MichalPlays said:
Hi, I recently bought an used OnePlus 8 Pro and it was already updated to Android 11. After repairing it, I discovered that it's not possible to run TWRP on this firmware version.
Couldn't I just go ahead and downgrade the OS in order to run TWRP on it or is it basically impossible like on the latest Samsung Galaxy S-series devices?
Would be glad if someone could answer me that question. I kinda tried to boot into twrp because I was too quick to read the thread but it just caused my device to run into Qualcomm Emegency Mode.
Click to expand...
Click to collapse
I think the answer depends why do you need twrp. If you just want to flash a rom like me, you can find a custom rom supporting android 11,for example lineage os and you can flash all files it requires without twrp.
If you want to flash a android 10 rom or you just want to flash twrp , i don't know how, maybe you should downgrade.