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?
Related
Hello everyone. I just sold my Moto X so I will no longer be updating this toolkit. I will try and help anyone with questions/problems when needed.
Back by popular demand...
I have had some people asking for links for my previously deleted toolkit.
So I have decided to revamp the toolkit for dev edition devices only. (Currently only supporting GSM dev (AT&T and T-Mobile) and VZW Dev)
With this toolkit you will be able to the following...
1) Root your device (unlock bootloader, install TWRP, install superSU)
2) Unroot your device
3) Return to stock
4) Debloat (google, moto, vzw stuff)
5) Activate mobile hotspot (VZW only)
6) reboot (recovery, bootloader, device)
7) Customize (bootanimation, bootlogo, ringtones, notifications)
How to use
1) Click download below
2) Extract zip file
3) Turn you phone on
4) Make sure USB debugging is enabled
5) Plug your phone into the computer.
6) Run moto_x_mac_tools.tool
7) FOLLOW ONSCREEN INSTRUCTIONS
Screenshots
See attachments...
Download
Moto X Toolkit v2.03
Change Log
v2.01 - Fixed some bugs with restoring back to stock, removed ReadWrite status (with dev edition this status is not needed)
v2.02 - Added downgrade from 4.4.2 to 4.4
- When returning to stock, or downgrading, USER DATA will be erased (no longer an option)
- There are only 2 variants of the dev edition so I changed to Verizon and GSM
v2.03 - Updated to latest supersu and TWRP
Please do not redistribute/mirror this toolkit. If you would like to link it in any other thread, please include a link back to this thread, give proper credit.
As with anything you will find on XDA, I am not responsible for anything that occurs to your phone or computer by using this toolkit.
Credits
DHacker29 / Hashcode - TWRP
Chainfire - SuperSU
imnuts - VZW tether
Google
Motorola
Awesome, I used your old toolkit to flash stock recovery (so I could take the ota) and then back to TWRP. It was so easy! I'm sure others will appreciate this as well.
iamjackspost said:
Awesome, I used your old toolkit to flash stock recovery (so I could take the ota) and then back to TWRP. It was so easy! I'm sure others will appreciate this as well.
Click to expand...
Click to collapse
Toolkit is ready for download!!
unlock with moto first?
Do I need to unlock my bootloader with Motorola before using the toolkit? I do have a VZW Dev device, but wanted to confirm.
This utility is amazing and a must for anyone with a Mac! Thanks x100!
moonzilla said:
Do I need to unlock my bootloader with Motorola before using the toolkit? I do have a VZW Dev device, but wanted to confirm.
Click to expand...
Click to collapse
You can either unlock before using the toolkit. Or you can use the toolkit to guide you through the unlock. If you go to root device. The 1st question is if you are unlocked or not. If not, it will guide you through the process of unlocking the bootloader (semi-automatic). Let me know if you have any questions.
Mike
Thank you for re-posting this tool.
I am trying to go back to stock 4.4 to get the OTA (I have a Dev Ed VZN Moto X). I followed the on screen directions and downloaded the VZN 4.4 file (640 MB file). Then the phone reboots to bootloader (ReadWriteMode is 0). I press ENTER since the device has booted into FB mode and it says USB connected, the ReadWriteMode reads error: device not found (I did not unplug the phone from the computer).
Is there a fix for it? The same thing happens when I try to download 4.4.2.
Thanks
wmjchoi said:
Thank you for re-posting this tool.
I am trying to go back to stock 4.4 to get the OTA (I have a Dev Ed VZN Moto X). I followed the on screen directions and downloaded the VZN 4.4 file (640 MB file). Then the phone reboots to bootloader (ReadWriteMode is 0). I press ENTER since the device has booted into FB mode and it says USB connected, the ReadWriteMode reads error: device not found (I did not unplug the phone from the computer).
Is there a fix for it? The same thing happens when I try to download 4.4.2.
Thanks
Click to expand...
Click to collapse
When in fastboot mode. The readwrite will say device not found. An ADB command is used to check the readwrite status. And ADB commands do not function while in fastboot mode.
You are ok to continue.
mjphillips1981 said:
When in fastboot mode. The readwrite will say device not found. An ADB command is used to check the readwrite status. And ADB commands do not function while in fastboot mode.
You are ok to continue.
Click to expand...
Click to collapse
Thanks.
I pressed enter to continue but my phone just reboots and restore does not work.
But when I tried to flash the stock recovery, readwrite says 0 and works like a charm. The problem only occurs when I try to restore the device.
wmjchoi said:
Thanks.
I pressed enter to continue but my phone just reboots and restore does not work.
But when I tried to flash the stock recovery, readwrite says 0 and works like a charm. The problem only occurs when I try to restore the device.
Click to expand...
Click to collapse
I will test on my device. I will let you know what I find out.
mjphillips1981 said:
When in fastboot mode. The readwrite will say device not found. An ADB command is used to check the readwrite status. And ADB commands do not function while in fastboot mode.
You are ok to continue.
Click to expand...
Click to collapse
mjphillips1981 said:
I will test on my device. I will let you know what I find out.
Click to expand...
Click to collapse
Thank you!!
wmjchoi said:
Thanks.
I pressed enter to continue but my phone just reboots and restore does not work.
But when I tried to flash the stock recovery, readwrite says 0 and works like a charm. The problem only occurs when I try to restore the device.
Click to expand...
Click to collapse
I found a typo in the script. I am trying it now. Should see a new download shortly. Thanks for pointing this out.
mjphillips1981 said:
I found a typo in the script. I am trying it now. Should see a new download shortly. Thanks for pointing this out.
Click to expand...
Click to collapse
Not a problem. Again, thank you for making a great tool! I will test out the new version and report if there are any problems. Let me know when the new one is up.
wmjchoi said:
Not a problem. Again, thank you for making a great tool! I will test out the new version and report if there are any problems. Let me know when the new one is up.
Click to expand...
Click to collapse
v2.01 is ready for download.
mjphillips1981 said:
v2.01 is ready for download.
Click to expand...
Click to collapse
It worked. I was able to upgrade to 4.2.2. Thank you so much. One thing though, the color on the screen is off. So far it looks like the color red is off. This might be my device only. I am going to flash 4.2.2. again and see if it happens again.
wmjchoi said:
It worked. I was able to upgrade to 4.2.2. Thank you so much. One thing though, the color on the screen is off. So far it looks like the color red is off. This might be my device only. I am going to flash 4.2.2. again and see if it happens again.
Click to expand...
Click to collapse
I just did the factory restore to 4.4.2 and all of my colors are ok.
Make sure you erase user data when it asks you. But this will erase everything.
mjphillips1981 said:
I just did the factory restore to 4.4.2 and all of my colors are ok.
Make sure you erase user data when it asks you. But this will erase everything.
Click to expand...
Click to collapse
I did the factory restore again to 4.2.2 but I still have the same issue. I think something is wrong with my display. I think I need to call vzn and have them send me another unit.
---------- Post added at 07:24 PM ---------- Previous post was at 06:47 PM ----------
mjphillips1981 said:
I just did the factory restore to 4.4.2 and all of my colors are ok.
Make sure you erase user data when it asks you. But this will erase everything.
Click to expand...
Click to collapse
Should i downgrade to 4.4? Or is it a bad idea?
wmjchoi said:
I did the factory restore again to 4.2.2 but I still have the same issue. I think something is wrong with my display. I think I need to call vzn and have them send me another unit.
---------- Post added at 07:24 PM ---------- Previous post was at 06:47 PM ----------
Should i downgrade to 4.4? Or is it a bad idea?
Click to expand...
Click to collapse
Here is what I would do...
Just install TWRP and install Eclipse 3.2.1. This is the ROM that I use. It is great!! See if that fixes your color issue. If it does not. They I would say your device is f-ed up.
http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-blur-based-v2-2-t2521509
mjphillips1981 said:
Here is what I would do...
Just install TWRP and install Eclipse 3.2.1. This is the ROM that I use. It is great!! See if that fixes your color issue. If it does not. They I would say your device is f-ed up.
http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-blur-based-v2-2-t2521509
Click to expand...
Click to collapse
I tried flossing Eclipse 3.2.1 and the color was still off. My camera is not working as well. Maybe I will lock up the boot loader and restore it to 4.2.2 again. But your tool works great.
Currently on the phone with Motorola...
I should not downgrade to 4.4, right?
wmjchoi said:
I tried flossing Eclipse 3.2.1 and the color was still off. My camera is not working as well. Maybe I will lock up the boot loader and restore it to 4.2.2 again. But your tool works great.
Currently on the phone with Motorola...
I should not downgrade to 4.4, right?
Click to expand...
Click to collapse
I am not sure if you can downgrade or not with a dev edition. I have never tried. I know some people that have a consumer VZW (locked bootloader) cannot downgrade.
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.
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
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
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?