Related
So this thread started as just a guide for root but with all the questions being asked lately I have decided to turn it into a full blown info thread this is going to take some time and some section might be empty so please bare with me.
Device Variants
(this display is not 100% correct still working out some issues and info!)
XT1049 - Republic Wireless
XT1052 - European - Sim ?
XT1053 -T-Mobile US, Dev Ed
XT1055 - US Cellular - Sim ?
XT1056 - Sprint - Sim Unlocked
XT1058 - AT&T, Rogers, Claro, Movistar, Vivo, Oi, TIM - Sim Unlocked
XT1060 - Verizon - Sim Locked
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What Devices Can Unlock There Bootloader
In this section we are going to go over what devices can have there bootloader unlocked and what ones can't this is very simple.
(if it dose not says Dev Ed next to the carrier then I am talking about consumer model.
Locked Bootloader – Verizon, AT&T, Republic Wireless
Unlockable Bootloader – Sprint, US Cellular, T-Mobile, Rogers, all Dev editions
Personally these are the ones I am not sure about yet so if you have one please let me know so I can add them.
? - Claro, Movistar, Vivo, Oi, TIM
If you want to check to see if your device is unlockable please go to motorola's website below
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Downgrading Bootloader
there has been a lot of issues around this process so I want to post the info right at the top so people stop bricking there device and we can get past this
here is a quick list of what can be done with bootloader downgrading
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
here is a thread dedicated to the discussion of bootloaders and modems
http://forum.xda-developers.com/showthread.php?t=2635366
Informative Thread Google Cached
READ CAREFULLY
WARNING
DO NOT FLASH THE NEW 4.4.2 SBF FIRMWARE UNLESS YOUR CARRIERS FIRMWARE IS AVAILABLE.
FOLKS HAVE FLASHED OTHER CARRIERS FIRMWARE AND AS A RESULT THEY HAVE NO DATA CONNECTION,
YOU CAN NOT DOWNGRADE, SO IF THIS HAPPENS CHANCES ARE YOU'LL HAVE A PHONE THATS UNUSABLE UNTIL AND IF YOUR CARRIERS SBF SHOWS UP.
THERE IS A CHANCE THAT EVEN AFTER YOU FLASH THE CORRECT FIRMWARE, YOUR RADIO SIGNAL MAY NEVER WORK
I will not in any fashion help anyone to upgrade nor downgrade their moto, this thread is for info only. I personally will not take any responsibility for any issues. You own it ., you alone broke it
Motorola bootloader unlocking website https://motorola-global-portal.custh...-your-device-a
WARNING WARNING
DO NOT FLASH ANY OTA 4.4.2 ,OTA ROM OR ANY SUCH MEANS OF UPGRADING WITHOUT HAVING YOUR SPECIFIC CARRIER 4.4.2 SBF FIRMWARE AS A BACK UP
WARNING WARNING WARNING
IF YOU HAVE A LOCKED BOOTLOADER ONLY FLASH YOUR SPECIFIC CARRIERS SBF FIRMWARE, OTHERWISE YOU WILL END UP WITH A HARD BRICKED DEVICE
************************************************** ********
If you Frankenstein a way of downgrading do not post it here, this thread is not about tricks, hacks or any such garbage. This thread is to inform folks in the correct way of maintaining your moto to work. Plain and simple
There's a tremendous amount of firmware flashing which is causing harm to many users phones.
Realize that having a unlocked boot loader moto, regardless if its a DE will also suffer from hard bricks.
Unlocked boot loaders can flash other variants system.img's without to many issues
Modems are a different story, some user report no data with European modems, so I suggest using your specific carriers modems
Stay away from motoboot.img (boot loader) or gpt.bin(partition table) be warned
Remember you and you alone are responsible for any hard bricks
********************************
This is a simple chart what can and can't not be downgraded, Thanks to Dray_jr 
the only OTA that can downgrade is 4.4 to 4.2.2 Post Cam
here is what we know right now that might make more sense
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
************************************************** **************
WARNING if you manage to flash back to 4.4 or even 4.2.2 with the new 4.4.2 BOOTLOADER DO NOT UNDER ANY CIRCUMSTANCE ACCEPT ANY OTA, YOU WILL HARD BRICK YOUR DEVICE, PROOF BELOW
Quote
******** "it was running on 4.4.2 software, then i downgrade to 4.2.2. all was fine, but OTA killed it.
So after that, i read that 4.4.2 instaled new bootloader =( that cant be downgraded, and can bricked the phone, it was my mistake =(
So i think i should sent it to Motorola and if i lucky one, they should repair it, or resend new one. or if bad luck i will throw it to the trash =)"*******
Files inside sbf firmware:
Motoboot.img (bootloader)
gpt.bin ( Partition table)
NON_HLOS (modem)
System
Recovery
Bootloaders:
4.4.2 North , Central & South America:
Rogers 30.B4
US Cellular 30.B4
Brazil Retail 30.B4
T-Mobile 30.B4
Sprint 30.B4
Europe:
UK 30.B3
Modems:
Rogers 4.4.2
Stock Recovery:
Rogers Stock Recovery 4.4.w
4.2.2 pre camera boot loader 30.70
4.2.2 post camera bootloader 30.71
Issues:,
Confirmed by Steve x , you can not downgrade bootloader from 4.4.2
WARNING WARNING
The Brazilian phone and central American phones will not have a data connection with the uk or DE firmware, so do not flash any European firmware, be warned
I will credit correct posters when i get back to my pc
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Custom Recovery's
Now this is fairly simple there are 3 custom recovery options for us right now 2 for unlocked bootloaders and 1 for locked
here are the options we have and links to there threads for info and downloading
TWRP
http://techerrata.com/browse/twrp2/ghost
CWM
http://forum.xda-developers.com/showthread.php?t=2612149
Safestrap
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How to Take OTA on Root Device
flashallthetime said:
Ok tired of answering thus question constantly
To accept and flash an ota you must have the following phone set up
1) Stock recovery. No it will no flash with twrp or cwm
2) All root removed completely from your system
3) Xposed framework completely removed from your system, uninstalling will not work,you need to flash the xposed Disabler zip
4) Any mods to any system file must be reverted to stock
5) Running the stock odex ROM
6) Any system apps frozen must be unfrozen
If you have at any point of time flashed any 4.4.2 firmware along with the boot loader 30.B3 or 30.B4
DO NOT FLASH THE OTA, YOU WILL HAVE A HARD BRICKED MOTO
HOPE THIS HELPS
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Locked Bootloader
[SIZE="3"]Step one[/SIZE]
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
RockMyMoto(4.2.2 root exploit)
http://forum.xda-developers.com/attachment.php?attachmentid=2369524&d=1383521170
Cydia Impactor(Required for 4.2.2 root exploit)
http://www.cydiaimpactor.com/
MotoWpNoMo(Kill Write Protect on Locked Bootloaders)
Win - http://www.rumrunner.us/MotoWpNoMo-0.0.4.zip
Linux - http://www.rumrunner.us/MotoWpNoMo-0.0.4.tar
SlapMyMoto(4.4 Root exploit)
http://forum.xda-developers.com/attachment.php?attachmentid=2463879&d=1387477699
RSD Lite(Used for downgrading to 4.2.2 camera update)
https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
4.2.2 Camera Update Firmware(download firmware for your device)
http://forum.xda-developers.com/showthread.php?t=2568334
Below are Complete Kits that i put together for Each Carrier Moto X
it contains all the files needed to Root/Downgrade/Return To Stock or what ever you need to do.
I will be posting Links as i upload them.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step two
Downgrade to 4.2.2 Camera Update
If you are on the 4.4 update already your are going to have to downgrade your device to 4.2.2 camera update. The best way to do this is to follow the guide in the link below.
Ok so more and more people are Bricking there phone with RSD Lite so i am going to add in the guide to manually flash all the img's because i no longer will refer to RSD Lite for the fact that i dont find it safe anymore.
To Flash back to 4.2.2 Camera Update Manually Follow the Below Steps it is very simple.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
Now it is time to move on to Step three and root your device
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Three
Rooting 4.2.2 camera update and disabling write protection
Before you can start to root 4.4 you first need to root 4.2.2 camera update and disable write protection. below are two links the first one is to root 4.2.2 camera update and the second one is for disabling write protection
4.2.2 Camera Root Exploit
http://forum.xda-developers.com/showthread.php?t=2509590
Disable Write Protection
http://forum.xda-developers.com/showthread.php?t=2551113
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Four
Returning back to stock again so you can start rooting 4.4
i know you have already done this but in order to root 4.4 you have to be completely stock. So use the same guide and firmware as the last time to restore your device to stock again i no longer will recommend RSD Lite so below is the steps to manually flash your device back to stock
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Five
Root 4.4 Finally
Now that we are back to 4.2.2 camera update it is finally time to start the process to root 4.4 just follow the guide below and you will finally have your device on 4.4 with Root
4.4 Root Guide
http://forum.xda-developers.com/showthread.php?t=2538896
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How To Unlock Your Bootloader
Unlock your Bootloader
This Will Erase your Data/ Factory Reset your phone
In order to install TWRP/CWM and SuperSU you need to first unlocked your boot loader. below is a link to Motorola's guide to do just that.
Click on the link below and pick your Moto X by what carrier you are with
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215/action/auth
im going to try and do this the best i can but no matter what i do your going to have to go to the moto website to get the unlock key
download the SDK and install it.
locate ware it was installed normally (C:\Program Files\Android\android-sdk)
open Command Prompt and type
Code:
CD C:\Program Files\Android\android-sdk\platform-tools
put phone into bootloader
type below commands in CMD
type
Code:
fastboot oem get_unlock_data
it should come back with something like this
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Now we need to remove all the (bootloader) and make the key into one line
we then need to paste this into the box on the bottom of the Moto unlock page and hit the button "Can my Device be Unlocked"
if your device can be unlocked you need to accept the license agreement and then click the button to request your key. It will then email you your unlock key.
Copy your unlock key then click the link Step 3
now if you left your device connected and everything ware it was then great if not we need to put are phone back into bootloader and open a CMD and CD it to the same directory as before.
then type
Code:
fastboot oem unlock UNIQUE_KEY
ware Unique_key being the code you copied from your email.
now your bootloader is unlocked.
Sorry this guide is not great but it is the best i can do for the fact that you have to be on the moto website to get your unlock key. i hope this helps somewhat.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting Unlocked Bootloader
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
TWRP Recovery
http://techerrata.com/browse/twrp2/ghost
CWM Recovery
http://forum.xda-developers.com/showthread.php?t=2612149
SuperSU
http://download.chainfire.eu/supersu
MFastboot(Used for flashing TWRP)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
How to install TWRP/CWM Recovery and SuperSU
Now that you have your bootloader unlocked its time to install are custom recovery and SuperSU so we have Root
Before we worry about that phone please make sure you have installed the SDK and then copied the mfastboot files over to the directory your ADB is in.
also before we put the phone into bootloader mode we need to copy the SuperSU.zip over to are phone
Now that we have all that moved over everything that we need. it is time to get are phone into the bootloader you can do that by turning off your phone, Then turning it back on while holding volume down + the power button.
once into the bootloader plug your USB cable in and set your phone down.
now we need to open a CMD window and CD to the directory ware we placed the MFastBoot files.
this is my location but i use the Moto X toolkit yours is going to be ware ever you install the SDK
so in the CMD window type the command below but change the path to ware your files are located
Code:
CD C:\Program Files\stillthisguy\Moto X Toolkit
now that we are in the right location it is time to install TWRP/CWM we are going to do that by typeing the commands below
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
or what ever the name of your recovery img is
as soon as you type the above command to flash TWRP/CWM we need to boot the phone into recovery before we let it boot to android we can do that via the buttons below.
click the Volume - button until it highlights Recovery then press the Volume + button to select it and it should boot into recovery.
If you do not immediately boot your phone into recovery after you flash it, recovery wont work.
here is a step by step that might help everyone abit
Cozume said:
Try this:
1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
If that doesn't work, repeat but omit step 4.
Click to expand...
Click to collapse
Now click on Install and find your SuperSU.zip that we copied over and click on it and install it. when it is done installing you can reboot your phone and enjoy having root access.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download pick what firmware you want from the link below
http://sbf.droid-developers.org/phone.php?device=0
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Full OTG support on 4.4.2 or older builds via Qualcomm settings
aviwdoowks ask for me to include his guide in my post so here yall go if you need support the link below is to the original thread
OP Thread
Update
This is, at least, a stock/rootless solution. The OTG/UsbDisk is now system wide! /storage/UsbDisk! Root Explorer/Explorer (free)! The standard issue "Documents" apk browses it too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You may use many apps to browse your new /storage/UsbDisk, this is a good one.
https://play.google.com/store/apps/details?id=fm.clean
You need to create a shortcut to qualcomm settings.
The: com.qualcomm.qualcommsettings.apk is in your system/app!
I posted it for custom rom users, but it will not show up even if you install it.
I use Super Manager donation. The free version works too. (apk manager, choose activity button. The gear: launches the activity, the arrow creates a shortcut on homescreen.). I use Xperia launcher.
Then enable usb mass storage and OTG mode - peripheral. The usb will get reset but there is no need to keep it on. OTG mode sticks. Edit: try it w/o the usb checked it may not be needed at all.
Done.
Go File manager, /storage. Permissions will be rwx even from the free version.
You have a new mount/unmount option in settings/storage:
Be sure to use (^ above button) the unmount command as forgetting you have a write operation in progress and yanking out the otg adapter can trash your SD card!
I do not wonder why Moto did not enable this ability!
No need to download the attached apk. It is in your system apps already. But some custom ROMs may not have it.
USEonlyIFnotONyourPHONE.4.4.2com.qualcomm.qualcommsettings.apk
USEonlyIFnotONyourPHONE4.4.0.com.qualcomm.qualcommsettings.apk
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Credits
jcase
beaups
TechSavvy2
zhp pilot
Hashcode
Phil3759
flashallthetime
aviwdoowks
if i forgot anyone please let me know
Nice guide! First to reply, lucky!
Sent from my XT1058 using Tapatalk
I guess it would be nice to add the root tutorial for unlocked bootloader, even though it's a quick process. Some people might have little worry about voiding warranty.
Sent from my Moto X
RenSoAbrupt said:
I guess it would be nice to add the root tutorial for unlocked bootloader, even though it's a quick process. Some people might have little worry about voiding warranty.
Sent from my Moto X
Click to expand...
Click to collapse
ok sounds good i will add it
guide for unlocked Bootloaders has been added i think i got everything right lol. please let me know if there are any error's or is i am missing anything. enjoy
Thanks much for this.
Wish things were a lot more straight forward though.
Sorry but I'm not going to grab someone's guide and remake it most of the guides I linked to the creator has done a very good job with them so I want them to get the credit for it
Sent from my XT1056 using XDA Premium 4 mobile app
Yes! This is exactly what I needed. I had the jist of what needed to be done, but had trouble wrapping my head around the correct order of all the different steps. When a root process requires links to 10 different guides, you really need a Master guide like this. Thanks
Sent from my Nexus 7
No problem man glade it helped
Sent from my XT1056 using XDA Premium 4 mobile app
dray_jr said:
No problem man glade it helped
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i have botloader unlocked
i flashed recovery
///solved to get into recovery
when i boot into recovery says no comands
danger2u said:
i have botloader unlocked
i flashed recovery
///solved to get into recovery
when i boot into recovery says no comands
Click to expand...
Click to collapse
i answered your question in your thread in Q and A
TWRP problem...
So I flashed TWRP to my phone. The flash went through fine, but when I tried to boot into recover it just comes up with the No Command error. Any thoughts?
AceBearpaws said:
So I flashed TWRP to my phone. The flash went through fine, but when I tried to boot into recover it just comes up with the No Command error. Any thoughts?
Click to expand...
Click to collapse
Yes this is a very common problem and i am going to edit the OP to try and make sure people dont make this mistake.
ok this is a simple fix
1.boot you phone into bootloader
2. CD adb to the folder with your recovery in it
3. re run the fastboot flash recovery imagename.img
4. do not boot your phone into android
5. right after your phone flashes TWRP type adb reboot recovery
6.it should boot right into recovery this time
for some reason after your flash TWRP you have to immediately boot your phone into recovery before you allow youe device to boot into android or you will have this issue.
Thanks! I'll give it a shot tonight!
---------- Post added at 12:40 PM ---------- Previous post was at 12:09 PM ----------
easting said:
Thanks! I'll give it a shot tonight!
Click to expand...
Click to collapse
Anyone try on XT1060 (VZW)?
I've got a problem hopefully you can help.
I've unlocked my bootloader via the moto website and getting the warning when I restart to say the bootloader is unlocked. I seem to be installing the recovery ok but when I typing adb reboot recovery I'm getting error: device not found.
When I have my phone turned on and I type adb devices it lists my phone. When I'm in fastboot and type adb devices my computer doesn't find my phone.
Do you have any ideas?
Thanks!
dray_jr said:
Yes this is a very common problem and i am going to edit the OP to try and make sure people dont make this mistake.
ok this is a simple fix
1.boot you phone into bootloader
2. CD adb to the folder with your recovery in it
3. re run the fastboot flash recovery imagename.img
4. do not boot your phone into android
5. right after your phone flashes TWRP type adb reboot recovery
6.it should boot right into recovery this time
for some reason after your flash TWRP you have to immediately boot your phone into recovery before you allow youe device to boot into android or you will have this issue.
Click to expand...
Click to collapse
Yeah I actually tracked down your post on another thread, and got it all fixed.
Though I will say this, once I flashed when I typed in adb reboot recovery it said it could not find my device for some reason. If this happens to anyone else you can still get recovery to work as described above with one small difference. It seems the moto x has a tendency to turn right back on the second you turn it off from fastboot. If you are ready for it you can quickly hit power + volume down quickly before it has a chance to boot, and it will get you back into fastboot and the recovery image will work from there.
Thanks!
~ Ace
AceBearpaws said:
Yeah I actually tracked down your post on another thread, and got it all fixed.
Though I will say this, once I flashed when I typed in adb reboot recovery it said it could not find my device for some reason. If this happens to anyone else you can still get recovery to work as described above with one small difference. It seems the moto x has a tendency to turn right back on the second you turn it off from fastboot. If you are ready for it you can quickly hit power + volume down quickly before it has a chance to boot, and it will get you back into fastboot and the recovery image will work from there.
Thanks!
~ Ace
Click to expand...
Click to collapse
Hi Ace
When you are in bootloader does adb reboot recovery work at all for you? How did you get it to reboot into recovery. I just tried flashing the recovery, restarting straight into bootloader and still cant use adb reboot recovery and selecting recovery boots android and starts the phone.
matust said:
Hi Ace
When you are in bootloader does adb reboot recovery work at all for you? How did you get it to reboot into recovery. I just tried flashing the recovery, restarting straight into bootloader and still cant use adb reboot recovery and selecting recovery boots android and starts the phone.
Click to expand...
Click to collapse
I would try reflashing the recovery one more time sounds like something went wrong
Sent from my XT1056 using XDA Premium 4 mobile app
When I flash 4.2.2 (camera update) to downgrade, the device gets stuck at boot splash. Typically with other devices I've owned, this is a sign of a bad kernel flash or an incompatible kernel. Though I've run through multiple times and get the same issue every time.
VZW locked bootloader.
Flashing using mfastboot for Linux.
Bootloader and terminal show successful data transfer and flash on all partitions.
Boot splash just shows the "M" logo without "a Google company" written underneath.
Flashing back to 4.4 yields no issues.
Any thoughts?
Sent from my XT1060 using Tapatalk
dray_jr said:
I would try reflashing the recovery one more time sounds like something went wrong
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've flashed the recovery several times before trying to reboot into recovery and it still isn't working. When I flash the recovery I get the acknowledgement on the command line and the phone. So I think the recovery is flashing. I have set up adb on another computer to try again and its not working either.
When my phone is in fastboot if I type adb devices I get error: no device found. If I type fastboot devices my phone shows up. Any other ideas? This is frustrating me to no ends!
---------- Post added at 08:23 AM ---------- Previous post was at 07:44 AM ----------
After doing some more googling it looks like adb commands won't work when your in fastboot. adb commands only work while the phone is on or in recovery. This sounds like why adb devices won't list the device and why adb reboot recovery won't reboot it to recovery
Ok I now have TWRP installed...yay
There may have been a problem with my firmware from the 4.4 OTA that was stopping me from installing twrp. I reinstalled the stock moto firmware using method 2 from here http://forum.xda-developers.com/showthread.php?t=2446515
I then followed the guide from this thread and installed TWRP with the exception that adb reboot recovery doesn't work in fastboot and did as Ace said and rebooted straight to fastboot and selected recovery from there.
Happy days
I finally managed to install Brazil Lollippop 5.0 OTA on XT1033. I mentioned the detailed process below, following it correctly will get you lollipop on your device.
Note: To install this OTA on your XT1033 you should have your Bootloader unlocked. I don't hold any responsibility if you brick your device.
Downgrading is causing some serious Issues. Be careful
thanks @deeplyyoung for screenshots
ROOTING TUTORIAL CAN BE FOUND HERE :
http://forum.xda-developers.com/moto-g/general/guide-root-xt1032-xt1033-moto-g-running-t2965507
TUTORIAL FO INSTALLING CUSTOM RECOVERY AFTER INSTALLING LOLLIPOP ON MOTO G
http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905
Converting your Asia XT1033 into Brazil version by restoring this Brazil retail file
DOWNLOAD THESE FILES
Lollipop OTA File:
MEGA1--> https://mega.co.nz/#!XMxUgZYC!AnUkb3...Hd3p3kU0xrVhmM
MEGA2-->https://mega.co.nz/#!PoQVEZyL!Jm92SU...jzN9aiO5iOmWLc
MEDIAFIRE-->http://www.mediafire.com/download/0x...asil.en.BR.zip
DEV-HOST--> http://d-h.st/buH [WORKING - Checked 24.12.14]
MEDIAFIRE --> http://www.mediafire.com/download/w112mtufl414nat/Blur_Version.210.12.40.falcon_umtsds.Brasil.en.BR.zip [WORKING Checked 24.12.14]
BRAZIL RETAIL 4.4.4 :
Filefactory--> http://www.filefactory.com/file/7koj5z8zk1mf/XT1033_RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml.zip
Mediafire--> http://www.mediafire.com/download/5...4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml.zip
Google Drive--> https://drive.google.com/file/d/0Bxf-Y_J8GLrJQndtNzhUQmFIV1E/view
Dev- Host--> http://d-h.st/7sG
----------------------------------------------------------------
mFastbootv2 : http://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280
Minimal ADB & Fastboot Drivers: https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view?usp=sharing
You Can read this article on my blog too : http://www.mightygeekstuff.com/install-android-5-0-lollipop-ota-zip-moto-g-2013-xt1033/
Steps to Restore Brazil Retail 4.4.4 Firmware:
NOTE: Flashing this Retail 4.4.4 Firmware will will all the userdata, so backup important files before doing this.
1) Reboot the phone into bootloader mode. There are 2 ways to do this.a) The 'hardware' way.a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.b) The 'software' way.a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open "Minimal ADB and Fastboot".
Type:
Code:
[SIZE=4]adb reboot-bootloader[/SIZE]
You should see the Moto G bootloader screen with the following options:
Code:
Code:
Normal
Powerup
Recovery
Factory
Barcodes
BP Tools
2) Now place & extract the Brazillian Retail File & mFastbootv2.zip in a same folder. Now rightclick anywhere inside the folder while holding Left Shift & select 'Open Command Window Here'. This will take you to the command prompt.
3) Now execute each & every command mentioned below one by one in the same order
Code:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
4) After executing the steps mentioned above, you should now be rebooted into a fully stock Moto G Brazillian firmware.
5) Now connect your phone to the computer & copy the Lollipop OTA zip file in the root of your internal SD card.
Steps to Flash Lollipop OTA onto XT1033:
1) Turn off you phone & boot it into bootloader mode by holding ' Volumed Down + Power ' for 3 seconds.
2) You will be provided with the below options
Code:
Normal Powerup
Recovery
Factory
Barcodes
BP Tools
Navigate & highlight Recovery using Volume Down button & press Volume Up button only once.
3) Now you'll come up with the following screen. Don't hesitate its common.Just carefully press ' Volume Up + Power ' for 3 seconds & release the buttons which will reveal new options on the screen.
4) Now select the option apply update from SD card & select the OTA file which you've copied earlier
5) Now the update starts, wait for a while it will take 15 minutes to update & Voila you finally managed to get lollipop on your device.
LEAVE A COMMENT ON MY WEBSITE, EVEN A THANKS WILL BE APPRECIATED.
COMMENT AT
http://www.mightygeekstuff.com/install-android-5-0-lollipop-ota-zip-moto-g-2013-xt1033/
I Hope This Helped you, Please hit Thanks as a Token of Appreciation
My device is show this in installation:
"system/app/LatinImeGoogle.apk" has unexpected contents.
Installation aborted.
Anybody help me?
Sent from my XT1033 using XDA Free mobile app
waltinho2 said:
My device is show this in installation:
"system/app/LatinImeGoogle.apk" has unexpected contents.
Installation aborted.
Anybody help me?
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
did you modify the OTA ? I mead did you edit any files inside it ?
This type of error occurrs when OTA is modded.
Nooo, I'm just downloaded the zip and put on root folder.
Sent from my XT1033 using XDA Free mobile app
waltinho2 said:
Nooo, I'm just downloaded the zip and put on root folder.
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
@waltinho2 will u b kind enough to upload & share the recovery image of brazilian firmware if u have downloaded it..thanks[emoji1] [emoji1]
Locked Bootloader
lilsidsri said:
I finally managed to install Brazil Lollippop 5.0 OTA on XT1033.
Note: to install this OTA on your XT1033 you should have your Bootloader unlocked.
screenshots will be added soon
Step 1 ) Convert your Asia XT1033 into Brazil version by restoring the Brazil retail file mentioned in this thread
http://forum.xda-developers.com/moto-g/general/link-xt1033-ota-5-0-lollipop-brazilian-t2963565
Step 2 ) After successfully restoring Brazil stock firmware, download and place the OTA file in the root of your internal Sd card.
Step 3 ) No boot into bootloader by powering on your device while holding ' Power + Vol Dwn ' for 3 seconds & select Recovery option.
Step 3) Now you'll face a screen with Green android & Red riangle image, dont worry now just press ' Vol Up + Power ' for 3 seconds and you'll get recovery options.
Step 4) Now select the option apply update from SD card & select the OTA file.
Step 4) wait for the updation process to finish & enjoy Lollipop on your device.
HIT THANKS IF THIS HELPED YOU.
Click to expand...
Click to collapse
Hi There, I have XT1033 the Asia Retail version, non rooted, bootloader locked any way of me getting the lollipop update installed on my phone....
sandyisgood said:
Hi There, I have XT1033 the Asia Retail version, non rooted, bootloader locked any way of me getting the lollipop update installed on my phone....
Click to expand...
Click to collapse
No you cant.. wait for update for Asia retail
Everything going well thill step 4, when I select the file to update i get the following messages:
-Finding Update Package
-Opening Update Package
-Verifying Update Package
-Installation aborted
Do you know why?
sandyisgood said:
Hi There, I have XT1033 the Asia Retail version, non rooted, bootloader locked any way of me getting the lollipop update installed on my phone....
Click to expand...
Click to collapse
I'm on asia retail too, no way to do it besides waiting or converting to BR
That Retail BR link is dead.
joaovitor2763 said:
Everything going well thill step 4, when I select the file to update i get the following messages:
-Finding Update Package
-Opening Update Package
-Verifying Update Package
-Installation aborted
Do you know why?
Click to expand...
Click to collapse
Have u flashed Braz 4.4.3 stock & then u updated OTA? if yes download Braz stock 4.4.4 and give a try, as same happened with me last nyt thrice n then I downloaded the Brazilian stock 4.4.4 n successfully updated ... @lilsidsri few ss for yr ref..
deeplyyoung said:
Have u flashed Braz 4.4.3 stock & then u updated OTA? if yes download Braz stock 4.4.4 and give a try, as same happened with me last nyt thrice n then I downloaded the Brazilian stock 4.4.4 n successfully updated ... @lilsidsri few ss for yr ref..
Click to expand...
Click to collapse
Link for bazil 4.4.4 is not working.
Can you please upload it on Gdrive?
Thanks
deeplyyoung said:
Have u flashed Braz 4.4.3 stock & then u updated OTA? if yes download Braz stock 4.4.4 and give a try, as same happened with me last nyt thrice n then I downloaded the Brazilian stock 4.4.4 n successfully updated ... @lilsidsri few ss for yr ref..
Click to expand...
Click to collapse
I first installed the brazil retail 4.4.4 just as you may see bellow:
Meuuks13 said:
That Retail BR link is dead.
Click to expand...
Click to collapse
Worked fine for me...will try to upload on drive.
Sent from my XT1033 using XDA Free mobile app
deeplyyoung said:
Have u flashed Braz 4.4.3 stock & then u updated OTA? if yes download Braz stock 4.4.4 and give a try, as same happened with me last nyt thrice n then I downloaded the Brazilian stock 4.4.4 n successfully updated ... @lilsidsri few ss for yr ref..
Click to expand...
Click to collapse
yes, I installed 4.4.4 & then installed the OTA.
And everything is working very smooth.
Somebody plz provide retail brazil 4.4.4 mirror?
Sent from my Moto G using XDA Free mobile app
Hi if anyone was successful in updating can you please upload a nandroid backup
Same problem
joaovitor2763 said:
Everything going well thill step 4, when I select the file to update i get the following messages:
-Finding Update Package
-Opening Update Package
-Verifying Update Package
-Installation aborted
Do you know why?
Click to expand...
Click to collapse
I'm exactly the same problem, unlocked the bootloader,
I'm using the stock retail Br 4.4.4 and it did not work,
someone help?
I dont know what to do!
The link for Brazil Retail 4.4.4 is dead. Please re-upload the ROM again preferably on Devhost or Mediafire.
This might be weird but no matter what key combination I try after choosing recovery from bootloader I just cannot see the extra options. So I am unable to flash the new OS. My phone is running on 4.4.4 brazil version and the boot loader is unlocked (status:3)
Edit: The actual procedure is as follows (it worked like this on my phone):
1. Enter recovery
2. Hold volume up key for about 10 seconds
3. While still holding the volume up key press the power button and hold both the keys for few seconds
4. Release and you'll have the option to install from SD card.
ALL IN ONE GUIDE
Unlock + Root + Backup + Restore + Downgrade
For Moto G 2014 (2nd Generation)
titan (3G) : XT1063, XT1064, XT1068, XT1069
thea (4G/LTE): XT1072, XT1077, XT1078, XT1079
(Updated 1st August, 2017)
Requirements:
1. Moto G 2014 2nd Generation (titan/thea)
2. Unmodified Stock ROM
3. Windows PC & Stable Internet Connection
4. Good Quality USB Cable & Functioning USB Port
5. Lots Of Patience & Common Sense
This guide is divided into 4 parts, read the below post & the comments before asking any question. Dont quote the entire post in the comments & ask what is only necessary.
PART I : UNLOCKING
This part is compulsory before proceeding to PART II. Your warranty will be voided after sending a request for an unlock key to Motorola used for unlocking process.
PART II : ROOTING
This part consists of 2 steps, flashing TWRP & flashing SuperSU Zip. After PART II is done, you can now flash custom ROMs, mods, scripts on your Moto G 2014.
PART III : RESTORING
This part is for those who wish to go back to the same stock firmware i.e. 6.0 to 6.0, 5.0.2 to 5.0.2 in case of boot loop, stuck at Motorola logo/boot-animation, BOOTLOADER UNLOCKED screen, OTA Update. You dont need an unlocked bootloader to flash the same stock firmware.
PART IV : DOWNGRADING
This part is for those who wish to revert back to previous Android version. i.e. 6.0 to .0.2 or 5.0.2 to 4.4.4. Please be very careful in this part as it can lead to dead devices if you dont follow the instructions correctly.
Code:
#include
/*
* Your warranty is now VOID !
*
* I am not responsible for bricked devices, dead SD cards,
* accidental data wipe or a thermonuclear war.
* If you have any concerns about steps included in this
* guide please do some research before trying it!
* YOU are choosing to make these modifications & if you
* point the finger at me for messing up , I will laugh at you.
*
* GOOD LUCK !
*/
PART I : UNLOCKING
NOTE:
The warranty of all Non-European phones is lost permanently after UNLOCKING bootloader. LOCKING the bootloader again after UNLOCKING won't give your warranty back.
The warranty of all European phones is not lost after UNLOCKING bootloader. To claim warranty of an UNLOCKED European phone you will need to live in the European Union.
Requirements:
Minimal ADB + Fastboot Drivers v1.4.2
Motorola Device Manager Drivers v2.5.4
Unlock Bootloader Tutorial
Unlock Bootloader YouTube Video
Bootloader LOCKED, Status Code 0 : Bootloader was not UNLOCKED before by the user & is factory LOCKED, UNDER Warranty.
Bootloader UNLOCKED, Status Code 3 : Bootloader is UNLOCKED by the user, Warranty VOID.
Bootloader RELOCKED, Status Code 2 : Bootloader was UNLOCKED by the user & is LOCKED again by the user, Warranty VOID.
1. Users with LOCKED bootloaders will have to first UNLOCK their bootloader before proceeding, this will VOID your WARRANTY.
2. Users with UNLOCKED bootloader need not worry as this process will not wipe anything from the internal storage.
3. Users with RELOCKED bootloader will have to UNLOCK their bootloader again before proceeding, phone will be erased again after UNLOCKING.
4. After UNLOCKING the bootloader your phone's internal storage will be erased. Your installed apps, contacts, SMS, call logs, data like photos, music, videos in internal storage will be WIPED completely.
5. Use 'SuperBackup' App from Playstore & set the location of backup files to external sdcard.
6. Before proceeding make sure you backup everything & move your data from internal storage to external sdcard or PC.
PART II : ROOTING
Requirements
Minimal ADB + Fastboot Drivers v1.4.2
Motorola Device Manager Drivers v2.5.4
TWRP v3.1.1-0 for titan
TWRP v3.1.1-0 for thea
SuperSU v2.82 Stable
A) Flashing TWRP
1. You need to unlock the bootloader before proceeding/
2. Install Motorola & Fastboot Drivers & restart your PC. Copy the SuperSU Zip inside your phone storage.
3. Go inside the installed adb fastboot folder. Hold "Shift" key & right click inside the folder & click on "Open CMD Window Here".
4. Copy the TWRP image file inside installed adb fastboot folder.
5. Switch off the phone, press & hold "Volume Down" & "Power" & release after 4-5 seconds.
6. Connect phone to PC . You will see "USB Connected" on the phone screen.
7. Type and press enter after each command
For titan (3G) : XT1063, XT1064, XT1068, XT1069
Code:
fastboot flash recovery twrp-3.1.1-0-titan.img
fastboot boot recovery twrp-3.1.1-0-titan.img
For thea (4G/LTE): XT1072, XT1077, XT1078, XT1079
Code:
fastboot flash recovery twrp-3.1.1-0-thea.img
fastboot boot recovery twrp-3.1.1-0-thea.img
7. Your phone will now boot into TWRP.
B) Backup Stock ROM (Optional)
1. Inside TWRP, select 'Backup', select 'System', 'Boot' & 'PDS' partitions & swipe to backup your Stock ROM.
C) Flashing SuperSU Zip
1. Select "Install" option, Select the location of SuperSU Zip & flash it, go back & select "Reboot", select "System".
2. Open the App Drawer & check for SuperSU app & then download 'Root Checker' app from Play store to check for root access.
PART III : RESTORING
Requirements
Minimal ADB + Fastboot Drivers v1.4.2
Motorola Device Manager Drivers v2.5.4
Softbrick : Stock 5.0.2 Factory Firmware Image Installer
Hardbrick : Unbrick Moto G 2014 (2nd Gen)
1. You won't need to UNLOCK the bootloader to flash the firmware of your variant for your region. i.e. You can flash firmware on a LOCKED bootloader. However to flash a firmware for different region, your bootloader needs to be UNLOCKED. Check your Moto G 2nd Gen Model No & Regional Variant from here before proceeding. You will need it for downloading factory images for your corresponding phone.
2. If your device gets stuck in following situations it has soft bricked.
- Stuck on Motorola logo or "Unlocked Bootloader" screen.
- Stuck on boot animation or device restarts automatically (boot loop)
- Cannot boot into recovery mode.
- Can boot into fastboot mode only.
3. If your device gets stuck in following situations it has hard bricked.
- Cannot boot into fastboot mode.
- Cannot power on or cannot charge.
- Cannot boot into recovery mode.
Step By Step Troubleshooting Of Your Device
1. Check if it switches on or boots into fastboot menu, if it doesnt maybe the battery is depleted. Use a minimum 1A output charger & keep it plugged in overnight for atleast 10-12 hours. Repeat for 2-3 days. If it still doesnt power on, this means your phone is hardbricked & recovery may or may not be possible. Motherboard replacement might be needed. You will loose all your data & your IMEI number will be changed after your motherboard is replaced.
2. If it switches on & is stuck on Motorola logo/bootanimation or "Unlocked Bootloader" screen, hold power button till phone screen turns off. Your phone will restart, let it continue the booting process. If it still stuck, hold power button till phone screen turns off. After it turns off immediately press volume down while holding power button. Release both after 2-3 seconds. You will now boot into fastboot menu. This means your phone is softbricked & can be recovered by flashing correct factory image for your device. Flashing incorrect image or downgrading from a higher Android version to lower (Eg Marshmallow to Lollipop) may render your device permanently hard-bricked/dead.
PART IV : DOWNGRADING
Requirements
Unlock Bootloader Here
Unlock Bootloader YouTube Video
Minimal ADB + Fastboot Drivers v1.4.2
Motorola Device Manager Drivers v2.5.4
5.0.2 Factory Firmware Image Installer
1. Boot into fastboot mode. Check your bootloader version from top 2nd line. It should say something like "48.86 (sha-5497-c9). 4886 is your bootloader version.
2. Marshmallow 6.0 to Lollipop 5.0.2 : If your bootloader version is 4886 (Marshmallow Bootloader), you need to make some changes in the easyinstaller.bat file inside the Stock Factory Firmware Image that you download or while flashing the ROM manually.
- Download Lollipop 5.0.2 Factory Firmware image zip from PART III RESTORING Section
- Unzip the contents & open easyinstaller.bat with notepad.
- Find the 2 lines "mfastboot.exe flash motoboot motoboot.img" & delete both of them.
- Delete the motoboot.img file inside the extracted contents.
- Run the easyinstaller.bat
- Do not type "mfastboot.exe flash motoboot motoboot.img" while flashing the Lollipop ROM manually
3. Lollipop 5.0.2 to Kitkat 4.4.4 : If your bootloader version is 4882/4883(Lollipop Bootloader), you need to make some changes while flashing the ROM manually.
- Download Kitkat 4.4.4 Factory Firmware image zip.
- Unzip the contents.
- Delete the motoboot.img file inside the extracted contents..
- Do not type "mfastboot.exe flash motoboot motoboot.img" while flashing the Kitkat 4.4.4 firmware image manually.
4. If you downgrade your bootloader version i.e flash a 4883 Lollipop bootloader on your existing 4886 Marshmallow bootloader, your phone will be hard-bricked / permanently dead. Therefore follow the instructions above carefully. I am not responsible for dead phones.
CREDITS
@Lucas Eugene for his thread 'Unlock Bootloader - Moto G (2nd Gen) [UPDATED]'
@Tomsgt for his YouTube video 'How to unlock the boot loader on your Motorola phone Moto X, G, & E all versions'.
@Chainfire for creating CF Auto Root & SuperSU.
@luca020400 for maintaining TWRP.
@reefuge for his thread '[STAGE FRIGHT][XT106x][5.0.2][LXB] Stock 5.0.2 Easy Installer via FastBoot Tool'
Do I have to change anything if I have the bootloader already unlocked (especially to avoid the factory reset)?
Nagass said:
Do I have to change anything if I have the bootloader already unlocked (especially to avoid the factory reset)?
Click to expand...
Click to collapse
Just flash the latest SuperSU http://download.chainfire.eu/supersu with twrp. That's it.
Nagass said:
Do I have to change anything if I have the bootloader already unlocked (especially to avoid the factory reset)?
Click to expand...
Click to collapse
Please read the OP
Unlocked bootloader wont wipe anything after rooting.
Just remove install_recovory.sh from /system/etc/. when you bootep into twrp the first time
After flash supersu and reboot
It displays failure remote failure when I run bat.exe
Thank you so much, this tutorial is perfect. :good::good::good:
Now my girlfriend can enjoy her 5.0.2 rooted with twrp 2.4.8.0 installed.
Great
iamanubhav said:
It displays failure remote failure when I run bat.exe
Click to expand...
Click to collapse
https://forums.motorola.com/posts/132580d3df
thaaaaaaaaaaanks @luca020400
and I can delete the application motorola?
If I understood correctly, this method does not require unlock key from motorola to unlock bootloader. So, if I unlock the bootloader and restore the lock again later, then there won't be any way that motorola can get to know if it was unlocked ever (for warranty purpose )??
Thanks for this!
However, it results in the same issue I've found ANY time I've tried to install ANY version of SuperSU with ANY android version on this phone (1063). That is: after flashing supersu, I get a boot loop. The first few times this happened, I cursed and reformatted the entire phone. For anyone else who has encountered this, I just figured out a way around it! It looks like this problem *only* affects the recovery partition, which is easily re-flashed.
Here's what worked for me:
While boot looping, press and hold vol down + power until screen stays black for 5-10 seconds, then release. You'll get to fastboot mode here. Then, connect with a usb cable and in a cmd prompt, from within your adb directory, type fastboot flash recovery <recovery image name.img> and hit enter. Once it flashes sucessfully, you'll be able to start back up with "normal startup" from the device's fastboot menu and all should be well. And if you've done this to correct a boot loop brought on by this autoroot, you'll actually still have root once you start up. Hooray!
The recovery image that you flash can be TWRP (link above) or the stock android recovery (which I found on this forum somewhere, but will upload with a link as soon as Mega is nice to me again).
Hope this helps someone else.
himsin said:
If I understood correctly, this method does not require unlock key from motorola to unlock bootloader. So, if I unlock the bootloader and restore the lock again later, then there won't be any way that motorola can get to know if it was unlocked ever (for warranty purpose )??
Click to expand...
Click to collapse
You need to unlock it
These are the step after the unlock on lollipop roms
imp .questions
Hey thanks for this thread I have successfully rooted my phone
Q. And if Motorola pushes the 5.1 ota can I update my is to 5.1?I have just rooted and the recovery is also stock
luca020400 said:
You need to unlock it
These are the step after the unlock on lollipop roms
Click to expand...
Click to collapse
So, this method won't unlock the bootloader?? The very first warning in OP gave me the impression that it will also unlock the bootloader :silly:
himsin said:
So, this method won't unlock the bootloader?? The very first warning in OP gave me the impression that it will also unlock the bootloader :silly:
Click to expand...
Click to collapse
Yes , the tool unlock your bootloader
But anyway you need the motorola code and unlock process
luca020400 said:
Yes , the tool unlock your bootloader
But anyway you need the motorola code and unlock process
Click to expand...
Click to collapse
Now I am more confused.... If the tool unlocks the bootloader then shall I assume that it asks for the unlock code during process?
himsin said:
Now I am more confused.... If the tool unlocks the bootloader then shall I assume that it asks for the unlock code during process?
Click to expand...
Click to collapse
Yes it ask for unlock code
Didn't work for me on Linux
fastboot-linux binary included with auto-root seems to be not working.
I tried to use fastboot from ubuntu repositories, which works, but couldn't correctly boot auto-root image.
I used openrecovery-twrp-2.8.4.0-titan.img with "normal" procedure described here , and everything worked perfectly.
Thanks anyway!
luca020400 said:
Yes it ask for unlock code
Click to expand...
Click to collapse
Thanks for clearing the doubts
himsin said:
If I understood correctly, this method does not require unlock key from motorola to unlock bootloader. So, if I unlock the bootloader and restore the lock again later, then there won't be any way that motorola can get to know if it was unlocked ever (for warranty purpose )??
Click to expand...
Click to collapse
Yes they understand, since your STATUS number changes from 0 to 3.
When you relock it changes from 3 to 2.
So your warranty is lost forever. Be careful.
You can find this number on the display when you're on fastboot mode (turn off the device and then press power + volume down for aboout 5 sec and release)
I was encouraged to make a separate thread for this, so I did.
Here we're going to try and port the Verizon Nougat update to all Moto Z phones.
I said I'd upload the code into GitHub to make it easier to change stuff, but that got too confusing so I just used Google Drive lol. Anyway, let's get started.
I'll start by editing the update script in the zip, and I'll need somebody to verify that it works. Just be forewarned that things might break (thus the alpha status). If things break, there are other threads with all the Marshmallow stock zip files, flash that and try again. Make sure to check those threads before you flash though, because if you break your phone and then check those threads to find your zip just to realize that they don't have your zip, then you're screwed. Please, please, please, PLEASE make a backup of your ROM. I'm here to fix problems with this ROM, not to fix your phone because you didn't backup your data.
Backup Without TWRP or Unlocked Bootloader (When you're trying to prepare for a bootloader unlock)
http://forum.xda-developers.com/showpost.php?p=69821066&postcount=38
Alternative method :
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
spicial thanks to @papampi
Downloads:Verizon Stock Unzipped: https://drive.google.com/open?id=0ByioJuadKHC6c3BkMnVydDRzQlk
EU Unzipped (WIP) by @erfanoabdi (See Post #17): https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA
Main Verizon Firmware Lolinet: https://mirrors.lolinet.com/firmware/moto/griffin/official/VZW/XT1650_GRIFFIN_VERIZON_6.0.1_MCLS24.246-36-3_cid2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Main Verizon Firmware Google Drive: https://drive.google.com/open?id=0ByioJuadKHC6MjJDXzhJSXlBaDA
Downloading Zips from Google Drive
http://forum.xda-developers.com/showpost.php?p=69821121&postcount=39
New Downlaod Link :
Main RETMX Firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Main TELUS Firmware (NPL25.86-30) : https://mirrors.lolinet.com/firmwar..._subsidy-TELUS_regulatory-DEFAULT_CFC.xml.zip
Main RETUS Firmware (NPLS25.86-17-3-8) : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Installation Guide:Download and extract Main TELUS Firmware on PC
Make Sure You have backup of your whole Device [System, Boot, OEM, Data, Internal Storage]
Flash System, Boot, OEM, Fsg, Modem Partitons :
Code:
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
(continue it it has more chunks ...)
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase cache
(fastboot erase userdata) (Not Needed But Recommanded)
Boot into TWRP :
Code:
fastboot boot twrp.img
(or flash it)
use adb sideload (Advanced -> ADB Sideload) and flash this ZIP from attachments to Disable Force-Encryption (Not needed but Recommanded)
Code:
adb sideload UPDATE-AnyKernel2.zip
wait to complete flashing
ROOT : (OPTIONAL)
Follow this Guide : https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
use adb sideload (Advanced -> ADB Sideload) and flash this ZIP from attachments to get systemless Root access
Code:
adb sideload superuser-r259.zip
Reboot
(For Rooted Guys) install phh's SuperUser From PlayStore : https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en
(it's working and confirmed on XT1650-03 and 05, RETUS, EU, CN, ...)
ENJOY
After Installing Nougat With This Method You Can take Back to Stock Marshmallow Or Install New CM14.1 Builds This is safest and Easiest Method To Install Stock Nougat on Moto Z
Why not help out XDA and spam click a few ads? (and then close the tabs cuz who really wants to buy stuff from ads lol. Either way, XDA gets money just for you clicking on them )
XDA:DevDB Information
Android Nougat, ROM for the Moto Z
Contributors
SoulDJ673, erfanoabdi
ROM OS Version: 7.x Nougat
Based On: Stock Verizon Nougat OTA.zip
Version Information
Status: Stable
Created 2016-11-24
Last Updated 2017-07-16
Updates
Update 5:
Added erfanoadbi's EU port to the downloads list. We need testers!
Update 6:
When I added erfanoabdi as a contributor it reset this post lol. I've fixed it as much as I could though.
Update 7:
The system.data.patch file finished uploading on the Verizon Unzipped Link
Update 8:
Added installation instructions for the EU test to the OP
Update 9:
Added an alternative link for the Verizon firmware as some people were having problems with the first link
Update 10:
Added Google Zip Downloading and ADB Backup Information to OP
Update 11:
EU Test doesn't work
Update 12:
EU Test works now thanks to erfanoadbi's awesome work
Update 13:
Added stuff about Moto Voice error to OP
ADB and Sideload
If you don't know how to sideload, you'll first have to have adb installed on your pc. If you're on Windows, refer to @Snoop05's post here: http://forum.xda-developers.com/show....php?t=2588979 and download the installer for adb and fastboot. If you're on a Mac, refer to @AshtonTS's post here: http://forum.xda-developers.com/show....php?t=1917237. Also, be sure to throw these awesome people some thanks
For my fellow peoples on Linux:
Ubuntu: sudo apt-get install android-tools-adb android-tools-fastboot
Arch Linux: sudo pacman -S android-tools
Red Hat and others: You people are straight up savages and probably already know how to get a hold of it lol.
Open your terminal, the command prompt for Windows users, and cd to wherever the adb binary is (Linux users don't have to do this because it's already in your path, unless you installed it some way other than the package manager). Move the ota.zip to that directory. Enable USB debugging on the Moto (Settings > About Phone > Click Build Number 7 times, then Settings > Developer Options > USB Debugging) and then plug the Moto into your PC. Type "adb reboot recovery" (Mac users type "./adb reboot recovery"), and then wait. (If this doesn't work, look on the Moto and see if there's an authentication dialogue) On the Moto you'll soon see the Android robot lying on it's back and a red triangle above that. The screen will read "No command". Press and hold the power button for 2-3 seconds and then quickly also press Volume up and then release both buttons. On mine I have to do this button pressing thingy a few times, but eventually the recovery menu will come up. When it does, use the volume buttons to go down to the "Apply update via ADB" option and press the power button to select it. Go back to the computer and type "adb sideload ota.zip" (Mac users don't forget the "./" at the front) and it'll start to sideload the zip onto the phone. After that just wait and soon it'll install Nougat. (Ofc now we know that this isn't always the case)
I imagine the intention is to flash this from stock recovery rather than TWRP? I get E:footer is wrong E:Signature verification failed Installation Aborted
Stock recovery won't mount either the internal or external storage, and using adb sideload it just says
"unable to load ota.zip"
It doesn't appear to even try to open or verify the file itself, maybe it's too large?
I tried sideloading twrp.zip, just to see if it would do Anything at all, and that file is loaded and rejected (because my bootloader is locked)
I have reteu, not verizon, but I should at least get an error message.
Maybe I just have to wait, they claim to have begun rolling out world wide, but I've been hammering that update button once an hour since monday...
Via TWRP it gets stuck as it's expecting the Google folder in META-INF>Com. I added it from the original OTA and it's throwing up Griffin product name errors. Going to try a few things.
H00pyFr00d said:
I imagine the intention is to flash this from stock recovery rather than TWRP? I get E:footer is wrong E:Signature verification failed Installation Aborted
Click to expand...
Click to collapse
Yes, stock recovery is the goal but if you have TWRP then you can use that. Just know that the modem files and stuff are strictly for Verizon, so I wouldn't try to force flash it until I get those replaced.
H00pyFr00d said:
Going to try a few things.
Click to expand...
Click to collapse
Ok great
Shadowdancer123 said:
Stock recovery won't mount either the internal or external storage, and using adb sideload it just says
"unable to load ota.zip"
It doesn't appear to even try to open or verify the file itself, maybe it's too large?
I tried sideloading twrp.zip, just to see if it would do Anything at all, and that file is loaded and rejected (because my bootloader is locked)
I have reteu, not verizon, but I should at least get an error message.
Maybe I just have to wait, they claim to have begun rolling out world wide, but I've been hammering that update button once an hour since monday...
Click to expand...
Click to collapse
To be on the safe side, yeah I'd wait until the official OTA comes out. If you want it early tho that's cool too, just upload your current stock rom and I can play switcheroo on some necessary files.
With the limited backup capabilities of unrooted android and scarcity of fastboot rom files..
I'm just gonna sit here and click refresh on the update button. XD
Shadowdancer123 said:
With the limited backup capabilities of unrooted android and scarcity of fastboot rom files..
I'm just gonna sit here and click refresh on the update button. XD
Click to expand...
Click to collapse
Lol true. I'm gonna keep trying tho
SoulDJ673 said:
I was encouraged to make a separate thread for this, so I did.
Here we're going to try and port the Verizon Nougat update to all Moto Z phones.
I said I'd upload the code into GitHub to make it easier to change stuff, but that got too confusing so I just used Google Drive lol. Anyway, let's get started.
I'll start by editing the update script in the zip, and I'll need somebody to verify that it works. Just be forewarned that things might break (thus the alpha status). If things break, there are other threads with all the Marshmallow stock zip files, flash that and try again. Make sure to check those threads before you flash though, because if you break your phone and then check those threads to find your zip just to realize that they don't have your zip, then you're screwed. Please, please, please, PLEASE make a backup of your ROM. I'm here to fix problems with this ROM, not to fix your phone because you didn't backup your data.
Now that we've gotten that out of the way, here's the link to download it: null
Just so you know, if you try downloading it before around 13:00 EST, you won't have the full thing. My internet isn't the best, so it's gonna take a while.
Happy Thanksgiving everyone
Update:
Internet Crashed :/
Update 2:
I got most of the ota to upload but not all of it, but now as a wonderful Thanksgiving present I've got more drama in my life :/. I'll take a break for a day or two, hopefully Moto doesn't send out the rest of the OTAs so my attempts are for nothing.
XDA:DevDB Information
Android Nougat, ROM for the Moto Z
Contributors
SoulDJ673
ROM OS Version: 7.x Nougat
Based On: Stock Verizon Nougat OTA.zip
Version Information
Status: Alpha
Created 2016-11-24
Last Updated 2016-11-24
Click to expand...
Click to collapse
Hi @SoulDJ673, thanks for working on this project.
could you please give me list of files on this zip? is it contains "system.new.dat"?
could you please only upload "system.new.dat" for me, this shouldn't be heavy too mach
thanks again
_________
Sorry,
i found your uploaded zip here http://forum.xda-developers.com/showpost.php?p=69764157&postcount=42
I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..
janjan said:
I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..
Click to expand...
Click to collapse
Awesome, Thanks a lot.
Needing Only One or Two Small Files
erfanoabdi said:
Hi @SoulDJ673, thanks for working on this project.
could you please give me list of files on this zip? is it contains "system.new.dat"?
could you please only upload "system.new.dat" for me, this shouldn't be heavy too mach
thanks again
_________
Sorry,
i found your uploaded zip here http://forum.xda-developers.com/showpost.php?p=69764157&postcount=42
Click to expand...
Click to collapse
Sorry I didn't answer, where I'm at it was around 4 AM and I was too tired to do anything, and also I've been having some issues in my life rn. But, things are better so I'll be more present. For the future though, if you ever just need a small file I just added a Google Drive link with the unzipped ota so that way you won't have to download the whole 1.5GB zip
EU Version
janjan said:
I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..
Click to expand...
Click to collapse
Thanks a lot, it's been hard trying to even think of ways to port this without having any of the devices I'm trying to port it to lol. If it works, throw me a link and I'll put it in the header post and add you as a contributor.
SoulDJ673 said:
Sorry I didn't answer, where I'm at it was around 4 AM and I was too tired to do anything, and also I've been having some issues in my life rn. But, things are better so I'll be more present. For the future though, if you ever just need a small file I just added a Google Drive link with the unzipped ota so that way you won't have to download the whole 1.5GB zip
Click to expand...
Click to collapse
No problem bro
Thanks
But let me tell you you can't just patch updater-script to make it working on any unlocked devices.
As I see and tested on this zip file, Motorola OTA is working with system.patch.dat which means you have to find head system.img and patch this OTA file on it, I mean all files on this zip is only patchable on "mcls24.246-36-3" system firmware
So you(we) have to patch them on device and make backup of system partition and use it to flash via fastboot or emulate this progress some where else (other rooted device or Android emulator)
So far
I got mcls24.246-36-3 firmware and flashed on my device (everything looks fine)
And I started flashing system.patch.dat and system.new.dat on it but no success
I can verify system patch (very good) but I can't patch it
It seems this is bug of the TWRP I'm going to build google stock recovery without verification check and tell you result's.
I'll upload my works maybe it's useful
main firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
my zip : https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA
erfanoabdi said:
No problem bro
Thanks
But let me tell you you can't just patch updater-script to make it working on any unlocked devices.
As I see and tested on this zip file, Motorola OTA is working with system.patch.dat which means you have to find head system.img and patch this OTA file on it, I mean all files on this zip is only patchable on "mcls24.246-36-3" system firmware
So you(we) have to patch them on device and make backup of system partition and use it to flash via fastboot or emulate this progress some where else (other rooted device or Android emulator)
So far
I got mcls24.246-36-3 firmware and flashed on my device (everything looks fine)
And I started flashing system.patch.dat and system.new.dat on it but no success
I can verify system patch (very good) but I can't patch it
It seems this is bug of the TWRP I'm going to build google stock recovery without verification check and tell you result's.
I'll upload my works maybe it's useful
main firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
my zip : https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA (waiting for system.patch.dat)
Click to expand...
Click to collapse
Ok awesome, as for the updater-script, I didn't think that'd work but I thought maybe it could be a start. I'm still kinda new to this tbh. Thanks for the info though, it'll help me get better with this kind of stuff. I'm very skilled in Linux but Android is kinda different so it's a bit of a learning curve lol.
nice
papampi said:
Awesome, Thanks a lot.
Click to expand...
Click to collapse
thank you
Installation Guide Added on OP, Please test it
This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M
Reserved for future use
can i follow this step for ZE520KL ?
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.
DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me
Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP
Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.
I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!