as always I'm not responsible for any damage in your device (or lost files)
Always backup everything first - nandroid and titanium.
TL;DR for more experienced users: flash stock boot, stock recovery and stock system images (system via mfastboot since its chunks) and then install OTA zip file in the stock recovery (via sd or sideload)
If you have rooted your Moto Maxx and are trying to install the OTA for Lollipop, you are probably getting errors due to modifications on you system.
Simply removing SuperSU doesnt work, you have to restore your system to stock.
If you received the OTA notification, download it and don't install.
0- After downloading, grab the zip file from /cache/ and save it on your computer.
Filename will be something like Blur_Version.XX.XX.XX.quark_retbr.retbr.en.BR.zip
1- Download brazilian retbr full 4.4.4 firmware from here
http://forum.xda-developers.com/dro...tbrxt12254-4-4kxg21-50-9cid12subsidy-t2992444
Decompress it and you should see these files:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
recovery.img
boot.img
2- Download mfastboot (google it) (I used both regular fastboot and mfastboot)
3- Decompress mfastboot and put all files in the decompressed folder above
All files should be in the same folder: mfastboot.exe, boot.img, recovery.img and all system sparsechunks.
Of course they can be in different folders if you know how to use paths in command
4- Unroot
Go to SuperSU app -> configurations -> uninstall root
I recommend uninstalling xposed, busybox etc (I didnt have those, not sure if they will mess with something)
5- Put your phone in bootloader mode
adb reboot bootloader
5- Flash stock kernel, recovery using regular fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
6- flash stock system to fix install-recovery.sh bug/validation, using mfastboot:
Flashing stock boot and recovery was not enough for me. I was getting an error saying /system/etc/install-recovery.sh has unexpected contents.
To solve this, I flashed the stock system image by using mfastboot:
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
Code:
C:\mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (259107 KB)...
OKAY [ 8.130s]
writing 'system'...
OKAY [ 4.122s]
finished. total time: 12.259s
C:\mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (254153 KB)...
OKAY [ 7.958s]
writing 'system'...
OKAY [ 3.282s]
finished. total time: 11.250s
C:\mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.208s]
writing 'system'...
OKAY [ 3.719s]
finished. total time: 11.937s
C:\mfastboot.exe flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262142 KB)...
OKAY [ 8.207s]
writing 'system'...
OKAY [ 3.880s]
finished. total time: 12.098s
C:\mfastboot.exe flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (144756 KB)...
OKAY [ 4.533s]
writing 'system'...
OKAY [ 2.330s]
finished. total time: 6.871s
After this your system is back to stock.
All you have to do now is enter in stock recovery, go to "install zip from adb" and sideload the zip you saved in step 0.
1.2- Reboot your phone to stock recovery
You should see a broken android laying on the floor
in this screen, press Power+VOL UP together and hold for like 2 seconds and release.
A menu should appear. If it doesnt, try again many times - it can be tricky
2.2- Select install zip from ADB or something like that
Now you should be able to see your device in your computer via adb devices command
You should see your device ID and a sideload string when you type this. If you dont, you have incorrect drivers
3.2- Sideload the OTA zip file
In your command prompt find the OTA file you saved in step 0 and then
adb sideload filename.zip, exemple:
adb sideload Blur_Version.XX.XX.X.quark_retbr.retbr.en.BR.zip
If everything goes ok, just wait and relax, if could take a while for the first boot.
Phone will hang on a blank screen with motorola Logo for a while. Dont panic.
Obviously you will lose root by doing this.
Very good i need do that, but i do full wipe for test all, you can flash from sd its works too only need copy file in sd when software release.
I have stock recovery, only I have root, with a simply factory reset I can erase root?
Can I leave boot loader unlocked? Or I need lock the boot loader?
Sent from my XT1225 using XDA Free mobile app
flowserver said:
I have stock recovery, only I have root, with a simply factory reset I can erase root?
Can I leave boot loader unlocked? Or I need lock the boot loader?
Sent from my XT1225 using XDA Free mobile app
Click to expand...
Click to collapse
you dont need to relock your bootloader
I havent tried to just factory reset, but I saw people trying just this without succcess, because seems like super su modifies some files and after uninstalling supersu they're not the same anymore, so when you try to install the OTA you will get an error since validation for file md5/sha will fail
respider said:
you dont need to relock your bootloader
I havent tried to just factory reset, but I saw people trying just this without succcess, because seems like super su modifies some files and after uninstalling supersu they're not the same anymore, so when you try to install the OTA you will get an error since validation for file md5/sha will fail
Click to expand...
Click to collapse
Does anyone have the OTA yet? Or is this just prep for the future?
Gundabolu SC said:
Does anyone have the OTA yet? Or is this just prep for the future?
Click to expand...
Click to collapse
yes, soak test is happening
someone could post the Lollipop OTA file here?..
flowserver said:
I have stock recovery, only I have root, with a simply factory reset I can erase root?
Can I leave boot loader unlocked? Or I need lock the boot loader?
Sent from my XT1225 using XDA Free mobile app
Click to expand...
Click to collapse
No factory reset dont remove root for me, only this tutorial removes
where is the OTA zip???
This tutorial is to unroot device and back to stock
Lollipop ROM
Where's lollipop zip rom?
this is a guide to install OTA zip If you received the OTA notification and if you have a rooted phone
this is not a rom, this is a guide/howto
Mexico Maxx
Great tutorial, maybe a dumb question, the BR image file works the same on the MX Maxx? Or do I need to download the mexican retail image?
Thanks!
Quetzalfp said:
Great tutorial, maybe a dumb question, the BR image file works the same on the MX Maxx? Or do I need to download the mexican retail image?
Thanks!
Click to expand...
Click to collapse
I think should works fine, but motorola said mexican already have soak too so.
maybe this will help to someone who received Lollipop and wants to share with us the OTA
matheus_sc said:
I think should works fine, but motorola said mexican already have soak too so.
Click to expand...
Click to collapse
Thanks, I know that is coming to Mexico too, but from the tutorial says that we need some files from the brazillian image to return to pure stock before the update, this files works for the mexican devices or I need to download the MX image?
Quetzalfp said:
Thanks, I know that is coming to Mexico too, but from the tutorial says that we need some files from the brazillian image to return to pure stock before the update, this files works for the mexican devices or I need to download the MX image?
Click to expand...
Click to collapse
probably you just need to replace with mexican images
I'm not sure if recovery/boot/system are all the same, but if you use everything from mexico you should be fine
I have 2 questions sorry for my ignorance.
1 is there a link to download the other zip?
2 is this update compatible with the xt1225 Puerto Rico version?
Sent from my XT1225 using XDA Free mobile app
respider said:
probably you just need to replace with mexican images
I'm not sure if recovery/boot/system are all the same, but if you use everything from mexico you should be fine
Click to expand...
Click to collapse
Thanks! I'll give it a try if I get the OTA notification and let you know
Atrix_Lover said:
I have 2 questions sorry for my ignorance.
1 is there a link to download the other zip?
2 is this update compatible with the xt1225 Puerto Rico version?
Sent from my XT1225 using XDA Free mobile app
Click to expand...
Click to collapse
Updates only works in Brazilian firmware but dont release yet
Related
Hello, I'm trying to help people who installed the soak test of Lollipop but is not enjoying the ROM with lots of bugs and want to go back to KK.
THIS IS ONLY FOR XT1225, BRAZILIAN FIRMWARE RETAIL UPDATED VIA OTA
YOU NEED TO HAVE YOUR BOOTLOADER UNLOCKED
It will work even if you have root on lollipop
Do it at your own risk!
So, this is the procedure:
DOWNLOADS
1 - Download the Stock ROM from here:
RETBR_XT1225_4.4.4_KXG21.50-9
2 - Download Motorola Drivers from HERE
3 - Download Moto Fastboot from HERE
* IT NEED TO BE MOTO FASTBOOT, known as "mfastboot" . Android Fastboot wont handle the system flash.
INSTRUCTIONS
1 - Backup your phone, otherwise you will lose everything on it
2 - Extract ROM files to a folder (I did on " C:\MAXX\ " )
3 - Extract Moto Fastboot files on same folder you extracted the ROM
4 - Shutdown your phone and put it on fastboot mode (when off, press Power Button + Volume down)
5 - Plug your phone on your PC
6 - Install Motorola Drivers NOW. (For me it only install the driver at this time. If you have the proper driver installed already, skip this step)
7 - Open a command prompt and go to the folder that you extracted the ROM and Moto fastboot
8 - Now, you need to type every line, pressing enter when is a new line and waiting the process to be sucessfully
Code:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.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 system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
For me it worked, now your phone will reboot and boot right again on KK
I had tried to do with RSD Lite but it always fail on flash the partition.
So, this procedure above is tested by me and it works.
Well all i just did was to restore my twrp backup and then flash my radio.img and that's it didn't lose anything and my cell works like charm just like before flashing lollipop
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
remember that this tutorial is ONLY FOR WHO UPDATES WITH OTA.
if u updated the phone with official OTA ,u can t downgrade to 4.4.4
or if the firmware img of 5.0.2 will go out and u will flash it U CAN T GO BACK TO 4.4.4 either.
always make a nandroid backup in twrp of 4.4.4 .it will be useful.
I've received a OTA without TWRP.... so, I did not could make a nandroid
Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
This was the case with the 2013 Moto X, there is no such problem with the 2014 model. It is unlikely to be a problem with the XT1225. Motorola learned from that mistake.
do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?
arcaneck said:
do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?
Click to expand...
Click to collapse
Did you install the lollipop via OTA after flashing brazilian firmware ?
yes i did
It's the same procedure but with the mx firmware
works fine thanks
Works for me too
do you have the mx ota?
Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!
I've installed the zip file of the soak test (I didn't receive it through OTA), will this procedure work for me? Really tired of the instability of 5.0.2
I have the same problem
megadu said:
Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!
Click to expand...
Click to collapse
I have the same problem.
After the command "mfastboot flash boot boot.img ". Do not process more.
Can anyone help me? Please!
Have you unlocked the bootloader?
boot.img can never been be downgraded. If you downgrade from version 5.x to 4.4.4 you have to skip that file.
I update my motorola using this guide http://forum.xda-developers.com/droid-turbo/general/guideinstall-lollipop-ota-root-ur-moto-t3029690 , can i do the downgrade ?
Thanks!
im have the same question, im using now cm12 with twrp, bootloader unlocked. can i go back to stock 4.4.4 using this tutorial? its safe?
OTA currently being deployed, but there are no signs of the FXZ or SBF files. Motorola has not released them and no one has tried the MDM update trick (method explained by similar threads) for the XT1053 model.
If any user acquires it, please upload it and post link here. Thank you.
Let's hope for the best!
Looks like the recovery images for xt1053 have been posted to the moto customer portal:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
This is great news!!! Trying to get access to it now...
UPDATE: I was able to flash successfully from a windows box.
----------------------------------
I seem to be having some issues with flashing system.img, hopefully I'm just doing something wrong. Using the copy of fastboot within the Darwin folder of the download and I'm on OSX 10.10.3 if that matters.
------------------------------------------------------------------------------
./fastboot flash system ../system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
Sparse-Flash is enabled!
sending sparse 'system' (785466 KB)...
OKAY [ 49.379s]
writing 'system'...
OKAY [ 36.278s]
sending sparse 'system' (587908 KB)...
OKAY [ 37.032s]
writing 'system'...
(bootloader) Invalid sparse image data
OKAY [ 0.192s]
finished. total time: 122.882s
------------------------------------------------------------------------------
Hm, this is great news. I honestly wasn't expecting the SBF to be posted this soon.
Now, how does one go about turning it into an xml.zip?
JimJ2Mz said:
Hm, this is great news. I honestly wasn't expecting the SBF to be posted this soon.
Now, how does one go about turning it into an xml.zip?
Click to expand...
Click to collapse
just use fastboot.. Moto probably included the bat file for it anyway (like they did with 4.4.4)... or you can probably grab the XML out of the 4.4.2 SBF and pretty much use it with the 5.1 files.
EDIT: No, at least on the XT1053 5.1 rom on their site, Moto did not include either a BAT file for fastboot, nor did they include the XML for RSDlite...
To make your own FLASH.BAT... open notepad... copy/paste the following lines into it.. save as.. "all files" and name it flash.bat... (copied directly from the flash.bat included in the XT1053 4.4.4 rom on Moto's site.)
Code:
SET fastboot=mfastboot.exe
%fastboot% getvar max-download-size
%fastboot% oem fb_mode_set
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot motoboot.img
%fastboot% reboot-bootloader
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% erase customize
%fastboot% erase clogo
%fastboot% oem fb_mode_clear
pause
NOTE: this does ASSUME that you are using the fastboot included in the rom you downloaded which is moto's fastboot. Using stock fastboot from the Android SDK/Platformtools will fail flashing system.img due to its size.
Thanks for the find! Can I flash the developer edition ROM onto my 16gb GSM unlocked XT1053?
bub181 said:
Thanks for the find! Can I flash the developer edition ROM onto my 16gb GSM unlocked XT1053?
Click to expand...
Click to collapse
The GSM Developer Edition XT1053, and the XT1053's sold on MotoMaker as GSM Unlocked (ships with T-Mobile SIM) and GSM Unlocked (ships with Net10 SIM) all use the same ROM/SBF/FXZ files.
KidJoe said:
The GSM Developer Edition XT1053, and the XT1053's sold on MotoMaker as GSM Unlocked (ships with T-Mobile SIM) and GSM Unlocked (ships with Net10 SIM) all use the same ROM/SBF/FXZ files.
Click to expand...
Click to collapse
Ok great thanks. I'm just waiting for Motorola to give me access to the download. If someone already has it could they post here please?
bub181 said:
Ok great thanks. I'm just waiting for Motorola to give me access to the download. If someone already has it could they post here please?
Click to expand...
Click to collapse
Please someone post it here!!!
bub181 said:
Ok great thanks. I'm just waiting for Motorola to give me access to the download. If someone already has it could they post here please?
Click to expand...
Click to collapse
santiagute said:
Please someone post it here!!!
Click to expand...
Click to collapse
Only took me about 2hrs wait to get link last night when I requested.
Why does motorola take 4 hours to approve a download?
Motorola let me access to file. Downloading now. 880 MB.
ufukcoskun said:
Motorola let me access to file. Downloading now. 880 MB.
Click to expand...
Click to collapse
Shared already
Hello, i'm uploading a backup of the OTA update for XT1053 i did with TWRP after wiping data, dalvik cache and factory reset twice.
It is rooted and i removed some system apps i don't use like email and some google apps like google books, movies, etc.
Don't know if it will work flashing as a restore with TWRP as i didn't test.
Should i keep uploading or i better cancel the thing?
I'm downloading the 5.1 files now and I have a question because it's been a while since I've done any flashing with this device and remember it being a pita to work with.
If I do this part
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
Click to expand...
Click to collapse
but not this part
$ fastboot erase userdata
$ fastboot erase cache
Click to expand...
Click to collapse
it won't wipe any of my data or settings, correct?
csos95 said:
I'm downloading the 5.1 files now and I have a question because it's been a while since I've done any flashing with this device and remember it being a pita to work with.
If I do this part
but not this part
it won't wipe any of my data or settings, correct?
Click to expand...
Click to collapse
fastboot erase userdata would wipe the phone, apps, data, like a factory reset.
fastboot erase cache will wipe the phone's cache.. since you are upgrading to 5.1 which uses art and not Dalvik, its worth erasing cache.
I'm having a problem after flashing. Now when I try to boot my phone it goes straight to recovery. I tried reflashing and restoring from a backup, but neither works.
Looking at the terminal in recovery, it's showing that it can't mount /cache either
EDIT: fixed it by manually formatting /cache, restored from backup(still didn't boot), flashed stock 4.4.4, and now im on android is upgrading. So I guess not lollipop for me for now
EDIT 2: got 5.1 ota notification as soon as motorola update services update. It's 694.6MB and it's claiming 122 minutes left to download
EDIT 3: I now have 5.1 installed and working.
lavero.burgos said:
Hello, i'm uploading a backup of the OTA update for XT1053 i did with TWRP after wiping data, dalvik cache and factory reset twice.
It is rooted and i removed some system apps i don't use like email and some google apps like google books, movies, etc.
Don't know if it will work flashing as a restore with TWRP as i didn't test.
Should i keep uploading or i better cancel the thing?
Click to expand...
Click to collapse
Here's the link: https://drive.google.com/file/d/0B3XeIVyUffMKVm1rbUdCbWpwd0U/view?usp=sharing
I downloaded 5.1 file from the following link. After flashing it, my system version is "222.21.15.ghost_row.Retail.en.US vzw" and my bootloader is also "Verizon" although my device is XT1053. How can i solve it?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Yeah, I think the title is enough. The factory images are live now for volantis and volantisg. Maybe we can collect here some first impressions. I am unfortunately not able to flash atm.
https://developers.google.com/android/nexus/images
Flash-all script worked like a charm, setting everything up right now
But it's not February yet.
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Cool man , I'm waiting for your review, , but I'm sure to flash this into my N9 tomorrow . I'm just too eager to wait any longer
Good thing I reverted my n9 back to stock. Will flash tonight. No Ota also.
Flash.sh fail
maarten08 said:
Flash-all script worked like a charm, setting everything up right now
Click to expand...
Click to collapse
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
I'll be flashing my 9 tonight too.
I kept my 6 on Lollipop rather than running the preview on it, but yesterday I did flash the preview so that it would use M's auto backup. That way I can flash it this week and not worry about signing into apps.....which is nice during tax season.
PhoenixIce22 said:
Mine fails at sending 'system' (2245234 KB)...
FAILED (remote: data length is too large)
Trying to do a manual flash now... we'll see!
Click to expand...
Click to collapse
Do u have latest fastboot? That error was happening to others because of old fastboot. Otherwise maybe just make sure the hash matches and u have a good download and usb debugging is on.
Sent from my SM-G900V using Tapatalk
Anybody tried flashing yet? I keep getting 'system cannot be loaded' error whilst carrying out manual flash. i.e. fastboot flash system system.img etc etc
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
I was on 5.1.1 (Latest Image). I applied the 6.0 update, now I am just sitting at the black Google Screen and it won't boot. Any suggestions???
Diesel779 said:
I flashed each .IMG file separately, formatted date to remove encryption, flashed TWRP, flashed fed-patcher them FIRE-ICE kernel. Running great here
Click to expand...
Click to collapse
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Is the installing process for rooted devices the same as for the former builds?
like here:
http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img
gt43aw said:
Do u need fed patcher if u flash a kernel that does not force encryption? I thought you wouldn't. Haven't tried it though.
Brian
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
You don't need FED patcher if you flash an already un-force-encrypted kernel. FED patcher just takes the stock kernel and un-force-encrypts it.
Haven't updated my flashing VM in a while, so likely not. I know my ADB is 1.0.32, not sure what version of fastboot I have on there. I'm a bit of a Ubuntu noob, so I'm doing lots of web researching, LOL
Be sure to update the bootloader if getting a system partition size error! For M-preview this went from 3.44.1.0123 (LMY48M) to 3.48.0.0135 (confirmed the factory image is still this for MRA58K)... Otherwise you get system partition size errors (BIG update).
I will be making a rooted/no-force-encrypt ROM and kernel as soon as I see the newer manifests on googlesource... I am assuming selinux to permissive is still required for root. Once you have it unpacked:
fastboot flash bootloader bootloader-flounder-3.48.0.0135.img
fastboot reboot-bootloader
Then flash the system and boot images:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash system system.img
DO NOT DO THIS if your device is using a no-force-encrypt kernel! You WILL have to factory reset! Back up OFF the device to a PC or OTG FIRST... Then you can restore.
While flashing SYSTEM it will send the update in 5 chunks - from my device:
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.869s]
sending sparse 'system' (499853 KB)...
OKAY [ 26.326s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.701s]
sending sparse 'system' (495930 KB)...
OKAY [ 25.524s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 20.212s]
sending sparse 'system' (495450 KB)...
OKAY [ 25.732s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.792s]
sending sparse 'system' (443364 KB)...
OKAY [ 22.984s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 19.222s]
sending sparse 'system' (310634 KB)...
OKAY [ 16.188s]
writing 'system'...
(bootloader) Device State : Unlocked
OKAY [ 12.593s]
finished. total time: 209.162s
NOOB Question:
where can I get the Information if my kernel is "no-force-encrypt kernel"?
I'm using the stock kernel 3.10.40 (28.jul) build LMY48M (rooted)
UDPATE:
in Settings -> security -> enrcypt tablet-> encrypted: means "force-encrypt kernel"?
Deleted
No force encryption stock kernel
For those who want to flash Marshmallow immediately but wanted to keep the device un-encrypted, download this zip, extract the boot image and flash through fastboot.
Guide for installing new security update with fastboot and with a bootloader-unlocked Pixel XL.
This is basically the same thing as usual but with the new structure.
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This is the solution.
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
I assume you already have anything to do fastboot command. If not, see this good thread.
1) Download your system image for Marlin (Pixel XL) on google website.
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
2) Unzip the file marlin-nde63v-factory-a66866ba.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-nde63v.zip
4) Reboot into bootloader
Code:
adb reboot bootloader
5) Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot flash bootloader bootloader-marlin-*.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Here we go, you have a fresh unrooted vanilla android with latest security patch.
6) To add TWRP and Root:
Code:
fastboot boot /path/to/twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
Root thread for more information.
TWRP thread for more information.
** Reserved **
cam30era said:
@firewave,
Thanks for posting the guide. Just like Nexus devices except for the slot files. After unzipping the factory image, I do notice 15 additional files (other than boot, system, vendor, etc) that I've never seen before on a Nexus device. Do you happen to know what those are for, and why we don't flash them if doing a manual fastboot flash?
Thanks, in advance....
Click to expand...
Click to collapse
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
firewave said:
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
Click to expand...
Click to collapse
aboot is actually part of the bootloader.
death2all110 said:
aboot is actually part of the bootloader.
Click to expand...
Click to collapse
yep, it's why I'm unsure what to do with. Probably nothing.
I will loopmount the file at home and see.
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
wx9kvh said:
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
Click to expand...
Click to collapse
In the op in bold, he said it will not erase your data or apps
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
dablitzkrieg said:
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
Click to expand...
Click to collapse
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
chapelfreak said:
In the op in bold, he said it will not erase your data or apps
Click to expand...
Click to collapse
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
wx9kvh said:
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
Click to expand...
Click to collapse
That makes sense, our posts are an hour apart or so.
Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
I appreciate the help. The link you provided me, I've downloaded it, but for some reason cant launch the app after I unzip the file. I've been at this for like 4 hours. I've tried so many different things and can't get past the Google screen. Please help
I was able to utilize the old tool. I'm all set. Thanks
chapelfreak said:
That makes sense, our posts are an hour apart or so.
Click to expand...
Click to collapse
Lol. No big deal haha.
Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
Scott...can I flash the radio.img from V to the Verizon X. This radio is horrible
ADB Sideload Works too
Alternatively, use the instructions found on this page followed by a re-flash of your preferred kernel and a fastboot boottoroot to regain root.
https://developers.google.com/android/nexus/ota
So i just followed all of these instructions, and when going into about phone, it shows that i am now on an N build and still with the October security patch. What did i miss?
Update :
I believe I fixed the issue. The little window with the commands in it for some reason had scrolled up and I missed the flashing the "bootloader-marlin-*" step.
Update 2 :
I am now on X with the November security update. GREAT GUIDE!
Followed it to a T and soft bricked mine so now trying to find a way to fix or toss it out the windows haha. Just a heads up guys.
Ended up using the skipsoft tool and pushing a factory update same results but lost data/apps no biggie.
This is odd i followed the instructions trying to flash X to my phone coming from NDE63P and somehow ended up on NDE63N (Ignore this i missed a command)
What steps do I need to add if I want to completely restore back to factory settings (format userdata)? Or would it be the same to just factory reset through the newly restored stock recovery?
Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that