Related
I just receveid an OTA update, but the installation stuck because the system is rooted.
I found the update.zip file on my Handy, but it contains some directory (Meta-inf, patch and system) and a big file update.app that I believe contais all the update file.
Is it possible to extract the file from update.app and then create an update that can I launche from TWRP? And if so how could I do it?
Thanks
You can't.
flash back a stock recovery.
After ulocking bootloader and root the OTA didn't work with original recovery that's why I wanto to create an update that works with TWRP
did you try?
ItalianWolf said:
did you try?
Click to expand...
Click to collapse
Yes I reinstalled the original recovery that you can find in t he root package and I completely unroot the phone using the unroot command in SuperSu.
Then I launch the update but after reboot it stuck at 11%, so I create the dload folder in my handy memory and copied there the content of update.zip and then forced the update. In this case, after reboot, it load until 99% that it reboot, but the installed version is still the 170 and not the 188.
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
ItalianWolf said:
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
Click to expand...
Click to collapse
What does here mean?
Which thread?
Thanks
Harlock1978 said:
What does here mean?
Which thread?
Thanks
Click to expand...
Click to collapse
Sorry, forgot link: http://forum.xda-developers.com/p8l...-lite-android-6-0-marshmallow-t3305550/page40
You need the Huawei Update Extractor Tool, and do the following:
Load the UPDATE.APP file inside the HUET
Extract boot.img, system.img, and cust.img, from UPDATE.APP inside the HUET
Flash the respective files via Fastboot
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
AmINoS007 said:
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
Click to expand...
Click to collapse
If you have to, flash the B052 recovery... you can always flash the Marshmallow recovery if it doesn't let you update.
I only flashed boot.img, cust.img, and system.img, when I upgraded; didn't flash Marshmallow's recovery at all.
Don't think you can even get OTA updates on the Marshmallow beta anyway (even via a normal bootloader-locked device).
Sorry for my late answer but I was travelling only with a Mac and I couldn't use Huaweu Update extractor.
This are the file that you can find in UpdateApp 188:
00.SHA256rsa.img
01.crc.img
02.curver.img
03.verlist.img
04.efi.img
05.fastboot1.img
06.boot.img
07.recovery.img
08.recovery2.img
11.cache.img
13.dtimage.img
14.dsp.img
15.fastboot.img
16.hifi.img
17.mcuimage.img
18.modemimage.img
19.modemnvm1.img
20.teeos.img
21.trustfirmware.img
And also the following directory:
META-INF
patch
system
Which file should I install, I didn't find a system.img and there are two different recovery
Thanks
You should not install any OTA with TWRP...
Flash back the stock recovery, update, then flash the twrp again, it's way easier and more secure, than doing a flashable zip from an OTA update without knowing what to do with the file within.
The OTA updates usually doesn't contain the SYSTEM.IMG file you are looking for, it contains individual files and scripts to patch up the current system partition to work with the new update.
From the two recoveries you should use the RECOVERY.IMG (the one without the 2 in it).
But again, I do recommend to flash the original recovery(not the one in the update), do the update, and put twrp back.
Where can I find the original recovery from ALE-L21C432B170, so that I can flash the original recovery again?
TIA
I found the original recovery and flashed it then I did a complete unroot and tried again to do the OTA update but it stopped at 11%.
Is there a different way to update?
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.
Hi all,
I currently have a P9 Lite with VNS-L31C432B371 firmware installed.
Recently, I received the VNS-L31C432B381 update via OTA. Unfortunately, when the phone reboots into recovery mode, the update does not even start; instead, I get redirected to the custom recovery (TWRP 3.1.0.-2, system partition read-only) "homescreen".
Is there a way to update to B381 without wiping the entire phone?
Thank you for your time.
The OTA update system uses the EMUI stock recovery so no, there is no way you can update your phone through the updater by using the custom recovery
SALVO9 said:
The OTA update system uses the EMUI stock recovery so no, there is no way you can update your phone through the updater by using the custom recovery
Click to expand...
Click to collapse
Ok, thank you!
Another question: is there a way to obtain the stock EMUI recovery and flash it to execute the update?
_n0153_ said:
Ok, thank you!
Another question: is there a way to obtain the stock EMUI recovery and flash it to execute the update?
Click to expand...
Click to collapse
Yes.
Download your build's update.zip, extract the zip to desktop, you'll then have an update.app (you probably need the full ~2GB build, not OTA, e.g I use B370);
Extract recovery.img from the update.app via HuaweiUpdateExtractor;
boot to bootloader;
fastboot flash recovery recovery.img.
Done.
JHD94 said:
Yes.
Download your build's update.zip, extract the zip to desktop, you'll then have an update.app (you probably need the full ~2GB build, not OTA, e.g I use B370);
Extract recovery.img from the update.app via HuaweiUpdateExtractor;
boot to bootloader;
fastboot flash recovery recovery.img.
Done.
Click to expand...
Click to collapse
Thank you!
I succeeded in extracting and installing the recovery from the update.zip. Unfortunately the OTA failed anyway.
At this point, I think I should just wipe the phone and install the complete update from here.
_n0153_ said:
Thank you!
I succeeded in extracting and installing the recovery from the update.zip. Unfortunately the OTA failed anyway.
At this point, I think I should just wipe the phone and install the complete update from here.
Click to expand...
Click to collapse
Well I , like you, had a custom recovery. The 3-button method didn't work for me and even after restoring the stock recovery I was unable to install the update.
I unpacked the Update.APP file and flashed through fastboot the BOOT, RECOVERY, VENDOR and SYSTEM .img files and I was succesful but now I have the Model number as generic_a15 and Build number NRD90M test-keys. I can only assume some of the other img files carry the information about my phone. At the moment is stable enough but I can't open the Security menu.
If someone has any idea on how to flash the other img files, please let me know
okaar said:
Well I , like you, had a custom recovery. The 3-button method didn't work for me and even after restoring the stock recovery I was unable to install the update.
I unpacked the Update.APP file and flashed through fastboot the BOOT, RECOVERY, VENDOR and SYSTEM .img files and I was succesful but now I have the Model number as generic_a15 and Build number NRD90M test-keys. I can only assume some of the other img files carry the information about my phone. At the moment is stable enough but I can't open the Security menu.
If someone has any idea on how to flash the other img files, please let me know
Click to expand...
Click to collapse
well, if you flash your oeminfo zip, you should get it back
mjz2cool said:
well, if you flash your oeminfo zip, you should get it back
Click to expand...
Click to collapse
I only have old oeminfo.img packages, do you know how I can build one? There is a PRODUCT.img but it is considerably bigger than the oeminfo package that I have seen.
I flashed all the old B370 files, update.zip and update...hw_eu.zip, with DC Phoneix (a non free tool but saved me from.a bricked phone). After that, I flashed the new package and got the Security settings and Developer Options to work again.
Does someone have the original recovery for OREO?
I have TWRP and Magisk Installed and cannot install OTA or FULL-OTA with twrp.
I need the stock recovery for OREO.
I would appreciate if someone can share it.
eRecovery doesn't work for me and I don't want to format the device again (I already bricked it once and don't want to play with HWOTA - testpoint method was needed to get it back to life)
I've extracted the recovery myself
Here is a link for the stock recovery extracted from VKY-L29 8.0.0.365 firmware (for the C432) variant):
http://www.mediafire.com/file/dy4m97771qz6m7z/RECOVERY_RAMDISKB365.img
You can flash the .img file using TWRP (flash it over the recovery partition) - not tested with fastboot.
I was able to update to the last version using the FULL-OTA-PV file and my bootloader is still unlocked, then I flashed twrp, installed magisk and then again flashed the stock recovery for future updates.
USE AT YOUR OWN RISK!!!
Here is a link for the stock recovery extracted from VKY-L29 8.0.0.369 firmware (for the C432) variant):
http://www.mediafire.com/file/77hkxqtlu1f1r52/RECOVERY_RAMDISKB369.img/file
Stock recovery for VKY-L29 (ver c636)
mexusbg said:
Here is a link for the stock recovery extracted from VKY-L29 8.0.0.369 firmware (for the C432) variant):
Hi there. I have TWRP. I need stock recovery for VKY-L29 (ver C636). currently i am on 8.0.0.366 and want to get OTA update. Can i use your C432 variant? i have used Huawei Update extractor to extract the latest update.app but i am getting three recovery files, Recovery_Ramdis, Recovery_Vbmeta and Recovery_Vendor. i dont know which file to use or how to proceed. Any help will be much appreciated. Thank you
Click to expand...
Click to collapse
gucchh said:
mexusbg said:
Here is a link for the stock recovery extracted from VKY-L29 8.0.0.369 firmware (for the C432) variant):
Hi there. I have TWRP. I need stock recovery for VKY-L29 (ver C636). currently i am on 8.0.0.366 and want to get OTA update. Can i use your C432 variant? i have used Huawei Update extractor to extract the latest update.app but i am getting three recovery files, Recovery_Ramdis, Recovery_Vbmeta and Recovery_Vendor. i dont know which file to use or how to proceed. Any help will be much appreciated. Thank you
Click to expand...
Click to collapse
It should work.
Do not use firmware extractor without creating a map for your device.... or you may brick it. The correct partition is recovery_ramdisk
Click to expand...
Click to collapse
Hello guys!
For the may update, a friend sent me a zip archive containing the stock boot.img that I used to flash in twrp when flashing kernels. Now that june update came up.. how can I create one in order to do the same thing? If it's helpful, it had a META_INF folder in it. Thank you in advance!