Hello Devs,
Just wondering if the new CyanogenMod 11 Nightlies has the boot install script in it or not , Since my device is S-OFF if the install script is present I should be able to install the boot.img from recovery itself rather than extracting it and flashing throught FASTBOOT.
Recently I found that some roms they they don't come with the install script for which I had to push the boot.img separately..
Can some one help me out with this one.
Thanks
ethanon said:
Hello Devs,
Just wondering if the new CyanogenMod 11 Nightlies has the boot install script in it or not , Since my device is S-OFF if the install script is present I should be able to install the boot.img from recovery itself rather than extracting it and flashing throught FASTBOOT.
Recently I found that some roms they they don't come with the install script for which I had to push the boot.img separately..
Can some one help me out with this one.
Thanks
Click to expand...
Click to collapse
Nope
Correct me if I am wrong , you mean to say that I will have to push boot.img separately , as the boot install script is missing in CM11
ethanon said:
Correct me if I am wrong , you mean to say that I will have to push boot.img separately , as the boot install script is missing in CM11
Click to expand...
Click to collapse
100% correct.
Related
Hi, first of all, my English is bad and i'm a noob at installing custom roms
My HOX+ is rooted and i have the TWRP Recovery installed.
So, i downloaded the newest CM11 Nightly for my device (enrc2b) from the Cyanogenmod site.
When i try to flash it with TWRP it says:
Skipping MD5 check: no MD5 file found
Can't install this package on top of incompatible data. Please try another package or run a factory reset
E:Error executing updater binary in zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140902-NIGHTLY-enrc2b.zip
I also downloaded a Snapshot version of CM11
It says:
Skipping MD5 check: no MD5 file found
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
Error flashing zip ' /sdcard/cm-11-20140308-SNAPSHOT-M4-enrc2b.zip
So finally i downloaded the CM10.2.1 Version
I wiped all cache and data and did a factory reset.
After flashing the .zip and rebooting the phone, but i got stuck in a boot loop (i think) because i waited like 20 minutes but the boot animation didn't change (blue guy with the arrow). Did i do something wrong
I just restored my phone to the backup i made (stock rom)
If you need any information about my phone or something just say it.
I also heard about using CWM instead of TWRP but i don't know how to change it.
PLZ HELP :crying:
CWM recovery
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
[email protected] said:
Install this recovery for installing CM.
And don't forget to redo your backup after installing the new recovery before installing CM.
Click to expand...
Click to collapse
Thx, I will try it
Sent from my HTC One X+ using XDA Free mobile app
I'm working with a Mac so it might take a while before i understand everything but i'll let you know if it worked.
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Anthony26 said:
So yesterday i installed the CWM and flashed Cyanogenmod11 Nightlies at 00:10. I got the boot screen with the guy and the arrow spinning, but when i wake up at 7:00 it was still in the Cyanogenmod boot screen wit the arrow (the arrow was lagging).
So i tried flashing the Snapshot version and it also didnt pass the screen with the arrow (lagging)
After that i flashed the CM10.2 and the arrow wasnt lagging anymore but it didnt pass the screen with the arrow
Every time before i installed another version i did a Factory reset in CWM
So am i doing something wrong plz help?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
did you flash the boot.img in fastboot before installing the rom?
reaper90 said:
did you flash the boot.img in fastboot before installing the rom?
Click to expand...
Click to collapse
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Anthony26 said:
Do you mean with "boot.img" the recovery-clockwork-touch-6.0.4.8-enrc2b.img
This is all i did (i dunno of the screenshot will display i uploaded it as attachment)
I've flashed the recovery.img, thats also the only thing i downloaded on the CWM site.
I also downloaded the Cyanogenmod rom on the CyanogenMod Download site or do i have to download it from the CWM enrc2b Roms?
Edit: I've found out that the boot.img is needed for the device to boot and that i can flash it in recovery.
But is there a special HOX+ boot.img or a Cyanogenmod boot.img or whatever i need? And where can i find it
Click to expand...
Click to collapse
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Thx,
I forgot to unzip the file :silly:
I'll try it and let you know of it worked
reaper90 said:
you can find it inside the rom zip file, just extract it into your adb/fastboot folder and flash it (in fastboot mode) using "fastboot flash boot boot.img". also i recommend (maybe not necessary) using "fastboot erase cache" before and after flashing boot.img.
Also you may need to reflash rom in recovery after flashing boot.img.
Click to expand...
Click to collapse
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Stock boot image
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Anthony26 said:
Alright i did what u said and i have 1 more question;
If i want to go back to the stock rom, do i need to flash a "stock" boot.img?
Edit: Cyanogenmod is working, i only need to install the Google apps (i think).
Click to expand...
Click to collapse
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
[email protected] said:
You can flash the Nik3r version to come back to the stock boot image.
And you need to flash the GAPPS in recovery for the Google apps
Click to expand...
Click to collapse
reaper90 said:
If you want to go back to stock completely (including relocked bootloader) you will need everything completely stock and matching your phones CID. Of course you will need to flash the corresponding boot.img for every rom. But as far as i know/tried, nik3rs oxp_kk kernel works for all 4.4 roms and the other version works for all Sense5 based custom roms and maybe stock rom (if you don't need relocked bootloader).
Click to expand...
Click to collapse
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Anthony26 said:
Thx, i have installed the Gapps and it's working good.
The only thing i notice is the fast battery drain, is it possible to underclock some thing so the battery last longer, and which apps are good for that?
And if i want to go back to the stock rom, i just have to go back to my "stock rom backup" in recovery and flash nik3rs oxp_kk kernel?
Click to expand...
Click to collapse
no, oxp_kk is just for 4.4 (kitkat) AOSP like roms. there's another non- kk version which works with 4.2.2/sense5 roms, but i don't know about stock roms. There's also a fallback kernel version which should work with all stock and custom 4.2.2/Sense 5 roms.
I just installed Cyanogenmod and whenever I boot into Cyanogen recovery and try to apply an update it fails. For example I tried installing the flashable .zip for NUT’s DualRecovery but got
Finding update package...
Opening update package…
Verifying update package…
E:footer is wrong
E:signature verification failed
Installation aborted.
same happens with a boot animation. By the way I have an unlocked bootloader.
You will need to put TWRP on to your device using fastboot commands, If you need help with that just ask me
K-NineHD said:
You will need to put TWRP on to your device using fastboot commands, If you need help with that just ask me
Click to expand...
Click to collapse
I'm going to need some help on with this. I tried ">fastboot flash recovery twrp-2.8.6.0-sirius.img" and it put the device into a bootloop.
I got it to work. Using Rashr I installed TWRP.
imgoingtowin said:
I'm going to need some help on with this. I tried ">fastboot flash recovery twrp-2.8.6.0-sirius.img" and it put the device into a bootloop.
Click to expand...
Click to collapse
After installing the NUT’s DualRecovery, TWRP thought my phone was tianchi ( Sony Xperia T2 Ultra ).
I got Cyanogenmod working at last ( by flashing the boot.img inside the zip ), Everything seems to work fine for me. I even flashed CM 12.1 unofficial port by infected_. It still works fine for me... Try flashing the boot.img again and see if it works.. Also have you flashed other kernels or mods?
ArrowHunt3R said:
After installing the NUT’s DualRecovery, TWRP thought my phone was tianchi ( Sony Xperia T2 Ultra ).
I got Cyanogenmod working at last ( by flashing the boot.img inside the zip ), Everything seems to work fine for me. I even flashed CM 12.1 unofficial port by infected_. It still works fine for me... Try flashing the boot.img again and see if it works.. Also have you flashed other kernels or mods?
Click to expand...
Click to collapse
I just said I got it to work with Flashr. And no I'm on the stock kernel.
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
UniAyeDee said:
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
Click to expand...
Click to collapse
+99 points for asking this question .
As per my knowledge the main problem lies in the boot.img file of MIUI roms because when you are flashing the TWRP you are messing with phone's orignal partition pattern,the boot.img's of MIUI rom checks evrytime if there is any tampering in phone's partition and as you know by flashing TWRP you tampered already , so as result your phone won't boot and gets in bootloop.
So to solve this problem devs developed some methods either you can make a cooked boot.img and flash it evrytime you get a new update to prevent bootloop,
Or you can flash lazyflasher.zip via twrp evrytime after installing new MIUI rom which will patch boot.IMG itself,
Or you can use cofface based recoveries which have lazyflash patch inbuilt and will patch the boot.IMG file evrytime you flash a MIUI rom.
NVDX11 said:
+99 points for asking this question .
As per my knowledge the main problem lies in the boot.img file of MIUI roms because when you are flashing the TWRP you are messing with phone's orignal partition pattern,the boot.img's of MIUI rom checks evrytime if there is any tampering in phone's partition and as you know by flashing TWRP you tampered already , so as result your phone won't boot and gets in bootloop.
So to solve this problem devs developed some methods either you can make a cooked boot.img and flash it evrytime you get a new update to prevent bootloop,
Or you can flash lazyflasher.zip via twrp evrytime after installing new MIUI rom which will patch boot.IMG itself,
Or you can use cofface based recoveries which have lazyflash patch inbuilt and will patch the boot.IMG file evrytime you flash a MIUI rom.
Click to expand...
Click to collapse
Thanks, clears things up. I think I've heard of tampering before but for some reason it wasn't a problem on the moto.
Is there an article or something I can read?
UniAyeDee said:
Thanks, clears things up. I think I've heard of tampering before but for some reason it wasn't a problem on the moto.
Is there an article or something I can read?
Click to expand...
Click to collapse
Yea i know what you are saying,previously i had xperia devices there wasn't a problem too but xiaomi phones have some diff. Methods i think,actually there is not an article about this thing but i am sure i had read that in some developer's post.
UniAyeDee said:
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
Click to expand...
Click to collapse
Update:
The system is known as "dm-verity"
Which enables verfying boot partiton evrytime a system boots if there is any modification.
It is included after 4.4 kitkat for security purpose.
Miui is using Boot.img with enabled dm-verity check.
So after rooting or flashing twrp phone won't boot.
So,what lazyflasher does is disables it.which is inbuilt part of cofface based recoveries.
Read more on dm-verity:
https://source.android.com/security/verifiedboot/
Custom super su from somewhere which roots boot via patch. Flash with twrp
Hi everyone!
I´m using the build of Lineage OS 20170225, everything works fine but when i try to flash a permissive kernel to fix the mods (is in the lineage thread), the recovery said "Error opening: ´/sdcard/...../boot.img/´ (Not a directory)"
What can i do?
I tried to change the root where the file is, but nothing changed...
Sorry for the bad english
Are you trying to open the boot.img file? In TWRP you need to swap to image install not zip, and flash it to the boot partition.
Also make sure you're on the latest TWRP (3.0.3-n2), and maybe re download the boot.img incase it's corrupted.
Hope this helps :good:
supacrazyguy42 said:
Are you trying to open the boot.img file? In TWRP you need to swap to image install not zip, and flash it to the boot partition.
Also make sure you're on the latest TWRP (3.0.3-n2), and maybe re download the boot.img incase it's corrupted.
Hope this helps :good:
Click to expand...
Click to collapse
You´re my hero!!!! hahahaha :victory:
Update the TWRP in the last version and finally could flash the kernel
elpela86 said:
You´re my hero!!!! hahahaha :victory:
Update the TWRP in the last version and finally could flash the kernel
Click to expand...
Click to collapse
Great! Glad it worked now :highfive:
Here is the last version at the moment of the Maze alpha ROM (tested only in 4GB version)
It's a complete ROM, not an OTA update, it can be flashed using the provided TWRP 3.2.1 version, I ported from a Jemmini (many thanks) version for Bluboo S1.
Unfortunately, the TWRP cannot be flashed (issue with the touch panel), only launched by fastboot.
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
There is also a SPFlashTool clean version of this ROM, useful in case of troubles (as official: no root, no busybox)
1- Reboot you phone in fastboot mode : adb reboot bootloader
2- Flash the provided TWRP : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3- Reboot to TWRP recovery
4- copy in your SDCARD and install, in the running TWRP, the downloaded ROM V09 : Maze_Alpha_4GB_v09_TWRP.zip
The first boot take some minutes so be patient.
Here the SPFlashTool versions :
MAZE_Alpha_4GB_V09_SPFT.zip
Here, if needed, my V09 TWRP backup (new one from 21/04/2018) :
TWRP_BACKUP_MAZE_Alpha_A_V09.zip
Credits to Jemmini and Magisk team.
Can you make this for the 6 gb version?
many thanks gonna ty it soon
Nautilus99 said:
Can you make this for the 6 gb version?
Click to expand...
Click to collapse
I do not have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
dreambo said:
I do note have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
Click to expand...
Click to collapse
Yes i know its sad, i did a backup of mine and root it but it didnt work the backup i had to do clean flash, if we can manage to have a twrp and a source of the stock roms we could make a deabloat and put update apps ( menssages, calendar etc) and put mods for awsome features i dont see RR or lineage putting thier hands on this phone
Thanks for this Rom.
Is there any root for the maze alpha x?
here
WiddleyScudds said:
Is there any root for the maze alpha x?
Click to expand...
Click to collapse
read
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
Click to expand...
Click to collapse
thorfr said:
read
Click to expand...
Click to collapse
I have an alpha x, not alpha.
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
rzoli71 said:
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
Click to expand...
Click to collapse
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
thank you
After I installed this rom, and freezed the hot knot, baidu_location FM Radio, etc, the BT connection did not break.
dreambo said:
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
Click to expand...
Click to collapse
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
ahorntaler said:
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
Click to expand...
Click to collapse
No I not have any source, I am just a simple user like any other.
If I have any source or if I can make a ROM for MAZE Alpha X, I will do it and I will share it with every body, as I do until now for the MAZE Alpha 4/64
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
iBolitN said:
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
Click to expand...
Click to collapse
Unfortunatly no. As you will see repeated times in the forum, people have issue with phone not booting after changing from stock recovery to twrp. This is do (most likely from) to verified boot setting. And by unlocking bootloader we can bypass verified boot. So without unlock you might get a successfull load into twrp, but android will not boot.
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
stargazer78 said:
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
Click to expand...
Click to collapse
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Thanks a lot for your reply....
the problem is that i cant boot into fastboot to unlock bootloader....
the phone bootloops all the time, shows the red state alert and even with vol+ pressed the menu to choose recovery or fastboot doesn't apear... thanks again.
dreambo said:
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Click to expand...
Click to collapse
Is there any way to unlock the bootloader in my situation or/and enter the fastboot mode in order to follow your steps... thanks.