Hi,
Soon (I hope), Flyme 5 will be available for our MX4. So I'd like to know before, how to reinstall flyme without loosing my Philz touch and unlocked BL.
Can I do something like that :
- Download an update.zip
- Convert system.new.dat to system.img
- Copy it to the root of the phone
- Via ADB, flash it with "dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system"
Can this be a good solution to keep Philz touch and unlocked BL ?
Thank you,
Clément
What I have done:
-downloaded MX4 4.2.8.2A (my MX4 is the Chinese version) ZIP, unpacked it in a folder and replaced the stock uboot.img file with the patched one;
-afterwards I have rebuilt the update.zip file with the new folder contents; then I have copied the modified update.zip file to the MX4 internal storage;
-flashed patched MX4 recovery file via FastBoot; got into recovery and flashed the modified update.zip by ticking both boxes (clear data);
My MX4 has booted afterwards just file and I was also able to keep my bootloader unlocked. You should follow these steps when you want to get back to Flyme when you have installed CM12.1 .
I know this method but Flyme 5 come with Android 5.1, patched uboot.img may be incorrect for this firmware no ?
furious.builder said:
Hi,
Soon (I hope), Flyme 5 will be available for our MX4. So I'd like to know before, how to reinstall flyme without loosing my Philz touch and unlocked BL.
Can I do something like that :
- Download an update.zip
- Convert system.new.dat to system.img
- Copy it to the root of the phone
- Via ADB, flash it with "dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system"
Can this be a good solution to keep Philz touch and unlocked BL ?
Thank you,
Clément
Click to expand...
Click to collapse
This probably wont work, I own a mx5 and when you try to go from flyme 5 to flyme 4.5 flashing system partition, it gets stuck at flyme recovery. Probably Flyme 5 requires new Flyme 5 kernel to boot, and it is not compatible with flyme 4.5.
You can also try to put patched uboot to flyme 5 update.zip and flash it, as said before
iicc said:
This probably wont work, I own a mx5 and when you try to go from flyme 5 to flyme 4.5 flashing system partition, it gets stuck at flyme recovery. Probably Flyme 5 requires new Flyme 5 kernel to boot, and it is not compatible with flyme 4.5.
You can also try to put patched uboot to flyme 5 update.zip and flash it, as said before
Click to expand...
Click to collapse
But with patched uboot.img from 4.2.8.2A while flashing Flyme 5 can it cause brick ? :/
furious.builder said:
But with patched uboot.img from 4.2.8.2A while flashing Flyme 5 can it cause brick ? :/
Click to expand...
Click to collapse
I think that it shouldnt cause brick, but maybe Meizu had developed other way to avoid users to unlock bootloader so it causes a brick.. I dont know
I do not think we will ever have a Flyme 5 + unlocked bootloader situation since the only combination right now is 4.2.8.2 + patched bootloader for the same version (patching newer bootloader won't work with current software). So when going to CM I guess it would be always the safest to downgrade to 4.2.8.2.
I think is real, because uboot.img responsible for the initial boot , all as Android is responsible boot.img.
But boot.img on Meizu with closed source.
So the only way will be to flash patched recovery then install official update.zip which will relock BL ? :/
It is the safest option. But you can downgrade to 4.2.8.2 and unlock bootloader to flash roms.
In the case that Meizu locks the downgrade to lower firmwares as they do with the M1 Note, maybe you can flash a lower flyme recovery and flash 4.2.8.2. This is the method to downgrade in M1 Note
Okay I understand But if BL is locked then it's not possible to flash an older stock recovery no ?
Yes, It is possible only if the recovery is from the same version. For example, you can flash chinese flyme recovery but not an international flyme recovery.
But only if boot (kernel) partition have not changed, if not maybe your phone will not boot and you will only can enter to fastboot..
So I dont know what would happen if flashing a Flyme 4.5 chinese recovery in Flyme 5 to downgrade in the case meizu locks the downgrade
Sent from my MX5 using Tapatalk
Okay thank you iicc so we need to wait for Flyme 5
Meizu has said they will not support multilanguaje on chinese roms in Flyme 5, so I think they would not lock the downgrade to Flyme 4.5.
Yeah I know, I'm very disappointed about that... I recommanded Meizu phones to many guys, including my father who doesn't speak English at all, so he bought a MX5 directly from China :/ Very bad choice from Meizu
I got an idea ! Can something like this work ? http://forum.xda-developers.com/showthread.php?t=2387941
furious.builder said:
I got an idea ! Can something like this work ? http://forum.xda-developers.com/showthread.php?t=2387941
Click to expand...
Click to collapse
Mmm probably yes, is a good idea.
Other way to do faster is flashing Flyme 5 system.img using "dd", turn down the phone, boot into the fastboot mode, flash boot.img from Flyme 5 and reboot.
Sent from my MX5 using Tapatalk
I'll try with 4.5.7A
I also read that at every boot Flyme wanted to flash stock recovery, it's not due to system.img nor boot.img ?
Got a problem.... system.img that I extracted from system.new.dat isn't correct so Android Kitchen don't packed it
(It said : NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM)
EDIT : I bypassed the problem I'm uploading the flashable zip for testers
Uploaded : https://mega.nz/#!DR9h0KAQ!ZfWMCbeZrxH7SyxlCeOMA8HT6Ilte51o2z9WbLkauW8
Related
All your actions with the phone is at your own risk. The authors are not liable. This is just your choice.
PLEASE read full instructions before you start.
RECOMMENDED ONLY FOR EXPERIENCED USERS.
This was tested ONLY on MEIZU MX4 and ONLY FIRMWARE 4.2.8.2A, ANY OTHER FIRMWARE/PHONE - YOU WILL RECEIVE BRICK PHONE.
(с)
ONLY FOR MEIZU MX4 AND ONLY FIRMWARE 4.2.8.2A. Don't use the that apk on Lollipop or your device will brick
Hello everyone, i changed chinese apk for unlock bootloader, and replaced chinese recovery, on TWRP 2 8.6.0 recovery.
1. Download Flyme OS 4.2.8.2A stock firmware an official webpage Meizu
2. Flash it in stock recovery and select WIPE DATA
3. Get root permission
4. Download and install that APK - drive.google.com/open?id=0B_Gd_o_kBWgLNHFuZW5kMlFzV2s
5. Open that app, and provide root permission.
6. Press "Press to UNLOCK BootLoader" - and wait, you will see "Unlock Finished"
7. After, will be available recovery mode, and you press to "Enter Recovery Mode"
8. Your phone reboot and enters for normal recovery - TWRP 2.8.6.0.
Thanks for the great work!
At last we're getting closer to opening up our meizu phones.
Can the phone with this, unlocked bootloader flash "I" international roms from OTA?
How to relock?
ideosx5 said:
How to relock?
Click to expand...
Click to collapse
Reflash FLyme rom (with Flyme recovery, be carefull!)
Or flash stock uboot
Successfully upgraded MX4 "A" edition phone to "I" using following method:
Installed 4.2.8 "A" stock firmware.
1. Installed apk method unlock (this thread).
2. Downloaded 4.5.7 "I" firmware, extracted and created system.img using (linux):
$ sdat2img system.transfer.list system.new.dat system.img
for windows, see this guide from Meizufans.
3. Boot into fastboot mode (now unlocked) using "VOL -" + "POWER"
4. fastboot flash boot boot.img
WAIT
fastboot flash system system.img
WAIT
5.Reboot into recovery
6. Full wipe
7. Install super su
8. Reboot
VOILA - 4.5.7 "I"
Remember to block/deactivate system updates once system has booted for first time.
Is it possible for someone to upload recovery.img of TWRP please ? I'd like to try
---------- Post added at 10:16 AM ---------- Previous post was at 09:22 AM ----------
I got it, I'm fixing the splash screen dimensions ahah^^
---------- Post added at 11:03 AM ---------- Previous post was at 10:16 AM ----------
It was a little harder than I expected but it's here : http://www.mediafire.com/download/26b963db1k489db/new-recovery.img
Learnincurve said:
Successfully upgraded MX4 "A" edition phone to "I" using following method:
Installed 4.2.8 "A" stock firmware.
Click to expand...
Click to collapse
Good, but there is easy way download that rom, and install it for TWRP(select full wipe, include internal storage) - emmaus.pro/MX4_custom_roms/Flyme/4.5.7i_twrp.zip
and there all stock Flyme roms for twrp - emmaus.pro/?dir=MX4_custom_roms/Flyme
Author all rom "nikk3d" russian 4pda users - 4pda.ru/forum/index.php?showuser=2196261
And this method works even on newest firmware, let's say 4.5.6i downgraded to 4.2.8i via 4.0.4i? Or is a easy variant of previous method, patched uboot by meizu remains after 4.5.6i upgrade if i understand, no matter if you downgrate to Kitkat?
update for TWRP : http://www.mediafire.com/download/f6a65ccpgrfaopw/TWRPr5.img
Changelog :
I corrected "Select storage" position, corrected some shifts on the main screen
zaurikk said:
Good, but there is easy way download that rom, and install it for TWRP(select full wipe, include internal storage) - emmaus.pro/MX4_custom_roms/Flyme/4.5.7i_twrp.zip
and there all stock Flyme roms for twrp - emmaus.pro/?dir=MX4_custom_roms/Flyme
Author all rom "nikk3d" russian 4pda users - 4pda.ru/forum/index.php?showuser=2196261
Click to expand...
Click to collapse
I have an MX4 originally with Ubuntu touch, I tried to flash 4.5.7i from emmaus.pro.
It failed, updater binary error. I checked the recovery log and it says write error, no space left.
Does anybody have any clue?
Thanks,
Note: I already tried a wipe out (even internal storage). No issues with the cyanogenmod roms from emmaus.pro.
Is someone trying to make fom Meizu MX5?
Sent from my MX5 using Tapatalk
itresw said:
I have an MX4 originally with Ubuntu touch, I tried to flash 4.5.7i from emmaus.pro.
It failed, updater binary error. I checked the recovery log and it says write error, no space left.
Does anybody have any clue?
Thanks,
Note: I already tried a wipe out (even internal storage). No issues with the cyanogenmod roms from emmaus.pro.
Click to expand...
Click to collapse
i think, mx4 ubuntu touch version, and standard china version, - internal partitions(storage) name - different, so you gives write an error.
isko01 said:
Is someone trying to make fom Meizu MX5?
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
Now it is impossible.
zaurikk said:
Now it is impossible.
Click to expand...
Click to collapse
Thanks for reply . Can I know how much is good Caynogenmod on MX4? Is everything working good?
Sent from my MX5 using Tapatalk
isko01 said:
Thanks for reply . Can I know how much is good Caynogenmod on MX4? Is everything working good?
Sent from my MX5 using Tapatalk
Click to expand...
Click to collapse
Yep, all needed function now it work - gsm module, wi-fi, bluetooth and etc.
The only problem, that ROM not officially for Cyanogen team, that rom created by ordinary users and updated 1-2 times on month.
i tried on M2 note, i suppose it bricked.is it possible earlier condition working?i look up some unbrick videos, can repairs make my phone working?thanks.
No way to unbrick it, this is for MX4 not M2 Note !!! You'll need to change the motherboard, sorry
zaurikk said:
Yep, all needed function now it work - gsm module, wi-fi, bluetooth and etc.
The only problem, that ROM not officially for Cyanogen team, that rom created by ordinary users and updated 1-2 times on month.
Click to expand...
Click to collapse
Thanks to all user's who making this for MX4. They are really engineers! I hope they will try for MX5.
Yes, the problem it is not official, and we cant get new update.
Why we don't write a email to Canynogen and tell them that we open the bootloader and put CM. But we want they make CM for MX4 and MX5, with new CM and updates?
Sent from my MX5 using Tapatalk
my meizu is bricked, ne response please help me
hi someone had tested this app already? is it surely gonna work??
and after i will unlock the bootloader i can instal any rom? like Mokee and CM12.1??
THIS GUIDE IS FOR ALL MIUI BASED ROMS WHETHER IT IS OFFICIAL, UNOFFICIAL(Xiaomi.eu,sphinx) OR MODDED(smiui).This is for the people who unlocked bootloader through the unofficial way.
http://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-waiting-permission-t3349886
People with officially unlocked bootloader can also try just to be on safer side...nothing to lose right?
Many people after unlocking their bootloaders flashed miui recovery/fastboot roms through twrp/miflash and got their device hardbricked with locked bootloader, which is a pretty messed up situtation, (follow this guide if you are a victim
http://en.miui.com/thread-245347-1-1.html
) and the only way to unbrick from that state is test-point method which voids warranty of course. Others who flashed fastboot roms with default recovery using miflash ends up with locked bootloader too, so I'm gonna share steps by which you can flash full recovery/fastboot roms and not get harbricked/locked bootloader:-
1) First let me tell you why it happens, every recovery rom zip file has a firmware-update folder containing a emmc_appsboot.mbn file, that file relocks bootloader everytime a full rom recovery rom is flashed, fastboot roms also have the same emmc_appsboot.mbn file.
2) To flash recovery roms through twrp, delete the emmc_appsboot.mbn file from the firmware_update folder inside the rom zip file, and then flash rom. Winrar works best, open the recovery zip file with winrar and open firmware-update folder and right click on the emmc_appsboot file and select delete, wait for it to complete(takes some time). For fastboot roms extract the download fastboot file and delete the file emmc_appsboot.mbn file from the images folder. Also in order to keep your desired recovery like TWRP intact, delete the recovery.img file. Edit :- Tested it on my Redmi note 3 pro, deleting only the emmc_appsboot.mbn file works, no need of deleting entire firmware-update folder.
3) To update roms, first download OTA through updater app (or download it from pc) and then open the OTA zip file (located inside downloaded roms folder) and delete emmc_appsboot.mbn file inside the firmware-update folder and then flash through twrp. OTA's can relock bootloader and hardbrick(as it happened in Mi4c).Can't flash OTA due to build fingerprint error? Follow this guide
http://en.miui.com/thread-262947-1-1.html
4) After flashing rom through twrp, flash modified boot.img specific for that miui version, or else you will get bootloop. Guide to make modified boot.img http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
Original Boot.img is located inside recovery rom zip.For those who dont want to do it manually, link for downloading modified boot.img
http://miuidroid.com/rn3/boot_images/
(credits to magdag)
It is required to flash modified boot.img even if you updated through OTA.
P.S:- I've tested all this using my Redmi note 3 pro, should work on other devices too. Any suggestions for improving the guide is welcome.
If I helped pressing thanks won't cost you a thing.:good:
Can you update or post the modded boot image for latest SD 7.2.3.0 Stable global rom?
I have 7.1.8. global rom with officially unloced botloader and TWRP. If I want to install the update I just download the OTA from the updater app in my phone, then remove the emmc_appsboot.mbn and flash. Do I need to flash a modified boot image after that?
anshude1 said:
Can you update or post the modded boot image for latest SD 7.2.3.0 Stable global rom?
Click to expand...
Click to collapse
okay give me sometime, I'll upload on gdrive
Rajdip said:
okay give me sometime, I'll upload on gdrive
Click to expand...
Click to collapse
here you go
https://drive.google.com/open?id=0B5bSNUUrjm6JSk1lZWx5VlRqbkU
Can you please make a modified boot.img for China Stable?
sanuj.bhatia said:
Can you please make a modified boot.img for China Stable?
Click to expand...
Click to collapse
will do
Edit:- https://drive.google.com/open?id=0B5bSNUUrjm6JQTZscE5YZUhuNlE this for china stable 7.2.2.0
Rajdip, you wrote to first flashing rom through twrp and after that flash modified boot.img. How can I flash file boot.img through twrp?
Maby can I copy midified boot.img into rom zip file and after flashing rom?
KrzysiekGP said:
Rajdip, you wrote to first flashing rom through twrp and after that flash modified boot.img. How can I flash file boot.img through twrp?
Maby can I copy midified boot.img into rom zip file and after flashing rom?
Click to expand...
Click to collapse
img file can flashed via TWRP, when you select install option on TWRP , look for "install image" option on right bottom part of screen, now select the modified img and then select boot and then flash.
Rajdip said:
will do
Edit:- https://drive.google.com/open?id=0B5bSNUUrjm6JQTZscE5YZUhuNlE this for china stable 7.2.2.0
Click to expand...
Click to collapse
Can you make one for the latest 7.2.3?
sanuj.bhatia said:
Can you make one for the latest 7.2.3?
Click to expand...
Click to collapse
Look at post # 5... The link is already there for 7.2.3
i've succes flash official rom v stable cn 7.2.3.0...but i 've problem cannot turn on wifi....any idea how to fix it?
Rajdip said:
THIS GUIDE IS FOR ALL MIUI BASED ROMS WHETHER IT IS OFFICIAL, UNOFFICIAL(Xiaomi.eu,sphinx) OR MODDED(smiui).This is for the people who unlocked bootloader through the unofficial way.
http://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-waiting-permission-t3349886
People with officially unlocked bootloader can also try just to be on safer side...nothing to lose right?
Many people after unlocking their bootloaders flashed miui recovery/fastboot roms through twrp/miflash and got their device hardbricked with locked bootloader, which is a pretty messed up situtation, (follow this guide if you are a victim
http://en.miui.com/thread-245347-1-1.html
) and the only way to unbrick from that state is test-point method which voids warranty of course. Others who flashed fastboot roms with default recovery using miflash ends up with locked bootloader too, so I'm gonna share steps by which you can flash full recovery/fastboot roms and not get harbricked/locked bootloader:-
1) First let me tell you why it happens, every recovery rom zip file has a firmware-update folder containing a emmc_appsboot.mbn file, that file relocks bootloader everytime a full rom recovery rom is flashed, fastboot roms also have the same emmc_appsboot.mbn file.
2) To flash recovery roms through twrp, delete the emmc_appsboot.mbn file from the firmware_update folder inside the rom zip file, and then flash rom. Winrar works best, open the recovery zip file with winrar and open firmware-update folder and right click on the emmc_appsboot file and select delete, wait for it to complete(takes some time). For fastboot roms extract the download fastboot file and delete the file emmc_appsboot.mbn file from the images folder. Also in order to keep your desired recovery like TWRP intact, delete the recovery.img file. Edit :- Tested it on my Redmi note 3 pro, deleting only the emmc_appsboot.mbn file works, no need of deleting entire firmware-update folder.
3) To update roms, first download OTA through updater app (or download it from pc) and then open the OTA zip file (located inside downloaded roms folder) and delete emmc_appsboot.mbn file inside the firmware-update folder and then flash through twrp. OTA's can relock bootloader and hardbrick(as it happened in Mi4c).Can't flash OTA due to build fingerprint error? Follow this guide
http://en.miui.com/thread-262947-1-1.html
4) After flashing rom through twrp, flash modified boot.img specific for that miui version, or else you will get bootloop. Guide to make modified boot.img http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
Original Boot.img is located inside recovery rom zip.For those who dont want to do it manually, link for downloading modified boot.img
http://miuidroid.com/rn3/boot_images/
(credits to magdag)
It is required to flash modified boot.img even if you updated through OTA.
P.S:- I've tested all this using my Redmi note 3 pro, should work on other devices too. Any suggestions for improving the guide is welcome.
If I helped pressing thanks won't cost you a thing.:good:
Click to expand...
Click to collapse
Currently I'm on 6.4.14 (CHINA LATEST DEV ROM) ,Can i use 6.4.14 Fastboot ROM in place of 7.1.8 Global stable rom to unlock using unofficial method . After unlocking bootloader , i want to directly upgrade to latest global stable rom 7.2.3.0 with TWRP and root. I have recovry ROM (OTA) of 7.2.3.0 .
What would be the appropriate steps to do that without any problems ?
Please tell me step by step as i will follow exactly that steps and don't want to risk even a bit by using my half knowledge . I know i have to read the guide but i get lost in between , would appreciate if you could tell me exact steps .
akhil17kr said:
Currently I'm on 6.4.14 (CHINA LATEST DEV ROM) ,Can i use 6.4.14 Fastboot ROM in place of 7.1.8 Global stable rom to unlock using unofficial method . After unlocking bootloader , i want to directly upgrade to latest global stable rom 7.2.3.0 with TWRP and root. I have recovry ROM (OTA) of 7.2.3.0 .
What would be the appropriate steps to do that without any problems ?
Please tell me step by step as i will follow exactly that steps and don't want to risk even a bit by using my half knowledge . I know i have to read the guide but i get lost in between , would appreciate if you could tell me exact steps .
Click to expand...
Click to collapse
Yeah you can use china dev rom for unlocking bootloader, and after that to upgrade to global 7.2.3.0 you need a full recovery rom, OTA wont work, also WHENEVER YOU DOWNLOAD A OTA/ROM OPEN IT WITH WINRAR, OPEN THE FIRMWARE-UPDATE FOLDER AND DELETE THE emmc_appsboot.mbn file or else you will hardbrick your device and the only wasy from recovering from it is by opening your phone
Mayoz said:
i've succes flash official rom v stable cn 7.2.3.0...but i 've problem cannot turn on wifi....any idea how to fix it?
Click to expand...
Click to collapse
Did you flash the modified boot.img of 7.2.3.0?
Rajdip said:
Yeah you can use china dev rom for unlocking bootloader, and after that to upgrade to global 7.2.3.0 you need a full recovery rom, OTA wont work, also WHENEVER YOU DOWNLOAD A OTA/ROM OPEN IT WITH WINRAR, OPEN THE FIRMWARE-UPDATE FOLDER AND DELETE THE emmc_appsboot.mbn file or else you will hardbrick your device and the only wasy from recovering from it is by opening your phone
Click to expand...
Click to collapse
Hi , can you make sure again that China dev ROM will work in place of stable 7.1.8.0 without any problem ?
Also 7.2.3.0 which I've is full ROM i think it's "miui_HMNote3ProGlobal_V7.2.3.0.LHOMIDA_74136dde89_5.1.zip" and it is 0.99 GB in size.
So after unlocking bootloader , i can normally boot into current china dev ROM and directly upgrade to 7.2.3.0 through updater app with just emmc_appsboot.mbn deleted from it ?
I guess there is no need to delete boot.img as i still haven't flashed the twrp and root yet and will flash both of files after upgrading to 7.2.3.0 .
Plz tell if my steps are correct or not ?
akhil17kr said:
Hi , can you make sure again that China dev ROM will work in place of stable 7.1.8.0 without any problem ?
Also 7.2.3.0 which I've is full ROM i think it's "miui_HMNote3ProGlobal_V7.2.3.0.LHOMIDA_74136dde89_5.1.zip" and it is 0.99 GB in size.
So after unlocking bootloader , i can normally boot into current china dev ROM and directly upgrade to 7.2.3.0 through updater app with just emmc_appsboot.mbn deleted from it ?
I guess there is no need to delete boot.img as i still haven't flashed the twrp and root yet and will flash both of files after upgrading to 7.2.3.0 .
Plz tell if my steps are correct or not ?
Click to expand...
Click to collapse
What about you use the miui global 7.2.3.0 directly for unlocking bootloader the unofficial way? after that you can flash TWRP if you want, and you cant update using updater app, you have to update directly from TWRP.
anshude1 said:
Look at post # 5... The link is already there for 7.2.3
Click to expand...
Click to collapse
I guess that boot.img is for Global Stable 7.2.3!?
Rajdip said:
What about you use the miui global 7.2.3.0 directly for unlocking bootloader the unofficial way? after that you can flash TWRP if you want, and you cant update using updater app, you have to update directly from TWRP.
Click to expand...
Click to collapse
Well to do that i have to download again the GB of flashboot rom of miui global 7.2.3.0 and i really have painful slow internet so thought of first unlocking bootloader and then later upgrade through Recovery zip file.
What do you suggest for best way as i just don't want to f**k up my device..
So if updater app can't flash the Official MIUI roms even with unlocked bootloader then what's the point of recovery ROM of different types such as global stable,beta china stable beta if you want to switch ROM's ?
Why in redmi note 3 there are so hurdles to switch /downgrade/upgrade ROM after unlocking bootloader ? I have done all flashing stuff on some other android phones too but there was never a risk for relock of bootloader and overwrite of custom recovery while flashing ROMS ..so why all this hurdles in Redmi Note 3 as it doesn't make sense to unlock bootloader after each and every upgrade /downgrade of ROM's or it is only due to the fact that it has been unlocked through unofficial way ?
akhil17kr said:
Well to do that i have to download again the GB of flashboot rom of miui global 7.2.3.0 and i really have painful slow internet so thought of first unlocking bootloader and then later upgrade through Recovery zip file.
What do you suggest for best way as i just don't want to f**k up my device..
So if updater app can't flash the Official MIUI roms even with unlocked bootloader then what's the point of recovery ROM of different types such as global stable,beta china stable beta if you want to switch ROM's ?
Why in redmi note 3 there are so hurdles to switch /downgrade/upgrade ROM after unlocking bootloader ? I have done all flashing stuff on some other android phones too but there was never a risk for relock of bootloader and overwrite of custom recovery while flashing ROMS ..so why all this hurdles in Redmi Note 3 as it doesn't make sense to unlock bootloader after each and every upgrade /downgrade of ROM's or it is only due to the fact that it has been unlocked through unofficial way ?
Click to expand...
Click to collapse
This is what xiaomi made of themselves, every move is f*****g hassle right now. I understand the problem of slow internet. You have unlocked bootloader right? why dont you just leave MIUI and install the AOSP rom. no more hassle no bricks.
**All credit to @shakalaca for his dedication. Also thanks to Enjie in Taiwan Asus Zentalk forum.
**Do it at your risk
This guide is to help you flash custom rom, like CM 13, in unlocked Android 6.0.
The point of this thread is to pack signature files into TWRP and boot.img so that we can boot from custom roms.
This thread won't be needed if TWRP/Custom Rom patch into MM the signature file in the future. For now, sorry for the mess.
1.Add signature to TWRP
a. Download your favorite twrp. The latest official twrp is doable.
b.Download and unzip the attached file: recovery_z00a.sig
c.Copy the above 2 files in the same directory.
d.Activate cmd window in your pc (window button + R, type cmd, Enter)
e.Add signature to TWRP in cmd window: (Suppose you put all files in c:\) , replace <twrp.img> with your TWRP file name.
Code:
cd c:\
copy /b <twrp.img> + recovery_z00a.sig recovery_mod.img
Now you will see a new file, recovery_mod.img created.
2.Add signature to boot.img
a. Unzip and extract boot.img from custom rom.
b. Download and unzip the attached file: boot_z00a.sig
c.Copy the above 2 files in the same directory.
d.Activate cmd window in your pc (window button + R, type cmd, Enter)
e.Add signature to boot.img in cmd window: (Suppose you put all files in c:\)
Code:
cd c:\
copy /b boot.img + boot_z00a.sig boot_mod.img
Now you will see a new file, boot_mod.img created.
3.Unlock MM6.0.
Refer to this thread. This is a 2 click unlock procedure. The device should be unlocked before we can flash twrp and custom rom.
4. After the device is unlocked, in bootloader, flash TWRP recovery now:
Code:
fastboot flash recovery recovery_mod.img
5. Boot from TWRP
6. Flash custom rom from TWRP
7. After done flashing custom rom in TWRP, flash boot_mod.img from TWRP.
Or, from bootloader:
Code:
fastboot flash boot boot_mod.img
8.Reboot system.
*My suggestion is to put the revised kernel in SD card. Later on If you upgrade custom rom, it is easier to flash the repacked boot_mod.img again in TWRP.
god bless you
Thanks But is there any way I can add the signature in kernel and recovery in android without pc. Can I use those commands in android terminal?
Thanks,man
pless support Z008
MrPhamHpGYC said:
pless support Z008
Click to expand...
Click to collapse
Z008 files
Any other easy method for noob like me please..
Sent from my ASUS_Z008 using XDA-Developers mobile app
kjinx01 said:
Any other easy method for noob like me please..
Sent from my ASUS_Z008 using XDA-Developers mobile app
Click to expand...
Click to collapse
It won't be easy unless TWRP and Custorm Roms patch the signature files with them. Maybe we should wait after ASUS roll out its official release.
i try step by step and its work , i flash blurOS on my marshmallow based zenfone . thanks for your hardwork mate
Thanks a lot!!! I already wanted to throw this damn Z00A against the next wall, since neither 5.0 nor 6.0 were working flawlessly. But CM13 is fantastic! Best rom so far. Will never go back to stock.
delete
which rom do i use? can i use cm13 to get the boot.img file
Guys, I want to root my Z00A (MM beta -- .111 build). Is there a way without unlocking the bootloader?
Also I want to know whether the Asus official bootunlocker tool can be used in this MM .111 build so that I can flash CM13 instead.
Thanks in advance.
rohithramesh96 said:
Guys, I want to root my Z00A (MM beta -- .111 build). Is there a way without unlocking the bootloader?
Also I want to know whether the Asus official bootunlocker tool can be used in this MM .111 build so that I can flash CM13 instead.
Thanks in advance.
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/zenfone2/general/android-6-0-beta-root-xposed-downgrade-t3404321
Hi. where I can find more modern sig keys? I make custom kernel for marshmallow and use old ramdisk from 4.21.40.61 firmware. If I take ramdisk from boot.img from newer firmware and tnen pack back into boot.img, then to sign boot.img, device can't start. I suppose the reason of this- incompatible key?
Hi,
How could I manually sign these files on Ubuntu-based OS? I'm no longer use Windows as my daily OS. Thanks.
Also: Could anyone provide MM final signature keys?
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Also: Could anyone provide MM final signature keys?
Click to expand...
Click to collapse
yes, I get it and use it for sign my lastest kernels. for recovery sign you may use old keys, it compatible
Hi guys , my zf2 is unlocked and rooted ( MM stock .134 )
Is possible sign stock boot.img and stock recovery.img for pass the verification on boot ??
siteswap said:
Hi guys , my zf2 is unlocked and rooted ( MM stock .134 )
Is possible sign stock boot.img and stock recovery.img for pass the verification on boot ??
Click to expand...
Click to collapse
That's what I want to know. And, I want to know too if there is any ota for the marshmallow, and want to flash it, the bootloader needs to be relocked or not? And, dont need to un- systemless root+xposed, right?
Someone who uses MM beta before and succesfully flash ota with unlocked bootloader + systemless root and xposed can you confirm me please?
Sent from my ASUS_Z00A using Tapatalk
I used MM beta, and after that i update to MM ( .134 ) official Fw , and my bootloader was locked.
For unlock+root i used shakalaka metod in xda index.
At moment the last ota that you can find is .134 in Asus site , but i dont know if in future the new ota will relock bootloader
UPDATE: This is now unneeded because threr is a faster way ro unlock bootloader on official MM here, he updated for official MM
Hi, I discovered an unlock method for official MM!! This maybe long but's it totally safe
You need:
Adb and fastboot environment ready PC
LP RAW File
Android 6.0 Beta Unlock tool
Android 5.0 One-Click Unlock tool
First version of beta MM (Z00A) (Z008)
Official MM zip (find it on Asus site)
Thanks to all people upload these links
Just do the following:
Flash the lastest LP via AFT (using raw file given above), wipe all data. If you already on MM, you have to downgrade
Unlock your bootloader using 1 click tool given above
Boot to stock recovery and sideload the first version of beta MM
Unlock the bootloader using MM beta unlock tool above
Boot to stock recovery
Two case here:
Case 1: You can't boot stock recovery
Normally boot your phone (to Android)
Setup it as a new phone
If it shows there is a new firmware, don't update!!!
Enable Developer options, then enable usb debugging
Copy the official MM zip to external sd card
Open command prompt, run adb reboot recovery, accept the adb permission if prompted
After it boots to recovery, select Apply update from SD, then choose the zip file you've copied before
Wait for it to update, it may stuck at flashing splashcreen, don't worry, it's trolling you, may be Asus forgot to update the script
Goto step 7
Case 2: You can boot stock recovery
Sideload the official MM zip (adb sideload <filename>.zip)
Goto step 7
7. Flash this TWRP (fastboot flash recovery <twrp>.img)
8. Root your phone using this method
9. Reboot, if it shows "Your phone has failed verification bla bla..", then you've success. It may reset loop like note 7 in the first time start, don't worry.
9. Enjoy :highfive:
Note: If you're facing with battery problems on MM, factory reset it in Settings > Backup and Reset > Factory Reset > Erase everything
Successfully on my ZE550ML
The warning screen is normal so don't worry and there is no way to fix it for now
Reverse
Reverse #2
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
NiTesh said:
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, BL will be relocked once you upgrade to MM.
If you want to unlock MM BL(6.0), refer to this thread.
Or you can downgrade to Lollipop referring to this thread. Then your BL(5.0) is unlocked.
Upgrade to MM
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
R3D SoX F4N said:
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
Click to expand...
Click to collapse
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
can anyone please upload official recovery for Zenfone 2 ZE551ML, currenty i have twrp installed on Android version 5.0 LP Stock
HungNgocPhat said:
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
Click to expand...
Click to collapse
i have twrp recovery at the moment cause i followed mr_gouvad2000 tuturial..
what do you sugest?
flash WW_ZE551ML_2.20.40.196_20160815.raw?
WW_ZE551ML_2.20.40.194_20160713.raw?
and then go and do what you told?
cheers
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
tridet18 said:
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
Click to expand...
Click to collapse
someone correct me if i am worng but....
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Look for this version WW-4.21.40.134
Hello, thank you but this version is official, i need de first beta 6.0
R3D SoX F4N said:
someone correct me if i am worng but....
Look for this version WW-4.21.40.134
Click to expand...
Click to collapse
that version...i can´t find it anywere..maybe someone here knows were to find it?
Updated the first MM beta link in OP
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
tridet18 said:
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
Click to expand...
Click to collapse
Have you downloaded the correct build? There are build for MM bootloader, if you flash the normal builds, it will fail and reboot to recovery again. Gapps is the same for all builds
After you install that special build, do not update to newer nightlies, it will fail. For updates, check the link i give you and see if there is a new MMBL build.
About that, here is the post: http://forum.xda-developers.com/showpost.php?p=68542370&postcount=8551
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
tridet18 said:
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
Click to expand...
Click to collapse
Run the script again (i gave you in above post). Download the CM13 in that link, not in the OP of CM13 thread. Flash that CM13 and Gapps (Gapps is universal for MMBL and LPBL).
May be you have corrupt download, I'm currently running CM13 on MMBL
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
hlp
tridet18 said:
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
Click to expand...
Click to collapse
how u unlocked bootloader
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Shahaf said:
Hello,
I tried to root my 9T(model M2010JI9SG) following this guide:
I used twrp from this link:
Xiaomi Mi 9T / Redmi K20
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
version 3.5.2_9-0
after I flashed twrp, I got into fastboot mode, which I can't leave.
I tried doing volume up +power, volume down+ power, and all the buttons as well, nothing worked, every time it goes back to fastboot,
I tried to redo everything, still didn't fix, and tried to flash stock via mi tool, didn't work too.
Please help me fix that,
Thanks!!!
Click to expand...
Click to collapse
OMG
You should first of all know your phone model
"Redmi 9T" reads as different name than "Mi 9T", isn't it?
Hence you MUST NEVER flash TWRP for Redmi K20/Mi 9T (guide clearly says it is for that phone, check the big picture in your post) to your Redmi 9T
oh damn, I can fix that somehow?
Shahaf said:
oh damn, I can fix that somehow?
Click to expand...
Click to collapse
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
zgfg said:
Check on twrp.me is there TWRP for your Redmi 9T
Or download the so called Fastboot/TGZ ROM for your M2010JI9SG, extract recovery.img (stock Recovery) and flash it back over the wrong TWRP
For more details search on XDA for Redmi 9T subforum (this one is for Mi 9T), there should be users and freaks who can better help you for the same phone
Click to expand...
Click to collapse
Thank you, I will check with them!
Shahaf said:
Thank you, I will check with them!
Click to expand...
Click to collapse
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
zgfg said:
Here you can find firmwares for lime:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
You should (?) know what was your installed firmware, download the same Fastboot/tgz and extract (TGZ=Tar+GZIP) your original stock recovery.img, and flash it from Fastboot (just like you flashed the wrong TWRP)
You could also use MiFlash tool to flash the whole firmware, but it must be not needed
Click to expand...
Click to collapse
It worked!!! now my device is working, now in order to root, which twrp should I use?
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
zgfg said:
You don't need TWRP. Extract boot.img (like you extracted recovery.img). Install Magisk apk and use the method Install (Magisk), then Select and patch your boot.img (do not tick Recovery option)
Find the patched img in Download folder, transfer to PC and flash from Fastboot - this time to boot partition, not to recovery partition
If anything goes wrong, flash back the stock boot img
Btw, on that Redmi 9T, do you have A12 (or A11 or what) and is it MTK chipset?
Generally, use Magisk Stable v23 from TJW:
Magisk/README.MD at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
But if A12 or MTK and if it ain't work, you can try Magisk Alpha ('pilot' builds for the new Magisk to be soon? released)
Click to expand...
Click to collapse
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Flash (not boot) a healthy un-patched stock "boot.img" that is signed with your ROM version to the device and see if that works.
Shahaf said:
I tried to do it, after I patched boot.img I transfered it to my PC and did fastboot boot boot_patched.img
it did ok on sending, but then failed on booting(unknown command), any fix for that?
Click to expand...
Click to collapse
fastboot boot xxx.img boots one time to the xxx.img
For flashing (permanently) to boot you need to use:
fastboot flash boot xxx.img
Before flashing the 'stock' or patched boot img, pls double check: compare your firmware name in Settings / My device against the fastbboot/tgz package you downloaded and extracted the boot.img from
Recovery images might be the same for several firmwares, but boot.img is more critical. If extracted from the wrong firmware, it will not be your real stock boot.img and will not boot
You can use this app (now when your phone boots) to download and look for the proper firmware:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Shahaf said:
It worked!!! now my device is working, now in order to root, which twrp should I use?
Click to expand...
Click to collapse
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
zgfg said:
I would trust to the following thread on Xiaomi.eu forum, to find the suitable TWRP for your device.
Post #1, link to AFH, then scroll to lime (if that's the code name for your Redmi 9T):
[TWRP][RECOVERY] List of relevant recovery in one place
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/ I have compiled a list of relevant recovery in one place, i think it will be useful. Updates are monitored each day. Welcome, friends! How to install TWRP https://xiaomi.eu/community/threads/installing-a-custom-recovery.67841/
xiaomi.eu
Based on experience with my 9T I would pick
twrp-3.5.2_10-3-lime-brigudav.img
I.e., Xoaomi.eu provides weekly and stable firmwares that are usually well ahead of the official firmwares (on my Mi 9T, daily driver and businesses phone I was 9 months on their weeklies until I switched to their Stable two months ago)
The point is that Xiaomi.eu firmwares for most phones (I just checked, Redmi 9T is on the list) require TWRP to flash
That means if people recommend the TWRP as there, it nust be the right one
Once you have TWRP you can back up your boot partition. You will get boot.emmc.win and that will be your exact stock boot.img
You can still use the Patch and Flash method to install Magisk (as described you earlier), by patching that boot.emmc.win
Click to expand...
Click to collapse
it worked! thank you