Related
PHOENIX UNLEASHED JS8
Its not just a rom, its a Cauldron of Awesomeness!!
WINNING!!!
It's that time again, Team Phoenix has now brought you Phoenix version Ultimate JS7!! This is the same great Phoenix ROM everyone knows and loves plus so much more!
Screen Shots
{
"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"
}
DOWNLOAD PHOENIX ULTIMATE JS7!
MIRROR
What it includes:
1. JK4 Modem
2. Speed Mod version C w/ memory tweaks
3. Security patch
4. FUGU Tweaks
5. New default font
6. New email apk
7. Telenav GPS
8. My(Adam's GPS File combo)
9. Lagfix, tweaks and BLN install on first boot(easy to change if this is not to your liking.)
I am sure there is more!
Included Apps
1. Tibu
2. Telenav voice guided GPS
3. XDA app
4. Latest SGS tools
5. Faster Fix GPS
6. My modded dialer from Phoenix 6.0
7. Voodoo Sound
8. Updated, themed market
9. Market Finger print is now fixed(Thanks to Geohentix for bringing it to my attention).
MODEMS
Alternate Modems
More Modems Here
KERNELS
Firebird
Glitterballs
SuckerPunch Voodoo
SuckerPunch non-Voodoo
Di11Pickle
Very much appreciated but by no means required. Thank you!
Credits:
Team Phoenix
Di11igaf-always considered by me to be a silent part of Team Phoenix
JoeDV
ETheRealRemnant-Telenav finder
Comdei
blank to move to first post
Change log
Change log from 7.0 to Phoenix Ultimate!
*JK4 modem
*Clean call recording mod
*Pandora works
*Dialer includes MMS option instead of 2nd VM button
*Updated SGS Tools
*Phoenix themed Miui Music apk
*Volume link in settings
*Stay on while plugged in added to settings
*Video player added back in
I think there is more but I need sleep.
Change log from whatever the last release was to PHOENIX UNLEASHED!
Code:
Phoenix Unleashed:
Theme updated
Removed Telenav(source of battery drain)
put clock back in status bar but added toggles to remove whole clock or just am/pm
Updated to latest Captivate Tools(SGS tools)
FUGU Tweaks (great with JS8)
Speed Mod version D Kernel
Good 'ol JK4 modem
I know there is more but it is 2 am, give me a break!
FYI-Reverted to classic Phoenix Theme
So is this one
FAQ
Will be Updating soon
DO NOT FLASH WITH THE USB PLUGGED IN!! YOU WILL NOT HAVE SIGNAL WHEN THE PHONE BOOTS.
3.5 starts here
Recovery:
Hold vol down + vol up
Hold power button
I wait for att screen, (keep holding)then for screen to go off,(keep holding) then the second time the att screen comes up release power button.
Download mode/odin: LINK TO ODIN ONE CLICK STOCK
1.Start odin first
2.Plug in usb to computer
3.Hold down vol up + vol down(not power)
4.Plug usb into phone
5.When you see the android with shovel, your in download mode!
How to flash PHOENIX Roms.
Roms Should be Flashed will 100% battery
1. BACK UP!!!
2. Use Odin One click to Flash Stock
2a. Wait for it to reboot and then re-enable debugging, hook phone back up to pc and Master Clear
3. Load Clock Work update zip (attached at end of post) and new rom file to Phone memory
4. Remove sim and external SD, and unplug from USB
5. Boot into Recovery and reinstall packages (You may have to reinstall packages twice to get to clockwork recovery)
6. Once in Clock work recovery (Green Text) Select install zip from SDcard
7. Next Select Choose zip from sdcard
8. Scroll down to Phoenix ( Current version) and select.
9. If prompted on reboot to select an option choose with backup and restore. (for auto lagfix)
10. Let it finish and dont touch it till you see the launcher screen. Will this take awhile? YES
How To Disable Vodoo
1.Open A file Explorer ex. Root Explorer
2.Navigate to the Vodoo Folder
3.Inside the Vodoo Folder create a Folder Named disable-lagfix
4.Reboot
5.It will seem to hang on the boot screen Just leave it alone till it fully boots
Or Download attached zip file, unzip and move folder to vodoo folder and reboot and then sit back and wait. It will take awhile so just leave it be
Wipe Battery Stats1. Connect the phone to the charger with the phone powered on, and allow the phone to charge until it shows 100%
2. Disconnect the phone from the charger, and power it off.
3. Reconnect the phone to the charger with the phone powered off, and allow the phone to charge until the battery indicator shows 100% (you can use vol-up/vol-down to make the indicator come back up when the screen goes to sleep).
3a. Repeat step 1, 2, 3
4. Disconnect the phone from the charger and power it on.
5. Once the phone is powered completely on, power it off again and reconnect it to the charger until the battery indicator shows 100%.
6. Disconnect the phone, power it on, and use it.
7. Use ADB or a Terminal Emulator to run the following command:
Code:
su
rm /data/system/batterystats.bin
7a. Reboot into clock work Recovery, and choose advanced CWM features and select wipe battery stats
How to back up your APPS + data (not system data) with Titanium Backup
Go to the market and download and install Titanium Backup
Load up Titanium Backup and allow super user.
Go into Preferences and change Backup Folder name to external_sd/TitaniumBackup (this will save a copy of the files to your external SD card for restoring after flash) then click back and it will reload.
Now go to batch and select backup all user apps. Select the apps you want and hit run batch (top of the screen) once it is finished (you will know as there is a notification in the drop down that it is done) Double check you external sd for the Titanium Backup folder, if it is there then you are good, if not double check the spelling. Make sure it is an underscore between external and sd. ex. external-sd = Wrong..... external_sd = right so it should read external_sd/TitaniumBackup
Ok So you Fully Bricked your Captivate Here is a last ray of hope
Download mode/JIG: ITEMS YOU WILL NEED TO BUY:
-301k OHM Resistor, no more no less & -MicroUSB Board
-Upon receiving items, go here.
-Remove SIM and MicroSD Card
-Plug in JIG and voila, you are back in download mode
-load up odin and flash back to stock
Themes and Stuff
Disable Vodoo before flashing themes like blackfroyo with recovery.
Voltage Settings (If Kernal Supports OC/UV)
VoltageApp settings will stick until reboot, but to get them to stay after rebooting, this is what worked for me; You will need Root Explorer for this one
Setup Voltage App like you want
Menu>Apply for Now
Menu>Save as boot settings
Open Root Explorer
Navigate to /etc/init.d
Locate file saved for boot settings (S_volt_scheduler)
Rename "S_volt_scheduler" to "S_98_volt_scheduler"
Save
Reboot
Open VoltageApp to verify settings stuck
AT&T Wap Settings
ATT
wap.cingular
not set
not set
[email protected]
not set
not set
http://mmsc.cingular.com
wireless.cingular.com
80
310
410
not set
internet+mms
Power Cycle without pulling battery
Hold volume up and power for 10 sec. (This will reboot your phone without a battery pull)
Backing Up your NV_data
Thread With more info
The reason its important to back up your NV_data (Non-volitile) is this has your imei, product code, unlock codes and model. This informatioin is not recreated with a JF6 OCD (One click downloader)
Certain Roms write data to your NV_data
(i think it was JPC leak from I9000 that was the first one. it changed everyones product code to I897ZKAKOR)
Axura changes the product code to I959ZKATMB or something like that
The Correct Product code for our Captivate is I897ZKAATT.
If your IMEI says 004999010640000 begin_of_the_skype_highlighting 004999010640000 end_of_the_skype_highlighting begin_of_the_skype_highlighting 004999010640000 begin_of_the_skype_highlighting 004999010640000 end_of_the_skype_highlighting end_of_the_skype_highlighting this is incorrect also and you may find your phone to stop making calls as this is like a debugging or prototype imei
Finally, if your unlock code is FFFFFFFF, you need this repair in order to unlock your code
All of these can be fixed with Helroz's Repair_nv_data.zip Found Here: http://perso.numericable.fr/helroz/P...ir_nv_data.zip
I did not create the software or any of the instructions, THis is credited to Helroz in the vibrant forum (please thank and donate to him) he came up with all of this, Im just sharing knowlage.
this can be found here: Unlocking Tmo Vibrant
http://forum.xda-developers.com/show...&postcount=103
Just read the read me first. then the .Doc Make sure you are at Stock JH7 (I didnt try jf6) and root with busy Box (Super One click by CLShort Fuse worked for me)
Then Step 2,3 and 4. Monitor your phone for SU access attempts, it has several and be patient and read what its asking you to look for,
Now if you havent Backed up your NV_data then now is the time. I Use root explorer and just copy the /efs folder to a safe place (I have a copy on my ext. sd card and a backup hard drive)
You can also Use SGS tools (not SGS tool Box) to do a product code check. This also copies all of the pertenant NV_Data files to a folder on your internal SD card. you can use these also if you want.
Flashing JPP Modem to enable 850
The only guaranteed method for enabling 850 on jpp that is proven to work every time is to:
Flash stock using odin
Flash jg8 modem
Flash rom with jpp modem
Hopping around to other modems and back to jpp after this will kill 850 as well.
For some this is not an issue as they are in areas where 850 is not utilized by AT&T but for others jpp will cause headaches if they try using it without following these steps.
Themes and Graphics
Disable Vodoo before flashing themes like blackfroyo with recovery. (if Running vodoo)
How to change Boot Animation.
1.Find the animation that you want (most be compatible with captivate)
2.Copy bootanimation.zip (it must be named this) with a file explorer that gets you to system files ex. Root explorer to system/media
3.Reboot
Fonts
http://forum.xda-developers.com/showthread.php?t=801160
http://forum.xda-developers.com/showthread.php?t=748916
Phoenix Patches
All Patches and Fixes attached below
Phoenix 1.5= Email and phone APK. Copy to system/app , clear data in email app and reboot
Email FC after changing email Fix
Thanks to Newter55 for the find
Download the libcamera.so from here: http://dl.dropbox.com/u/11343737/libcamera.so
Use root explorer or whatever method you prefer and make a backup copy of /system/lib/libcamera.so just in case you need to get it back.
Copy the libcamera.so you downloaded from above link over the existing one in /system/lib.
Delete or rename the existing email.apk in /system/app to test that this fix works.
Reboot phone.
Open Barcode Scanner and enjoy the fact that it no longer force closes.
This will allow people to use whatever email.apk they prefer...or if they are like me they can get rid of the apk altogether.
Ok Guys I wipped out all the Flaming in the thread. I have reopened it after the rules were met.
Here's a quick and dirty conversion to boot animation of that "Operation Phoenix" video if anyone wants it.
Download bootanimation.zip
app
Jeepsdaddy said:
How do you change the GPS server settings and wipe GPS data?
Click to expand...
Click to collapse
Sgs tools app, secret codes, lbs test mode, change supl settings, delete gps data
Sent from my SGH-I897 using XDA App
Also if anyone has issues with charge death or random shutoffs while charging. http://forum.xda-developers.com/showthread.php?t=887315
That kernel works well with this ROM.
Hey Adam thanks for all your hard work. This is my wallpaper
this looks so good adam!
A big congrats to you and your team...
Awaiting a full battery for the flashing to begin!
Smaller versions of the Operation Phoenix boot animation. It still looks fine even in the 10fps version IMO.
Tinyier uglier animated GIF rendition:
Small 10fps Version Download
Medium 16fps Version Download
Large 30fps Version Download
BTW, I Can't find the post now, but thanks to whoever originally found this animation.
zelendel said:
I agree with the sound. I even have a fire wav file that I used back on one of the boot animations for an old WM rom if you want adam
Click to expand...
Click to collapse
Hey Zel, Where did you get that Avatar, it would be sweet if we could light that on fire! Android Phoenix!
adamholden85 said:
NO FLAMING ALLOWED!! That is my # 1 rule. Smoke has helped me out tremendously. Let the past be the past. What's done is done. Smoke is the man in my book.
Click to expand...
Click to collapse
Sorry mate, wasn't meant as a flame.
Was just trying to say that there really isn't a leagl ground to try and shut down Phoenix, and I believe I speak for everyone when I say we would rather see you be able to develop Phoenix and make it all it can be, without the threat of a gun to your head.
All aside, I am looking forwards to hear what great things come out in the coming weeks.
Also, make sure you take time off and enjoy New Years with your family!
Yes we may be part of your family, but you gotta look after the RL ones too.
zelendel said:
Good morning everyone. As far as last night goes, it was taken care of so moving forward I am so looking forward to a 2.2.1 base with Phoenix beauty.
Click to expand...
Click to collapse
Morning...after 3pm.. Sheeshh
Felklaw said:
Personally, I have the following:
-Auto brightness (but use Screen Filter for night time)
-I initially had this set, but have since set it back to never sleep. Not really noticing big difference, and where I work and live, both are Wi-Fi already set up in my phone. Plus when Wi-Fi is off, I found my phone syncing would then use 3G on AT&T's stupid ass limited rates....
-Bluetooth off when not using it
-GPS turned off when not using it
-Have not touched the sync frequency
I had terrible battery the first few times, one MAJOR thing to do is go into SGS Tools and ensure you Update Stock Apps --> 3D Gallery
That stock gallery is a known battery raper. After doing that, I had 24hrs uptime and had 63% battery left.
Means I can go 2 days with moderate to medium usage (calls, texts, web browsing, games and App Market)
Gotta be happy with that!
Click to expand...
Click to collapse
+1 on all the steps but I wasnt aware of the gallery issue. If I read it right, this has the one baked in you reference. I have never gotten battery life to that level but following these steps did help me as well. You must have one bada$$ battery! Good post.
Good news/bad news
Good news, we are not getting shut down. Master's case was not strong enough. Bad news, who am I kidding, there isn't any. We are still moving firmwares though to get up with the times.
adamholden85 said:
Good news, we are not getting shut down. Master's case was not strong enough. Bad news, who am I kidding, there isn't any. We are still moving firmwares though to get up with the times.
Click to expand...
Click to collapse
Awesome news
adamholden85 said:
Good news, we are not getting shut down. Master's case was not strong enough. Bad news, who am I kidding, there isn't any. We are still moving firmwares though to get up with the times.
Click to expand...
Click to collapse
Excellent news.
Means 1 less stress for you and the team.
how can i chage the battery icon it looks like a christmas bell
Here is a free template I found that kinda looks cool if someone who knows html wants to screw with :
Preview : http://www.phoenix-hq.com
html files and images : http://phoenix-hq.com/Colorus.zip
Hi all !
As I couldn't find many information and hacks about the Asus ME572c (K007), I thought I might start by sharing my experience with the device.
For those who are having a hard time to find resources, here are the changes that I could carry out without messing all up :
Rooting the device :
It was fast and easy using the "ROOT ZenFone" app I found on an alternative market (could be on the play store, I didn't checked...) rooted and installed SuperSU in a few minutes, then I pushed in my usual root apps (firewall, explorer, busybox, uninstaller, patcher, ...) and started the bloat-shoot party.
Apps removal :
Once rooted, any (good) root removal app will do, pick your favorite and be careful to what you do : I frightened myself a few times doing those things and I still don't have any backup/recovery procedure besides a factory reset...
You may want to check dependencies before you delete an app and maybe check what's the app for : you may loose functionality you wanted to keep but that I didn't care about...
As I don't use google services I got rid of every google apps except google search (mainly for voice recognition) and maps : so keep in mind that if you want to keep google apps on your pad your may not go as far as I did.
I managed to keep a fully working device and to remove so far :
- all google apps (play store, framework, services,... ) except search & maps
- calendar, contact, phone/mobile applications and providers
- all apps containing "asus" in their name except : ASUS_Air_Status (seems to be needed for GPS) and com.asus.lockscreen (I never touch lockscreen apps : I had a bad experince :crying, but as it don't seem to be active at any moment, as it's a few kilobyte and even if I don't use any lockscreen : I won't take the risk. By the way, don't remove/freeze "keyguard" as well (will mess with locking/navbar or something else important for the OS...)
- CMclient/DMclient
- intel/widi named apps (screen casting ? not sure), cwsservicemanager, windows/multitasking (dual apps mode)
I'ts nor a detailed or a complete list but just clues to what you may try...
Most of the apps were first frozen, then deleted when no issues were found following few basic tests, but some apps can still run even when freezed (asus apps do that a lot), so pick a good process viewer to see through that. The result is a device which is quick from "power on" to "available", and has few running process letting plenty of resources available (around 600 Mb of memory used at start-up)
Usual tuning :
Whatever the device we have (HTC, Nexus, ...) we all have the usual set of performance enhancing modification we like to apply, here're mines:
- stop logging (logcat & dmesg)
- kernel/ioscheduler/mem/dalvik tuning (many apps to do that)
- disable error check/reporting (along with many other common build.prop modifications you'll find all over the web)
- good task killer / greenify / services, wakelock & autostart editor : no more resources hogging with no reason from the few apps left on the device...
CCL: I got mine since mid-December and I'm pretty happy with the tuning I've done so far : I obtained more and more perfs till it scores over 41 000 at Antutu ( just like my good ole Nexus 5 :silly: ). I don't have a reference mark with stock apps installed, I'll be interested if someone can submit some scores; I'll submit some screenshots with detailed marks in the next posts.
Besides all the removal I've been doing, everything seems to work fine on the hardware side (GPS, bluetooth, sound, ...), I got rid of some software features like dual apps, social networking, or Asus dsp manager (which woks quite well on this device, I may get it back...) bit I'm very happy with the current config.
I think I'll stop my pump-it-up frenzy there before it explodes, and wait for Asus to release Lollipop or if any ROM (I'd love a PAC-Rom) becomes available for this device.
Hi Gentaz, come on over to our ME572 thread and let's get this killer "7 tablet the support it deserves!
http://forum.xda-developers.com/showthread.php?t=2915779
I've also rooted and removed bloatware. Also disabled the navbar via build.prop because it takes up space in some off the apps I use.
I'm pretty new to android tuning, curious what tweaks you've performed. Care to elaborate?
I'm wondering if the mods want to move the thread I linked above to this subforum for more exposure?
Here are some screenshots :
Process and mem right after booting.
{
"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"
}
Antutu history best scores :
Sent from my K007 using XDA Free mobile app
Hi TujungaGuy,
Thanks, I read that thread you linked while waiting for the Memo to be delivered and it pointed me to this "ZenFone" app : the pad was rooted less than one after I got it, I didn't even care to test Asus apps
I'm not sure to find time to detail (and remember) the modifications I made for a specific environment and usage I have for this pad (telescope control and unix/linux networking). To me it's more like a computer than a "social/communicating/whatever most people see in this device" tablet. I'm currently writing a "quickref" in my wiki : I may publish this later on XDA if it's not too messy and incomplete.
Being myself a sysadmin, I have solid unix/Linux grouds but don't know much about the "android" part of the OS too, and I have to say, not really interested into learning it...
I was merely throwing ideas I had and that worked for me, but I'm willing to help : so I may start by answering questions if any or give directions in particular aera anyone would like to have look at.
Sent from my K007 using XDA Free mobile app
The most performance improving task, but the most dangerous and longest to figure out at the same time is a proper app management, eg which app can I move, freeze or delete without having the device not responding or loosing hardware abilities ( GPS, bluetooth, ...).
I can't submit a proper list of "safe to delete apps" but I made screenshots showing the apps I kept and the one I moved from /system to /data.
Starting from the 11.8.3.30 firmware published by Asus (I made the ota update), here is the list of curently installed apps on my ME572C, one may deduce by comparison the (long) list of apks that were deleted.
Frozen apps (I kept just in case...):
System apps :
User apps (without the one I installed), most of them were moved from system to userspace :
Some apps have their french name (sorry), but I didn't find a good app management tool showing the file names : I'll take any suggestion (a resubmit lists with proper names).
Hope this helps !
Sent from my K007 using XDA Free mobile app
PS: Corrected wrong screenshot (last one was a duplicate)
ME572c recovery
Today I did it : I changed a setting I shouldn't and my Memo became unusable (boot loop ?); even factory reset didn't do the trick...
So now I can make a How-to for recovery and rooting ;o)
Recovery (stock firmware) :
==> You'll need a MicroSD card on wich you have to put a file with you PC (or another device)
Prepare SD :
- Get update file from Asus (mine was UL-K007-WW-11.8.3.30-user.zip for 8.3.30 version and WW device)
- Copy file to FAT formatted MicroSD and rename it "MOFD_SDUPDATE.zip"
Go to droidboot mode :
- turn the K007 on with "Power" and "Volume UP" keys and keep'em pressed
- release "Power" when the screen turns on
- then release "Vol UP" a few second later when the Asus logo disappears
Flash :
- insert MicroSD into K007 slot
- Select "SD Download" using "Vol DOWN" key then confirm with "Power"
==> It will flash the device with the original Asus firmware and reboot to display the first launch wizard...
Not sent from my K007...
ME572c Root
Now For the rooting part.
==> You'll need a computer with adb or a MicroSD on which you can put files with another device
Download resources :
- download the RootZenFone app from "asuswebstorage" : https://www.asuswebstorage.com/navigate/s/1DC355CA300041BDAC1FBE7C9F749501Y
Install kit :
- using ADB (adb push RootZenFone-1.4.6.8r.apk /sdcard/) or using the MicroSD
- allow installation from unknown sources in android security setting
- install the app (use file browser to find apk file)
Root the device :
- Remove known wifi networks and disable wifi
- launch rooting application and proceed
- it did launch a "demo mode" but don't panic : press OK then quit this demo app then wait 10s then reboot
==> It will go into flash mode (small droid being serviced with a progress bar), then go for a normal start
Check :
- go in application list to find if SuperSU app is available
Thanks for the rooting info. You can just download the APK directly into the tablet's download folder as well. No need for a SD card or ADB. Just an FYI.
Sent from my K007 using Tapatalk
did the same....
I did the same today... tried the upload to SD card, I assume you are unzipping the file prior to putting it in? I tried both renaming and not renaming the file. I tried both zipped and unzipped on the disk. I am having no luck. Please help... I have added screen shots, both showing the same error I continue to receive.
Gentaz said:
Today I did it : I changed a setting I shouldn't and my Memo became unusable (boot loop ?); even factory reset didn't do the trick...
So now I can make a How-to for recovery and rooting ;o)
Recovery (stock firmware) :
==> You'll need a MicroSD card on wich you have to put a file with you PC (or another device)
Prepare SD :
- Get update file from Asus (mine was UL-K007-WW-11.8.3.30-user.zip for 8.3.30 version and WW device)
- Copy file to FAT formatted MicroSD and rename it "MOFD_SDUPDATE.zip"
Go to droidboot mode :
- turn the K007 on with "Power" and "Volume UP" keys and keep'em pressed
- release "Power" when the screen turns on
- then release "Vol UP" a few second later when the Asus logo disappears
Flash :
- insert MicroSD into K007 slot
- Select "SD Download" using "Vol DOWN" key then confirm with "Power"
==> It will flash the device with the original Asus firmware and reboot to display the first launch wizard...
Not sent from my K007...
Click to expand...
Click to collapse
If you read the how to it says copy and rename : so no unzip involved here...
Other checks you may peform :
- download : checksum your downloads (if no checksum given download twice and compare md5)
- version localization : there are WW, TW and a third version for the device and so are the firmwares released by Asus ==> did you use the good one for your device ?
- the error message you posted says error is on the footer (end) of the file : how did you copy it ? (I suggest using adb push) or maybe your sd is going bad or dosn'thave enough free space (there should be nothing else on it, it already worked with media files on it me) : try another one or an empty one you formated with your device (blank it using dd command).
Sent from my K007 using XDA Free mobile app
didnt work....
Thanks for your help. Im sure I am doing something wrong. From what I am able to tell (unable to start tablet to verify) I should also be installing the WW version. I actually, out of desperation, tried each version with no success. I did format the SD card after each version, also with no success. I would love to try adb but I am a bit of a noob to this and get lost with all the steps on the walk throughs I do find. Do you by chance have a step by step for the morons of us out there (everything from what programs, to what steps, and system requirements.....with screenshots if possible :fingers-crossed?
Thanks again for the help.
Gentaz said:
If you read the how to it says copy and rename : so no unzip involved here...
Other checks you may peform :
- download : checksum your downloads (if no checksum given download twice and compare md5)
- version localization : there are WW, TW and a third version for the device and so are the firmwares released by Asus ==> did you use the good one for your device ?
- the error message you posted says error is on the footer (end) of the file : how did you copy it ? (I suggest using adb push) or maybe your sd is going bad or dosn'thave enough free space (there should be nothing else on it, it already worked with media files on it me) : try another one or an empty one you formated with your device (blank it using dd command).
Sent from my K007 using XDA Free mobile app
Click to expand...
Click to collapse
Hi mlakia,
There's not much more to say : all details and screenshots that I could pick are in the how-to.
Besides I'm not using windows for the 'not on tablet' part thus screenshots would be useless...
All I can provide is :
- download Asus rom http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME572C/UL-K007-WW-11.8.3.30-user.zip as MOFD_SDUPDATE.zip (respect the case) on a empty fat formatted SD :
wget http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME572C/UL-K007-WW-11.8.3.30-user.zip
mv UL-K007-WW-11.8.3.30-user.zip MOFD_SDUPDATE.zip
md5sum MOFD_SDUPDATE.zip
289f23ac72bc6d78c9a8814774e83287 MOFD_SDUPDATE.zip
- then with adb :
adb push MOFD_SDUPDATE.zip /storage/MicroSD/
- or some other way to do it using you pc any other device that can write on the sd if you Memo is stuck (check the md5sum of the copied file !)
- launch recovery then flash from SD...
==> unless your download or SD is corrupt, maybe there's a real issue : you may try to call Asus helpdesk or open another thread in Q&A for more help on recovery.
Sent from my K007 using XDA Free mobile app
Hi !
Here's a refined, close to minimum, system apps list that are required for the OS and hardware to work properly. Sound apps (maxaudio & icesoundserver) can be removed but at the expense of a poor sound quality.
Keep in mind it's only the system required apps : although i deleted most of the preinstalled apps, I moved many of them as user apps (/data/app/ ) as I guessed they're not system related or don't need to be up all the time : unlike system apps you can greenify user apps.
You may see an non-standard app : rotation manager. I installed it as a system app as I wanted it to be always up, thus I can use the memo in permanent landscape mode preventing an oom kill.
But you have to have an IME (keyboard), the audiowizard app and maybe others to be able to use the pad (you may look very stupid without an IME...) !
As usual : I'm not responsible if your pad becomes a brick or gains world domination as a consequence of your tinkering...
List of system apps :
View attachment 3149796View attachment 3149798
List of user apps :
(many could be useless, I never saw any *context app running...)
View attachment 3149799View attachment 3149800View attachment 3149801
Sent from my K007 using XDA Free mobile app
Could not open attachments
Thanks very much for posting your refined lists.
Maybe it was just me, but I could not open any of the attachments in your latest post. When I clicked the attachment, it said something like "Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Could you double check the attachments, please? Thanks again!
I'm not able to view the attached file.
@abhijeet : can you avoid quoting whole posts in this useless manner plz ?
Sorry for bad attachments : I'll try to correct or I will repost...
Sent from my K007 using XDA Free mobile app
Edit didn't worked... so here are the screenshots :
System apps :
User apps :
Sent from my K007 using XDA Free mobile app
Update available!!! But failed to update. I think root caused this. Anyone experienced same result?
Gentaz said:
Here's a refined, close to minimum, system apps list that are required for the OS and hardware to work properly. Sound apps (maxaudio & icesoundserver) can be removed but at the expense of a poor sound quality.
Keep in mind it's only the system required apps : although i deleted most of the preinstalled apps, I moved many of them as user apps (/data/app/ ) as I guessed they're not system related or don't need to be up all the time : unlike system apps you can greenify user apps.
You may see an non-standard app : rotation manager. I installed it as a system app as I wanted it to be always up, thus I can use the memo in permanent landscape mode preventing an oom kill.
But you have to have an IME (keyboard), the audiowizard app and maybe others to be able to use the pad (you may look very stupid without an IME...) !
Click to expand...
Click to collapse
If I understand correctly, AudioWizard is a required app. Is that correct? I've been working on my own list of apps that are safe to remove (similar to what's linked in my signature - you can preview the one for the ME572C I've been working on here), and ran into an issue: I tried deleting the Sound Recorder app and Titanium Backup locked up. I left it for roughly ten minutes trying to install it before forcing a shutdown. After that I got stuck in a boot loop and had to flash the latest firmware. But I'm not sure if it's a coincidence and the removal of another app is what caused the boot loop, and not the failed removal of Sound Recorder.
By the way, your list is very helpful and I'll be sure to update my own later based on it!
Abhijeet357 said:
Update available!!! But failed to update. I think root caused this. Anyone experienced same result?
Click to expand...
Click to collapse
Root typically locks out OTA updates. On the ASUS firmware page for the tablet I see a new Version JP_V11.8.3.31 but I don't see that version for TW or WW yet. Also, just to guess, JP is Japan, TW is Taiwan, and WW is worldwide... is that correct?
pWEN said:
If I understand correctly, AudioWizard is a required app. Is that correct? I've been working on my own list of apps that are safe to remove (similar to what's linked in my signature - you can preview the one for the ME572C I've been working on here), and ran into an issue: I tried deleting the Sound Recorder app and Titanium Backup locked up. I left it for roughly ten minutes trying to install it before forcing a shutdown. After that I got stuck in a boot loop and had to flash the latest firmware. But I'm not sure if it's a coincidence and the removal of another app is what caused the boot loop, and not the failed removal of Sound Recorder.
By the way, your list is very helpful and I'll be sure to update my own later based on it!
Root typically locks out OTA updates. On the ASUS firmware page for the tablet I see a new Version JP_V11.8.3.31 but I don't see that version for TW or WW yet. Also, just to guess, JP is Japan, TW is Taiwan, and WW is worldwide... is that correct?
Click to expand...
Click to collapse
Check the Asus website now. The firmware update is available for WW.
ONEPLUS 3 - SUPPORTS ALL VERSIONS UP TO THE LATEST OXYGEN OS BUILD.
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Google, Nexus, OnePlus and Samsung Toolkits and supports many devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
* Root any public build automatically
* SkipRoot boot image to AutoRoot (selected builds)
* Sideload root/unroot files via Custom Recovery
* ALLINONE to Unlock, Flash Recovery, Root, Rename the restore file + install Busybox (G,N,O)
* ALLINONE to Flash Recovery, Root, Rename the recovery restore files + install Busybox (Samsung)
* Unlock/Re-Lock your Bootloader (G,N,O)
* Download Google Stock Image files directly to the ToolKit (G,N,O)
* Check md5 of google stock image before flashing
* Flash Google Stock Image (G,N,O)
* Flash any part of a stock firmware image to device [boot, system, recovery, etc.] (G,N,O)
* Download/sideload stock OTA image (G,N,O)
* Install BusyBox binarys on device
* Rename the Recovery Restore File present on Stock Roms (if stock recovery is being restored after flashing custom recovery image)
* Flash Stock Recovery, CWM touch, Philz_touch or TWRP Touch Recovery
* Pull /data and /system folders, compress to a .tar file and save to your PC
* Auto Update Toolkit at startup (PRO ONLY)
* Auto Update superuser file and custom recovery images to latest versions (PRO ONLY)
* Disable forced encryption on Nexus5X,6,6P and 9
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps
* Install EFS/Partition Backup/Restore app by Wanam
* Create tar with 1-Click for flashing via Odin
* Fix extSdCard write permissions in Android 4.4+
* Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC (selected builds)
* Useful Mods, Fixes and Tools Section
* Extras, Tips and Tricks section (includes guides)
* Backup/Restore your /efs partition (gsm only)
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC ( on builds with insecure image available)
* Mods section to automatically perform certain tasks on your device
* Boot to any recovery without Flashing it (G,N,O)
* Boot or Flash .img Files directly from your PC
* Quick Picks Professional Feature (10 slots)
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your phone
* Pull Files from your phone to your PC
* Set Files Permissions on your device
* Pull and Trim your Radio Image (gsm models only) to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Rip cache.img to zip file in CWM format
* Reboot device to Fastboot Mode or Android in fastboot mode (G,N,O)
* Reboot device to Fastboot Mode, Recovery, Android or Download Mode in adb mode
* Turn Initial Start Screen On/Off for next use
* Sideload any zip file via Custom Recovery
* Basic Toolkit for use with ANY Android device
Key: G-Google N-Nexus O-OnePlus S-Samsung
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: Grarak or TWRP custom recovery on OnePlus 3, ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Up' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**FAQ**
**VIDEOS**
I have finished all the work on the OnePlus modules for the 1, 2 and 3 devices and it is ready for testing.
You can download and test the Toolkit from the link in post#1. Please remember that this IS a test version at the moment as I do not own any OnePlus devices but I have checked all the code thoroughly and don't see any problems. I am especially pleased with the unlock/lock routines and will probably implement the code for the Nexus modules if it works well.
Everything can be checked (and please do) except downloading a stock build directly from the Toolkit as I am waiting to hear back from AndroidFileHost to see if I can get direct links to use in the Toolkit. The fastboot flash routines are working though and the Toolkit will detect the storage of the device (16GB or 64GB) and flash the relevant userdata image so you do not have to do that manually anymore.
I have used the Universal USB driver pack from CWM so if anyone has not installed OnePlus drivers yet PLEASE test if this works. I did originally include the official drivers from OnePlus but they close the Toolkit when the drivers installation starts and thats not great.
The ALLINONE routine should work fine and I have sent out some pro codes to testers to check it all works.
All builds are covered and the correct version of TWRP will be downloaded depending on the build selected. Please check everything and let me know of any bugs or textual errors (as I used a lot of the Nexus code) so I can release it publicly as soon as possible.
Thanks, Mark.
Great job, thanks a lot!!!
Dude, did a scan of your file and found this: Result: Detected: Trojan-Ransom.Win32.Cryrar.gib care to explain?
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
gruntyoldbag said:
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
Click to expand...
Click to collapse
Just saying, got that hit when I scanned the installer file. Might be wrong but I will not run it until dev explain why
TheErk said:
Dude, did a scan of your file and found this: Result: Detected: Trojan-Ransom.Win32.Cryrar.gib care to explain?
Click to expand...
Click to collapse
Did you read the first post of the thread?
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Click to expand...
Click to collapse
The Toolkit has been running over 4 years and there have never been any viruses in it.
Mark.
I ran this on my Nexus days, the guy is well known around, you can go with this.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
gruntyoldbag said:
Trojan?
I hope not - seems legit.
I have 2 problems:
1)
It never asks me to authenticate the PC on the phone after installing drivers - tried both driver versions.
But the Phone serial shows up in the menu, the driver test is fine and I can backup .apks.
2)
I can not flash the OTA
Is it because it is a full stock image instead of an OTA?
Click to expand...
Click to collapse
I found the problem right away, just deleted 1 word by accident when I was renaming things.
I have made new device modules and uploaded them. Delete the ConfigOnePlus3.exe file from the Tools folder (or run ToolkitClean and select the OnePlusThree), then rerun the Toolkit and select your device to download new modules. Should work then.
Mark.
mskip said:
Did you read the first post of the thread?
The Toolkit has been running over 4 years and there have never been any viruses in it.
Mark.
Click to expand...
Click to collapse
Thought I did! Thanks for the fast reply!
---------- Post added at 11:23 AM ---------- Previous post was at 11:11 AM ----------
Impressive tool you got here! Thanks!
mskip said:
Delete the ConfigOnePlus3.exe file from the Tools folder (or run ToolkitClean and select the OnePlusThree), then rerun the Toolkit and select your device to download new modules. Should work then.
Click to expand...
Click to collapse
I cleaned the toolkit and
**************
Also I had to restart the toolkit (my own error - I didnt use the toolkit to restart, but restarted manually) and I got:
************
Tried again and Windows installed more device drivers when accepting sideload from ADB.
Didnt work the 2nd time either.
**********
BTW: drivers are installed correctly
******
Btw: I really love your tool - nice, clean, fast and a lot of HELP in the menus
gruntyoldbag said:
I cleaned the toolkit and
**************
Also I had to restart the toolkit (my own error - I didnt use the toolkit to restart, but restarted manually) and I got:
************
Tried again and Windows installed more device drivers when accepting sideload from ADB.
Didnt work the 2nd time either.
**********
BTW: drivers are installed correctly
******
Btw: I really love your tool - nice, clean, fast and a lot of HELP in the menus
Click to expand...
Click to collapse
Thanks and thank you for staying with me, I have had to change some of the procedures for the OnePlus.
Should be all fixed now. One of the procedures I had to skip set the filename for the OTA image. Have added it back in.
Clean the module files, download the new ones and retest. Hopefully it should go through.
Mark.
It is sideloading now
Reboot was successful - thx
Btw: If you want the help text to be 100% correct:
When you reboot you have to chose ENGLISH (or you can chose chinese or madarin?)
And it is called 'Install from ADB' not from USB.
Then click OK to 'Do you want to update' (not 100% sure about this text - can not remember now.
************
Just tried option 11 from the main menu:
****
Booting to stock recovery gives me the same error.
gruntyoldbag said:
It is sideloading now
Reboot was successful - thx
Btw: If you want the help text to be 100% correct:
When you reboot you have to chose ENGLISH (or chinese or whatever)
And it is called 'Install from ADB' not from USB.
Then click OK to 'Do you want to update' (not 100% sure about this text - can not remember now.
Click to expand...
Click to collapse
Thank you. I have uploaded the fixes to all the OnePlus device modules so that part at least should work for them all now.
Does the language selection come up as soon as the device boots to recovery?
I put Install from USB as thats what it said in the flashing tutorial on oneplus.net I will change it to Install from ADB/USB just to be safe for all devices.
Thanks again for the feedback. If you want to test any of the pro functions (ALLINONE) then let me know and I will send an activation code to your inbox.
Mark.
gruntyoldbag said:
It is sideloading now
Just tried option 11 from the main menu:
****
Booting to stock recovery gives me the same error.
Click to expand...
Click to collapse
Have you unlocked your bootloader? This is required before flashing/bootings images to your device.
I can capture the error when trying to boot/flash with a locked bootloader to provide more help for the user.
Mark.
The language selection come up as soon as the device boots to recovery - yes.
No I didn't unlock the bootloader - I didn't think it was necessary - help text said something about unlocking - but not that it was required.
I just wanted to backup the device - not flash anything.
Yes let me try (ALLINONE) - send me a PM thx.
gruntyoldbag said:
The language selection come up as soon as the device boots to recovery - yes.
No I didn't unlock the bootloader - I didn't think it was necessary - help text said something about unlocking - but not that it was required.
I just wanted to backup the device - not flash anything.
Yes let me try (ALLINONE) - send me a PM thx.
Click to expand...
Click to collapse
I have changed the text when booting to recovery and added extra error control when flashing or booting an image without the bootloader unlocked. New device modules uploaded.
Now sending a pm to you with a code.
Mark.
PM received - PM sent
New text and error control seems to work :good:
I've noticed since I've followed the thread the days prior to my device arriving many have struggled to follow the current guides available. I am not responsible for your inability to read, bricked, or internally explosions on devices.
Step 1:
Go to your desktop and create a new folder I labeled mine 'KIWISDK' but you can call it whatever you want. This is where you will store all files during this process so you can easily access them.
{
"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"
}
Step 2:
Create and save a blank Wordpad/Word document into the newly created folder on the desktop title it 'bootloadercode'
Step 3:
Assuming you're not android developers or have the massive android SDK on your computers you need to download and install adb and fastboot from here.
Go ahead and put the installer in that folder just for safe keeping, run the exe to natively install adb/fastboot from anywhere on your PC. We will use this a few steps later.
Step 4:
Prior to unlocking your bootloader we have to do a few things first. Go ahead and power on your phone and go through the initial setup process.
You can use the following link (corrected from all the other ones) to create a new Huawei account (click register for free below the login. This website can be found here
Once you've created a user ID you can use this same link to access the bootloader unlock page later.
Step 5:
Once your device is fully initialized go to settings>about phone
click the build number 7 times as shown above. It will display a toast notification that you are now a developer.
press the back button (2) up from the about phone area of the settings you will now see
file:///C:/Users/Jesse/Desktop/developeroptions.png
Be sure that the 'developer options', 'enable OEM unlock' and 'USB debugging' toggles are in the on position.
Step 6:
Open the Huawei website posted in step 4. Login and accept the terms.
On your device go to the dialer and type the following into the keypad:
*#*#1357946#*#* Open the bootloadercode document we created in step 2 and record this number here, leave the word pad open to record the unlock code created on the Huawei website.
With the website open,
Carefully go to About Phone> After you select smart phone and type your model number KIW-L24 into the website open your about Phone>Status enter your Serial number and IMEI number (if your IMEI 1 number doesnt work, try again with your IMEI 2 number. Make sure you have all numbers and letters in this step complete with accuracy. DOUBLE AND TRIPLE CHECK.
Product Identification is the number located on the wordpad/word document copy and past it into this area. Generate the unlock code after typing in the pin.
Copy and paste the generated number onto the wordpad document for future reference and save the wordpad document.
Step 7:
Download TWRP revovery from here
Download the 3.0.2.0 version and save it to your folder you created in step 1
Download SuperSU from here
Save it into the folder on your desktop.
Download opengapps here
Save which ever version you choose to your desktop file (I go with Nano and Micro) Be sure to select the ARM64 and android 6.0 versions.
Also at this time download your favorite custom rom from the ROM/Kernel portion of our website and store it in that file (be sure to check if it needs gapps flashed along with it) if it is a CM based ROM it has to have the gapps either way I always like to keep a gapps zip on my SD card.
Step 8:
Plug your phone into your computer, open your external SD card drag and drop the superSU zip, Open Gapps Zip, and rom if you selected one for future access.
open a command prompt (cmd from Cortana or runcmd in earlier versions of windows.
type the following:
adb reboot bootloader
Your phone should reboot with a white screen, once it has type the following:
fastboot oem unlock 5019482736699543
(these are the numbers the website generated for your specific Identification# copy and paste from the wordpad document 'bootloadercode' It is the 16 digit long code.
Your device will factory reset do not unplug the device until complete.
unplug the device and redo the initial setup. Once complete repeat step 5 to enable USB debugging
Step 9:
Plug the device back into your computer, open the cmd prompt window and type
adb reboot bootloader
FLASHING CUSTOM RECOVERY:
locate the twrp-3.0.2-0-kiwi.img we placed in the folder on your desktop
to ensure you dont misstype anything in the command prompt type:
fastboot flash recovery then drag and drop the twrp-3.0.2-0.img file from the desktop folder to the cmd prompt
It will look something like this:
fastboot flash recovery C:\Users\Name\Desktop\KIWISDK\twrp-3.0.2-0-kiwi.img
**BE SURE THERE IS A SPACE BETWEEN recovery and C:\**
Hit enter.
Once complete type:
fastboot reboot
Step 10:
Let your phone fully reboot, once rebooted Power off your phone.
NANDROID BACKUP - THE MOST IMPORTANT STEP
1) With the phone off hold volume up , the while holding volume up press and hold the power button. You will see the boot logo come up hold for about 2 seconds more and release ( just to ensure )
2)Your phone will boot into TWRP Recovery
3) PRIOR TO FLASHING ANYTHING: Click Backup
Select your External SD card to backup too.
Swipe to backup.
once the STOCK ROM is backed, you can flash the superSU zip from your sd card rooting the stock rom, be sure to wipe cache/dalvik before rebooting.
If you choose to flash a custom rom you placed on your SD card: once stock is backed up:
1. Go to wipe and swipe to wipe stock
2. hit back and go to install
3. select the ROM file you wish to flash
4. select the gapps file
5. you can include SU even if rom is already rooted
wipe cache/dalvik and then reboot. Happy flashing!
will update screenshots and pics soon
this is a holding place
Thanks for this guide. I created an account but for the past 3 days I get the sorry, the server is busy..... Message on every phone and browser I've tried. I tried 3 phones, 7 browsers a windows laptop and an iPad and iPhone they all give me the same silly message after I hit the agree button to the unlock terms and conditions.
What have I done to screw up such an easy process?
954wrecker said:
Thanks for this guide. I created an account but for the past 3 days I get the sorry, the server is busy..... Message on every phone and browser I've tried. I tried 3 phones, 7 browsers a windows laptop and an iPad and iPhone they all give me the same silly message after I hit the agree button to the unlock terms and conditions.
What have I done to screw up such an easy process?
Click to expand...
Click to collapse
Did you try the link I provided?
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
954wrecker said:
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
Click to expand...
Click to collapse
Was merely trying to delute the guide to a step by step process leaving out no details for people not familiar with root.
954wrecker said:
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
Click to expand...
Click to collapse
Did the link work for you? I fixed some link issues in my html link I hope it works as flawlessly for everyone as it did myself.
The page looked the exact same when I agreed to the huge list of terms, but yours took me to the correct place to get the unlock code instead if the servers are busy page. Thanks for the help
Stuck on stock for 3 days really makes the non stock ROMs 10000% smoother! That emui is a trainwreck, it's going to be impossible to go back to that mess.
kobos311 said:
I've noticed since I've followed the thread the days prior to my device arriving many have struggled to follow the current guides available. I am not responsible for your inability to read, bricked, or internally explosions on devices.
Step 1:
Go to your desktop and create a new folder I labeled mine 'KIWISDK' but you can call it whatever you want. This is where you will store all files during this process so you can easily access them.
Step 2:
Create and save a blank Wordpad/Word document into the newly created folder on the desktop title it 'bootloadercode'
Step 3:
Assuming you're not android developers or have the massive android SDK on your computers you need to download and install adb and fastboot from here.
Go ahead and put the installer in that folder just for safe keeping, run the exe to natively install adb/fastboot from anywhere on your PC. We will use this a few steps later.
Step 4:
Prior to unlocking your bootloader we have to do a few things first. Go ahead and power on your phone and go through the initial setup process.
You can use the following link (corrected from all the other ones) to create a new Huawei account (click register for free below the login. This website can be found here
Once you've created a user ID you can use this same link to access the bootloader unlock page later.
Step 5:
Once your device is fully initialized go to settings>about phone
click the build number 7 times as shown above. It will display a toast notification that you are now a developer.
press the back button (2) up from the about phone area of the settings you will now see
file:///C:/Users/Jesse/Desktop/developeroptions.png
Be sure that the 'developer options', 'enable OEM unlock' and 'USB debugging' toggles are in the on position.
Step 6:
Open the Huawei website posted in step 4. Login and accept the terms.
On your device go to the dialer and type the following into the keypad:
*#*#1357946#*#* Open the bootloadercode document we created in step 2 and record this number here, leave the word pad open to record the unlock code created on the Huawei website.
With the website open,
Carefully go to About Phone> After you select smart phone and type your model number KIW-L24 into the website open your about Phone>Status enter your Serial number and IMEI number (if your IMEI 1 number doesnt work, try again with your IMEI 2 number. Make sure you have all numbers and letters in this step complete with accuracy. DOUBLE AND TRIPLE CHECK.
Product Identification is the number located on the wordpad/word document copy and past it into this area. Generate the unlock code after typing in the pin.
Copy and paste the generated number onto the wordpad document for future reference and save the wordpad document.
Step 7:
Download TWRP revovery from here
Download the 3.0.2.0 version and save it to your folder you created in step 1
Download SuperSU from here
Save it into the folder on your desktop.
Download opengapps here
Save which ever version you choose to your desktop file (I go with Nano and Micro) Be sure to select the ARM64 and android 6.0 versions.
Also at this time download your favorite custom rom from the ROM/Kernel portion of our website and store it in that file (be sure to check if it needs gapps flashed along with it) if it is a CM based ROM it has to have the gapps either way I always like to keep a gapps zip on my SD card.
Step 8:
Plug your phone into your computer, open your external SD card drag and drop the superSU zip, Open Gapps Zip, and rom if you selected one for future access.
open a command prompt (cmd from Cortana or runcmd in earlier versions of windows.
type the following:
adb reboot bootloader
Your phone should reboot with a white screen, once it has type the following:
fastboot oem unlock 5019482736699543
(these are the numbers the website generated for your specific Identification# copy and paste from the wordpad document 'bootloadercode' It is the 16 digit long code.
Your device will factory reset do not unplug the device until complete.
unplug the device and redo the initial setup. Once complete repeat step 5 to enable USB debugging
Step 9:
Plug the device back into your computer, open the cmd prompt window and type
adb reboot bootloader
FLASHING CUSTOM RECOVERY:
locate the twrp-3.0.2-0-kiwi.img we placed in the folder on your desktop
to ensure you dont misstype anything in the command prompt type:
fastboot flash recovery then drag and drop the twrp-3.0.2-0.img file from the desktop folder to the cmd prompt
It will look something like this:
fastboot flash recovery C:\Users\Name\Desktop\KIWISDK\twrp-3.0.2-0-kiwi.img
**BE SURE THERE IS A SPACE BETWEEN recovery and C:\**
Hit enter.
Once complete type:
fastboot reboot
Step 10:
Let your phone fully reboot, once rebooted Power off your phone.
NANDROID BACKUP - THE MOST IMPORTANT STEP
1) With the phone off hold volume up , the while holding volume up press and hold the power button. You will see the boot logo come up hold for about 2 seconds more and release ( just to ensure )
2)Your phone will boot into TWRP Recovery
3) PRIOR TO FLASHING ANYTHING: Click Backup
Select your External SD card to backup too.
Swipe to backup.
once the STOCK ROM is backed, you can flash the superSU zip from your sd card rooting the stock rom, be sure to wipe cache/dalvik before rebooting.
If you choose to flash a custom rom you placed on your SD card: once stock is backed up:
1. Go to wipe and swipe to wipe stock
2. hit back and go to install
3. select the ROM file you wish to flash
4. select the gapps file
5. you can include SU even if rom is already rooted
wipe cache/dalvik and then reboot. Happy flashing!
Click to expand...
Click to collapse
My PC finds the adb device before I type "adb reboot bootloader" but once in fastboot, it wont find it. How can I fix that?
It's already been found (on the first part) just type fastboot oem unlock fastboot and adb go hand in hand.
Remember once your bootloader is unlocked you will have to go through the initialization process and toggle developer options on again
AsapJuno said:
My PC finds the adb device before I type "adb reboot bootloader" but once in fastboot, it wont find it. How can I fix that?
Click to expand...
Click to collapse
Please follow the guide as stated.dont deviate thank you.
definitely tried that. Wouldn't be commenting if I didn't. Can you help
Pin Code Telephone # no longer works
I've tried a few days to get the PIN code with * # * # 1357946 # * # * however the number no longer works. Is there a new tele # or an alternate way to unlock the bootloader ?
error msg:
Connection problem or invalid MMI code
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
AsapJuno said:
definitely tried that. Wouldn't be commenting if I didn't. Can you help
Click to expand...
Click to collapse
ASAP Juno, it's already detected your device via adb adb/fastboot are linked just type the commands don't worry about checking fastboot.
any other methods for retrieving the pin code ?
jusdef said:
Pin Code Telephone # no longer works
I've tried a few days to get the PIN code with * # * # 1357946 # * # * however the number no longer works. Is there a new tele # or an alternate way to unlock the bootloader ?
error msg:
Connection problem or invalid MMI cod
Click to expand...
Click to collapse
kobos311 said:
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
Click to expand...
Click to collapse
I have both imei's and actually tried with a two different sim cards...AT&T and Google Fi.
I get the same error message since Saturday night., 7/16/16
Does anyone know of any other methods for retrieving the pin code ?
jusdef said:
I have both imei's and actually tried with a two different sim cards...AT&T and Google Fi.
I get the same error message since Saturday night., 7/16/16
Does anyone know of any other methods for retrieving the pin code ?
Click to expand...
Click to collapse
Let me be more clear, not the ones on the box, you need the digital file backed up via nandroid which originally you said you didn't have? The numbers on the box won't help
So when I install SuperSU, wipe, and reboot... it boots back into twrp
kobos311 said:
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
Click to expand...
Click to collapse
kobos311 said:
Let me be more clear, not the ones on the box, you need the digital file backed up via nandroid which originally you said you didn't have? The numbers on the box won't help
Click to expand...
Click to collapse
Wrong user, I didnt say I did not have imei's and I can't do a Nandroid backup if my phone isnt rooted. I'm trying to unlock my bootloader so I can take the steps to root and install TWRP. Huwai site will not let me submit the request without the pin #.
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?