2012-03-02
Huawei U8800 + the Atradius 2.3 Chinese generic version.
Fix
optimized auto focus
Download
http://www.huaweidevice.com/tcpsdow...category=cn&flay=software&downloadID=NDEyNTc=
=====================================================================
HUAWEI U8800Pro Android 2.3 V100R001C00B552CUSTC10D001 Russia(other aeras may not use this version)
Version: -- ( V100R001C00B552CUSTC10D001 )
http://www.huaweidevice.com/tcpsdownload/downLoadCenter?category=&flay=software&downloadID=NDQ0MTM=
well....in build.prop i can see that this B565 was built BEFORE the B552.....there's something wrong.
anyone tried?
Works fine. Root ant CWM works too. New Music2.apk
B552 had a separate facebook/twitter apps, this new has again the MultiSNS
On my B565 i have two icon of Youtube on application screen.
Only me have this bug ?
Anyone know if this version pop up the image folder booting in pink screen?
Thanks!
Yes, also this new base B565 has the pink screen mode, so you can copy the boot.img (stock kernel) and with the dsixda kitchen you can extract the system.img from UPDATE.APP (the major G update from step folders).
Today I did this procedure and my custom rom is working fine.
Of course there is always the problem of sdcard mounting (sometimes the external sd is mounted correctly, otherwise I need to reboot and then the external sd in mounted) and the problem of multitouch when you turn on the display after the lockscreen (look at this video and test by yourself if your device has the same bug: http://www.youtube.com/watch?v=avSdW2V8TLg and http://www.youtube.com/watch?v=64NvbFJD3rs)
Does this rom have all languages except for keyboard?
Thanks Kalo86. I'll test it this week when i have one free day.
I installed this rom but tell me how to root it.And i see that i have 2 music applications.The old one and the newone.How to delete the old one?And youtube has 2 icons launching the same app youtube version 2.3.4
nicolassp said:
I installed this rom but tell me how to root it.And i see that i have 2 music applications.The old one and the newone.How to delete the old one?And youtube has 2 icons launching the same app youtube version 2.3.4
Click to expand...
Click to collapse
If you want to root this new base you have to copy the boot.img file putting your smartphone in pink screen mode: you have to shutdown and hold down VOL Up, VOL down and Power button. Now you can plug your USB-micro usb cable to your pc and there will appear a new window, containing the image folder. The boot.img file is inside the image folder, just copy this on your desktop. The second step is to extract the system.img from the UPDATE.APP file, the biggest one inside the zip of the official Huawei rom.
There is a nice tool, named Dsixda Kitchen which helps you in the next steps to obtain a good custom rom and with this kitchen you can apply root access to the boot.img.
I hope to have helped you, anyway Google and this special Forum are your "best friends", you'll find all information.
Regards,
kalo86
nicolassp said:
I installed this rom but tell me how to root it.And i see that i have 2 music applications.The old one and the newone.How to delete the old one?And youtube has 2 icons launching the same app youtube version 2.3.4
Click to expand...
Click to collapse
is this gonna work?:
1, download ROOT tools, there are links below. (DooMLoRD_v3_ROOT-zergRush-busybox-su.zip)
2, ensure that ADB drivers are correctly installed
3, turn on usb debugging in settings -> applications -> debugging. turn off fast boot option in settings -> applications
4, open dialer, type *#*#2846579#*#*, projectmenu, background settings, log setting, on, go back, open dump & log, turn on all options.
5 , on the PC run runme.bat
6, wait for the complete restart.
7, OK Congratulations root complete!
http://forum.xda-developers.com/attachment.php?attachmentid=800333&d=1322674313
TUPAC_RIP said:
is this gonna work?:
1, download ROOT tools, there are links below. (DooMLoRD_v3_ROOT-zergRush-busybox-su.zip)
2, ensure that ADB drivers are correctly installed
3, turn on usb debugging in settings -> applications -> debugging. turn off fast boot option in settings -> applications
4, open dialer, type *#*#2846579#*#*, projectmenu, background settings, log setting, on, go back, open dump & log, turn on all options.
5 , on the PC run runme.bat
6, wait for the complete restart.
7, OK Congratulations root complete!
http://forum.xda-developers.com/attachment.php?attachmentid=800333&d=1322674313
Click to expand...
Click to collapse
1, download ROOT tools, there are links below. (DooMLoRD_v3_ROOT-zergRush-busybox-su.zip)
2, ensure that ADB drivers are correctly installed
3, turn on usb debugging in settings -> applications -> debugging. turn off fast boot option in settings -> applications
4, open dialer, type *#*#2846579#*#*, projectmenu, background settings, log setting, on, go back, open dump & log, turn on all options,
reboot phone
5 , on the PC run runme.bat
6, wait for the complete restart.
7, OK Congratulations root complete!
this way works for me
nicolassp said:
Does this rom have all languages except for keyboard?
Click to expand...
Click to collapse
yeah
the doomloard tool does not work with the 565 version.i tested by doing all the steps but it said it cannot fix permissions and push the applications in the phone.(φίλε ακαλε το δοκίμασες σε αυτην την έκδοση και έπαιξε?το δοκίμασα αλλά τίποτα..)
nicolassp said:
the doomloard tool does not work with the 565 version.i tested by doing all the steps but it said it cannot fix permissions and push the applications in the phone.(φίλε ακαλε το δοκίμασες σε αυτην την έκδοση και έπαιξε?το δοκίμασα αλλά τίποτα..)
Click to expand...
Click to collapse
yes, does not work with the 565 version
http://forum.xda-developers.com/showthread.php?t=1321582
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
So that means that the 565 version is not rootable?I think that someone told that this rom is rootable though.I anybody knows the way and delight me i would be pleased.
nicolassp said:
the doomloard tool does not work with the 565 version.i tested by doing all the steps but it said it cannot fix permissions and push the applications in the phone.(φίλε ακαλε το δοκίμασες σε αυτην την έκδοση και έπαιξε?το δοκίμασα αλλά τίποτα..)
Click to expand...
Click to collapse
Tested by me as well and it doesn't work with this ROM.
(Περιμενω με αγωνια παγωτο σαντουιτς)
TUPAC_RIP said:
Tested by me as well and it doesn't work with this ROM.
(Περιμενω με αγωνια παγωτο σαντουιτς)
Click to expand...
Click to collapse
yes, not rootable, but when you use "BOOT.IMG" from older version, it works. I allways use geno's kernel. Rooted, working
if anyone has tried to root 565 version with the replacement of boot.img link with the file and some steps i would be gratefull..but only if tested with this version because some people reported that after the replacement the device cannot turn on at all..(κι εγώ περιμένω το ics αλλά βλέπω κίνηση μόνο στο απλό και όχι στο προ..)
Related
Here We Go:
After Playing With the Fonts & bla bla bla. on my HD2 MDJ's CyanogenMod7 v2.5 & 2.6, i got my arabic RTL working good and Words are connected in sms, browser, apps, etc..
Download:
RTL PATCH ( attached )
FONTS ( attached )
Arabic Keyboard ( from the market )
Instruction:
1: Extract rtl-auto-patcher-0.0.4.zip
2: open the AndroidRTLPatcher.exe
3: Connect your Android Phone via USB
4: Click on TEST CONNECTION
5: if you using MDJ's CyanogenMod7 tick the same as the picture down:
PIC attached ( RTL Screenshot )
6: Click on Go Go Go !
7: wait until it asks to reboot the phone click yes and you done With RTL Patch.
Fonts:
1: extract the fonts & copy to your Memory Card
2: use ROOT EXPLORER (download from Market )
3: Copy the two fonts into the system/fonts and replace them.
4: download Keyboard of your choice from the market & Restart The phone>
5: you Dont you must have the same font as shown down
Screen shot attached ( arabic on HD2 )
Feel Free to ask..
wail alqasmee
nobody hav tested o tryd it.. cmon guys. i need ur rply if it works
would try it, but google prevents syrians from downloading programs from their site.
and I'm too lazy/wary of using routers and such, plus, using them in the past has put me through some troubles so...
I'll see if there's a workaround or something
Hey i've uploaded THE RTL Patch on Mediafire you can download the attached file to get the link
can we get Hebrew by same way???
i dont know how to.. but if you hebrew font from using PC font rename the font to DroidSansHebrew and replace it and check... if not than try with another font..
Hey Guys Guess WIth the RTL Patch i tested with the same uploaded fonts on
HD2 CoreDroid DHD V1
And arabic is working fine on it. connected letters..
thanks, I tried it but somehow the program doesn't find my phone
do I need the SDK for that or what?
I haven't got it yet because I don't want to go installing pointless programs on my PC. plus I can't download the SDK from Google's because of the block >.>
great work keep it up
this is funny, but when I manually added your font in the fonts library, it solved most of my problems :S
thanks
many many thanks for this
but i have an issue here,
the patch detects the phone & build without the type, i choose NAND as my rom manually, the patch starts to the point that it stops with error, something about it cant replace the files coz they are in use, says to try from recover mode, rebooted and tried from CWM but it also failed to apply the patch.
so i replaced the fonts manually, rebooted, arabic letters is connected with some letters not showing the right way, and of course no RTL
is there a solution ? i could live without RTL, just want all the letters to show the right way
can you check if HTC SYNC is open , otherwise close it and try again , that's work for me
aymen_ben_ammar said:
can you check if HTC SYNC is open , otherwise close it and try again , that's work for me
Click to expand...
Click to collapse
of course HTC Sync is off
everything works fine, to the point of the patcher starts " Patching Device " , it works for a couple of seconds then it fails
it says " File transfer Failed Because The System is in use it is recommended to start your phone in recovery and try again "
i tried patching from clockwork recovery mode with no luck
thanks anyway, i managed to solve it manually on my own
The RTL patcher in this post is really old.
I've since created a newer version with broader compatibility and better device detection: See here.
so here is the new edition with uk kernel, basically pretty much the same as before with correct sensor drivers now.
Changelog v1.3 (Android v2.2.1 edition) Download nandroid image here or mirror
- xavwanted's libOMX and MediaGallery.apk which seems to fix HD recording and playback
- Riley600's interactive governor fix
- callwaiting fix
- kousik's mount-o typo fix
- Mioze7Ae move /oc to /system/oc
- bootanim by helmi666
- Email.apk replacement
Changelog v1.2b (Android v2.2.1 edition) Download patch here
- fixes problems with callwaiting functionality.
Changelog v1.2a (Android v2.2.1 edition) Download nandroid image here
- 720P recording fix
- re-added old MediaGallery as Camera app requires it.
- there can be possible hickups with mediascanning (so you know)If you do see many FC's its a symptom of not having done factory reset, so this should indicate whether you need to do it or not.
Changelog v1.2 (Android v2.2.1 edition) Download nandroid image here
- fixed mediascanner issue
- removed old mediagallery (not supported) , now only Gallery3D available.
- removed VoiceCommands app, cpu intensive and taking much storage.
Note, due to the bug in mediascanner and decoding and on top ext2sd support, quadrant benchmarks drastically drops when ext2 is enabled, if the sdcard is not a class6 or higher.. but media decoding bug alone caused incorrect reportings, so dont be surprised when you test now.
Its a full nandroid for new and existing users. if you're using 1.1+ you do not need to WIPE settings, just restore nandroid and reboot, signatures will be recalculated and bootup takes maybe little more, but it works fine.
Patch update Changelog v1.1b (Android v2.2.1 edition) Download patch here
- HDMI added to settings menu, let me know how it works (not tested)
- different proximity sensor module (tested with z-devicetester seems better)
- facebook fix still included.
- Support for loading overclock module at startup.
- apps2ext partition support , will mount at startup if a 2nd partition is found.
its not advanced, so you need ext2/ext3 partition for now.
NOTE: Patches goes into /OpenRecovery/updates and is applied in openrecovery menu "apply update".
Changelog v1.1a (Android v2.2.1 edition) Download nandroid v1.1a link
- Based on 2.2.1 milestone framework leak
- Sync facebook is working
- Lockscreen is new (Blur like)
- see this link for framework theme's.
Changelog v1.1 (Android v2.2 edition) Download v1.1 link
- fixed: OCR camera function currently FC (crash) (Mobireader.apk added)
- fixed: Contacts apk will be replaced in next update.
- fixed: HDMI through media player
- fixed: /mnt/sdcard mount issue
If you want stock korean 2.2 with just english language and working sensors, download this nandroid dump, if you will probably need the 1.1 including recovery.apk to install this the easy way.
but else follow instructions in my other releases, and put nandroid backup into the /nandroid/openrecovery folder and restore using OpenRecovery.
See this post, if you wish to restore a stock rom, or to enable apps2sd filesystem on sdcard
Install instructions:
Make sure sdcard is visible, when you get to step 6 of instructions, or it all fails, same with restore..
A: users with stock 2.1 can proceed to step 1 in instructions.
B: users with stock SBF korean 2.2 rom , need to flash stock 2.1 and goto step 1
C: Users with 1.1+ of rom with OpenRecovery , can skip WIPE and factory reset, and a restore of the new nandroid backup included in the download link, and goto step 8 (and skip step 9 for factory reset)
root it (SuperOneClick ) - included with zip
install OpenRecovery , use included apk.
reboot phone once
copy the folder "nandroid" to root directory of your sdcard.
Make sure sdcard is not attached to pc using "mass storage share" to pc.
Run OpenRecovery app and "install Recovery".
Press Boot recovery
restore the backup "stock22xxxx"
wipe / factory reset in OpenRecovery
reboot
Issues reported by users in v1.2a:
- Radio FM volume cannot change.
- MediaGallery does not do videoplayback
Issues reported by users in v1.0:
- Radio FM volume cannot change.
- Sync account option for facebook / Twitter is not added in settings when account is configured.
- Camera language not going to change (its korean app, so not support for other langs)
- LEDS do work, its sensors that makes them go off/on (no need to report this anymore)
STATEMENT:
Please don't keep asking the following question directed to me, public or via PM;
- Can you include language XXXXXXXX .
Answer: NO
- Can you teach me how to do custom roms
Answer: NO
- will you include RTL for hebrew
Answer: NO
- will you make other roms like cyanogen,htc etc..
Answer: NO
for new users unable to write in public forums, i cannot answer all your PM's personally, as that gets to be a quite a few per day and many monthly...i am not a support central for xt720 community..i simply don't have that kind of time available.
Dexter_nlb said:
if i press camera button here (1-2 sec) it opens?
media button (the small one becide the cam button?) ? yes i see its not doing any action
from what i read now, the known accelerator driver issue + led,hdmi is 2 majors, im not sure about other issues becides the extra languages which for some seem to cause issue..
the way the launcher works is a matter of taste (seeing like 20+ android devices)
- if you're coming from stock 2.1 there is differences and more functions, but if you tweaked alot maybe less features are here, like dalvik.
- rotation is a problem if you plan alot of games with acc. functionality..
- I personally dont experience problems, except the buttons which personally i would love to fix now..
I think overall there is a positive feel about the first working release.
Click to expand...
Click to collapse
I am still unable to sync with facebook contacts, anyone else?
-->settings ---> accounts add the facebook account successfully but then not in the accounts list and then contacts in phone do not sync.
Dexter_nlb said:
It seems that many not being experienced users, still try to install and here is the instruction for installing the rom.
Install instructions (based on korean sbf):
1. Install korean sbf (STSKT_N_79.33.50R) using RSDLite ( link here )
- boot your xt720 into bootloader (press power up while holding VOL+ + and shutter button during bootup)
- when RSDLite application on pc says "connected" , your ready to flash
- select the SBF
- press start
2a. Set language to english, set usb mode into Charge Only and USB debugging on in the Settings->Apllications->Development menu.
2b. root it (using SuperOneClick) - ( link here )
3. install OpenRecovery , follow instructions on ( http://bit.ly/gIPoXo ) files included (OpenRecovery & OpenRecovery.zip )
5. copy the folder "nandroid" to root directory of your sdcard.
6. boot into OpenRecovery (adb shell reboot openrecovery)
7. restore the backup "stock22" in openrecovery
8. wipe / factory reset in OpenRecovery
9. reboot
Download here
APK for easy installation and rebooting into OpenRecovery is in the works (based on previous CWM recovery app)
Click to expand...
Click to collapse
Added a rule for people who do not know how to use SuperOneClick
hellmonger said:
I am still unable to sync with facebook contacts, anyone else?
-->settings ---> accounts add the facebook account successfully but then not in the accounts list and then contacts in phone do not sync.
Click to expand...
Click to collapse
deleted.. i misunderstood the q here
hi there ! is it the final version of 2.2 or still in testing process?
nice job and thank you all...
FM RADIO also missing.....
@Dexter, thank you for contacts.apk. But how to install it? After replace in /system/app it's says - It's not installed, and when i try to install it - it says: I can't be installed.
For more issues: how about light sensor, that detects when you speak on your phone?
On 2.1 when you speak touchscreen goes off and you cant press it errorly.
Thank you very much.
FM RADIO also missing.....
Click to expand...
Click to collapse
That from 2.1
Facebook account missing.
Dexter_nlb said:
deleted.. i misunderstood the q here
Click to expand...
Click to collapse
After full flash and all instructions followed corectly i can boot into 2.2 without any problems.
i set up my account with google, go to the market, download "facebook for android" install is succesfull, i then go to ==> settings menu ==> Accounts menu, add account, choose facebook, am successfull at login in to facebook, return to accounts menu = Facebook account is not there.
And my phone contacts do not sync with facebook.
Thank you
And my phone contacts do not sync with facebook.
Click to expand...
Click to collapse
Did you set your FB freinds to sync in the FB app?
joe206hdi said:
Just flashed korean sbf ... maybe due to i´d used launcherpro in stock rom i can´t get into the rom background and apps are still there in korean rom.
going back to european rom and do a wipe/reset before flashing again the korean one...
later more
@dexter can´t we use universal androot instead of super one click
Click to expand...
Click to collapse
finally fixed it
1.flashed again german stock rom sbf file
2. do a factory reset in stock recovery
3. flash korean sbf file while reboot unplug the usb - when rsd lite shows massage "reboot manualy" - phone is still in reboot ( when i don´t do this it won´t work ?!?!
4. go on with dexters xt720-2.zip nandroid procedure
@dexter unversalandroot won´t work - just tested before superoneclick - adb install worked fine but no root....
-------
bugs
camera options are still in english - i´m on german
more within tomorrow
Joe - thanks great work
anyone else get a Installation error Unknown reason -18 when trying to install battle bears. i loved that game. worked on 2.1 even tho it said it didnt
3rdstring said:
Did you set your FB freinds to sync in the FB app?
Click to expand...
Click to collapse
Is yours working?
Where are those settings please? not in the accounts menu cause facebook is not there, i am able to add it from that menu but then it disapeares, when i clic add again facebook option is availible but just clics to nowhere and returns to the add account page....
smurfb said:
I been following this thread, very intresting! I thought, would it not be possible to use the kernel from XT720 (2.1), beause its the same kernel version? Or is too much changed?
Click to expand...
Click to collapse
ok, i went back once more and flashed just 2.1 kernels from uk rom, and indeed all sensors work now.. but,but,but... no 3D accelerator is currently activated, so screen lags really alot..
but yes, with that kernel it still boot up fine, with a few changes.
edit: update - ITS WORKING!!! running with 2.1 uk release kernel , its working now, all sensors activated..
Where are those settings please? not in the accounts menu cause facebook is not there, i am able to add it from that menu but then it disapeares, when i clic add again facebook option is availible but just clics to nowhere and returns to the add account page....
Click to expand...
Click to collapse
In the facebook app if you tap on "Facebook" at the top you go to the page to navigate to news feeds, friends, etc. If you hit your options button there there is a settings screen that includes preferences for how contacts are sync'd.
HTH
3rdstring said:
In the facebook app if you tap on "Facebook" at the top you go to the page to navigate to news feeds, friends, etc. If you hit your options button there there is a settings screen that includes preferences for how contacts are sync'd.
HTH
Click to expand...
Click to collapse
Yes i saw those settings, unfortunately they have no effect or bearing on the accounts.
I believe this is a bug, yet no one has confirmed or denied being able to reproduce it.
All sensors activated!!
I think smurfb deserve a little thanks, for pushing the request/idea just to try loading the old uk kernel once more, so i did and this time i fixed the problems with loading the old kernel and lib/bin required, its not much and most (2.2) korean state is kept intact..
ill do some testing after the new nandroid backup and start uploading v1.0
Dexter_nlb said:
I think smurfb deserve a little thanks, for pushing the request/idea just to try loading the old uk kernel once more, so i did and this time i fixed the problems with loading the old kernel and lib/bin required, its not much and most (2.2) korean state is kept intact..
ill do some testing after the new nandroid backup and start uploading v1.0
Click to expand...
Click to collapse
does that mean u activated the 3d accelerator. and would replacing the settings.apk from 2.2 from motoroi enable hdmi since the settings arnt even there anymore in this version the hdmi libs and everything is still there jus no hdmi.
khalpowers said:
other way u can install terminal su on your phone after flash to froyo..then u can su from there...
Click to expand...
Click to collapse
IT WORKED!!!!!!!!!!!!!!! THANK YOU SO MUCH!!!!!!!!!!!
AND DEXTER!!!!!!!!! THANK YOU!!!!!!!!!!! You're amazing.
Ill be up to any testing you guys need me to do
easye420 said:
does that mean u activated the 3d accelerator. and would replacing the settings.apk from 2.2 from motoroi enable hdmi since the settings arnt even there anymore in this version the hdmi libs and everything is still there jus no hdmi.
Click to expand...
Click to collapse
yes, 3d is fully functional now. I dont think it will work, but i will find a way to add the functionality..
the korean rom has only english, which im sure not many appreciate, although camera as one is used from that rom so only english is enabled.
but i will for sure try and get HDMI working..
I got FMRadio app added, does it help?
Thank you so much for making this, Dexter. We are hungry of froyo, asking for more. But you deserve to take a break
which languages does it have?
I will install it soon. can someone upload a video of it?
How To Install Flyme OS 6.1.0.0G Global Stable on Chinese Pro 6 Plus devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a Guide to install the Global ROM Flyme OS 6Global on the Meizu Pro 6 Plus Chinese version.
Note: This is also a way to install Any custom ROM made in the future. If someone wanna Customize the ROM( Integrate Xposed and other stuff) feell free to do it.
What does this mean:
Meizu released two versions of the Pro 6 Plus, a chineese version (A) for china and an International version (G) for the devices sold in other countries (International). If you bought your Pro 6 plus from official meizu store on your country, it will come with the G version, but if you bought it from Aliexpress or any other Chinese store, you will buy a Chinese version, some seller may send you the international version if you are lucky but the majoritynot.
Global / International version:
No bloatware, chinese apps..
Multilanguage ( all languages available)
Stock apps optimized for International use (Weather....)
seems to be smoother and faster than the chinese version.
Disclaimer
*** As always - Read everything carefully and Flash on our own risk! ***
I can and will not take any responsibility for bricked phones or lost data.What do we need:
Rooted Device
FlashFire app from playstore
Flyme 6.1.0.0G _Global_Stable_Pro 6 Plus for Flashfire
Instructions:
Its recomnended to back up your data (Titanium backup, your fotos etc)in case of disaster.
Update to a newer version:
Copy the new version to Internal storage
Open Flashfire, click on the + button and choose Flash Zip / OTA
Select the Downloaded ROM from the file explorer and select Mount system read write.
Now you will see a screen with all the actions that will be done, select the action called Reboot and un-thick the option Preserve recovery, leave Normal selected.
Finally click on FLASH and wait until the process ends.
Enjoy...
Note: In case of any problems and you want a clean installation, add the wipe action from the + button before flashing. But it should not be needed.
Note: it seems to be a problem with supersu if you don't wipe data before update. so to avoid problems, you should wipe before flash.
If you want to keep your apps and data, you should make a data (data partition only) backup from flashfire before updating. then wipe and update, follow instructions to root and to have super su. After that you can use flshfire to restore data backup (only data partition) .
also you can use kingroot but its not compatible with flashfire.
If you already updated, you can use titanium backup(give root permision from system root in settings, security root permissions)make a backup of your apps and then follow the guide below How to go back to stock chinese ROM in case of disaster, after that follow the instruction of new installation and when you have the that done, you can rstore your apps with titanium backup.
[/LIST]
First Time Installation:
Root:
Go to Meizu page and create and account. Enter a valid email as its needed to activate the account. if you already have an account, just skip this step.
Now go to Settings on your device and Select Meizu account, Log in with your new created account.
Go back and select Fingerprint & security , then select Root permission, scroll down and confirm. The device will reboot. Now its rooted but i recommend installing supersu because the built int root some times has failed for me.
Install SuperSu from playstore, open it and select Update su binary, choose Normal. wait until it finishes and reboot.
Now you have Root
Note: if you dont have Google Playstore, open meizu app store and search for supersu.
Install ROM:
Root your device
Install Flashfire from Playstore
Download This modified Flyme 6.1.0.0G _Global_Stable_Pro 6 Plus for Flashfire
[*]Copy the downloaded ROM to Internal storage
[*]Open Flashfire, give root permissions and click on the + button,
[*]Select Wipe and then ok
[*]Click again on the + button and choose Flash Zip / OTA
[*]Select the Downloaded ROM from the file explorer and select Mount system read write. See these screens for more information:
[*]Now you will see a screen with all the actions that will be done, select the action called Reboot and unthick the option Preserve recovery, leave Normal selected.
[*]Finally click on FLASH and wait until the process ends.
[*]Enjoy...
Optional:
You can Install gapps from flashfire along with the rom, just select Flash zip/ota and select Gapps zip, this way it will be installed after rom. Or you can use Google Installer which you can find in meizu appstore after reboot.
Note: For future updates, do not update the device from the Updates app included as it will donload the Gobal version of Flyme but it will fail because your device is still a chinese version.
How to go back to stock chinese ROM in case of disaster:
Download the latest version of chinese Flyme from: [url]http://www.flyme.cn/firmwarelist-101.html#3
Turn off the device (hold power button until it turns off.
Hold Volume + button and power button at the same time until the phone vibrates. it will enter recovery mode.
Connect your device to your PC by usb, you will have access to a folder named Recovery. Copy the update.zip to this folder and wait for it to finish.
Go back to the device and select the options Upgrade System and Clear data.
Hit Start and wait until it finishes.
Older Versions:
Flyme OS 6.7.4.11_beta_Global_Pro 6 Plus for Flashfire
Thanks for this tutorial! It was very detailed and easy to follow.
In the future when I want to perform an update, do I need to go through FlashFire in order for it to work correctly on a Chinese version of the device? Also, where do you download the "G" versions of the beta firmware? I know their next release is a stable version and I know it comes out after the A version; just wondering where you go to download it. Cheers!
ShaolinMilk said:
Thanks for this tutorial! It was very detailed and easy to follow.
In the future when I want to perform an update, do I need to go through FlashFire in order for it to work correctly on a Chinese version of the device? Also, where do you download the "G" versions of the beta firmware? I know their next release is a stable version and I know it comes out after the A version; just wondering where you go to download it. Cheers!
Click to expand...
Click to collapse
For future update you can download the stable from http://www.flymeos.com/firmwarelist?modelId=46&type=1. Or the betas from flyme forum. You will have to edit the installation script to be able to flash through flashfire and don't get error and avoid firmware problems. Anyway i will upload the future updates modified for flashfire.
bihariel said:
For future update you can download the stable from http://www.flymeos.com/firmwarelist?modelId=46&type=1. Or the betas from flyme forum. You will have to edit the installation script to be able to flash through flashfire and don't get error and avoid firmware problems. Anyway i will upload the future updates modified for flashfire.
Click to expand...
Click to collapse
Thanks!!! I tried looking through the zip file to see what you changed, but didn't know which file to go into. I assume it's not as easy as opening up a file in notepad and changing some data on there.
ShaolinMilk said:
Thanks!!! I tried looking through the zip file to see what you changed, but didn't know which file to go into. I assume it's not as easy as opening up a file in notepad and changing some data on there.
Click to expand...
Click to collapse
Its not hard to do but yes, i you dont know what are you doing is dangerous. Dont worry i will upload future updates.
bihariel said:
Its not hard to do but yes, i you dont know what are you doing is dangerous. Dont worry i will upload future updates.
Click to expand...
Click to collapse
Thanks dude! Looking forward to it.
im surprised at how small the response to this phone is....just stumbled upon it while looking for a new device.
this is rather off-topic but this seems to be the most active thread
thanks for that.
i have question,i can flash the Flyme 5.2.7.0G by this method?
@bihariel Hey I have a question for you. Have you ever experienced a sudden change in battery life out of nowhere? When I first installed this firmware, the battery was perfect. All of a sudden after charging my phone, the battery is draining at an unprecedented rate especially on standby. I charged the phone to 100%, disabled all notification/wifi/cellular network and left it on overnight to activate the battery calibration. The problem still exists however. It's draining about 1% every 2 minutes on standby which is ridiculous.
I'm just wondering if you ever encountered this issue before.
Sent from my PRO 6 Plus using XDA-Developers Legacy app
mr.mgmg said:
thanks for that.
i have question,i can flash the Flyme 5.2.7.0G by this method?
Click to expand...
Click to collapse
You can but you have to modify the script to avoid firmware files and recovery.img to be flashed, which would end in an installation abort,
ShaolinMilk said:
@bihariel Hey I have a question for you. Have you ever experienced a sudden change in battery life out of nowhere? When I first installed this firmware, the battery was perfect. All of a sudden after charging my phone, the battery is draining at an unprecedented rate especially on standby. I charged the phone to 100%, disabled all notification/wifi/cellular network and left it on overnight to activate the battery calibration. The problem still exists however. It's draining about 1% every 2 minutes on standby which is ridiculous.
I'm just wondering if you ever encountered this issue before.
Sent from my PRO 6 Plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not really, the battery is surprising me on this ROM. Maybe you sould use a battery monitoring app and see whats draining it. If not, do a factory reset and see if it still prsists.
bihariel said:
You can but you have to modify the script to avoid firmware files and recovery.img to be flashed, which would end in an installation abort,
Click to expand...
Click to collapse
so,how we can do that?
i think the 6.7.4.11_beta_Global no stable yet
u can edit the Flyme 5.2.7.0G?
bihariel said:
How To Install Flyme OS 6.7.4.11 Global on Chinese Pro 6 Plus
This is a Guide to install the Global ROM Flyme OS 6.7.4.11 on the Meizu Pro 6 Plus Chinese version.
Note: This is also a way to install Any custom ROM made in the future. If someone wanna Customize the ROM( Integrate Xposed and other stuff) feell free to do it.
What does this mean:
Meizu released two versions of the Pro 6 Plus, a chineese version (A) for china and an International version (G) for the devices sold in other countries (International). If you bought your Pro 6 plus from official meizu store on your country, it will come with the G version, but if you bought it from Aliexpress or any other Chinese store, you will buy a Chinese version, some seller may send you the international version if you are lucky but the majoritynot.
Global / International version:
No bloatware, chinese apps..
Multilanguage ( all languages available)
Stock apps optimized for International use (Weather....)
seems to be smoother and faster than the chinese version.
Disclaimer
*** As always - Read everything carefully and Flash on our own risk! ***
I can and will not take any responsibility for bricked phones or lost data.What do we need:
Rooted Device
FlashFire app from playstore
Flyme OS 6.7.4.11_beta_Global_Pro 6 Plus for Flashfire
Instructions:
Its recomnended to back up your data (Titanium backup, your fotos etc)in case of disaster.
Root:
Go to Meizu page and create and account. Enter a valid email as its needed to activate the account. if you already have an account, just skip this step.
Now go to Settings on your device and Select Meizu account, Log in with your new created account.
Go back and select Fingerprint & security , then select Root permission, scroll down and confirm. The device will reboot. Now its rooted but i recommend installing supersu because the built int root some times has failed for me.
Install SuperSu from playstore, open it and select Update su binary, choose Normal. wait until it finishes and reboot.
Now you have Root
Note: if you dont have Google Playstore, open meizu app store and search for supersu.
Install ROM:
Root your device
Install Flashfire from Playstore
Download This modified Flyme OS 6.7.4.11_beta_Global_Pro 6 Plus
Copy the downloaded ROM to Internal storage
Open Flashfire, give root permissions and click on the + button,
Select Wipe and then ok
Click again on the + button and choose Flash Zip / OTA
Select the Downloaded ROM from the file explorer and select Mount system read write. See these screens for more information:
Now you will see a screen with all the actions that will be done, select the action called Reboot and unthick the option Preserve recovery, leave Normal selected.
Finally click on FLASH and wait until the process ends.
Enjoy...
Optional:
You can Install gapps from flashfire along with the rom, just select Flash zip/ota and select Gapps zip, this way it will be installed after rom. Or you can use Google Installer which you can find in meizu appstore after reboot.
Note: For future updates, do not update the device from the Updates app included as it will donload the Gobal version of Flyme but it will fail because your device is still a chinese version.
How to go back to stock chinese ROM in case of disaster:
Download the latest version of chinese Flyme from: http://www.flyme.cn/firmwarelist-101.html#3
Turn off the device (hold power button until it turns off.
Hold Volume + button and power button at the same time until the phone vibrates. it will enter recovery mode.
Connect your device to your PC by usb, you will have access to a folder named Recovery. Copy the update.zip to this folder and wait for it to finish.
Go back to the device and select the options Upgrade System and Clear data.
Hit Start and wait until it finishes.
Click to expand...
Click to collapse
Hello everyone, thanks a lot bihariel for this guide.
I have successfully installed the beta with flashfire and it's all ok!
Some people say flashfy is not a very safe method, what do you think? I'm not an expert.
However, I did not go to the flymex account synchronization, now I've installed the closed beta apps yesterday and it works perfectly well!
We wait for the stable then!
Can you explain how you modified the update for the future? Thanks so much.
Are Alternative Methods to Flashfire? Type ADB?
In Italy a seller on his blog posted this guide, but I could not install it:
"The tutorial for installing firmware G in the Asian Meizu Pro 6 Plus smartphone is really very simple and does not require solid modding basics, you just have to be careful about installing ADB drivers correctly.
Load the battery completely before you begin the procedure and save all your important data
On your PC or on a Cloud as you will need to make the full factory reset.
Prerequisites Preinstalling Firmware G in Meizu Pro 6 Plus:
1-Smartphone fully charged
2-Any antivirus and / or firewalls disabled
3-Driver ADB properly installed, restart your PC after installation!
4-Enabled Root permissions through Flyme account (Fingerprint and Security Menu)
5-USB Debug Mode Enabled in Developer Options (Accessibility Menu)
G Firmware Installation in Meizu Pro 6 Plus:
Decompress the Meizu_Pro6plus_Flyme 5.2.7.0G.zip archive and copy it to the root folder
Of Meizu Pro 6 Plus the file system-i.img
Decompress the archive adb_tool.zip and in the folder obtained we select the file
Cmd.exe to open the command window
Write in the command window:
Adb shell
We give Send and permission to ADB through the pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the shell @ Pro6Plus command window
WARNING: If the pop-up display does not appear, ADB drivers have not been installed correctly!
Write in the command window:
su
We give Send and permission of ADB SHELL root permissions through
The pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the command window the symbol #
WARNING: If the pop-up display does not appear, root permissions are disabled!
Write in the command window:
Dd if = / sdcard / system-i.img of / dev / block / platform / 155a0000.ufs / by-name / system
We give Enter, we will see the cursor blink, we do not touch anything until the flash procedure
The system will not be completed and the screenshot message below will appear
Meizu pro 6 plus 01
Disconnect the usb cable from the Meizu Pro 6 Plus and restart it by holding down the button
Power for a few seconds, the startup process will take a few minutes, do not alarm and we start booting.
When the terminal is started we go in
Settings> About phone> Storage> Factory data reset>
We see Factory reset and Format internal storage>
Select START RESET"
I put into google translate, if you want the original in italian language let me know.
mr.mgmg said:
so,how we can do that?
i think the 6.7.4.11_beta_Global no stable yet
u can edit the Flyme 5.2.7.0G?
Click to expand...
Click to collapse
I read in some chinese forum that we cant downgrade but...
Download the ROM 5.2.7.0G, open the zip and editthis file \META-INF\com\google\android\updater-script
You can use this picture as a guide, delete the red lines:
Tony72 said:
Hello everyone, thanks a lot bihariel for this guide.
I have successfully installed the beta with flashfire and it's all ok!
Some people say flashfy is not a very safe method, what do you think? I'm not an expert.
However, I did not go to the flymex account synchronization, now I've installed the closed beta apps yesterday and it works perfectly well!
We wait for the stable then!
Can you explain how you modified the update for the future? Thanks so much.
Are Alternative Methods to Flashfire? Type ADB?
In Italy a seller on his blog posted this guide, but I could not install it:
"The tutorial for installing firmware G in the Asian Meizu Pro 6 Plus smartphone is really very simple and does not require solid modding basics, you just have to be careful about installing ADB drivers correctly.
Load the battery completely before you begin the procedure and save all your important data
On your PC or on a Cloud as you will need to make the full factory reset.
Prerequisites Preinstalling Firmware G in Meizu Pro 6 Plus:
1-Smartphone fully charged
2-Any antivirus and / or firewalls disabled
3-Driver ADB properly installed, restart your PC after installation!
4-Enabled Root permissions through Flyme account (Fingerprint and Security Menu)
5-USB Debug Mode Enabled in Developer Options (Accessibility Menu)
G Firmware Installation in Meizu Pro 6 Plus:
Decompress the Meizu_Pro6plus_Flyme 5.2.7.0G.zip archive and copy it to the root folder
Of Meizu Pro 6 Plus the file system-i.img
Decompress the archive adb_tool.zip and in the folder obtained we select the file
Cmd.exe to open the command window
Write in the command window:
Adb shell
We give Send and permission to ADB through the pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the shell @ Pro6Plus command window
WARNING: If the pop-up display does not appear, ADB drivers have not been installed correctly!
Write in the command window:
su
We give Send and permission of ADB SHELL root permissions through
The pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the command window the symbol #
WARNING: If the pop-up display does not appear, root permissions are disabled!
Write in the command window:
Dd if = / sdcard / system-i.img of / dev / block / platform / 155a0000.ufs / by-name / system
We give Enter, we will see the cursor blink, we do not touch anything until the flash procedure
The system will not be completed and the screenshot message below will appear
Meizu pro 6 plus 01
Disconnect the usb cable from the Meizu Pro 6 Plus and restart it by holding down the button
Power for a few seconds, the startup process will take a few minutes, do not alarm and we start booting.
When the terminal is started we go in
Settings> About phone> Storage> Factory data reset>
We see Factory reset and Format internal storage>
Select START RESET"
I put into google translate, if you want the original in italian language let me know.
Click to expand...
Click to collapse
I can tell you that for now the safest method is flashfire because it install the ROM in same way that the Recovery does, that is: it wipes the system partition and installs the ROM with correct permissions.
The method you mention is more risky( to get a bootloop) because it overwrites the ROM files directly over the System partition with the OS still running on phone. This drives into a system hang freeze. of course you have to turn it of by holding power button until it restarts. Then you have to go recovery and do a factory reset if you get bootloop.
I tried this method before Flasfire but it gave me bootloop so then i used Flashfire because it do the same job that Recovery does.
About the modifications, its really simple. Just open \META-INF\com\google\androidupdater-script and delete all the lines in red in this picture (these lines check if your phone is Chinese version or global and update the firmware files.)
Also you can delete the files related to those lines just for safety (boot.img, recovery.img, logo.bin, ldfw, bootloader..)
bihariel said:
I can tell you that for now the safest method is flashfire because it install the ROM in same way that the Recovery does, that is: it wipes the system partition and installs the ROM with correct permissions.
The method you mention is more risky( to get a bootloop) because it overwrites the ROM files directly over the System partition with the OS still running on phone. This drives into a system hang freeze. of course you have to turn it of by holding power button until it restarts. Then you have to go recovery and do a factory reset if you get bootloop.
I tried this method before Flasfire but it gave me bootloop so then i used Flashfire because it do the same job that Recovery does.
About the modifications, its really simple. Just open \META-INF\com\google\androidupdater-script and delete all the lines in red in this picture (these lines check if your phone is Chinese version or global and update the firmware files.)
Also you can delete the files related to those lines just for safety (boot.img, recovery.img, logo.bin, ldfw, bootloader..)
Click to expand...
Click to collapse
Thanks a lot!, I'll read all as soon I could
BE Careful
Removed
bihariel said:
I read in some chinese forum that we cant downgrade but...
Download the ROM 5.2.7.0G, open the zip and editthis file \META-INF\com\google\android\updater-script
You can use this picture as a guide, delete the red lines:
Click to expand...
Click to collapse
i flashed the 6.7.4.11 but i have problem when i open the front camrera and close the camrea not open again
now i want back to the 5.2.7.0G but when i want edit the script is Different about your picture.
u can edit the just script and upload and then i will add to zip
mr.mgmg said:
i flashed the 6.7.4.11 but i have problem when i open the front camrera and close the camrea not open again
now i want back to the 5.2.7.0G but when i want edit the script is Different about your picture.
u can edit the just script and upload and then i will add to zip
Click to expand...
Click to collapse
Salam,
The camera bug is weird, i don't have that bug, i open the camera ( front and back) many times and it works perfectly, maybe you changed something in camera setting ( erasing camera app data should help)
Anyway, the script is exactly the same as mine, its just you are using and editor with Arabic orientation.
Just use the app Notepad++( google it) and open it in English lang.
If not, just upload the script for me and i will edit it.
bihariel said:
Salam,
The camera bug is weird, i don't have that bug, i open the camera ( front and back) many times and it works perfectly, maybe you changed something in camera setting ( erasing camera app data should help)
Anyway, the script is exactly the same as mine, its just you are using and editor with Arabic orientation.
Just use the app Notepad++( google it) and open it in English lang.
If not, just upload the script for me and i will edit it.
Click to expand...
Click to collapse
ealaykum alssalam
thanks bro for help
i flashed the rom without change anything in script and its work
u know when the stable rom will out?
Hi guys!
I'm from Brazil and in the last two days I was reading about the Android 9 Pie update to our Mi A2.
I also read that today it started to roll out to India and some European countries.
For curiosity I installed ExpressVPN, conected to an Holland server and tried to download the OTA. It worked flawlessly.
I flashed via fastboot the Magisk patched boot of 10.0.1 build and got the Magisk also working flawlessly.
For the Camera2 API, I just edited the Magisk module and added the line "persist.vendor.camera.HAL3.enabled=1". Then I installed it through Magisk module screen. It also worked.
These are the steps I did:
1 - Obviously you will need to be on Android 9 Pie
(Try to download the OTA via VPN or wait to get it in your country)
2 - Download this file and extract it: https: // drive.google.com/open?id=1b9jRc1gZuPJatds5RkuCiJtuE7UCH5wh
(Remove the spaces)
3 - Turn your phone off and boot it in Fastboot Mode by pressing and holding Power + Vol Down and then, plug into the USB;
4 - In the extracted files, open the folder "Plataform Tools" and then open the Power Shell window.
(Inside this folder I added the original "boot.img" and the "patched_boot.img", all from 10.0.1 build)
5 - In PowerShell, just type: fastboot boot patched_boot.img
(It should boot with Magisk installed)
6 - Open Magisk, tap Install and chose to install directly. Reboot
(It will prevent Magisk get uninstalled after reboot)
7 - Transfer the files "Camera 2 API Enabler - Pie.zip" and "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk" to your phone memory.
8 - Open Magisk, go to "Modules", then tap the yellow buttom, search for the "Camera 2 API Enabler - Pie.zip" file and then install it. Reboot
9 - Once the phone rebooted, install the "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk".
(Go to Developer Options and unchek "camera.enable_micro", so you can use 5MP on front camera)
10 - Done! You're now on Android Pie with Magisk and Google Camera
Ricardo Guariento said:
Hi guys!
I'm from Brazil and in the last two days I was reading about the Android 9 Pie update to our Mi A2.
I also read that today it started to roll out to India and some European countries.
For curiosity I installed ExpressVPN, conected to an Holland server and tried to download the OTA. It worked flawlessly.
I flashed via fastboot the Magisk patched boot of 10.0.1 build and got the Magisk also working flawlessly.
For the Camera2 API, I just edited the Magisk module and added the line "persist.vendor.camera.HAL3.enabled=1". Then I installed it through Magisk module screen. It also worked.
These are the steps I did:
1 - Obviously you will need to be on Android 9 Pie
(Try to download the OTA via VPN or wait to get it in your country)
2 - Download this file and extract it: https: // drive.google.com/open?id=1b9jRc1gZuPJatds5RkuCiJtuE7UCH5wh
(Remove the spaces)
3 - Turn your phone off and boot it in Fastboot Mode by pressing and holding Power + Vol Down and then, plug into the USB;
4 - In the extracted files, open the folder "Plataform Tools" and then open the Power Shell window.
(Inside this folder I added the original "boot.img" and the "patched_boot.img", all from 10.0.1 build)
5 - In PowerShell, just type: fastboot boot patched_boot.img
(It should boot with Magisk installed)
6 - Open Magisk, tap Install and chose to install directly. Reboot
(It will prevent Magisk get uninstalled after reboot)
7 - Transfer the files "Camera 2 API Enabler - Pie.zip" and "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk" to your phone memory.
8 - Open Magisk, go to "Modules", then tap the yellow buttom, search for the "Camera 2 API Enabler - Pie.zip" file and then install it. Reboot
9 - Once the phone rebooted, install the "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk".
(Frontal camera will only work with 3MP)
10 - Done! You're now on Android Pie with Magisk and Google Camera
Click to expand...
Click to collapse
I downloaded ExpressVPN and changed to Holland, I still don't get the update.
Yepi69 said:
I downloaded ExpressVPN and changed to Holland, I still don't get the update.
Click to expand...
Click to collapse
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Amigo, tem que ser Power Shell mesmo? Aqui me dá opção do Prompt de comando apenas.
OTA
After using this method can I update normally without VPN?
Ricardo Guariento said:
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Click to expand...
Click to collapse
Ricardo Guariento said:
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Click to expand...
Click to collapse
This one worked like a charm, it is downloading now.
Ricardo Guariento said:
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Click to expand...
Click to collapse
It worked flawlessly, damn you Brazilians and your ''Brasileirices'' kkkkk
Hmm After doing this, will I loose ota update?
Ricardo Guariento said:
I really don't know why I managed to get this in the first try.
Try to follow this (steps made by users that got it)
-Remove SIM card;
-Reset to factory state;
-Start the initial configuration;
-Choose Nederlands;
-Don't log-in in Google Account;
-Don't activate GPS when asked;
-Once phone starts, download ExpressVPN;
-Choose to use it as trial;
-Choose Holland/Nederlands server;
-Try the OTA.
Click to expand...
Click to collapse
Duude, big thanks to you, worked for me too. Only I used Nord VPN, as Express said that Trial is not available.
You've made my Day.
Works the download boot in reboot, bootlop 9 times, and starts and says "couldn't update".
Ricardo Guariento said:
Hi guys!
I'm from Brazil and in the last two days I was reading about the Android 9 Pie update to our Mi A2.
I also read that today it started to roll out to India and some European countries.
For curiosity I installed ExpressVPN, conected to an Holland server and tried to download the OTA. It worked flawlessly.
I flashed via fastboot the Magisk patched boot of 10.0.1 build and got the Magisk also working flawlessly.
For the Camera2 API, I just edited the Magisk module and added the line "persist.vendor.camera.HAL3.enabled=1". Then I installed it through Magisk module screen. It also worked.
These are the steps I did:
1 - Obviously you will need to be on Android 9 Pie
(Try to download the OTA via VPN or wait to get it in your country)
2 - Download this file and extract it: https: // drive.google.com/open?id=1b9jRc1gZuPJatds5RkuCiJtuE7UCH5wh
(Remove the spaces)
3 - Turn your phone off and boot it in Fastboot Mode by pressing and holding Power + Vol Down and then, plug into the USB;
4 - In the extracted files, open the folder "Plataform Tools" and then open the Power Shell window.
(Inside this folder I added the original "boot.img" and the "patched_boot.img", all from 10.0.1 build)
5 - In PowerShell, just type: fastboot boot patched_boot.img
(It should boot with Magisk installed)
6 - Open Magisk, tap Install and chose to install directly. Reboot
(It will prevent Magisk get uninstalled after reboot)
7 - Transfer the files "Camera 2 API Enabler - Pie.zip" and "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk" to your phone memory.
8 - Open Magisk, go to "Modules", then tap the yellow buttom, search for the "Camera 2 API Enabler - Pie.zip" file and then install it. Reboot
9 - Once the phone rebooted, install the "Google Camera - 5.1.018 Arnova8G2 8.3b1 (Pie).apk".
(Frontal camera will only work with 3MP)
10 - Done! You're now on Android Pie with Magisk and Google Camera
Click to expand...
Click to collapse
will my phone will get ota updates after unlocking bootloader and enabling camera2api ???
miillerjr said:
Amigo, tem que ser Power Shell mesmo? Aqui me dá opção do Prompt de comando apenas.
Click to expand...
Click to collapse
Pode ser, não tem problema.
RubenPCA said:
After using this method can I update normally without VPN?
Click to expand...
Click to collapse
I think so!
You just faked your region, the OTA file will be the same for everyone.
In my case, the phone was fully set up (with Google Account and all the stuffs) and I managed to get the OTA. It has no sign of a Netherlands-like phone at all.
ClownIndo said:
Hmm After doing this, will I loose ota update?
Click to expand...
Click to collapse
No, this is a legit OTA.
You will lose OTA if you screwed up with system partition.
If you install Magisk and use its modules, you still be able to get the OTA.
Hemant Dhillan said:
will my phone will get ota updates after unlocking bootloader and enabling camera2api ???
Click to expand...
Click to collapse
You still get the OTA with unlocked bootloader.
Follow the instructions on OP and you will enable Camera2 API without touch the system partition, so you will have no problem with future OTA's.
Does the ROM remain rooted after following this procedure?
Does rooting with magisk loses ota?
Without editing build prop and other stuffs
Using magisk modules only
bidhu said:
Does the ROM remain rooted after following this procedure?
Click to expand...
Click to collapse
Follow all the steps and you will be on Pie, with Magisk and GCam.
johnsci911 said:
Does rooting with magisk loses ota?
Without editing build prop and other stuffs
Using magisk modules only
Click to expand...
Click to collapse
If you use Magisk Modules you will be able to get OTA's.
do i need to have bootloader unlocked for this?
I got bored so I made a HavocOS guide. Enjoy!
I am not responsible for any bad things happening to your device/angry parents because YOU messed your phone up. If it somehow broke after you did this, it's not my problem.
oh yea also I didnt make the OS. this is just a guide.
Downloads in video description.
I wanted to make this quick and simple so here's a video:
----------------------------------------------------------
Written guide:
-
Pt. 0: quick prerequisites that i forgor to write before
-
consider reading through the guide before you do it
make sure oem unlocking is enabled on your phone. if you dont know how to do that uhh here's how:
1. go to settings
2. scroll down to about
3. tap the build number until it asks for your screen lock
4. go to system
5. go to developer options
6. enable oem unlocking.
7. if its grayed out its because your phone is cringe, sorry.
-
Pt. 1: Downloads
-
Download all of these files
Google USB driver Extract with 7z or WinRar.
Platform Tools Click "Download for Windows" and extract with 7z or WinRar.
Stock Firmware Extract with 7z or WinRar.
TWRP/Kernel Don't extract this.
HavocOS Don't extract this.
-
Pt. 2: Drivers
-
How to install Android drivers:
1. Put your phone in fastboot mode (turn off your phone and turn it back on with power button and vol down.)
2. Open Device Manager on your PC.
3. Click on the dropdown for "Other Devices"
4. Find "Android"
5. Double click on "Android"
6. Click on "Update Driver"
7. Click on "Browse my computer for drivers"
8. Click on "Let me pick from a list of available drivers on my computer"
9. Double click on "Show all devices"
10. Click on "Have Disk"
11. Click on "Browse"
12. Find the usb_driver folder that you extracted earlier and in that folder, select android_winusb.inf and hit "Open"
13. Select "Android Bootloader Interface" and it "Next"
14. If there are any warnings, just press "Yes"
Drivers have been installed.
-
Pt. 3: Installing command line tools
-
How to install platform-tools systemwide.
1. Find your platform-tools folder and move it to somewhere where it can stay there forever, E.g. the root folder in your C drive (C:\). I don't recommend putting it on your desktop because that will add useless clutter.
2. Go to your start menu and look up "Environment Variables"
3. Click on "Environment Variables"
4. Scroll down on the bottom; "System Variables" section, find "Path", and double click on it
5. Click on "New"
6. Click on "Browse"
7. Navigate to your "platform-tools" folder
8. Click on platform-tools
9. Click "Ok."
10. Click "Ok."
11. Click "Ok."
12. Click "Ok."
(lol)
oh also i forgot to mention, unlock your bootloader now
steps to do that here:
1. open cmd
2. enter fastboot flashing unlock
3. hit yes on the prompt that appears on your phone
4. you might need to enter fastboot flashing unlock_critical (if cmd gives you an error saying it doesn't exist or something just kinda ignore it, i'm only putting it here just in case)
5. you should be good to continue
-
Pt. 4: The Installation.
-
Installing HavocOS
1. MAKE SURE THAT YOUR PHONE IS IN FASTBOOT MODE.
2. Open aura-p-release-3201
3. Run flash_all.bat (double click on it)
4. Wait until it finishes running.
5. As soon as it closes and your phone screen turns black, immediately hold the power and volume down buttons and enter fastboot mode.
6. Open Command Prompt (CMD)
7. Flash the Kernel by typing fastboot flash boot <boot.img> and replace <boot.img> with the file path to your boot.img file. (Tip: you can drag the file into CMD to put in the file path.)
8. Flash HavocOS by typing fastboot flash system <HavocOS PHH.img> and replace <HavocOS PHH.img> with the file path to the HavocOS PHH.img file. Ignore the errors.
9. Wait until everything finishes and unplug your phone (if you want to)
10. Use volume buttons to go down to "Recovery Mode"
11. Select "Recovery Mode" with your power button. (Tip: double tap the power button to get past the bootloader unlocked warning screen)
12. Swipe to allow modifications
13. Tap on wipe > format data > type "yes" > press "OK"
14. Press back until you get to the TWRP home screen
15. Tap "Reboot" > tap "Recovery" > then tap "Do not install"
16. Wait until it reboots back into recovery.
17. Follow steps 12-14, then hit "Reboot" > then hit "System"
If it doesn't boot into the setup screen, open fastboot mode and format the data once more, then reboot into system.
----------------------------------------------------------
and here are the easiest and also some of the dumbest GSI root instructions ever:
Download Magisk-v21.4.zip
1. Open TWRP and mount everything. (except for USB storage. micro sd card is optional.)
2. Put Magisk-v21.4.zip on your phone (in file explorer)
3. Open the TWRP file manager (advanced > file manager)
4. Navigate to /system/system/bin
5. Find resetprop and tap on it
6. Rename resetprop to phh-resetprop
7. tap on install
8. install Magisk-v21.4.zip
9. Boot up your phone, open magisk, and update everything.
10. Turn on MagiskHide in the settings of magisk manager.
11. Profit$ (lol)
SafetyNet should pass if you did it properly (I would find it kinda funny if you managed to mess up those easy instructions)
Alright guys, have a nice day!
p.s: I might begin work on a user-friendly auto-installer soon.
Thank you OP, finally got Android 11 fully working including SafetyNet, camera/flashlight, Bluetooth and SD card. The only tricky part was the Bluetooth - got help from this comment - needed to delete both APKs before first boot.
pigjr said:
Thank you OP, finally got Android 11 fully working including SafetyNet, camera/flashlight, Bluetooth and SD card. The only tricky part was the Bluetooth - got help from this comment - needed to delete both APKs before first boot.
Click to expand...
Click to collapse
yea i forgot to include that part. I thought you didn't need to do that before boot tho. I managed to get BT working by deleting BluetoothResCommon.apk and renaming RazerAuraBluetoothRes.apk to BluetoothResCommon.apk.
all the links for 4.1 are dead you got any bro?
Cylow333 said:
all the links for 4.1 are dead you got any bro?
Click to expand...
Click to collapse
There is a mirror in the description of the video.
Dude you are a different type of god thank you so much I can finally sleep now.
Quick question: is this version of Havoc have no issues with receiving SMS? Previous versions of it cause this annoying issue that after few minutes from restart SMS stop arriving to phone and the only fix at that time was just to restart it. Tried some patches from telegram but basically end up with no fix.
drumiec said:
Quick question: is this version of Havoc have no issues with receiving SMS? Previous versions of it cause this annoying issue that after few minutes from restart SMS stop arriving to phone and the only fix at that time was just to restart it. Tried some patches from telegram but basically end up with no fix.
Click to expand...
Click to collapse
not that i know of
Uhh is there anyway to edit the buildprop without getting a bootloop? I tried with buildprop editor and i vant see any of the info if i change something and when i restart it goes in a loop.
Cylow333 said:
Uhh is there anyway to edit the buildprop without getting a bootloop? I tried with buildprop editor and i vant see any of the info if i change something and when i restart it goes in a loop.
Click to expand...
Click to collapse
I have never tried editing the buildprop so I don't know, sorry.
Marcos8760 said:
yea i forgot to include that part. I thought you didn't need to do that before boot tho. I managed to get BT working by deleting BluetoothResCommon.apk and renaming RazerAuraBluetoothRes.apk to BluetoothResCommon.apk.
Click to expand...
Click to collapse
So do I have to reflash in order to fix Bluetooth?
Sadly my main reason for losing is that I'm running into a mako issue with HavocOS. systenUI keeps crashing whenever the on-screen keyboard is displayed. This happens with the default installed gBoard and SwiftKey beta. It also crashes when the screen goes to sleep. I followed all the steps from the video. Only thing I did besides that was restore a backup from Google Drive so I didn't have to manually install everything. I'm sadly out of ideas and might have to switch to normal GSI or back to LineageOS so the device is stable enough to use.
gumbyx84 said:
So do I have to reflash in order to fix Bluetooth?
Sadly my main reason for losing is that I'm running into a mako issue with HavocOS. systenUI keeps crashing whenever the on-screen keyboard is displayed. This happens with the default installed gBoard and SwiftKey beta. It also crashes when the screen goes to sleep. I followed all the steps from the video. Only thing I did besides that was restore a backup from Google Drive so I didn't have to manually install everything. I'm sadly out of ideas and might have to switch to normal GSI or back to LineageOS so the device is stable enough to use.
Click to expand...
Click to collapse
I have never had to fix BT before first boot.
And also, that's kinda weird. I've never had any systemUI crashes with the keyboard, although i have had a weird bug where the entire OS crashes and it reboots into a state where its impossible to use. however, to fix that, i just reflashed and i never encountered the bug again. your install might have been a lemon. maybe install again?
Marcos8760 said:
I have never had to fix BT before first boot.
And also, that's kinda weird. I've never had any systemUI crashes with the keyboard, although i have had a weird bug where the entire OS crashes and it reboots into a state where its impossible to use. however, to fix that, i just reflashed and i never encountered the bug again. your install might have been a lemon. maybe install again?
Click to expand...
Click to collapse
Do I need to flash back to stock or can I do a "dirty" reflash?
gumbyx84 said:
Do I need to flash back to stock or can I do a "dirty" reflash?
Click to expand...
Click to collapse
Eh. I think flashing back to stock might be better.
Marcos8760 said:
Eh. I think flashing back to stock might be better.
Click to expand...
Click to collapse
Trying out now. I'm at work so I don't have my laptop with me. Trying it work a live CD image lol
Update: It's been sitting on the "Powered by Android" screen for 20+ minutes. I already tried a data wipe from the bootloader. I can get into TWRP. I'm going to give it another 10 minutes then try flashing HavocOS again.
Update 2: I've made progress. Now it's stick on the HavocOS loading screen. It's been like that for 20+ minutes. Tried the bootloader data format.
Update 3: I was finally able to flash HavocOS at home without issue. I flashed Magisk before even booting into the OS and it seems to be working ok. After it rebooted to complete the setup/install, the issue came back. I'm just flashing HavocOS without Magisk for now.
Hello,
Thank you for the guide, i have installed the android 11 successfully, but i got a startup loup when i tried to restart the phone (in a normal way ), the havoc logo started up then the password, but it just louping between them..
Please help
Hello I did exactly what you said for magisk I updated everything but the problem is that I don't have access to superuser and nor to the module in magisk in my razer phone 2 with havocOS.
Do you have a solution to this problem thank you ?