Download
v3.2.1-0
Sauce: Github
Fixed /system mounting issues
let me know if you have any issues and I will do what I can to fix them.
Credit: @Josh1x for having the h870 device tree put together for me to clone and update. I will fix the original author on my master branch as soon as I get some time
Thank you!
Works like a charm. No issues here, thanks bro.
---------- Post added at 02:27 PM ---------- Previous post was at 01:42 PM ----------
Also this recovery also fixes the error messages apon flashing mods and what not
How can we apply it if no fastboot commands work
Trippyy Doee said:
How can we apply it if no fastboot commands work
Click to expand...
Click to collapse
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
So this is all we've been waiting for ?! Finally can haz root ? ?
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
when i go into recovery mode all i get is no command. what should i do?
purplekushDGK said:
when i go into recovery mode all i get is no command. what should i do?
Click to expand...
Click to collapse
I think you might have to reflash recovery but idk I'm not the best with this
MudaTrucka said:
I think you might have to reflash recovery but idk I'm not the best with this
Click to expand...
Click to collapse
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
purplekushDGK said:
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
Click to expand...
Click to collapse
No problem, I thought I'd at least try to help
@KAsp3rd W00T -- glad to see that you built this.
The new version of the lafsploit will be out later today, and with it you can use any recovery your want. It handles all the hash verifications internally. It is about as automated as I can make it.
It will be:
./flash-h918-laf.py # Flashes the h918 laf without the need of LG UP, so no brick risks if people aren't paying attention
./root-h872.sh <recovery.img> # If specified, it will use the recovery.img passed, if not, then it will use this version which will be included in the repo
./post-root.sh # This takes care of all the final steps.
So three commands, and that is it. If I could force a reboot back into download mode, it would be one command, but a reboot into download mode is required between each command..
-- Brian
MudaTrucka said:
No problem, I thought I'd at least try to help
Click to expand...
Click to collapse
Can you tell me this method? I cannot get this image to stick, it always reverts back to H870, meaning I cannot flash anything custom (guess I could run Remix H870-would that work?)
agmyers76259 said:
Can you tell me this method? I cannot get this image to stick, it always reverts back to H870, meaning I cannot flash anything custom (guess I could run Remix H870-would that work?)
Click to expand...
Click to collapse
Flash the image to recovery, use the steps in the root thread to get it to stick and make sure you're actually booting into recovery and not laf
runningnak3d said:
@KAsp3rd W00T -- glad to see that you built this.
The new version of the lafsploit will be out later today, and with it you can use any recovery your want. It handles all the hash verifications internally. It is about as automated as I can make it.
It will be:
./flash-h918-laf.py # Flashes the h918 laf without the need of LG UP, so no brick risks if people aren't paying attention
./root-h872.sh <recovery.img> # If specified, it will use the recovery.img passed, if not, then it will use this version which will be included in the repo
./post-root.sh # This takes care of all the final steps.
So three commands, and that is it. If I could force a reboot back into download mode, it would be one command, but a reboot into download mode is required between each command..
-- Brian
Click to expand...
Click to collapse
Any idea when this might be ready good sir? I am not in a good place right now with my G6, could really use these commands---stuck in TWRP and can boot a rom, but somehow didnt follow your Step 3 in the Root guide, and my misc.img didnt get moved over, thus I have a rom that cannot connect to Wifi due to lack of MAC--this update would be huge, as I would go back to stock and restart this mess.
TIA
That won't help you now. Hopefully you still have the backup of your misc partition that was made in step 2. If so, boot to TWRP, and run:
adb push misc.img /sdcard/
adb shell dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc
-- Brian
how do you flash the update
how do you flash the update? its not a option in the system app
purplekushDGK said:
Opemilekan's method actually worked, had to flash supersu then used flashify to flash h872 twrp. thanks for the response man
Click to expand...
Click to collapse
I used flashify and was promted for a decryption password upon booting recovery. Am I doing something wrong?
(Note that I can still access storage on the original download mode twrp, but not on this one)
Like everyone else I'm also confused as to how I can get the h872 recovery to work without breaking anything since I have the h870 recovery on laf
Stupid question I think, but I get a "Traceback (most recent call last):" after entering ./partitions.py --restoremisc twrp-3.2.1-0-h870.img .
Is there a specific place to put the TWRP ing file ? I think when I run the command its not finding the img.
MudaTrucka said:
Follow the steps exactly in this guide https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 afterwards flash the image provided here in recovery
Click to expand...
Click to collapse
Hey so I already followed this tut last week and have been on root but having issues that this recovery fixes, how can I flash to this TWRP?
Related
My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!
Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?
Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.
Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img
I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.
Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery
I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.
Oh, did you check the md5 checksum of your download?
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers
I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!
Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery
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.
ATTENTION!
You MUST read all the guide BEFORE doing it, if you do it without reading all of it first you may ends up bricking your phone!
Prerequisites:
Asus ZE500KL (may work on ZE500KG, but haven't tested, do it on your own risk) on Marshmallow, NOT LOLLIPOP!
Also, it must have fully booted AT LEAST one time, otherwise, you'll soft-brick it.
If your phone is not on Marshmallow, you can use THIS guide insteadDownload and put the unlocker zip file and the SuperSu zip file in the phone
How To:
1 - Install adb and fastboot driver (follow THIS guide)
Now you can connect the phone to your computer2 - Reboot in fastboot mode with one of the following method:
a -Volume Up while booting upb -With adb, after enabling USB debugging in developer settings, using:
Code:
adb reboot bootloader
Now that you are in bootloader, you have to boot in TWRP,
download THIS recovery (is the twrp one) and boot in to it, using this command:
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
Code:
fastboot boot TWRP-x-x-x-x.img
(Obviusly the recovery name must be the one you downloaded)
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
It should automaticaly enter in recovery.
Now you MUST flash FIRST ZE500KL_BootloaderUnlock.zip, otherwise you'll brick your phone
Btw, the recovery will mount your phone's memory, so you can put now the files in the phone, if you forgot to do it before
AFTER you installed the unlocker zip, you can install the SuperSu zip
When the install is complete, clear the cache and reboot your phone, now you can enjoy your root!
Downloads:
Latest @MiauLightouch TWRP - 3.0.0.2 Mirror
Latest SuperSu zip - 2.65 Mirror
Bootloader Unlocker (from @MiauLightouch original post) - Mirror
Credits:
@MiauLightouch for pretty much everything
@LuK1337 , @luca020400 and everyone on #titandev for being awesome
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
MuzgontarAco said:
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
Click to expand...
Click to collapse
I would recommend Z00L/T, you will get cm13, official unlock at least.
You Say " May Work On ZE500KG" Is ze500kg already receive Marshmallow Update?
MiauLightouch said:
I would recommend Z00L/T, you will get cm13, official unlock at least.
Click to expand...
Click to collapse
thanks for the advice but my choices are poor with about 5 phones in this price range with this one looking waay better.. getting it via contract so yeah..
How to install supersu zip? Tia.
Working! Have you tried to flash Viper4Android? On lollipop this will break Call recording and FM Radio, maybe this will not be a problem on MM?
Seanjhon027 said:
How to install supersu zip? Tia.
Click to expand...
Click to collapse
Inside TWRP there is a big "Install" button, press it and select the zip
what is the meaning of booted
mohamedelkholy said:
what is the meaning of booted
Click to expand...
Click to collapse
context?
until you saw the lock screen, that's what "booted".
stuck waiting for device
C:\Users\Clynt\Desktop\Android M>adb reboot bootloader
C:\Users\Clynt\Desktop\Android M>fastboot boot twrp.img
< waiting for device >
Ok I don't know where I get wrong but I got this error.
Img file name is ok because I renamed it.
Drivers were installed already.
Developers mode is enabled already.
Windows 7 64bit
Tried rooting this using lollipop and everything went well.
thanks!
UPDATE: i got it. it has something to do with the drivers.
Without opening the bootloader.
Notice. I have not tried it.
http://www.asus-zenfone.com/2016/05/how-to-root-asus-zenfone-2-laser-ze50kl-marshmallow.html?m=1
thanl you man i have rooted my zenfone 2 laser
Thanks very much for this guide and your work.
Can I install the new update v13.10.7.1 when I opened bootloader.
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
thanks
thks TS
now my phone its rooted
Muminek111 said:
Without opening the bootloader.
Notice. I have not tried it.
No... when trace a perequisite link Given..
you really need to unlock bootloader first
wulfe13 said:
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
Click to expand...
Click to collapse
i think isnt permanent, this step is needed to boot into twrp then flashing a unlockBL..
to make permanent.. the command must "fastboot flash recovery twrp_X.X.X.X.img"
but make sure to unlock bootloader first...
CMIIW
Click to expand...
Click to collapse
Is it me or everytime I reboot the device after rooted, it's going back to unrooted?
Root is a success tho, great job, OP!
Edit: okay, not every reboot, but after several reboots, then it went back unrooted
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?
greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.
I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck
I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root
Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.
mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!
greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot
mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot
fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?
DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff.
What has been tested and works:
- Touchscreen
- Installing flashable zips
- Flashing images
- Flashing the recovery itself
- Creating backups (to internal storage, sdcard or OTG)
- Restoring from backups
- Terminal
- adb
- Rebooting to system, recovery, bootloader, ...
That doesn't mean that other things don't work. It just means they weren't tested yet. As I proceed with testing I will update the above list.
Usage (without flashing)
Bash:
# boot to bootloader
adb reboot bootloader
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
If you want to flash you have 2 options
Bash:
# boot to bootloader
adb reboot bootloader
# ********* OPTION 1 *********
# Flash to active slot (replace <slot> with either a or b, depending on the current active slot).
# Of course, you can flash to both by first specifying a and then b.
fastboot flash recovery_<slot> twrp-3.5.2_10-kiev.img
# ********* OPTION 2 *********
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
# Once in the recovery, copy the twrp image file to your internal storage
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
# Then go to Install, then Install image, select the twrp image you pushed before.
# Then select the Recovery partition and swipe to confirm.
# Before swiping you will have the option to decide if you want to flash to both slots.
Download: google drive
Sources will be posted in due time and this post will be updated accordingly.
Built for: Motorola Moto G 5G (Motorla One 5G Ace)
My model: XT2113-3 (kiev)
Credits
To the guys over here for the device tree, especially to SyberHexen for providing me with useful information.
reserved
reserved
Great!
Tested on my Moto G 5G XT2113-3. Seems to work properly. Good job. Awaiting to flash it.
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
It won't brick. I used it. (only once)
clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
h3xmind said:
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
Click to expand...
Click to collapse
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Tomspector said:
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Click to expand...
Click to collapse
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me.
I will do it now,
I would help
h3xmind said:
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me
Click to expand...
Click to collapse
I will do it now
Tomspector said:
I will do it now,
I would help
I will do it now
Click to expand...
Click to collapse
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Tomspector said:
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Click to expand...
Click to collapse
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
h3xmind said:
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
Click to expand...
Click to collapse
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Ok, thanks for your help. I won't be testing anything tomorrow. I have a day off with my family
Tomspector said:
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Click to expand...
Click to collapse
Should be here: https://mirrors.lolinet.com/firmware/moto/kiev/official/
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Anyway, I flashed it by doing the following:
Bash:
# boot to bootloader
adb reboot bootloader
# boot to twrp
fastboot boot twrp-3.5.2_10-kiev.img
# push the recovery image to the Download folder
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
Once inside the recovery I went to Install, then Install image, once I selected the twrp-3.5.2_10-kiev.img file that I previously pushed, twrp asked me on which partition I would like to flash it. I selected the Recovery partition. (Although I ask myself why does the phone have a separate recovery partition if it is an A/B device. I still have to figure this out. Normally in these devices one would have to pack the recovery into the boot imate and than flash the whole thing to the boot partition.)
Then I rebooted to recovery and it took me directly to twrp. The problem, however, is that the touch screen didn't work anymore. So, I guess I got myself some extra work But it'll be fun. I can't wait to put my hands on it.
Did you manage to find the rom for your phone?
PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
I tried Hexen's recovery. It's easily fixable to make the touch work. It took me two minutes. I'll let the guys working on it know how to do it. But first I have to figure out why does the touch screen stop working once you flash the recovery.