I had this trouble when I tried to flash a kitkat rom from 4.2.2
For those who had trouble on flashing new roms :
1. Update to the lastest CWM version
2. Flash bootloader makoz20i from http://forum.xda-developers.com/showthread.php?t=2105983&nocache=1
3. Reboot Bootloader
4. Flash ROM
5. Flash GAPPS
6. Flash newest version of SuperSU
And you're all set
just a minor thing but, just the img name of bootloader is 20i, when u install it says 30i.
Related
i was updating my s advance with CyanogenMod 12.1 [26/11/15].........currently i have 4.1 jellybean indian version ddlup8 with root access ........... whenever i went for recovery i install cwm 6.8 it installs for little time only. please tell where i am wrong i want to install 5.1 lollipop on my device, i follow these steps but installation always gets cancel .......
1. i ve rooted my devive
2. i installed recovery cwm
3. i back up my data
4. wipe data
5. wipe cache
6. wipe dalchvik cache
7 then i install cyanogenMOd 11 ( buit it doesnt install)
so i tried directly installing cyanogenMOd 12 with cwm but does work
so please tell me what is the problem and what step should i follow.
I want to install CyanogenMod 12.1 [26/11/15] but error comes like:
apply parsed perms : isetfilecon of /system/lost+
not supported on transport endpoint
set metedata recursive:
E:Error in /sdcard/cm12.1_
(status 7)
installation aborted
Try using TWRP instead of CWM
Patil.sid101 said:
i was updating my s advance with CyanogenMod 12.1 [26/11/15].........currently i have 4.1 jellybean indian version ddlup8 with root access ........... whenever i went for recovery i install cwm 6.8 it installs for little time only. please tell where i am wrong i want to install 5.1 lollipop on my device, i follow these steps but installation always gets cancel .......
1. i ve rooted my devive
2. i installed recovery cwm
3. i back up my data
4. wipe data
5. wipe cache
6. wipe dalchvik cache
7 then i install cyanogenMOd 11 ( buit it doesnt install)
so i tried directly installing cyanogenMOd 12 with cwm but does work
so please tell me what is the problem and what step should i follow.
I want to install CyanogenMod 12.1 [26/11/15] but error comes like:
apply parsed perms : isetfilecon of /system/lost+
not supported on transport endpoint
set metedata recursive:
E:Error in /sdcard/cm12.1_
(status 7)
installation aborted
Click to expand...
Click to collapse
Extract boot.img from cm12.1 zip file
Flash boot.IMG
Reboot recovery
Flash cm12.1 zip file followed by GAPPS
Voilà.. All done
Or you can install this modded CyanogenMod 12.1 with integrated gapps, works on old cwm too: https://www.dropbox.com/s/v41kau37sxyct7i/CM12.1.zip?dl=1
Patlcs said:
Extract boot.img from cm12.1 zip file
Flash boot.IMG
Reboot recovery
Flash cm12.1 zip file followed by GAPPS
Voilà.. All done
Click to expand...
Click to collapse
how to flash boot.img please explain in detail.
currently i have flashed 4.12 stock rom and root.zip
but twrp recovery is not installing and cwm recovery is not working
please help me to update
Patil.sid101 said:
how to flash boot.img please explain in detail.
currently i have flashed 4.12 stock rom and root.zip
but twrp recovery is not installing and cwm recovery is not working
please help me to update
Click to expand...
Click to collapse
you can try to use the temporary CWM recovery to flash the boot.img file.
as i said earlier, extract the boot.img file from the rom file and then flash it via the recovery.
I am faceing the same problem
Patlcs said:
you can try to use the temporary CWM recovery to flash the boot.img file.
as i said earlier, extract the boot.img file from the rom file and then flash it via the recovery.
Click to expand...
Click to collapse
Hi
I am faceing the same problem. Can u Explain in Details how to use CWM recovery to flash the boot.img file ?
souravsadvanced said:
Hi
I am faceing the same problem. Can u Explain in Details how to use CWM recovery to flash the boot.img file ?
Click to expand...
Click to collapse
Wow i didnt think that i would reply to something i said 2 years ago xD
Hmm i am a bit rusty now as i upgraded to the s7 and now note 8 where i have not rooted or installed custom roms for a while so try it at your own risk.
If i recall correctly, you need to extract the boot.img file from cm12.1 using 7zip or winrar on your pc
Then there should be another thread for a temporary cwm recovery. Download the file and flash it when u are in recovery mode.
After flashing that temp cwm file, it should boot into it automatically and then flash cm11 followed by gapps
Last week my K013 bricked , so I follow the tutorial below to unbrick:
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049
when I sideload CN-3.2.23.182 ROM , I have some interested in it and OTA to the CN-3.2.23.201 Version..........
but when I flash back to WW-182 ROM , the problems come
--the Kernel Version stay at CN-3.2.23.201 !
So the recovery Version is CN and will brick if it get any WW OTA
I try several way but not work
here is what I try:
acording to the tutorial
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049
1 .I flash into CN-182 ROM but Kernel Version still CN-201
2. flash into WW-182 ROM but Kernel Version still CN-201
3. flash into CN-182 ROM and then flash into WW-182 ROM......still no work
4. flash via IntelAndroid-FBRL-07-24-2015.zip to flash.....still no work , the CWM recovery cannot replace that CN recovery , it change back to CN recovery as soon as it restart
5. I also try
http://forum.xda-developers.com/memo-pad-7/general/asus-me176c-cx-unlock-bootloader-t3315603
but it's not work on early version
Is there any way that I could flash my K013 Kernel?
I rooted my OP3 but for some reasons installed stock ROM in TWRP and then flashed Stock Recovery. But now Update 3.2.4 fails in stock recovery and I can't sideload it neither the full ROM.
I appreciate any leads.
Thank you
If you don't have them already, download the latest version of TWRP twrp-3.0.2-1-oneplus3.img as well as the latest ROM OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip.
go into fastboot and run `fastboot flash recovery twrp-3.0.2-1-oneplus3.img` to reflash TWRP
reboot into recovery
flash/install OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip then press "Wipe cache/dalvik"
if you don't want to keep TWRP and root you can reboot system now and be finished, otherwise flash/install twrp-3.0.2-1-oneplus3.img to Recovery partition (click "Install Image" to make the file visible)
reboot into recovery (very important!)
flash SuperSU or whatever
reboot system
I would install Global Dev ROM 7.2.16 miui_MI5Global_7.2.16_ab1851be8e_7.0.zip in TWRP (last version 3.0.2-3) but after installation, my phone not boot to system it stuck at mi.com screen.
If I flash other custom ROMs then everything is OK
Does this mean that I can't install official MIUI zip files in TWRP?
zukers said:
I would install Global Dev ROM 7.2.16 miui_MI5Global_7.2.16_ab1851be8e_7.0.zip in TWRP (last version 3.0.2-3) but after installation, my phone not boot to system it stuck at mi.com screen.
If I flash other custom ROMs then everything is OK
Does this mean that I can't install official MIUI zip files in TWRP?
Click to expand...
Click to collapse
This has been discussed many times. Do not flash stock miui rom with TWRP. Use Miflash tool instead.
in the setting
choose the 'support official update'
@muchlas46
I can't use Miflash because if I will flash this file using Miflash then TWRP will be overwrite.
And If I would do that and then install again TWRP it will be asking me in first entry to decrypt data so I have to format freshly installed Global Dev ROM so I'm back in start point.
I would have TWRP, unlocked bootloader(have it) and GLOBAL dev, so to do that?
https://forum.xda-developers.com/mi-5/development/tool-flashable-firmware-twrp-easy-t3474898
flash "Latest one -> Developer 7.2.9 Firmware:",then flash custom ROM(ex:Lineage OS)
I don't wan't custom ROM, I want to install official ROM from this e.g Global dev :
http://en.miui.com/download-299.html#443
anh have this official ROM with TWRP as recovery, is any hint to do this?
I want the EXACLY same thing LOL and i try everything but i cant have TWRP and Global dev, sorry i just wait with you for one solution.
I have idea how to do this but I'am afraid bricking my phone
Inside official fastboot file, after extracting is folder "images" inside is recovery.img file - this is stock recovery.
It could be maybe possible to replace this file to twrp file and leave it with the same name, then during Mi-flash will be TWRP installed instead stock recovery.
1. flash the firmware given above.
2.nougat miui often doesn't boot with only a clean twrp flash,that's why you have to flash the nougat firmware posted above.
else
1.flash 6.11 marshmallow global beta.
2.reboot
3.now flash nougat beta
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Step 1/2
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Havoc-OS-v2.4-20190502-jasmine_sprout-Official.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
Anyone can help me?
Thanks
nnexuss said:
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Try to use twrp 3.2.3 and follow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
mma_1494 said:
Try to use twrp 3.2.3 and follow this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
I already tried this version but not the guide...
I'll try when I arrived at home
nnexuss said:
Hi, fellows,
High need urgently help!
I was on stock Pie with all critical unlock, bootloader unlock and root too ... So I decide to change to a costume firmware.
Now I'm on twrp-installer-3.3.0-0-jasmine_sprout.zip with all the partitions decrypted and when I tried to flash a custom firmware like Havoc OS v2.4 or Pixel Experience ... Happen this error.
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Their is only one way to recover your phone just follow this step
1. Flash stock firmware(stock rom) vie fastboot using MI Flasher
this is bring back you phone and if you want to install custom rom then follow this
1. boot twrp
2. wipe all the data from slot A and B partition(internal storage as per you choice )
3. boot to slot B and copy past the custom rom file in slot B
4. flash that rom and boot to slot B and then flash Gaaps and other staff you want
5. reboot and enjoy.
NOTE: changing the slot require reboot twrp in simple words every time you change the slot you have to reboot the phone and boot again to twrp..
i hope this will work for you..:good:
If you don't have stock flash file then try from step 2. see whether it will work or not otherwise follow from beginning.
facing the same issue
i tried the same and getting the same error. even the twrp3.2.3.0 never worked while tried to flash that one more than 20 times, after flashing 3.2.3.0 my phone either boots normally or it gets completely power off. and if i try to boot into recovery using volume keys and power key , it boots in stock recovery. please help
Mine its ok now... i don´t know whats happen but suddenly it flash withou any problem.
See if it helps...
Make sure you're running a proper working Recovery
Flashing instructions:
Dirty flash (assuming you have rom on slot A):
1. Download all required files and place them to internal memory (ROM, twrp installer, gapps, magisk, ..)
2. Boot twrp to slot B and flash ROM and twrp installer
3. Reboot twrp to slot A and flash gapps (optional magisk)
4. Now reboot to system
Clean flash (assuming you have rom on slot A):
1. Download all required files and place them to internal memory (ROM, twrp installer, gapps, magisk, ..)
2. Boot twrp to A slot and wipe everything except for internal
3. Reboot twrp to B slot and flash ROM and twrp installer
4. Reboot twrp to slot A and flash gapps (optional magisk)
5. Now reboot to system
If you are coming from stock:
1. Download latest TWRP installer and image
2. Open cmd and type fastboot boot twrp.img (change twrp to its actual name)
3. You should be on slot A in twrp, if not change it and reboot to bootloader and repeat step 2.
4. Format data
5. Now follow instruction for clean flash
Click to expand...
Click to collapse
Credits: Fullbustah
I have this issue and none of the steps worked.
I got my device 2 days back and it was in Oreo. I tried to update to pie but the update keep failing. I unlocked the phone and flash latest official fastboot rom using mi_flash and installed magisk using this guide:
https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
Everything went smooth.
Today I tried to go further and instal PE rom using this guide:
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Everything goes smooth until I boot to TWRP and try to flash the rom. It gave the error posted by OP. I have tried the following things since:
1. Try another two roms, same issue
2. Flash stock Pie using mi_flash then temp boot to TWRP latest version from 'a' partition, wipe everything, then boot from 'b' partition, wipe everything, try to flash. Same issue.
3. Install TWRP (it installed without any issue), reboot to installed TWRP, flash rom, same issue.
4. Try to flash with 'a' as active. Same issue.
5. All other possible combos (i think) of the above. In all cases everything goes as expected until I try to flash the rom.
Currently I have flashed the factory image back. Any help will be greatly appreciated.