Database Develop

Help. Rooted Dev edition VZW. Took OTA update infinite loop now

I totally forgot I was rooted and had TWRP and I took the OTA update.
Now the phone is in an infinite loop of rebooting.
What do I need to do to remedy this?
Thank you

Same phone, same problem but I was using clockwork mod recovery. You need to flash the stock recovery using Factbook, then the other update will take.
There are some existing threads that will fill you in with the details!
Good luck.
Sent from my Nexus 7 using Tapatalk

There are PLENTY of threads saying you can NOT install the OTA while you have a custom recovery like TWRP or CWM installed. Doing so causes a boot loop. Almost every one of those posts (at least the ones I've made) says if you get into this situation you need to erase your cache to get out of the boot loop
Boot the phone into fastboot/bootloader mode. Then use mfastboot on the PC to erase your cache. Return to stock and try again.
If you are close enough to stock, you can just try to boot the phone into mfastboot mode, flash STOCK recovery, and see if you can install the OTA, or if it will fail (due to varying too much from stock).

this sticky was helpful
MFastboot(Used for manually downgrading to 4.2.2)
MFastboot
For firmware Download pick what firmware you want from the link below... make sure its the one you have. you cannot downgrade
http://sbf.droid-developers.org/phone.php?device=0
reboot to the bootloader
i used only part of the code from the sticky
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
i was then able to then flash OTA whilst keeping the bootloader unlocked, kept root, kept all my files and settings intact.

Ditto. I just downloaded the pre update firmware and extracted the recovery.IMG file and flashed it with flashify uninstalled xposed framework and boom three reboots and the update is done . reinstall xposed framework and all my settings are still there . VZW Dev edition. Didn't even lose root.
Sent from my XT1060 using Tapatalk

That's how it's done simple and effective.

I did that code line that jadeddjay posted but only did the step through the recovery.img. I then rebooted and it worked perfectly and installed the OTA. I then went back into fastboot and installed TWRP and am rooted again.

Downgrade from Lollipop 5.0 to Kitkat 4.4.4; Change version; Upgade Again

Many of you have trouble changing to another version to get lollipop update or downgrading to kitkat.
Here are some tips:
To downgrade or to change version eg. Global (xt1063 Blur_Version.21.11.17.titan_retuglb.retuglb.en.US) to US (xt1063 Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) follow the codes below while flashing using fastboot cmd
NB: make sure you are going to flash the same version (global/Us/etc....) of firmware while downgrading!:
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
Now, to upgrade to lollipop agai from the flashed version, follow these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da....
explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
To root your device using cf autoroot follow this link: http://forum.xda-developers.com/moto-g-2014/help/solved-cf-chainfire-autoroot-problem-t2942154
Hit thanks if it helps

Thank you for these instructions.
Is it really possible to downgrade? I was always under the impression that motorola did not allow rolling back to previous firmwares, unless the bootloader was not changed during the upgrade..
Also just to clarify, this does not require unlocking the boot-loader? (to down-grade; i see the steps to install a recovery for upgrade to lollipop)
I ask because most of these commands seem to be available to use with a locked boot-loader, from my experience (moto x). You state that the boot-loader does not need to be locked.. but this seems redundant.
Does it need to be UN-locked?
Sincerely,
confuddled.

Hi, i have soft bricked my moto g xt1068 when i have update to lollipop, can i use this method for downgrade to KitKat with bootloader locked ? Thanks.

Cool OP

thanks
Yes guys it really works just in few minutes I try this method too. Now I enjoying the fun
Of previous version lolipop was very very bad

Anonymous 360 said:
Many of you have trouble changing to another version to get lollipop update or downgrading to kitkat.
Here are some tips:
To downgrade or to change version eg. Global (xt1063 Blur_Version.21.11.17.titan_retuglb.retuglb.en.US) to US (xt1063 Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) follow the codes below while flashing using fastboot cmd
NB: make sure you are going to flash the same version (global/Us/etc....) of firmware while downgrading!:
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
Now, to upgrade to lollipop agai from the flashed version, follow these steps:
after downgrading, go to bootloader, install twrp 2801 and flash supersu2.16 (that means, root your device ! ))
reboot and copy your lollipop update file (same variant) to the internal storage
now, again go to bootloader and flash the recovery: Fastboot flash recovery recovery.img
Now go to recovery and select your lollipop update... ta-da....
explanation:
After entering recovery node, Press the Volume Up and Volume Down buttons for around 5 seconds. Now while holding those two, press and release the Power button.
Your device will now be booted into stock recovery mode, displaying Android System Recovery <3e> text at the top of the screen.
apply adb trougt sdcard.... select file AND WAIT TO THE PROCess to finish
You dont need to lock the bootloader at all :good: :good:
To root your device using cf autoroot follow this link: http://forum.xda-developers.com/moto-g-2014/help/solved-cf-chainfire-autoroot-problem-t2942154
Hit thanks if it helps
Click to expand...
Click to collapse
Can i downgrade from android m to KitKat 4.4.4?

