Not sure why the original GPE 5.1 thread got closed, but anyway I've created a TWRP flashable update for the LMY47O.H9 to LMY47O.H10 OTA that recently became available. It only works for clean H9 installs that are NOT rooted.
How-to and download: http://mostlyirrelevant.info/2015/10/07/lmy47o-h10-ota-update-htc-one-m8-gpe/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=2708589
Sent from my HTC6535LVW using Tapatalk
Getting an Error Executing updater binary in zip, error.
/system/bin/app_process32 has unexpected contents
/system/app/BasicDreams/BasicDreams.apk has unexpected contents
Please advise!
UPD1 Sorry, it was Philz recovery. Now I got TWRP and getting the same issue with app_process32
UPD2. It seems I have to unxpose and unroot first - but my M8 keeps rooting itself, cannot get into unrooted mode.
radeon_x said:
Not sure why the original GPE 5.1 thread got closed, but anyway I've created a TWRP flashable update for the LMY47O.H9 to LMY47O.H10 OTA that recently became available.
How-to and download: http://mostlyirrelevant.info/2015/10/07/lmy47o-h10-ota-update-htc-one-m8-gpe/
Click to expand...
Click to collapse
Thanks for the update, but it didn't work and causes an error like the post before this.
Unexpected error .... etc.
I got the same errors trying to sideload the original OTA zip through stock recovery, so it must be something in the zip itself.
Maybe a security measure to prevent installing on modded phones.
Would it be possible to post the entire H10 ROM .zip? I usually have problems updating just the OTA file. graffixnyc usually posted it but for some reason that thread got closed.
Thanks!
The issue with app_process32 seems to be related to rooted phones where /system/bin/app_process32 is a symlink to daemonsu. The question is how to unroot the phone. My one recovers rooted state itself...
sudaltsov said:
The issue with app_process32 seems to be related to rooted phones where /system/bin/app_process32 is a symlink to daemonsu. The question is how to unroot the phone. My one recovers rooted state itself...
Click to expand...
Click to collapse
Yeah sorry forgot to account for the app_process32 being modified when rooting.
I've modified the file (now v2) to support rooted LMY47O.H9 (download here: http://mostlyirrelevant.info/2015/10/07/download-update-ota-lmy47o-h9-to-h10-zip/)
Any other patch errors (i.e. not app_process32) are because you're not running a clean H9 install and there's nothing I can do about that.
EDIT: Also in case anyone missed it, there is a full H10 update zip posted here https://www.androidfilehost.com/?w=files&flid=39228, if this OTA patch doesn't work for you.
If you received the OTA notification for H10
Well, I have tried it twice (from H6 I believe to H9 and now from H9 to H10) and it worked and I did not loose any data files! I got the OTA notification and followed the following protocol (I am rooted and running TWRP):
1. Revert any app that had root access (i.e. Adblock... just revert and disable). If you have XPOSED framework you have to revert everything to stock!
2. Withing the SuperUser app (SU), fully "un-root" the phone.
3. Restart (probably not necessary)
4. Install H9 Recovery (I downloaded it from graffixnyc: http://forum.xda-developers.com/showthread.php?t=2708589) Do not forget to at least thank him!
5. Erase cache (Fastboot erase cache) just in case and Restart.
6. Install OTA :good:
7. Done! Now you have to install again TWRP via fastboot (erase cache once again, just in case...) for root access and re-install whatever you had before with root access. :laugh:
Long process but saves me a lot of headaches with data and any other errors may occur...
I uninstalled xposed. I installed v2. And... now I have kind of brick. The coloured dots moving endlessly. ((( Cleared the cache, of course.
sudaltsov said:
I uninstalled xposed. I installed v2. And... now I have kind of brick. The coloured dots moving endlessly. ((( Cleared the cache, of course.
Click to expand...
Click to collapse
Well the initial boot after clearing the cache takes a really long time of course.... But if it really and truly doesn't boot after several minutes just install the full H10 from that other thread.
Seems I have no choice but to sideload (thanks to TWRP) the full OTA H10..
radeon_x said:
Yeah sorry forgot to account for the app_process32 being modified when rooting.
I've modified the file (now v2) to support rooted LMY47O.H9 (download here: http://mostlyirrelevant.info/2015/10/07/download-update-ota-lmy47o-h9-to-h10-zip/)
Any other patch errors (i.e. not app_process32) are because you're not running a clean H9 install and there's nothing I can do about that.
EDIT: Also in case anyone missed it, there is a full H10 update zip posted here https://www.androidfilehost.com/?w=files&flid=39228, if this OTA patch doesn't work for you.
Click to expand...
Click to collapse
I updated succesfully!!
Follow those steps:
1st. Download the ROM : https://www.androidfilehost.com/?w=files&flid=39228
2nd. Copy the ".zip" to SDcard (Make sure to Backup all needed Apps and data.)
3rd. Wipe "Cache" and "Dalvik" !
4th. Install the ROM via Recovery, I used TWRP. In my case there is nothing wiped like internal SD, Data partition, BUT (Make sure to Backup all needed Apps and data.)
5th. Reboot to System
6th. If you are using Xposed you have to install the latest version (xposed-v75-sdk22-x86.zip) from this Tread: http://forum.xda-developers.com/showthread.php?t=3034811
Now enjoy!
cheers,
m_atze
But beware, all you do to your phone and it will be bricked etc. I am not responsible for. So use at your own risk!
m_atze said:
I updated succesfully!!
Follow those steps:
1st. Download the ROM : https://www.androidfilehost.com/?w=files&flid=39228
2nd. Copy the ".zip" to SDcard (Make sure to Backup all needed Apps and data.)
3rd. Wipe "Cache" and "Dalvik" !
4th. Install the ROM via Recovery, I used TWRP. In my case there is nothing wiped like internal SD, Data partition, BUT (Make sure to Backup all needed Apps and data.)
5th. Reboot to System
6th. If you are using Xposed you have to install the latest version (xposed-v75-sdk22-x86.zip) from this Tread: http://forum.xda-developers.com/showthread.php?t=3034811
Now enjoy!
cheers,
m_atze
But beware, all you do to your phone and it will be bricked etc. I am not responsible for. So use at your own risk!
Click to expand...
Click to collapse
Thanks, it's work for me.
btw the original thread is here http://forum.xda-developers.com/showthread.php?t=2706441
After multiple issues I just installed the H9 RUU unrooted from @graffxnyc, then installed the ota which popped up as soon as it rebooted.
For now I'm leaving it unrooted etc until marshmallow drops later this month.
Don't know whats the update for tho. But anyways installed. Maybe to prepare our system for Marshmallow update? Like what cyanogen did?
i'm not sure what's going on, but the update is a POS. Like sure it's a stagefright fix, but they've broken more than fixed it. Im having massive lag issues, the text windows are stuttering at times, unlocking the phone freezes it for a while and there are times where the notification sounds don't even sound off.
Sorry guys. I've had no problems at all.
This Version is woking like charm.
H10 update recovery
Could someone provide the recovery image from the H10 update?!
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've put together an unofficial ClockworkMod Recovery 6.0.1.1 until Koush adds to ROM Manager, tested working for all features except SD card mount. Working on the latter at the moment.
UPDATE: This recovery does work for both GT-N8000 (3g version) and GT-N8013 (wifi version), just confirmed. (8/16/2012)
Notes:
v1 - Touchscreen is a bit if when you have to scroll, please use the volume buttons for scrolling otherwise you may get accidental presses.
Changelog:
v1 - Everything working except SD card mount. You can backup/restore/ROM to internal or external SD card and other CWM features functional.
Flash this in ODIN or Heimdall:
Download HighOnAndroid v1 ClockworkMod Recovery 6.0.1.1
Also, here's stock recovery you can flash in ODIN or Heimdall to revert (and get OTA updates):
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Credits:
Of course to Koush! I used his builder then hacked graphics.c + other files to make it work.
reserved
reserved
Amazing! Can't wait to get my hands on my Note
Sent from my SCH-I535
Way to go buddy!
You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000
cdesai said:
You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000
Click to expand...
Click to collapse
I did initially but had to hack it to make it work.
zedomax said:
I did initially but had to hack it to make it work.
Click to expand...
Click to collapse
Hey Zedo! Check your PM !
I noticed it does not actually backup system.img on my device, nor did any of my attempts from the clockworkmod builder site either. It says it, but skips over in reality. This will be important to fix if indeed it is not backing it up...
EDIT: Nevermind... I guess the system.img was hiding from me
Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...
akxak said:
Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...
Click to expand...
Click to collapse
It's in your clockworkmod/backup directory. Now, with the new CWM, it stores backups as pieces of files under clockworkmod/blobs directory. This saves a ton of time when doing multiple backups as "blobs" store bits of your filesystem so when doing similar backups, it's not going to backup everything again.
Make sure you copy the whole clockworkmod folder to hard disk for moving though due to this new blobs feature. Your backup folder sizes might be much smaller because of this blobs thingee.
zedomax said:
I used his builder then hacked graphics.c
Click to expand...
Click to collapse
???
Please tutorial graphics.c ...Thanks by Notonlyeyes
I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?
gol-D said:
I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?
Click to expand...
Click to collapse
Did you do:
Code:
heimdall flash --recovery recovery.img
There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.
Zedomax......greatstuff...root access on the N8010 no problem at all
....................................................................................................
Entropy512
Will try to do this now... But it'll be N8010.
Ive got the file for the N8010 on my desktop, but XDA isnt letting me upload the file keeps failing - any thoughts?
Dc
Sent from my GT-N8010 using Tapatalk 2
Entropy512 said:
There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.
Click to expand...
Click to collapse
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.
zedomax said:
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.
Click to expand...
Click to collapse
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)
Entropy512 said:
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)
Click to expand...
Click to collapse
Well, I am just waiting for samfirmware to upload some official images, rather enjoy some of my note 10.1 first for awhile, it's pretty fascinating device, I've never used a tablet for a long time before getting this one, makes my life more productive. Yeah, what's up with Megaupload, that move by feds should have been illegal.
I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!
greenzkool said:
I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
Flashing a recovery or kernel image in Odin will cause the binary counter to increase.
Flashing it using dd or Mobile Odin from a rooted system will not make it increase.
So the "safest" way to root is currently to flash that root-injected system image linked a few posts above, as it's fully unrootable and won't trigger the counter.
I have visitors most of this weekend so won't be able to do much work - once I get my kernel source tree properly set up I'm going to work on getting TriangleAway working on this device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is only for Honor 8 Pro (DUK)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x.
Intended for usage on stock emui 5.x in combination with unlocked bootloader .
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-duk.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official PHH Superuser Beta 310[/U][/B]
1. download and flash [URL="http://superuser.phh.me/superuser-r310-beta.zip"]official PHH Superuser Beta 310[/URL]
2. install "Phh Superuser" from Google Play
3. Enjoy!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_honor_duk/releases/download/3.1.1-1/twrp-3.1.1-1-duk.img"][U]download twrp-3.1.1-1-duk.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 25. June 2017
Q: which H8 Pro models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
A: Yes you can! (Check FAQ)
Q: Can i install Magisk?
A: No (encrypted /data), Yes (decrypted /data)
Q: Does official SuperSU work?
A: No (encrypted /data), Yes (decrypted /data)
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with fileencryption disabled in fstab
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 8 Pro
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin/android_device_honor_duk
Version Information
Status: Beta
Created 2017-06-23
Last Updated 2017-06-25
Reserved
Changelog
Code:
[B]TWRP 3.1.1-1[/B]
* fix twrp on emmc based devices
Man that was fast. Will definitely flash this after I get my H8 Pro.
Sent from my Honor 8 using XDA Labs
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
blattes86 said:
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
Click to expand...
Click to collapse
this should work for every h8 pro utilizing emmc storage:
https://drive.google.com/open?id=0BxWP2gF_0Bd_OHBPWDctZmJCanc
It has been tested.
Regards
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
OldDroid said:
this should work for every h8 pro utilizing emmc storage:
It has been tested.
Regards
Click to expand...
Click to collapse
I flashed it, it works fine.
Thanks
adriansticoid said:
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
Click to expand...
Click to collapse
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
-=MoRpH=- said:
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
Click to expand...
Click to collapse
That's great news. Thanks for confirming. :highfive:
Sent from my Honor 8 using XDA Labs
I flashed emmc version and supersu. For going in twrp I've to clic in the middle of the volume button and the power on.
Interesting, i tried to install it but i'm stuck with installion...i know how to enter fastboot mode with phone plugged to my computer with android sdk on, but the adb files look to be missing when i check with cmd...
Can anyone here give a quick tutorial ? Thanks
New Version (3.1.1-1) available - You can find more infos in OP.
This release fixes partition mounting on emmc 5.1 based devices
Source code is now also up and can be built!
https://github.com/OpenKirin/android_device_honor_duk
Regards
Wow that was faster than I could learn to do it.
Great job. May I ask how you got the important informations to build this?
Did you inject su into the image to gain root and then read all the detailed data through terminal or adb or root file explorer?
Just asking cause i train my brain more and more in my spare time and want to get behind the knowledge base to learn. :good:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do I need to choose?
Cheers
Would this work on the Chinese V9 variant?
smouker said:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do IP need to choose?
Cheers
Click to expand...
Click to collapse
Format the whole internal storage to remove encryption.
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
can I restore Data via TWRP without problems?
adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
smouker said:
can I restore Data via TWRP without problems?
Click to expand...
Click to collapse
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
blattes86 said:
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
Click to expand...
Click to collapse
What do you mean to restart the partition is new encrypt?
adriansticoid said:
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
What do you mean to restart the partition is new encrypt?
Click to expand...
Click to collapse
sorry for my bad english.
After restart the phone...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All seems to be working except Encryption.
So that means you have to erase usedata!
If you don't know how to return back to a working state if something is broken, please think twice before flashing this.
Please do read the installation guide note !
IMPORTANT NOTE :
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
If you plan on using this on stock and have no root you wont be able to see any files due to encryption. To fix this FORMAT not wipe userdata then either flash supersu and not pass safety net or flash one of my roms(New one incoming)
Working
Everything except what's not working, see below
Not working / issues
Encryption
Logs
To get logs: Advanced ---> Copy log
Installation Guide :
1. Download all files below on pc.
2. BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
2.5 BACKUP ALL YOUR DATA AS IT WILL BE WIPED!
3. Boot your phone to fastboot mode.
3.a If you already have twrp disregard the next 2 lines
4. Flash the twrp from below. Using the command "fastboot flash boot /path/to/twrp.img
5. Boot to recovery through the fastboot menu.
6. Go to wipe---Format data(FOR UNENCRYPTION)
6.a IF ALREADY UNENCRYPTED JUST MAKE SURE YOU REFLASH YOUR ROOT OPTION
7. When it says type in yes do it.
8. Wait to finish then plug phone into pc.
9. Transfer supersu to your phone.
9.a Transfer magisk if you use it
10. go to install and find the supersu/magisk zip you just pulled over.
11. Flash it and reboot.
12. Profit!
12.25 Go through the setup process to get to settings. Go to security and check it your phone says encrypt. If it does your good.
IF WANTING UNENCRYPTION ON STOCK YOU HAVE TO FLASH SUPERSU AS MAGISK DOESNT FULLY UNENCRYPT THINGS YET IF ON A ROM LIKE MINE FLASH WHAT EVER LOL
Update Guide:
1. Download new twrp
2. Boot to twrp
3. click on downloaded twrp
4. flash
5. REFLASH WHATEVER ROOT YOU HAD SUPERSU OR WHATEVER OR ELSE YOU WILL BOOT LOOP!
Download Links :
Newest TWRP FLASHABLE PLEASE TAKE A LOOK AT NUMBER 5 ABOVE
FASTBOOT FLASHABLE TWRP 3.2.0.0
Newest SuperSu
Newest Magisk
CHANGELOG:
V3.2
UPGRADED TO LATEST 3.2.0.0
ADDED LATEST UPSTREAM FROM @Uzephi
V3.1
FIXED BOOTLOOP
NEWEST KERNEL AT THIS TIME OF WRITING
V3
Ability to flash bootlogos!
Ability to backup and restore bootlogos
Ability to Backup,Restore and wipe OEM partition.
Ability to flash magisk(must be stock with oem partition in tact to PASS if your ok with cts profile mismatch then modify all you want)(Our phones use the new AVB Verity DM Verity 2.0 pretty much lol)
Bug Fixes and other stuff im forgeting.
Twrp is now flashable! just download the zip in the current twrp and flash!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:JBATS
Source:JOEMOSSJR
Kernel Source:JOEMOSSJR
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-11-10
Nice
Sent from my SM-N930F using XDA-Developers Legacy app
Woow, very nice present GREAT JOB!!!
Great job man. The people in our group can't thank you or your people enough. We appreciate all the hard work you guys did to get this working for us. Thank you again!
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Uzephi said:
In your source, you used my nash_defconfig, please advise. TY for getting it to work!
https://github.com/jbats/android_ke...android-7.1/arch/arm64/configs/nash_defconfig
Edit: you also pasted the same info I did from line 647-822 on line 823-998, essentially having extra code not needed.
Click to expand...
Click to collapse
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
jbats said:
All history is maintained in the git repo linked in source. Credit is given in that aspect but essentially you only removed a few defconfigs than honestly you could have left alone. The prebuilt kernel included in recovery has been upstreamed a bit by myself. If anything I owe credits to Motorola for source.
Click to expand...
Click to collapse
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Uzephi said:
822-998 was already in nash_defconfig. You didn't need to add those lines again. Yes, all I did on that source was make sure the defconfig was correct because Motorola gave us a wonky defconfig as you know from Slack. I also cleaned up the other defconfigs which aren't needed when the source on my git was only for Nash and no other device, so it was code not needed. That's fine, I'll bow out and stop.
Click to expand...
Click to collapse
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
jbats said:
I'm not in the other chat group and don't mean to offend you. Maybe came off a bit harsh but when I said what you removed from the source was wrong I meant it to be more of constructive criticism. The extra lines are a oversight on my part from lack of sleep between working on the kernel and recovery. :good:
Click to expand...
Click to collapse
My kernel source can be built after a clone with any Linux install. I was actually going to upstream it this weekend, so no kernel work was needed besides the upstream.
joemossjr said:
All seems to be working except Encryption.
So that means you have to erase usedata!
Please do read the installation guide note !
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) .
Installation Guide :
Make sure you have unlocked bootloader
Backup all the data because it will be formatted
Reboot to bootloader
Use the command fastboot erase userdata
fastboot flash boot TWRP3.1.1.0nash.img (if you want permanent flash) or fastboot boot TWRP3.1.1.0nash.img (if you want temporary boot)
Then use @Chainfire cfar we have and run it normally (if you need instructions there here)
Once this does its thing you will have root and twrp!
boot to system and go through the setup process and make it to settings ----> security and see if you see encrypt.
If you do that means your good! You can now reboot to recovery and do what you want!
Download Links :
TWRP 3.1.1-0
CFAR
Bugs: Right now if you flash magisk it wont boot up due to the kernel not being decryptable still working on it atm!
Credits :
@jbats for putting in all the work and getting source together!
@themustached for helping with root
@Chainfire for supplying the cfar and being a beast
@topjohnwu for working magisk
Source:https://github.com/jbats/android_device_motorola_nash-twrp
Testers:
Please post below if you tested
Version Information
Status: beta
Stable Release Date: 2017-10-11
Created 2017-10-11
Last Updated 2017-10-11
Click to expand...
Click to collapse
(instructions were not clear I got my **** stuck in the toaster) jk but could I still do it if I didn't use cfar and got SuperSU a alternate way or will it not affect it
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
joemossjr said:
Lol this guy. I just tested a new way (apparently I was flashing an old twrp but I'm about to update the thread in a little bit) anyways you'll be able to just flash twrp and SuperSU and be good
Click to expand...
Click to collapse
Another question would I be able to flash this with flashfire my computer isn't booting up and if yes what would I select? (And yes I'm very new to all this I only started last year with all this Android modifications)
How are you rooted
joemossjr said:
How are you rooted
Click to expand...
Click to collapse
I'm on the stock boot image with SuperSU installed just a normal root no Xposed and no magisk either although I had magisk originally
( I used a friend's computer when I went to visit him if that's what you meant)
thread updated if any questions please pm me
Thanks ..getting device tomorrow ....
Sent from my Nexus 6 using Tapatalk
kenbrownstone said:
Thanks ..getting device tomorrow ....
Click to expand...
Click to collapse
No problem!
Is this all I need to do to get root and twrp?/seems simple or to simple to be honest.I know nothing about how to root/ROM a motoz..Had a z droid but was verizion..Got a tmo zforce2 coming ..
Sent from my Nexus 6 using Tapatalk
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Amd4life said:
Few things, awesome job.
Internal SD card is still encrypted, so all the files are jumbled.
SuperSU is installed
Only some files will flash (osmosis BusyBox), but other zip files will not write to the system properly(Xposed, meli sound mod are a no go).
Xposed will install through the app.
Curious as to what I did wrong?
Click to expand...
Click to collapse
your files are all jumbled because you didnt format data. xposed wont write right for some reason idk about the sound mod tho. Im about to update twrp here shortly
TWRP 3.2.1_r12 Moto Z2 Play (albus)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03
I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.
Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.
3.1.2_r18 version released. Check download link in OP
hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?
fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok
rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.
Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?
Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.
I make a full backup, so can I restore that backup file after LineageOS?
This works when go command fastboot boot .... ?
I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...
Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).
For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
Recommended TWRP from TWRP 3.3.1-xx Unified Unofficial by mauronofrio
**Official TWRP may not allow you to boot twrp.img**
OOSNativeCallRecording Module seems to be one culprit. Make sure to Uninstall before updating.
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop
you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image
mac796 said:
you should add what to do if you can't boot twrp. Happened to me after I removed Google dialer framework. Only thing I could get it to is bootloader. would not let me fastboot TWRp. I got an error every time. I had the flash boot image
Click to expand...
Click to collapse
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.
diaztradeinc said:
This happened to me the other day. Took me an hour to figure out that all I had to do was fastboot boot.img.
Click to expand...
Click to collapse
I will update it shortly, thank you for the feedback.
Bradl79 said:
For those who encounter a bootloop because of a Magisk Module or got a bootloop during an update because of a module
This will allow you to go and delete that bad module and allowing you to boot back into the OS
What you need:
TWRP from here
If you already have twrp then go to Instructions
If you do not have TWRP and do not want to Install, use this method
Boot to TWRP (for those of us who do not install TWRP)
Does not work with OxygenOS 9.5.3 and below
Make sure to have adb and fastboot files here
1. Download the TWRP image (not Installer) from post above
2. Boot to fastboot
3. Rename TWRP image to twrp.img and move to folder with adb and fastboot files (after you had extracted)
4. Type
Code:
fastboot boot twrp.img
Instructions
1. Boot to TWRP
2. Go to Advanced > File Manager > data > adb > modules
3. click on the folder of the module you want to delete
4. while inside that folder click on the little folder on the bottom right with the check mark on it
5. click Delete
Done... Reboot back to OS without a bootloop
Click to expand...
Click to collapse
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...
matze19999 said:
Just install the magisk module "Magisk Manger for Recovery".... Done. No need for such long instructions...
Click to expand...
Click to collapse
It's actually pretty simple, u just have to provide more instructions for people who haven't used twrp. There is no need to flash anything, ik that the uninmod does not work and I thought I tired mm and could not get it working either.
I use MM for TWRP since years and it always worked perfectly.
matze19999 said:
I use MM for TWRP since years and it always worked perfectly.
Click to expand...
Click to collapse
Have u used it with ur 7Pro yet? I tried it yesterday and would not flash along with uninmod would not mount magisk, I think it's issues with dual partition bc it did the same with my OP6
Bradl79 said:
Have u used it with ur 7Pro yet?
Click to expand...
Click to collapse
yeah. Whats not working for you?
matze19999 said:
yeah. Whats not working for you?
Click to expand...
Click to collapse
Got error when flashing, would u mind sharing the file?
Bradl79 said:
Got error when flashing, would u mind sharing the file?
Click to expand...
Click to collapse
I got the one to install from the download section but I've never used it I'm not sure how it works
He's right uninmod and stuff like that doesn't work at all now. It's unable to mount magisk.img it seems to be an issue with our twrp.
As for the statement about the issue being dual partitions that's wrong it's has nothing to do with that. I know he mentioned that uninmod and others did not work on op6 as well.. But it did cause I used uninmod on my 6 and 6T. This is an issue with this device only and possibly the twrp we have currently.
You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:
equlizer said:
You saved my ass today! I updated to 9.5.9 and had bootloops. I forgot to disable my magisk modules :silly:
Click to expand...
Click to collapse
Are u using OOSNativeCallRecorder module?
Yes i was using it. Just re-installed it.
Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?
spart0n said:
Saved my ass!
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
So do we need to disable modules before updating? The re enable after?
Click to expand...
Click to collapse
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson
mlock420 said:
Duh what you think? Lol naw for real tho...I've learned that after updating never reinstall mods that aren't up to date with the current os....I can't speak for all mods but magisk roms like renovate ice needs to be updated to the current os or problems will occur....I'm a noobish noob but I learned my lesson
Click to expand...
Click to collapse
Well what I'm getting at is that I deleted all 4 of my magisk mods and fixed the bootloop and then reinstalled all 4 of them and rebooted and everything is fine now. I was asking about should we disable all mods, reboot, update, install magisk, reboot, check root with magisk then reinstall all mods and reboot again?
equlizer said:
Yes i was using it. Just re-installed it.
Click to expand...
Click to collapse
You prob only need to Uninstall that next time b/c that is one that is causing issues. I do not use and I have multiple Modules that survive update not needing to uninstall all modules.
Thanks. I had problem with pernament bootloop after magisk instalation.