Database Users

UPDATE Verizon Soak Test Does Break Root in regard to PWNMYMOTO

According to Droid Life, the Verizon Soak Test that just came out today doesn't break root.
heres the link
http://www.droid-life.com/2013/10/2...o-x-rolling-out-to-testers-doesnt-break-root/
WARNING DO NOT UPDATE IF YOU ARE USING PWNMYMOTO, some people are confirming bootloops. I believe this "keeping of root" is in relation to motoroot, but as always, do so at your own risk.

looks like the editor of droid life was rooted via motoroot and it kept that. I believe we have seen that with other OTAs. maybe not as exciting.

Glad to hear this. Of course, I un-rooted when I got the invite a week ago because I figured I either wouldn't get the OTA or it wouldn't install if I stayed rooted. I wonder if I can root again.

Tried to update with PwnMyMoto installed
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.

tyguy829 said:
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.
Click to expand...
Click to collapse
I would try to clear your cache, hopefully that works for you
Sent from my XT1060 using Tapatalk

Can't Clear Cache
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?

tyguy829 said:
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?
Click to expand...
Click to collapse
would
fastboot erase cache
command not work in the bootloader?

tyguy829 said:
The problem is I don't know how to clear my cache because I don't have a recovery. Is there another way to do this?
Click to expand...
Click to collapse
I believe you can also clear cache through TiBu

Be careful according to JCase the soak does break root. Check his twitter.

I'm in the same boat as above. Phone stuck in a bootloop. If anyone figures it out I'll be in your debt. Also rsdlite doesn't detect my phone so I can't even restore it that way. I'm hoping there's at least a way to restore to factory through adb but Google is coming up empty.
- Nathan

tyguy829 said:
I saw that we could keep root through the update, so I went ahead and applied it. But, I forgot that PwnMyMoto also removed the recovery and replaced it with a boot image to allow writing to the system. Now I'm stuck in a bootloop-type thing. I can get it booted to the lockscreen, but then after 5-10 seconds, the standard android "Shutting Down" popup appears and the phone restarts itself. I know I could flash the stock recovery from the bootloader, but I want to keep system write. Is there a way for me to wipe my cache or something to get it to stop trying to apply the update? Thanks.
Click to expand...
Click to collapse
After your phone reboots hold down vol down + power to get into the bootloader. Now you can flash recovery through fastboot. Get the fastboot files from here if you don't already have it and the FXZ file for your carrier here. Now you can either just flash the recovery or flash the entire rom. If you just flash the recovery then the next time you boot it will reboot into recovery and run the update. If you choose to flash the entire rom then you will be wiping everything. To flash using fastboot you will first need to make sure the contents of the FXZ file are in the same folder as the fastboot files. Next open a command prompt and change the directory to the folder with your fastbboot files (eg. cd C:\). Now use the following commands to flash the FXZ files. If you choose to just flash the recovery then skip all the other commands except the command to flash recovery.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem fb_mode_clear
fastboot reboot

Thank you so much!! Worked like a charm as far as restoring my phone to defaults. The update is no longer showing in the software update section but that's ok. :good::good:
Dark9781 said:
After your phone reboots hold down vol down + power to get into the bootloader. Now you can flash recovery through fastboot. Get the fastboot files from here if you don't already have it and the FXZ file for your carrier here. Now you can either just flash the recovery or flash the entire rom. If you just flash the recovery then the next time you boot it will reboot into recovery and run the update. If you choose to flash the entire rom then you will be wiping everything. To flash using fastboot you will first need to make sure the contents of the FXZ file are in the same folder as the fastboot files. Next open a command prompt and change the directory to the folder with your fastbboot files (eg. cd C:\). Now use the following commands to flash the FXZ files. If you choose to just flash the recovery then skip all the other commands except the command to flash recovery.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse

Anyone know how to cancel the reminder on the update? My phone downloaded the update, when I click install later it makes me set a time to be reminded. Don't really want to lose root for this update. Any ideas?
Sent from my GT-N8013 using Tapatalk 4

whitlecj said:
Anyone know how to cancel the reminder on the update? My phone downloaded the update, when I click install later it makes me set a time to be reminded. Don't really want to lose root for this update. Any ideas?
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
delete the download through Tibu and then freeze the ota apk in Tibu

what i did to keep root with pwnmymoto was make sure my phone was 100% stock then root using pwnmymoto boot into recovery and back up root with ota rootkeeper. then i temp unroot and reboot to bootloader and flashed the original recovery back and installed the update which aborted near the end so i did it again and it did the same thing. after rebooting it was the new software update with no root so i flashed the boot.img into the recovery partition and booted back to recovery to restore root which you may have to grant a app su permisions for it to stick when you reboot. so far its running good. idk if the update applied properly but it booted up and runs great