Ota updates on unlocked bootloader? Please help

I just unrooted my moto g xt1068 and flashed stock rom. But for some reasons i am unable to relock the bootloader. Just want to know that will I be able to receive OTA updates even when the bootloader is unlocked or should i have to relock the bootloader?

why nobody answered my questions yet? Plz reply soon

sandy1636 said:
I just unrooted my moto g xt1068 and flashed stock rom. But for some reasons i am unable to relock the bootloader. Just want to know that will I be able to receive OTA updates even when the bootloader is unlocked or should i have to relock the bootloader?
Click to expand...
Click to collapse
Unlocked bootloader, doesn't matter with updates, or system flash..only when one needs Root, then the bootloader needs unlocked, unless a Root exploit is used..
sent by my
5.0_22.11.6 Lollipop (Rooted)
TWRP v2.8.0.1-titan
UPDATE-SuperSU-v2.16
XT1064 Moto G (2nd Gen.)
http://waynekent.com/page6.html
"Praise Jah" YOU people.!

Try this:
Flash Stock firmware using these commands in this order:
Code:
[B]mfastboot.exe oem lock begin[/B]
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
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 modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
[B]mfastboot.exe oem lock[/B]
mfastboot.exe reboot
Hope this helps

KrishnaSagar said:
Flash Stock firmware using these commands in this order:
Code:
[B]mfastboot.exe oem lock begin[/B]
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
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 modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
[B]mfastboot.exe oem lock[/B]
mfastboot.exe reboot
Hope this helps
Click to expand...
Click to collapse
i have already entered all these commands and successfully flashed stock rom. But when i enter mfastboot.exe oem lock, its shows as (bootloader) sst lock failure.

That is the standard procedure, but if you are getting errors then please refer to this thread:
http://forum.xda-developers.com/moto-g-2014/general/guide-explaining-boot-loader-locking-t2933827

KrishnaSagar said:
That is the standard procedure, but if you are getting errors then please refer to this thread:
http://forum.xda-developers.com/moto-g-2014/general/guide-explaining-boot-loader-locking-t2933827
Click to expand...
Click to collapse
I have followed the exact steps as mentioned in this thread. But still unable to relock the bootloader.
But I read somewhere that i can still get OTA updates even if bootloader is unlocked as long as i am in stock firmware and recovery. Is that true?

sandy1636 said:
I have followed the exact steps as mentioned in this thread. But still unable to relock the bootloader.
But I read somewhere that i can still get OTA updates even if bootloader is unlocked as long as i am in stock firmware and recovery. Is that true?
Click to expand...
Click to collapse
Yes. OTA updates are available on Unlocked Bootloader as long as you dont Root or change the recovery.

Thread hijack: If you have an unlocked bootloader and rooted xt1068 (and using Philz kernel) on the stock ROM, can you expect to get the OTA update?
I'm finding conflicting responses to this on searching and if I need to go back to stock recovery would happily do that, but I don't want to wipe my device.

grayme said:
Thread hijack: If you have an unlocked bootloader and rooted xt1068 (and using Philz kernel) on the stock ROM, can you expect to get the OTA update?
I'm finding conflicting responses to this on searching and if I need to go back to stock recovery would happily do that, but I don't want to wipe my device.
Click to expand...
Click to collapse
We shall see when the OTA is pushed to blighty. My advice would be to backup the boot, recovery and system partitions in their factory state before tinkering. I just rooted the stock ROM by booting from a TWRP image via fastboot, installed SuperSU and then used dd to image /boot, /recovery and /system to an external SD. If the OTA fails due to me having installed Xposed and removed system apps, I'll just restore the /system image and remove SuperSU... A wipe of the /data partition shouldn't be required.
If the OTA fails for you, I'd suggest flashing back the stock boot, recovery, and system images from the stock retgb firmware zip using fastboot and then trying the OTA upgrade process again.

