Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
Related
Hard brick for OPT happens when you change critical partitions. It will follow improper firmware flash or accidental erase of certain partitions. The phone won't show any response when hardbricked.
The solution for OPT is similar to OPO - you just need a Qualcomm driver and a recover package. The only full recovery package available is very big and it restore the phone to Hyrdogen OS, with everything wiped. So it would not be very attractive.
Fortunately, thanks to this post from Chinese supporting forum, a minimal version of restore package is provided. It does not wipe user data and guarantee a recovery entry. you would normally be freed using this package. if not, please use the full package in the end of the post
Download link for driver
Download link for Recovery tool
uncompress the files to a local folder.
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Now your OPT should be able to enter TWRP recovery. It still won't boot but you can manually flash anything again (like the full Oxygen OS package).
The procedure is tested by me twice. Enjoy!
p.s: sorry the recovery image in the A2001_save_brick_mini.rar is Chinese. Please download this file, change the name to recovery.img and substitute the file in the recovery tool before flashing.
UPDATE：full Oxygen OS 150805 restoration package for those who experience recovery entry problem. Note that this package wipes everything including internal storage!
Awesome, I will go ahead and make a full recovery tool that includes these files as well as the latest version of OxygenOS as I did with the Oneplus one.
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
CoreGaming said:
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
Click to expand...
Click to collapse
Like i did before with my mod of the toolkit
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
okay and were can i get this package for the OPT?
CoreGaming said:
okay and were can i get this package for the OPT?
Click to expand...
Click to collapse
Havn't made it yet, still need to work on it. It is a little different than OPO so it might take some time.
okay this will be great. Take your time i'm ready
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Lord Boeffla said:
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Click to expand...
Click to collapse
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Zyxxeil said:
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Click to expand...
Click to collapse
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Click to expand...
Click to collapse
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Click to expand...
Click to collapse
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Lord Boeffla said:
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Click to expand...
Click to collapse
HydrogenOS definitely has the option because it is how I flashed TWRP in the first place
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
Without recovery how do you flash hydrogenOS?
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Wow thanks, I was trying to do it with the one you posted but I couldn't since it was missing the info for system sectors. Now i can make my tool
Zyxxeil said:
Without recovery how do you flash hydrogenOS?
Click to expand...
Click to collapse
Using this tool and the full recovery package? Or am I missing something here?
khr0n0s said:
Using this tool and the full recovery package? Or am I missing something here?
Click to expand...
Click to collapse
The tool posted does not contain a system, but he is going to post the full one soon.
Zyxxeil said:
The tool posted does not contain a system, but he is going to post the full one soon.
Click to expand...
Click to collapse
Precisely, that is exactly what I meant. Fingers crossed that will solve this.
It could be I successfully recoverd following a hint by user @Zyxxeil (many thanks for the help).
If all works I will post soon what I did.
But - have everything running now again. Next I try to flash twrp again and root. If that worked, I will post the steps.
Andi
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Very nice. Wait for it...
Is a Version with Oxygen OS also aviable?
Quick fast post. Fix it up later.
Unofficial TWRP for the SM-G360T1
Step 1:
You should know how to flash twrp by now.
Step 2:
Profit
Download link:
https://www.androidfilehost.com/?fid=24052804347820600
Known issues:
Usb otg not working. Will fix later.
Enjoy. Hit thanks or donate and all that good crap [emoji14]
Mine
THANK YOU ONCE AGAIN @ShinySide!!! Not only for root, but now for a working custom recovery. Truly the 2 most important tools we could have for our phone.
FOR EVERYONE ELSE:
As usual, be sure to give @ShinySide your Thanks/Donations/etc.!!! He deserves it! Also, now that you have TWRP you might be wondering what to do next. Here are a couple of suggestions of things that I've already done and that I am quite happy with.
1) Theme it! - Here are some themes you can try out that will not only make TWRP more beautiful, but also provide a layout that is more intuitive and user friendly. These are listed in a Galaxy S2 thread yes, but I've attached a picture of the one that I'm currently running and I'm happy to say that it works on our phone like a charm. I've also used these themes on other phones in the past. Just follow the instructions in the OP of that thread and give the guy some thanks on that thread if you like them. There is no risk in this btw. Either it works or it doesn't and to get rid of it if you don't like it you just have to delete the theme folder that you placed in TWRP. (Try to use the files that say "480x800" as that's the resolution of our screen.) Here is the link: http://forum.xda-developers.com/galaxy-s2-plus/themes-apps/theme-materialised-t2933979
2) Add the Xposed Framework - Go to this link here: http://forum.xda-developers.com/showthread.php?p=62377731
Then, install the Xposed app from the link on that thread. After that, you're going to want to pick the file attached to the OP of that thread that is called "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip" and save it to the root of your external SD card. (Do not download the one that says "ARM64" in it. Just the one I mentioned.) Then, just flash it via TWRP and reboot. You should now have the Xposed Framework installed. Once, again be sure to give the OP thanks on that thread too!
NOTE: After flashing Xposed it may hang on the MetroPCS screen on the next reboot for up to 15-20 mins or so while it's doing stuff. If it's any longer than that, then just pop the battery out and reboot. It will boot properly after that while it reoptimizes some apps.
OK something not right everytime I flash the twrp I keep getting the 2.8.70 instead of the version of This 2.8.1.0 one I need help cause everything is correct I keep getting that old version instead of this new version but twrp 2.8.7.0 still works good but I want the version right here
Deandre7452 said:
OK something not right everytime I flash the twrp I keep getting the 2.8.70 instead of the version of This 2.8.1.0 one I need help cause everything is correct I keep getting that old version instead of this new version but twrp 2.8.7.0 still works good but I want the version right here
Click to expand...
Click to collapse
2.8.7.0 is right. The picture I attached of my themed one I just downloaded from the theme thread because I couldn't take a screenshot from TWRP. Everything is good. No need to worry.
Thanks....glad to know that but everytime I reboot to system from twrp it keep going right back to the twrp instead of system that's what I worry about I have to keep flashing the kernel root cause the twrp not working right but ima get the theme to see what happens next
Deandre7452 said:
Thanks....glad to know that but everytime I reboot to system from twrp it keep going right back to the twrp instead of system that's what I worry about I have to keep flashing the kernel root cause the twrp not working right but ima get the theme to see what happens next
Click to expand...
Click to collapse
It shouldn't be doing that. Also, you should just make sure your TWRP is properly installed first before you do anything else to it. Maybe try rebooting your phone just by holding the power button once instead of selecting reboot system and see if it boots correctly then.
Sent from my SM-G360T1 using Tapatalk
I don't think it's right now I have the same picture frame u have in the picture but still not 2.8.1.0 at the top it have the 2.8.7.0 up there at the top of it and another thing is I can't flash anything everything else good but can't swipe to install so I need to get this right cause I don't be having problems with nothing else when I do stuff for my device
Deandre7452 said:
I don't think it's right now I have the same picture frame u have in the picture but still not 2.8.1.0 at the top it have the 2.8.7.0 up there at the top of it and another thing is I can't flash anything everything else good but can't swipe to install so I need to get this right cause I don't be having problems with nothing else when I do stuff for my device
Click to expand...
Click to collapse
Again, it is supposed to be 2.8.7.0 . Don't go by the picture I posted it was just a sample of what I had. Not a screenshot. Also, it doesn't need to look like mine to work. Theming it was just for fun and should only be done after you've successfully installed TWRP. Anyhow, try flashing this stock recovery file here. Then, boot into stock recovery and make sure you can still reboot to Android from there. If so, then go back and try flashing the TWRP recovery file again instead and see if that fixes the problem. No one else should flash this file by the way unless they are trying to go back to stock recovery for whatever reason. Thanks!
Sent from my SM-G360T1 using Tapatalk
Good job
Awesome! Goood job dude, can't wait till you write up the proper instructions. I'm a noob so don't want to do something wrong.
Another masterpiece By @shineside....
A great BIG Thank you @Bogarty For helping to bring this all together.
We have root, we have TWRP, and that's all thanks to @ShinySide! Great work!
Ok yall I just did a splash screen if anyone don't know but everyone have the color theme already go to the page here http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 scroll down to the change the recovery splash screen download the AIK file First when it finish flash it before anything download the splash set zip when it finish unzip that file then u download the trap kernel root are if u already have it on the device use any root explore renamed the tar.md5 to .img now go to recovery flash that AIK before you start anything hit where u change your theme color but click on change splash then u put the trap kernel.img on the first slot then the second slot click inside the splash set folder choose what color u want then flash it then there u go a new splash screen set......this for anyone that don't know
bogarty said:
It shouldn't be doing that. Also, you should just make sure your TWRP is properly installed first before you do anything else to it. Maybe try rebooting your phone just by holding the power button once instead of selecting reboot system and see if it boots correctly then.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
So, should this NOT work and it continues to reboot to TWRP what comes next? ? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
i am oblivion said:
So, should this NOT work and it continues to reboot to TWRP what comes next? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try flashing through ODIN again. Make sure you are in actual download mode (meaning don't use the option in TWRP, use the key combo), and flash it again.
Maybe we could get another youtube video? What do you say, "TheDerek"?
xRaZeR_FuZioNx said:
Try flashing through ODIN again. Make sure you are in actual download mode (meaning don't use the option in TWRP, use the key combo), and flash it again.
Click to expand...
Click to collapse
Ok, that's next on the agenda. Gonna take a walk and get myself calmed down before I resume troubleshooting. Thanks for the helpful and speedy response. And the bit about booting into Download Mode using the button combo over the TWRP option - I actually had no idea there was a difference there. I've gathered several boot/recovery zips and tars just in case and am tracking down the T-Mobile version of the g360t1 firmware as well (to cover all my bases, because when it rains it pours ?). Anyhow, I'll report back once I have something to report and thanks again guys ?
i am oblivion said:
Ok, that's next on the agenda. Gonna take a walk and get myself calmed down before I resume troubleshooting. Thanks for the helpful and speedy response. And the bit about booting into Download Mode using the button combo over the TWRP option - I actually had no idea there was a difference there. I've gathered several boot/recovery zips and tars just in case and am tracking down the T-Mobile version of the g360t1 firmware as well (to cover all my bases, because when it rains it pours ?). Anyhow, I'll report back once I have something to report and thanks again guys ?
Click to expand...
Click to collapse
i am oblivion said:
So, should this NOT work and it continues to reboot to TWRP what comes next? ? Ok, you got me. It continues to reboot into TWRP. I've never encountered this scenario before (granted I've never flashed a custom recovery via ODIN before either, but it went as expected up until I did a backup and tried to reboot into the system) and no, I didn't bother with trying to fancy up TWRP. I don't want TWRP looking unfamiliar. Any help would be greatly appreciated.
Click to expand...
Click to collapse
It has to be something you guys are doing during the flashing process that is causing it to boot into TWRP instead of Android. I would try flashing the Trapkernel again from download mode to see if that gives you boot, then if so, try flashing TWRP again. Both should be flashed in AP slot of ODIN. Make sure OEM Unlocking is checked in developer options, etc.
If that doesn't work and it still boots to TWRP, then you may have messed something up in there somehow. Try flashing back stock boot and stock recovery and make sure boot and stock recovery were restored. Once that's working, then you can try reflashing Trapkernel and TWRP. Use this link for more info on restoring your phone and for links to the stock files if you need them.
http://forum.xda-developers.com/showthread.php?p=62906680
Sent from my SM-G360T1 using Tapatalk
Theres a problem, I cant moutn system in Twrp and because of that i cant update SU binary and some apps dont work :/
cmurder61 said:
Theres a problem, I cant moutn system in Twrp and because of that i cant update SU binary and some apps dont work :/
Click to expand...
Click to collapse
Try reinjecting TWRP using the option in settings.
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Click to expand...
Click to collapse
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
UPDATE: Confirmed, this method does work to update to DP5 from DP4.
Reserved
I'm going to try this.
Really want root on my sh**t.
But, theoretically, when DP5 is out, you'll have to do everything again, but with the Vendor image from DP5?
asj0422 said:
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
Click to expand...
Click to collapse
By how some people roll around these forums, I'd remove the lines from the copy/paste box-thingy you did... haha.
Edit: fell on my a**. Reminder for me to be more helpful
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Edit: fell from my pedestal, note to self: be more helpful.
asj0422 said:
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
Click to expand...
Click to collapse
Kudos. Always good to have a write up with steps for folks. Thanks for contributing. [emoji6]
Thanks for this post; I think it really helps having a quick reference for something like this. I can confirm that if you need to re-access TWRP, you can just flash the marshmallow vendor.img over adb, boot to TWRP, do what you have to do, return to bootloader, flash the nougat vendor.img in adb, and continue using your device. I had to use TWRP to flash the Adaway systemless support zip and doing that sequence I listed above worked as expected. It's not as ideal as having TWRP function with an encrypted device as it does on marshmallow, but at least it works.
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
benleonheart said:
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Click to expand...
Click to collapse
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
SyCoREAPER said:
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
Click to expand...
Click to collapse
Worry not, dear friend as I was also a noob back in '08/'09.
We all learn new things every day. I'm just saying that there are dedicated threads to help with newcomers and guide them step by step.
Edit: You're right. Thanks.
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Sweet! This was easy peasy and didn't lose my data. No serious issues, either. Thanks for sharing this info.
Cheers
Sent from my Nexus 6P using XDA-Developers mobile app
crossen0 said:
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
To be honest, I'm not sure. I've never had to deal with twrp and no password. I wouldn't think it would reset anything; I assume you just won't have to enter a password..?
What do you normally do for twrp?
thanks for the guide. Do you think if I'm already on DP4 I could flash the vendor image from an M build and continue from there?
edit: it worked!
Thank you this worked like a charm! Switched from a rooted+busybox stock build to rooted DP4. Now waiting for DP5
No problem! Glad it worked for you!
asj0422 said:
No problem! Glad it worked for you!
Click to expand...
Click to collapse
Just upgraded from my stock M + rooted + busy boxed + xposed build to DP5. TWRP and SU both working. Thanks for the guide.
Just updated to DP5 using this method (all flashes but vendor and recovery, flash M vendor, boot into TWRP, root, reboot to bootloader, flash DP5 vendor). Works perfect.
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
mtw4991 said:
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
Click to expand...
Click to collapse
Thanks for the extra info!
Question: doesn't twrp work with N as it did with M if you're not encrypted? I thought the issue with twrp and N was due to twrp's code not being able to decrypt - and that was the whole reason people were using the modified boot.img and decrypting was so twrp would work.
I can also confirm that this works with DP5. Will be updating OP shortly.
XDA:DevDB Information
[STOCK] Official Moto G5 Cedric firmwares [TWRP], ROM for the Moto G5
Contributors
Livi-Tech
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP or TWRP 64 bit
Based On: Stock
Version Information
Status: Testing
Created 2018-02-03
Last Updated 2018-02-03
--Requirements--
TWRP or TWRP 64 bit
--Downloads--
( waiting for upload )
--Setting up--
Power off your Moto G5 device
hold volume down and power button to boot into bootloader
press volume down twice till it says RECOVERY MODE
press the power button to select
wait for twrp to start up
tap wipe
tap advanced wipe
tap Dalvik / ART cache
tap System
tap Data
tap Cache
drag the blue arrow to the right to wipe
tap back
tap the <I button to go back
tap the <I again to go back
--Installing--
tap Install
tap select storage
tap internal storage or sd card depending where you downloaded your twrp zip file
tap the zip file
drag the blue arrow to the right to confirm flash
( Testing Status by the way, i've only tested on my device so would like some others to test this method, if something does go wrong I have a Fastboot install method that has been confirmed working on different variations of the G5 Cedric
What's the point of this? Does it do something different?
aaronboy205 said:
What's the point of this? Does it do something different?
Click to expand...
Click to collapse
TWRP is a portable way
some people are scared of using fastboot + this way they can keep twrp without the firmware not liking it + the TWRP installation is much faster but this method is mainly for people who want to keep twrp without needing to modify anything, are scared of fastboot or want to do a quick install
aaronboy205 said:
What's the point of this? Does it do something different?
Click to expand...
Click to collapse
Sometimes people don't want to do all the steps for going back to stock so having a flashable zip it's a bit faster and easier.
@Livi-Tech when I did flashable stock people had issues getting zip booted so I disabled dm verity and force encrypt from kernel but you can attach this to the main post so people don't run into the same issues.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Fedray said:
Sometimes people don't want to do all the steps for going back to stock so having a flashable zip it's a bit faster and easier.
Click to expand...
Click to collapse
It is, I wouldn't create something that didn't have a point to it, me personally I hate using fastboot because watching all the commands run kind of scares me a bit knowing something could go wrong
Fastboot
1) got to connect usb cable, open up command prompt, make sure the device is recognized
2) wrong command could mess stuff up
3) take ages
4) got to type in loads of commands
TWRP
1) portable method
2) automatic install
3) system doesn't play if you make modifications, flash any system modifying files, etc
4) much much faster than fastboot by miles
Fedray said:
Sometimes people don't want to do all the steps for going back to stock so having a flashable zip it's a bit faster and easier.
@Livi-Tech when I did flashable stock people had issues getting zip booted so I disabled dm verity and force encrypt from kernel but you can attach this to the main post so people don't run into the same issues.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Click to expand...
Click to collapse
My TWRP versions have boot.img files with dm-verity already turned off and disabled, thank you though
Livi-Tech said:
TWRP is a portable way
some people are scared of using fastboot + this way they can keep twrp without the firmware not liking it + the TWRP installation is much faster but this method is mainly for people who want to keep twrp without needing to modify anything, are scared of fastboot or want to do a quick install
Click to expand...
Click to collapse
Oh okay thanks! ?
WAITING
I´m waiting for this.
Download links ??
Reserve threads arent allowed on xda afaik. Hurry up or thread gets blocked
Sonisudhanshu said:
Download links ??
Click to expand...
Click to collapse
My internet cut out last night so still uploading
I'm uploading directly to XDA that's why no download links are available yet
Thread closed, place holders NOT permitted. PM me when you are ready to post a download link.
Waiting download link yet... :/
Do you have link to this firmware please?
jason13v8 said:
Do you have link to this firmware please?
Click to expand...
Click to collapse
I already have a fastboot tutorial
go onto my profile
click on thread started by livi-tech
you should find one that says official moto G5 Cedric firmwares [Fastboot]
jason13v8 said:
Do you have link to this firmware please?
Click to expand...
Click to collapse
I'm shutting this thread down for a while
unless there is someone willing to test my twrp version
Livi-Tech said:
I'm shutting this thread down for a while
unless there is someone willing to test my twrp version
Click to expand...
Click to collapse
I'll look for link to twrp version and test it for you today. There's already a debloated stock zip file here on XDA I flashed yesterday. I'll let you know how it goes thanks
---------- Post added at 09:44 AM ---------- Previous post was at 09:35 AM ----------
Livi-Tech said:
I'm shutting this thread down for a while
unless there is someone willing to test my twrp version
Click to expand...
Click to collapse
You don't seem to have a twrp version for me to test, the only one I see in your profile is fastboot which I avoid at all cost.
jason13v8 said:
I'll look for link to twrp version and test it for you today. There's already a debloated stock zip file here on XDA I flashed yesterday. I'll let you know how it goes thanks
---------- Post added at 09:44 AM ---------- Previous post was at 09:35 AM ----------
You don't seem to have a twrp version for me to test, the only one I see in your profile is fastboot which I avoid at all cost.
Click to expand...
Click to collapse
why do you avoid fastboot ( I already know some reasons someone might but curious about your reasons )
you've used fastboot before to unlock bootloader?
I've even tried fastboot erase all and all it wiped was data, System, cache so my device was perfectly okay,the Moto G5 bootloader seems more protected than other phones
and no I don't I was going to upload one but I bumped into problems on my device ( unrelated )
Livi-Tech said:
why do you avoid fastboot ( I already know some reasons someone might but curious about your reasons )
you've used fastboot before to unlock bootloader?
I've even tried fastboot erase all and all it wiped was data, System, cache so my device was perfectly okay,the Moto G5 bootloader seems more protected than other phones
and no I don't I was going to upload one but I bumped into problems on my device ( unrelated )
Click to expand...
Click to collapse
I have used fastboot a few times with sumsung devices but at present I have windows 10 and seem to get nowhere with it and yes I unlocked my bootloader I used one click root company to root and flash twrp £29 i think it's an XDA set up thing you give them permission to take over your computer and even their engineer nearly gave up after about 2 hours. I have used kingroot and Odin many time and persisted until success but with Moto G5 I surrendered and got help for the sake of time and energy. Plus your original post I thought said it was for people who struggle with fastboot. Like I said there is a stock zip available and it worked via twrp. If you can't upload them should you not delete the thread? Thanks:good:
jason13v8 said:
I have used fastboot a few times with sumsung devices but at present I have windows 10 and seem to get nowhere with it and yes I unlocked my bootloader I used one click root company to root and flash twrp £29 i think it's an XDA set up thing you give them permission to take over your computer and even their engineer nearly gave up after about 2 hours. I have used kingroot and Odin many time and persisted until success but with Moto G5 I surrendered and got help for the sake of time and energy. Plus your original post I thought said it was for people who struggle with fastboot. Like I said there is a stock zip available and it worked via twrp. If you can't upload them should you not delete the thread? Thanks:good:
Click to expand...
Click to collapse
I need someone to test ( not just the normal it boots up test because I already know it boots up and everything works )
My bootloader already says status: modified and right now I have an IMEI problem which is preventing me from making and receiving calls/texts, I won't upload my versions until I know they aren't going to trip the bootloader status or cause the same call/text problems I have for people who flash it
which is why i'm looking for a tester who doesn't care if their bootloader changes from official to modified and doesn't care if they lose ability to call and text.
with your fastboot Issue, could you have a look on my instructions in my [fastboot] thread and tell me if you get fastboot to recognize your phone, i'm not asking you to flash anything, just asking if you could use those instructions and see if fastboot picks up your Moto G5, ( i'm curious as to why your having so much trouble as I am also on windows 10 ) also currently what rom are you using on your Moto G5?
Just flash the zip in TWRP to change your boot logo. These should work for any model of the G6 Play. All backgrounds are white with the exception of the original boot logo. This was done to cover up that annoying bad key or N/A message. Enjoy!
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
the-her0 said:
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
Click to expand...
Click to collapse
Yep, check back in like 10-15min and I'll make that a logo.
Edit: Done!
Motorola Moon
This took me a few hours. Hope you folks like it. I'll probably make a few more over the next several days.
Is there a tutorial anywhere on how make these?
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Motorocker said:
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Click to expand...
Click to collapse
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
madbat99 said:
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
Click to expand...
Click to collapse
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Motorocker said:
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Click to expand...
Click to collapse
That's because TWRP can't read encrypted storage. Has to on your SD card.
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
flash713 said:
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
Click to expand...
Click to collapse
https://forum.xda-developers.com/mo...-boot-logo-maker-source-t2848667/post54841085
Can someone make boot.logo in HavocOs style?
Who can make logo.bin for havoc-os? I’m attaching a picture, and below it should be moto g6 play