FeaR_x_KhAoS said:
what i did to keep root with pwnmymoto was make sure my phone was 100% stock then root using pwnmymoto boot into recovery and back up root with ota rootkeeper. then i temp unroot and reboot to bootloader and flashed the original recovery back and installed the update which aborted near the end so i did it again and it did the same thing. after rebooting it was the new software update with no root so i flashed the boot.img into the recovery partition and booted back to recovery to restore root which you may have to grant a app su permisions for it to stick when you reboot. so far its running good. idk if the update applied properly but it booted up and runs great
Click to expand...
Click to collapse
anyone know if safestrap will be available after the ota (assuming we apply the update as you mentioned)?

has anyone tried rooting via motoroot 1.1 after doing the OTA from an unrooted device?

jayboyyyy said:
delete the download through Tibu and then freeze the ota apk in Tibu
Click to expand...
Click to collapse
Thanks for the response. Where do I find the download using tibu?
Sent from my GT-N8013 using Tapatalk 4

whitlecj said:
Thanks for the response. Where do I find the download using tibu?
Sent from my GT-N8013 using Tapatalk 4
Click to expand...
Click to collapse
check out here. It is a big list but i think it has what things to freeze for the OTA. there is just one maybe two i think.
http://forum.xda-developers.com/showthread.php?t=2432729
just checked that he only disabled motorola OTA. i am on Vzw and don't have an OTA yet so im not sure thats all you need to freeze. I read some where to freeze updater.apk as well. maybe its either or. I don't have updater.apk frozen but if motoOTA doesn't fix it then do updater as well

jayboyyyy said:
check out here. It is a big list but i think it has what things to freeze for the OTA. there is just one maybe two i think.
http://forum.xda-developers.com/showthread.php?t=2432729
just checked that he only disabled motorola OTA. i am on Vzw and don't have an OTA yet so im not sure thats all you need to freeze. I read some where to freeze updater.apk as well. maybe its either or. I don't have updater.apk frozen but if motoOTA doesn't fix it then do updater as well
Click to expand...
Click to collapse
You have to.freeze the update.apk and if you've downloaded the update its in your cache.

[Q] Kitkat big mess, bootloop only! Any help?

Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?

Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4

ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...

I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.

omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help

[Tutorial] Restore Nexus 9 to Stock

I have a defective device and in preparing to return it, I locked the bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
I was afraid that the N9 was like the N5 & 7 with the "tamper" flag, but after some digging (and advice from others out here), I decided to restore the factory image to see if that would overwrite the image. Yes! No more big fat red "I unlocked my bootloader and may have voided my warranty" message.
I can't take credit for this, but I thought I would consolidate everything I was finding in the Q&A threads into one spot, so I put this little tutorial together. Thank you @Pilz, @jd1639 & @PhilDX for your various posts.
Step 1 - Prepare your system
[Windows]
Since your bootloader is unlocked, you probably already have ADB and fastboot, but if not, grab the SDK from here, unzip and add the "platform-tools" directory to your PATH statement
If your drivers are set up properly and your device has Android debugging enabled, connect USB and execute `adb devices` from a command prompt you should see your device listed
Download the factory image for "volantis" here
The image is double zipped, so unzip, untar, then unzip the image-volantis-lrx21q.zip file into the same directory that contains the bootloader*.img file
Step 2 - Unlock bootloader
If you locked your bootloader, unlock again:
Code:
adb reboot bootloader
fastboot oem unlock
Step 3 - Flash stock image
The flash-all.bat script is broken, so you have to do it by hand:
Open a command prompt
cd into the directory where you unzipped the factory image files
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Before rebooting, relock the bootloader:
Code:
fastboot oem lock
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).

Typo: fastboot oem unlock

hirndurst said:
Typo: fastboot oem unlock
Click to expand...
Click to collapse
Hahaha! Thanks.

always good to know! thanks!

Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?

AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.

DarthSudo said:
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
Click to expand...
Click to collapse
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app

Thanks for this thread. Great guide.

jd1639 said:
You could also use fastboot -w instead of the erases
Click to expand...
Click to collapse
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)

Thanks for this. I RMA'd my Nexus 9 and sending it back tomorrow

DarthSudo said:
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Click to expand...
Click to collapse
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app

AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
jd1639 said:
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You guys are all right. I looked back at some of my notes and I've flashed plenty of devices w/o formatting the other partitions first. Just userdata and cache. Thanks!

Hey guys, just wanted to thank you for the fixed "script". This is now my flash-stock.sh script I use whenever I need to flash a nexus device as the one delivered by google just doesn't work (reboot loop due to crashing apps on startup or "missing system.img").
Works perfect and I always like to not dirty but rather make a clean flash as it just reduces the number of possible faults .
Cheers
Creamy

Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk

