Database Develop

[LOLLIPOP 5.1][STOCK] Cherry Mobile One H940 Official Links

Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.

do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks

Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.

intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you

Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/

OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.

erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.

intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.

erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.

intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance

Sir
can you capture ota for myphone uno

gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.

still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM

Working internal detect for pc and file ?

marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.

intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM

marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.

success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man

Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!

OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.

Help needed for soft bricked HTC One M7

Hey guys this is my first attempt at rooting and now I have a soft bricked phone. The phone just boots into the Android logo and nothing else. I accidently erased all my data using the custom recovery program called TWRP. I went to Wipe and pressed format data. Can you guys please help me fix it? Thanks

What ROM are you trying to use?

shady_sawyer said:
Hey guys this is my first attempt at rooting and now I have a soft bricked phone. The phone just boots into the Android logo and nothing else. I accidently erased all my data using the custom recovery program called TWRP. I went to Wipe and pressed format data. Can you guys please help me fix it? Thanks
Click to expand...
Click to collapse
You will have to push the zip with TWRP recovery and the command line. Are you S-Off?
Also thread titles like this is an easy way to get it ignored or even deleted before anyone can look at it.

I take it he's s-on he's just attempted to root
Try fastbooting the boot.img in terminal on your PC..

jenkins-84 said:
I take it he's s-on he's just attempted to root
Try fastbooting the boot.img in terminal on your PC..
Click to expand...
Click to collapse
Thanks for your replies guys. im a complete noob. I dont even know which ROM to use...but here are the details
*****TAMPERED*****
****UNLOCKED****
Its M7 PVT SHIP S-ON RH
HBOOT - 1.61.0000
RADIO-4T.35.3218.16
Open-DSP - v35.120 .274.0718
OS-7.19.401.102
e-MMC-boot 2048MB
Im using Teamwin Recovery Project v 2.6.3.0
Im using Ubuntu 14.04

OK no worries I'm at work atm so can't really help yet, but if you push I ROM zip on to your device using twrp whatever ROM you us sense or aosp follow instruction's from the thread once you flash the ROM. Go back into bootloader and flash the boot.img you extracted from the ROM.zip file

please tell me step by step the commands I need to type in my ubuntu terminal. Thanks again for your support

If you look around use search will be loads of threads that explain all this sorry ATM I'm a bit busy, will later if you no luck. If you look around the answer to your problems will be there hundreds of people will have been in same position your in thread after thread just have a look around

I looked around but using ubuntu there are few people in my position. .can anyone else tell me what i should do....

jenkins-84 said:
(...) Go back into bootloader and flash the boot.img you extracted from the ROM.zip file
Click to expand...
Click to collapse
Unlike some other HTC devices, the M7 does not requires to flash the boot.img separately after flashing a rom. Boot partition is not secured and is flashed automatically when flashing a rom from custom recovery. OP has formatted data partition which mean he have no OS (no rom) installed. So flashing the kernel (boot.img) will not solve his problem.
shady_sawyer said:
please tell me step by step the commands I need to type in my ubuntu terminal. Thanks again for your support
Click to expand...
Click to collapse
1) Your twrp version is outdated. Download twrp 2.8.6.0 for M7 and flash it:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
2) Boot your device in twrp main menu, with the 2.8.6.0 version you'll be able to see your phone storage on your computer like if it was a usb drive. Drag and drop your rom.zip to your phone internal storage (My computer --> One --> Internal storage --> your_rom.zip here)
Then in twrp select "install" browse you phone storage and select "your_rom.zip" and swipe to bottom slider to install. Once done reboot your device and voila.
If you don't want to use a custom rom and you only want to use your stock rom and have root, you could simply flash the 7.19.401.102 ruu to get your OS back and then reflash latest TWRP (2.8.6.0) so you can root your stock rom. If this is what you want I can give you step by step instruction for this too, just ask if you need.