rufflove said:
We shall see when the OTA is pushed to blighty. My advice would be to backup the boot, recovery and system partitions in their factory state before tinkering. I just rooted the stock ROM by booting from a TWRP image via fastboot, installed SuperSU and then used dd to image /boot, /recovery and /system to an external SD. If the OTA fails due to me having installed Xposed and removed system apps, I'll just restore the /system image and remove SuperSU... A wipe of the /data partition shouldn't be required.
If the OTA fails for you, I'd suggest flashing back the stock boot, recovery, and system images from the stock retgb firmware zip using fastboot and then trying the OTA upgrade process again.
Click to expand...
Click to collapse
It's probably a bit late for me to use dd before I installed Xposed. Thankfully I did back up using CWM before I wiped in installing Lollipop from a thread on here. I think I'll just wait till Motorola decides to push OTA over here.

grayme said:
It's probably a bit late for me to use dd before I installed Xposed. Thankfully I did back up using CWM before I wiped in installing Lollipop from a thread on here. I think I'll just wait till Motorola decides to push OTA over here.
Click to expand...
Click to collapse
Aye, but you should be able to flash back the stock system image from the 4.4.4 release using Motorola's fastboot. I dunno if the standard fastboot or any of custom recovery distros support sparse images. There must also be some way of converting the partial, sparse files into a normal image, too... I guess the questions is whether it's more of faff to start from a formatted data partition, or not.

rufflove said:
Aye, but you should be able to flash back the stock system image from the 4.4.4 release using Motorola's fastboot. I dunno if the standard fastboot or any of custom recovery distros support sparse images. There must also be some way of converting the partial, sparse files into a normal image, too... I guess the questions is whether it's more of faff to start from a formatted data partition, or not.
Click to expand...
Click to collapse
I used to understand these phones, but everything just seems so much more complicated these days!
I'm getting old.

[Q] Pure Edition not restoring to stock correctly, can't boot

I recently got a Pure Moto X 2014 and immediately unlocked it. I then tried to root it using the boot image in this thread:
http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264
Apparently that is not the right thing to do for a Lollipop phone, as I found out after booting it (note: I did not flash the boot image, only booted it). The result was it would not boot past the watery 'M' screen.
I've tried to restore using a couple of stock images:
1. the files Motorola shares with you to restore to stock (TMO_21.21.42.victara_tmo)
2. The Lollipop image from graffixnyc (http://www.graffixnyc.com/motox.php) TMO_21.21.42.victara
I'm doing so with the recommended commands using the moto version of fastboot provided with the Motorola download:
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
When I do this with the Moto firmware, it boots until the barren fall-like earth picture and then goes black. When I flash the Lollipop image it sticks at the watery 'M'.
I tried installing crdroid ROM, and though I can get to TWRP recovery, it won't install the zip because it "can't install this .package on top of incompatible data."
What can I do? Thanks in advance.

https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Do that ^
Not sure why you didn't use the official image/ wipe user data & cache, but that'll fix it.

Looks like the step I was missing was wiping data. I formatted data from TWRP and that allowed install of CM based ROM, then I went and restored the Lollipop image including the "erase userdata" command. Everything is happy now.
I knew I'd figure it out as soon as I asked, just didn't want to lose user data. Thanks for trying to help!

How to root N6F26Q 7.1.1?

Hey, how do I root the Nexus 6 on 7.1.1 and the Build Number is N6F26Q? Thanks.

I use Magisk

But how do I root? A link to a tutorial would be helpful.

php111 said:
But how do I root? A link to a tutorial would be helpful.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Go here and you should be fine? Is this your 1st time rooting the nexus ?

php111 said:
But how do I root? A link to a tutorial would be helpful.
Click to expand...
Click to collapse
Step-1
https://www.youtube.com/watch?v=29U7X4NgoUY
Look up Shamu Latest TWRP
Step-2
https://www.youtube.com/watch?v=84D2-UnUIA4
Look for the latest stable SuperSU
Done

Or this way which is longer.
Make sure the phone is in fastboot mode.
Than:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
First, delete the recovery file or replace with the TWRP recovery (just rename the TWRP recovery to recovery.img and yes, to replace when copy/paste, that should do the job).
Now reboot again and boot into recovery and than wipe cache and dalvik and flash SuperSU and wipe cache and dalvik again.
Someone above asked me is this my first root? No, my first root was on a Galaxy S3 which I do not have the S3 anymore. What made me to lose the root on the S3 was I took an OTA update and it KNOX the device so I could not root.
Yes, this is my first root on Nexus. No, it is not my first root in regards to Android

Wugs toolkit does it fine in one click
Sent from my EVA-L09 using Tapatalk

I just flashed supersu 2.78 in twrp, that worked