bruce7373 said:
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...

DarthSudo said:
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
Click to expand...
Click to collapse
Thx, that seems simple enough. But I made the initial system (stock) backup before I rooted. That's why I was thinking restoring that would work. I just wasn't sure about the recovery, whether the restore would put the stock recovery back or not.
Sent from my Nexus 6 using Tapatalk

DarthSudo said:
I have a defective device and in preparing to return it, I locked to bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Click to expand...
Click to collapse
Hi,
is there a way to get rid of that red message if your bootloader is locked and you cannot boot into OS?
Thanks!

EDIT* Nevermind

Hey. Sorry for reviving this thread.
I installed Remix OS on my N9 and (after discovering that performance is horrible, with ~80% RAM usage on idle) after a reboot, Remix OS won't get past it's boot splash. I am attempting to flash my device back to stock.
I never touched the bootloader (never did any 'fastboot flash bootloader ...' or anything), so it it still necessary to flash the bootloader image, or can I just flash the system.img, boot.img, vendor.img etc.?

The bootloader had never changed so there is no reason to flash it.
Sent from my Nexus 9 using XDA Free mobile app

6.0.1 - How to flash?

I am looking for a clear explanation of how to flash Android 6.0.1 with root and encryption disabled without wiping data. With all the explanations through the forum, all the "if's" and "but's" get confusing and can be clear as mud. Thanks for your help.

i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I

nextelbuddy said:
i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I
Click to expand...
Click to collapse
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.

how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img

ShaunWinSC said:
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.
Click to expand...
Click to collapse
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Ovrclck said:
how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
Click to expand...
Click to collapse
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.

nextelbuddy said:
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.
Click to expand...
Click to collapse
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?

ShaunWinSC said:
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?
Click to expand...
Click to collapse
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.

nextelbuddy said:
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.
Click to expand...
Click to collapse
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.

I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
ShaunWinSC said:
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.
Click to expand...
Click to collapse
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.

nextelbuddy said:
I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.
Click to expand...
Click to collapse
Have u flashed vendor.img ???
That's probably the problem :silly:

kauemelhado said:
Have u flashed vendor.img ???
That's probably the problem :silly:
Click to expand...
Click to collapse
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol

nextelbuddy said:
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol
Click to expand...
Click to collapse
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message

kauemelhado said:
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message
Click to expand...
Click to collapse
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!

I have flashed these three Files via the readme commands(fastboot flashing) and did not have my data partition wiped. and now FC's on ubermallow custom rom.

nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
Some people are having this problem with EX kernel. But I guess the kernel is not the problem.
I'll flash the update later on today, then i'll tell you how that work for me hehe

nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61

kauemelhado said:
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61
Click to expand...
Click to collapse
Nice, how did you made it? Did you leave the recovery.img?

Martini3001 said:
Nice, how did you made it? Did you leave the recovery.img?
Click to expand...
Click to collapse
I flashed stock recovery and later on flashed twrp.
I was getting the android of death when booting into TWRP.
So, I did this:
-fasboot flash recovery *twrp*
-fastboot reboot-bootloader
*on your fone* using the volume buttons search for "RECOVERY"
-boot into recovery
-thank me!
lololol

I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?

MPAI said:
I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?
Click to expand...
Click to collapse
after you flash TWRP, if you reboot, the system will flash the stock recovery back if its not the original
after u flash TWRP, u need to boot into recovery, and then flash the expected SuperSU.zip
the supersu zip script will edit the system and disable the flashing of stock recovery

Unable to update OTA since repair - alternatives?

Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil

clarkey586 said:
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
Click to expand...
Click to collapse
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal

DaMadOne said:
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
Click to expand...
Click to collapse
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:

clarkey586 said:
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
Click to expand...
Click to collapse
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* Here is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...

DaMadOne said:
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* .... is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
Click to expand...
Click to collapse
Haha suppose you're right! Sure I'll probably just wipe my device in the end, be nice to have a clean go at MM haha.
The bootloader status was indeed locked so I don't know what's causing the issue?
Anyway, thanks a million for the help I'll update if/when all goes well :good:

Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated

clarkey586 said:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
Click to expand...
Click to collapse
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.

DaMadOne said:
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
Click to expand...
Click to collapse
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!

clarkey586 said:
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
Click to expand...
Click to collapse
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.

DaMadOne said:
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
Click to expand...
Click to collapse
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again

clarkey586 said:
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
Click to expand...
Click to collapse
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?

DaMadOne said:
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
Click to expand...
Click to collapse
Had to use the 2nd OTA.zip but I didn't really try any of the remove sim card stuff or waiting long. No unlockable bootloader either but I'm satisfied for the moment haha.