alray said:
Unlike some other HTC devices, the M7 does not requires to flash the boot.img separately after flashing a rom. Boot partition is not secured and is flashed automatically when flashing a rom from custom recovery. OP has formatted data partition which mean he have no OS (no rom) installed. So flashing the kernel (boot.img) will not solve his problem.
1) Your twrp version is outdated. Download twrp 2.8.6.0 for M7 and flash it:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
2) Boot your device in twrp main menu, with the 2.8.6.0 version you'll be able to see your phone storage on your computer like if it was a usb drive. Drag and drop your rom.zip to your phone internal storage (My computer --> One --> Internal storage --> your_rom.zip here)
Then in twrp select "install" browse you phone storage and select "your_rom.zip" and swipe to bottom slider to install. Once done reboot your device and voila.
If you don't want to use a custom rom and you only want to use your stock rom and have root, you could simply flash the 7.19.401.102 ruu to get your OS back and then reflash latest TWRP (2.8.6.0) so you can root your stock rom. If this is what you want I can give you step by step instruction for this too, just ask if you need.
Click to expand...
Click to collapse
Thats what i was lookin for. Thanks a lot bro..... you are the man. Its all good now.

[Marshmallow 6.0+] How to Root , Fully unroot & update to New SuperSU Properly

I see lots of confusion going on in many Roms & other threads for rooting 6.0 specially due to that System-less SuperSU.
so i'm sharing what i have done to root 6.0 & update SuperSU through 2.61 to 2.64.
now before we begin be clear on that System-less SuperSU patches only kernel & ramdisk for root.
Still making Full Backup/nandroid is always a good thing before trying something new, it'll save you if anything goes wrong.
Rooting Marshmallow 6.0+ 1st time
1) Be on Marshmallow Rom ( stock / custom) with unlocked boot loader..... i have tested this stock & Cataclysm.
Click below to see how to Unlock Bootloader.
Beware : it'll wipe your device entierly to factory reset state ( all things will be wiped out : contacts , apps , music, videos & your personal files etc. so backup every thing.
reboot into boot loader & use bellow command for unlocking boot loader
Code:
fastboot oem unlock
2) Download latest version of SuperSU ( currently 2.64) from Here & Place it in Phone Storage
2B) (optional) if you want to use Custom kernel (like ElementalX) then download it's falshable zip & pace it in Phone Storage as well
3) Download TWRP 2.8.7.1 from Here. & flash it with fastboot command.
Code:
fastboot flash recovery twrp-2.8.7.1-hammerhead.img
4) after flashing TWRP inter into recovery without Rebooting Phone . ( why ? open hidden content ) {PS: smart people make nandroid backup at this step}
if you reboot phone just after flashing twrp & then try to enter in to recovery mode, you will see stock recovery instead of TWRP. bcz TWRP was flashed only as temporary recovery without root.
4B) (optional) if you want to use custom kernel then flash it now ! ( yes before rooting bcz it needs to be patched) ( not needed.... you can flash custom kernel after completing entire root process bcz it turns out that SuperSU just patch ramdisk, not kernel so custom kernel can be flashed after rooting without any problem. btw i still flash custom kernel before rooting and never had problem so it's your call when to flash custom kernel )
5) Now Flash SuperSU.zip in TWRP which you have from link in 2nd point.
6) Click Reboot System in TWRP. It will tell you your device isn't rooted & ask your permission for rooting it. DO NOT ( I repeat Do not) swipe to grant it, always Select NO ( it says so bcz twrp still don't detect system-less root )
7) Remember 6th point after Flashing any other zip in future as well.
PS: If you change your kernel after rooting you need to flash SuperSU.zip again after it
Updating SuperSU for already rooted Marshmallow 6.0+
all steps are important for properly updating SuperSu so don't skip any of them. Otherwise already patched Kernel or ramdisk will give you an error while flashing updated SuperSu!
1) Open SuperSU app. Click "Full Unroot" & wait until auto reboot completes. ( this step will remove root & restore your original kernel that was auto backup while rooting 1st time.)
2) Flash Stock boot.img from factory image via fastboot command. ( important step for those who used custom kernel while/after rooting )
Code:
fastboot flash boot boot.img
(you can get boot.img by extracting image-hammerhead-xxxxx, from factory image.)
3)Reboot Phone.
4) Now follow Rooting Marshmallow 6.0+ 1st time method from step 2. ( you can skip step 3 if you already have TWRP )
.........................................................................................................................
Cataclysm specific info

( reserved for future SuperSU changes )
A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu").
Click to expand...
Click to collapse
what does above statement from Chainfire's SuperSU 2.64 mean ?
Well, it means on Android 6.0+ if you are using Custom Rom & Custom kernel which are already patched for SELinux Policies for root on /system partition then from v2.64 SuperSU script will check it & if they seems fine then Su binary will be placed in /system instead in installing Root as system-less mode & patching kernel & all.
(correct me if i'm wrong )

Thanks for this. Makes things clear for me.
Maybe you can add something about Android Pay. Like, does it work? Or, how to make it work. I see a lot of confusion on that when discussing the new SuperSU as well.
Sent from my Nexus 5

bmcgarry84 said:
Thanks for this. Makes things clear for me.
Maybe you can add something about Android Pay. Like, does it work? Or, how to make it work. I see a lot of confusion on that when discussing the new SuperSU as well.
Sent from my Nexus 5
Click to expand...
Click to collapse
No Android Pay will Not work if you root your device in any way.
Some users reported earlier that "system-less" root helped them to keep Android Pay working.. But itt was just placebo & luck. It stopped working for most of them after some time.
So for now there is no way to keep Android Pay working with root. ( atleast not to the my knowledge)
(Actually Android Pay isn't working with Root is Good security feature..one can argue that other pay works even after rooting but there's chance (may be just a little) to interfere it by thieves. & Google won't risk it until they find complete secure solution. )

Hmmm. Android Pay has been working for me on 6.01 with both 2.63 & 2.64 su. Used it only twice in the last week, so that may not pass the "it's working permanently" test. It is working though (at Whole Foods). I had to delete the xbin file mentioned in the supersu thread. I even have Viper4Android installed, which modifies system.

first boot after point 6. everything was fine.
then i opened Busybox and " It looks like bb is installed, but it does not appear to be the versionthay you selected to have installed, you may want to try the installation again, but this time using a differentinstallation location."
then I made restart and I have lost root. SuperSu " There is no SU binary installed, and SuperSu cannot install it............"
Edit. Second attempt whitout custom kernel ( hellscore ) and looks like everything is working now. ( i unistalled and reistalled busybox )

Mairo said:
first boot after point 6. everything was fine.
then i opened Busybox and " It looks like bb is installed, but it does not appear to be the versionthay you selected to have installed, you may want to try the installation again, but this time using a differentinstallation location."
then I made restart and I have lost root. SuperSu " There is no SU binary installed, and SuperSu cannot install it............"
Edit. Second attempt whitout custom kernel ( hellscore ) and looks like everything is working now. ( i unistalled and reistalled busybox )
Click to expand...
Click to collapse
may be custom kernel related.. most of custom kernel for nexus 5 comes with busy box. so you don't need to flash it again.
If you want to update busybox use /xbin installation method. ( it'll modify your /system but it's easy)
( if you don't want to modify your /system at all you can use /bin location for BB installation. it should work fine ( though i never used this.) )
personally i use ElementalX which comes with busybox so i don't go to hassle to update it again..it works just fine without anything

lynnux said:
Hmmm. Android Pay has been working for me on 6.01 with both 2.63 & 2.64 su. Used it only twice in the last week, so that may not pass the "it's working permanently" test. It is working though (at Whole Foods). I had to delete the xbin file mentioned in the supersu thread. I even have Viper4Android installed, which modifies system.
Click to expand...
Click to collapse
personally i don't have any experience with Android Pay bcz it's not available in my country & i don't think i''l be any soon.
so if it's working for you then it's good
in future if it stop working, let us know how it stopped (if you can figure it out) it'll be helpful for other people.

there is something with hellscore kernel and su2.64. I tried 2 different ways right now.
First i flashed under twrp hells b16 ( it says successfully )and then su.2.64. ( succesfull) then I boot up and no hellscore kerne.
Then I just tried to flash only hellscore whitout SU2.64. then I get hellscore kernel but then no root. Then I just went to back TWRP and flashed Su.264 and I got root and stock kernel .
I think I need talk with Hellscore about this b16 version and su2.64.

Mairo said:
there is something with hellscore kernel and su2.64. I tried 2 different ways right now.
First i flashed under twrp hells b16 ( it says successfully )and then su.2.64. ( succesfull) then I boot up and no hellscore kerne.
Then I just tried to flash only hellscore whitout SU2.64. then I get hellscore kernel but then no root. Then I just went to back TWRP and flashed Su.264 and I got root and stock kernel .
I think I need talk with Hellscore about this b16 version and su2.64.
Click to expand...
Click to collapse
What your recovery log says when you flash SuperSU after hellscore ?
Can you attach it, i want to check it out.
(i think there is option to save log after flashing zip in twrp )

jineshpatel30 said:
What your recovery log says when you flash SuperSU after hellscore ?
Can you attach it, i want to check it out.
(i think there is option to save log after flashing zip in twrp )
Click to expand...
Click to collapse
sorry cant give it right now. I restored everything from nandroid backup. befor I used b16 with su2.62-3 and they worked great together. but after restoring same like 2.64.
my battery starting to get empty.. cant test it and send log right now.

Mairo said:
sorry cant give it right now. I restored everything from nandroid backup. befor I used b16 with su2.62-3 and they worked great together. but after restoring same like 2.64.
my battery starting to get empty.. cant test it and send log right now.
Click to expand...
Click to collapse
Okay no problem
If you give it try in future,plz save log file

jineshpatel30 said:
Okay no problem
If you give it try in future,plz save log file
Click to expand...
Click to collapse
here it is. I made a new istall also before . Then I used your guide and got root. Then I reboot back in twrp and flashed hellscore then su2.64 again. and then made reboot. And no Helscore kernel.

Mairo said:
here it is. I made a new istall also before . Then I used your guide and got root. Then I reboot back in twrp and flashed hellscore then su2.64 again. and then made reboot. And no Helscore kernel.
Click to expand...
Click to collapse
Well i'm not an expert in this matters but your log shows lots of errors while flashing SuperSu after hellscore.
It can't Mount partitions & can't create /su folder & errors while patching also.
I recommend you to show this log to Kernel Dev asap..he will know what to do exactly.
Btw you flashed stock boot.img before flashing hellscore right ?
If not now try bellow steps exactly.
Flash stock boot.img via fastboot (no need to flash system or anything else as you are flashing hellscore again )
Now reboot phone & then go to recovery.
Now flash hellscore & then SuperSU.
& reboot.
See & report result. (If you already done above steps property then no need to try again just report logs to Dev )

jineshpatel30 said:
Btw you flashed stock boot.img before flashing hellscore right ?
Click to expand...
Click to collapse
Jeap. Tried these steps. I sent this log to Hells dev.

fastboot flash recovery twrp-2.8.7.1 goes wrong
Hi, I try the root on nexus 5 with stock rom 6.01, when I flash recovery twrp, obtain this message:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery twrp
-2.8.7.1-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14694 KB)...
OKAY [ 0.738s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.845s
so, when i go to recovery, without rebooting as suggested, I don't have twrp recovery.
Any suggestion?
Thanks

wiifan said:
Hi, I try the root on nexus 5 with stock rom 6.01, when I flash recovery twrp, obtain this message:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery twrp
-2.8.7.1-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14694 KB)...
OKAY [ 0.738s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.845s
so, when i go to recovery, without rebooting as suggested, I don't have twrp recovery.
Any suggestion?
Thanks
Click to expand...
Click to collapse
You have to unlock your bootloader first. CAUTION! THIS WIPES YOUR PHONE!
Background information and how to unlock the bootloader read here: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/

wiifan said:
Hi, I try the root on nexus 5 with stock rom 6.01, when I flash recovery twrp, obtain this message:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery twrp
-2.8.7.1-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14694 KB)...
OKAY [ 0.738s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.845s
so, when i go to recovery, without rebooting as suggested, I don't have twrp recovery.
Any suggestion?
Thanks
Click to expand...
Click to collapse
as suggested by Smoosh you need to Unlock Bootloader.
Beware : it'll wipe your device entierly to factory reset state ( all things will be wiped out : contacts , apps , music, videos your personal files etc. so backup every thing.
reboot into boot loader & use bellow command for unlocking boot loader
Code:
fastboot oem unlock
Smoosh1 said:
You have to unlock your bootloader first. CAUTION! THIS WIPES YOUR PHONE!
Background information and how to unlock the bootloader read here: http://www.addictivetips.com/mobile/what-is-bootloader-and-how-to-unlock-bootloader-on-android-phones-complete-guide/
Click to expand...
Click to collapse
thank for replying him i thought people come to this thread already know about unlocking but now i need to add that as well in OP

Bootloop
My phone has entered into a bootloop after flashing on the TWRP recovery. TWRP opens, runs a script for like 5 seconds, and then my phone restarts, repeat. How do I fix this? I have tried to wipe the memory multiple times and even reflash twrp, with no success.

@jineshpatel30 Pls help
hi bro @jineshpatel30 pls help me out.
Im running on stock 6.0.0 and rooted with recovery twrp-2.8.7.1-hammerhead.img and hellscore hC-b11-M kernal. Im using cataclysm Nov release 6.0.0 as my daily driver in secondary rom (and its pre rooted by the rom builder) and stock 6.0.0 as my primary rom.
Recently cataclysm released its Dec 8 stable release 6.0.1, i have clean flashed the same in secondary and its working perfect but no root access, after going through too many forums in xda i have flashed SuperSU 2.61 on the same to root it. but its just showing patching ramdisk in twrp more than 30 mins and nothing is happening. :crying:
Now kindly help me to root the same(cataclysm Dec 8 stable release 6.0.1) in secondary... can i flash SuperSU-2.64 directly over cataclysm?? is that safe?? is that make any problem to primary stock??? pls guide me as im not getting any proper answre from any of the forum and there is too many members like me still confused flashing the SuperSu 2.64 in a multirom and its after effects. :fingers-crossed:
Primary Rom: Stock 6.0.0 as primary, Kernal : hC-b11-M
Seconary Rom: Cataclysm Nov release 6.0.0, Kernal : hC-b15-M
Recovery: TWRP 2.8.7.1
Baseband: M8974A -2.0.50.2.27
Booloader: hhz12k
awaiting for your valuable reply hope you will help me:fingers-crossed:

Any updated GUIDE for install kernel ?

Hi so im new to HTC modding, i bought second handed M7, its complete stock.
I want elementalx kernel (i suppose its best ? ) to have htc logo functional (and also little underclock etc for battery saving).
Is there any step by step guide for do that, with no screw anything ?
(mine is M7_UL)

mmm273 said:
Hi so im new to HTC modding, i bought second handed M7, its complete stock.
I want elementalx kernel (i suppose its best ? ) to have htc logo functional (and also little underclock etc for battery saving).
Is there any step by step guide for do that, with no screw anything ?
(mine is M7_UL)
Click to expand...
Click to collapse
There isn't much more to say about the install process than what's already said in ElementalX thread:
INSTALLATION
1. Install zip from recovery
2. Follow the instructions, if you don't know what to do, use the preselected options
3. Reboot
Click to expand...
Click to collapse
Your bootloader can be unlocked using instructions at www.htcdev.com/bootloader
Twrp recovery is flashed using fastboot in bootloader mode:
Code:
fastboot flash recovery twrp-3.2.1-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
and finally save the correct elementalX version on your phone storage and install with twrp.

ok but in future how i recover stock recovery and kernel ?

@mmm273
mmm273 said:
ok but in future how i recover stock recovery and kernel ?
Click to expand...
Click to collapse
It's very easy. Just go into fastboot mode, switch into RUU mode via "htc_fastboot.exe", install the stock RUU zipfile even via "htc_fastboot.exe" and that's it. In the HTC stock RUU-zips everything is included, even stock recovery, kernel, and so on...
I recommend for ALL fastboot-operations with HTC devices to use the special "htc_fastboot.exe", it works smooth for me.
Code:
htc_fastboot.exe oem rebootRUU
Wait for the silver HTC progress bar, then:
Code:
htc_fastboot.exe flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
If this step failed after installing "pre-update" hboot, that's normal. Start the flash procedure IMMEDIATELY a second time (or -- as in my case -- it is automagically done by the flash proceeding).
This flash tooks approx. 10 minutes. If you got your windows command prompt back, the final step is (even if the silver progress bar is NOT at the end, that's normal too):
Code:
htc_fastboot.exe reboot
and the system will start like a brand new original M7.
I did this many times with one of my different M7's (one for daily use, several others for testing and experiments), and all the time it worked without any trouble.
(Yet I'm using Slim7-1.17 7.1.2 Nougat with GPE-firmware on all devices, it runs much much better as any stock rom from european HTC Sense).
Happy flashing,
samhhmobil

mmm273 said:
ok but in future how i recover stock recovery and kernel ?
Click to expand...
Click to collapse
If your phone is running the latest version, you won't need the stock recovery anymore so there is no need to backup the stock recovery.
You can backup your stock kernel using twrp "backup" menu. Make a backup of the "boot" partition, this is the kernel. If you need to restore your stock kernel, just restore that backup using twrp "restore" menu. Also, stock recovery and kernel can be extracted from a firmware.zip or ruu.zip matching your phone version if you really need them (someone probably already extracted them and uploaded somewhere, if you can give me the output of "fastboot getvar version-main" I can tell you if your stock recovery and kernel are already uploaded).
You can still flash a ruu to restore your phone back to stock like described above, but flashing a ruu only to restore the stock kernel is a really drastic solution (will reset the whole phone back to stock, rom/recovery/kernel/everything and you'll loose your data).
---------- Post added at 02:14 PM ---------- Previous post was at 01:57 PM ----------
samhhmobil said:
If this step failed after installing "pre-update" hboot, that's normal. Start the flash procedure IMMEDIATELY a second time (or -- as in my case -- it is automagically done by the flash proceeding).
Click to expand...
Click to collapse
If using htc_fastboot.exe you must NOT do the flash command a second time. htc_fastboot.exe will take care of the hboot pre-update itself: will flash the hboot, output the "90 pre-update error", make the phone reboot itself back to ruu mode and flash the remaining partitions without any action from the user. Just so you know it's not magic but how it's intended to work when using htc_fastboot
The second flash was only needed if using the regular fastboot.exe from the sdk-tools for 6.xx.xxx.x RUU and older (7.xx.xxx.x ruu must be flashed with htc_fastboot.exe because of the ruu file size)

thanks all, it working
Well until i tried magisk, can't get safety check pass

Question Magisk ROOT MIUI 14

I would like to know if someone has managed to root with magisk from CMD without twrp?

You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .

or965 said:
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
Click to expand...
Click to collapse
ive use your method but my phone still gone to bootloop. im using eu rom currently.

martin132014 said:
ive use your method but my phone still gone to bootloop. im using eu rom currently.
Click to expand...
Click to collapse
What did you do? I wrote several options.

Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP

System23 said:
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
Click to expand...
Click to collapse
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.

or965 said:
What did you do? I wrote several options.
Click to expand...
Click to collapse
I use the method for eu that you posted. First i install magisk 25.2 and then i patch the rom boot.img. I boot to fastboot and flash the patch boot.img using the command. It flash successful then i reboot. But it still bootloop.

And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.

martin132014 said:
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
Click to expand...
Click to collapse
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method

martin132014 said:
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
Click to expand...
Click to collapse
and what your experience with that!!! Tell me why you like this!!!

System23 said:
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
Click to expand...
Click to collapse
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.

martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
ok a Tip to you!!! when you only Backup Data Partition you can restore it and all Contacts,SMS,Accounts,Apps are availibile again on new ROM!!!
Why you dont use the Magisk.zip and flash it via TWRP after Flash ROM!!! you can rename Magisk.apk to Magisk.zip and flash it!! than you dont need other steps to Root!!! when it dosnt work use the recovery.img to Patch it and try this Method for Rooting, but dont forgett when ya do so you need to try the Buttons-Combo to start in Recovery to boot the System in Root and you have no Recovery-Mode at this Method!!! Also to use Recovery again you must Flash it again via Fastboot!!
And in TWRP use the WIPE Option to make a Factory Reset or WIPE a Single Partition, after some Flashing CROMS its needed to be WIPE the Data Partition!!!

martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
you can ask me what you would i share my Informations with ya!!! when iam not knowing iam googleing it out to find a solution!! the talk we have start are hope helpfully!! when ya have intresst we can stay in kontakt and make what we can, even its public 4 all or PM!!! PS i must not hide my Knowledge, but PM its OK too!!!