Database Info

[ROM] New stock Rom DEFY JRDNEM_U3_2.51.1 UK

New official version stock English rom for UK v2.51.1 released.
DOWNLOAD: Defy Rom v2.51.1

thanks, but where can we find the changelog of this new rom ?

Great! Will give it a try.

might try this tomorrow, although I can't see it being anything major, at the end of the day its not been push OTA as an update yet. I just tried the supposedly "no blur" firmware too and there was still loads of blur on it!

it is unrootable for the moiment.

Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.

TPGamer said:
Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.
Click to expand...
Click to collapse
i don´t know, but i have the "deblured" 2.34.1 firm rooted with z4root and with the clockwork recovery working

Thanks, have installed and its a nice improvement.
Not a giant leep but more of a polish. I must be one of the few people that likes the email client in motoblur.

i aint going anywhere near this it its not rootable then - there nothing wrong with 2.21 imo. And I like the blur email app too lol

If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?

the problem is that you can not flash any older than this and without root you can not flash custom recovery and can not restore nand backup.
if you flash older the phone wont boot.

Yep now unable get root access. Oh well

im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.

TPGamer said:
If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?
Click to expand...
Click to collapse
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working

andyirons said:
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working
Click to expand...
Click to collapse
we need another exploit for this rom atleast

jboogie3 said:
im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.
Click to expand...
Click to collapse
I´ve just flashed back from 2.34.1 to 2.21.0 with no major problem.
Looks like 2.51.1 UK comes with a secret within.

jboogie3 said:
we need another exploit for this rom atleast
Click to expand...
Click to collapse
yes, indeed

ya... moto patched it.. my devices goes offline after doing the - ./rageagainstthecage-arm5.bin using the droid2root method... if only it could stay online then we could have root

what the fnck....I just flash the 2.51 two hours ago. i've try atleast 3 method to root this ...all failure....Fnck moto.....

see what they did is baited you in with "noblur" and now your stuck without root!

[Q] Root Failure (All Methods Attempted) FIXED :D

Heres the issue. I am no noob at this whatsoever and have tried EVERYTHING. I have used every program I could find to attempt root and none can seem to gain root access. The install SuperUser or SuperSU and every time root fails even if said app is installed. Please help Im doing a talk on August 20th that I NEED this device for. All help appreciated. Thanks!

Im slightly confused as your sig says rooted stock
But anyway I recently got myself a Razr HD and I used http://forum.xda-developers.com/showthread.php?t=2241788 to root and unlock bootloader
My device was 4.1.2 and I did not want to downgrade but this one worked :victory:

More info needed. Is your bootloader unlocked? If not, which firmware are you on?

killrhythm09 said:
More info needed. Is your bootloader unlocked? If not, which firmware are you on?
Click to expand...
Click to collapse
Nothings been modified. Plus I hope you know that to unlock the bootloader it requires root

dr_strangetrick said:
Im slightly confused as your sig says rooted stock
But anyway I recently got myself a Razr HD and I used http://forum.xda-developers.com/showthread.php?t=2241788 to root and unlock bootloader
My device was 4.1.2 and I did not want to downgrade but this one worked :victory:
Click to expand...
Click to collapse
Thank you, I think I may have worked out my issue! I was using 1.2 of that program. I think thats why. Let me give this a go

Tried again with this guy and still got failure. I always get this:
[*]This May Take A Few Minutes
[-]Failure

Ok well what do you know. 3rd times the charm eh? I tried a third time this time after reflashing stock firmware, antennas, etc... Thanks!

Well done and welcome to the club

dr_strangetrick said:
Well done and welcome to the club
Click to expand...
Click to collapse
Thanks haha xD Coming from a Galaxy Nexus GSM Dev Edition, this is oddly restraining. There seem to be only a few ROMs available for this device.

Quality is better than quantity

[Q] 4.4.3 update help?

So I've had my nexus 5 for the past couple months and was recently prompted to download the latest update, 4.4.3. The thing is, when the update is finished downloading and I'm told to reboot my phone to install it, I get an error message- the green android dude is on its back with a red exclamation point above it. I've reset my phone and attempted to reinstall the update, but no luck. Anyone else have this problem? How do I get around it and download the update?

ksalam said:
So I've had my nexus 5 for the past couple months and was recently prompted to download the latest update, 4.4.3. The thing is, when the update is finished downloading and I'm told to reboot my phone to install it, I get an error message- the green android dude is on its back with a red exclamation point above it. I've reset my phone and attempted to reinstall the update, but no luck. Anyone else have this problem? How do I get around it and download the update?
Click to expand...
Click to collapse
I had the same problem but i was rooted so i thought that rooting messed something up,so i unlocked the bootloader and installed manually.But if you're running full stock then i don't know what causes the problem.
PS:I'm sorry if my english is not perfect,i hope you understand what i'm trying to say.

If you're rooted with a custom recovery, the OTA will not work.
See this OTA help thread...
http://forum.xda-developers.com/showthread.php?t=2523217
Or you can flash 4.4.4 with fastboot and not worry about the OTA....guide for that here....
http://forum.xda-developers.com/showthread.php?t=2513701
Good luck!

Benthemad said:
I had the same problem but i was rooted so i thought that rooting messed something up,so i unlocked the bootloader and installed manually.But if you're running full stock then i don't know what causes the problem.
PS:I'm sorry if my english is not perfect,i hope you understand what i'm trying to say.
Click to expand...
Click to collapse
Guess I should've mentioned I rooted my device right out the box- I had a feeling that had something to do with it, which is why I reset my phone.I'll give your suggestion a shot.

Benthemad said:
I had the same problem but i was rooted so i thought that rooting messed something up,so i unlocked the bootloader and installed manually.But if you're running full stock then i don't know what causes the problem.
PS:I'm sorry if my english is not perfect,i hope you understand what i'm trying to say.
Click to expand...
Click to collapse
KJ said:
If you're rooted with a custom recovery, the OTA will not work.
See this OTA help thread...
http://forum.xda-developers.com/showthread.php?t=2523217
Or you can flash 4.4.4 with fastboot and not worry about the OTA....guide for that here....
http://forum.xda-developers.com/showthread.php?t=2513701
Good luck!
Click to expand...
Click to collapse
thanks!

OP @ksalam
If you tried the search you would have found something by yourself easily. Thats the suggestion to each one of us in the FORUM rules as well.
Please start searching now instead of making new ones and clustering.
Thanks
THREAD CLOSED

Droid Mini/Ultra/Maxx SU6-7.7?

Just wondering if anyone has any insight on SU6-7.7 on the Droid line? Whether or not anyone know or hear anything about downgrading to a different SU version? I have the firmware file for the latest SU6-7.7 in case anyone wants it.
https://drive.google.com/open?id=0B7hPMTc_G5VPMFVqZmdMSXJEbjA
It would be nice if Motorola/Lenovo would let us do what we want with a phone they no longer "support".

Thanks, I was looking for this.

RichardCA said:
Thanks, I was looking for this.
Click to expand...
Click to collapse
Sure thing! Let me know if you need anything else!

SalmanJohnson2011 said:
Sure thing! Let me know if you need anything else!
Click to expand...
Click to collapse
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?

RichardCA said:
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
Click to expand...
Click to collapse
I believe that you can replace the stock boot logo with an unlocked or locked bootloader. There are a quite a few logos to choose from. When you pick one, you fastboot the image.

Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
Not sure at the moment. XD I'll reply back to this post or PM you if I do. Thanks again! If you have any more info, please let me know!

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
When you flashed it to your mini/ultra, where you on SU6-7.7?

SalmanJohnson2011 said:
When you flashed it to your mini/ultra, where you on SU6-7.7?
Click to expand...
Click to collapse
I jumped around a lot. I was playing with marshmallow and lollipop builds and needed to revert back. But I was on the Motorola stock SU4.21 when I flashed it.
I used the process on this page, and got zero errors:
http://forum.xda-developers.com/showthread.php?t=2580060

Help please!!!
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:

edgar1994 said:
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
Click to expand...
Click to collapse
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.

Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.

ashal said:
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
Click to expand...
Click to collapse
Nope. I've tried and it doesn't work.

SalmanJohnson2011 said:
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Click to expand...
Click to collapse
Man this really sucks i hope someone finds a way around this :crying:

edgar1994 said:
Man this really sucks i hope someone finds a way around this :crying:
Click to expand...
Click to collapse
I Agreed dude. I'm with you! I don't know why I keep getting Verizon phones. XD Regardless of what I learned. Haha

SalmanJohnson2011 said:
Nope. I've tried and it doesn't work.
Click to expand...
Click to collapse
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.

ashal said:
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
Click to expand...
Click to collapse
For me, I tried going down one update at a time and it still doesn't work.

it says devoloper phones only
can I flash to my ultra even tho its not a dev phone??

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.

root successful
Davey126 said:
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
Click to expand...
Click to collapse
Dear i have successfully rooted mine droid mini su6-7.7 with kingo root (not global) v3.4 successfully now i have superuser app in system directory
---------- Post added at 05:42 AM ---------- Previous post was at 05:20 AM ----------
Dear friends i have successfully root mini droid mini su6-7.7 with kingo root v3.4 (not kingo root global). actually i was trying to flash su4.21 over su6-7.7 with RSD lite v6.1 but failed with max get var and after that tried to flash with RSD lite 5.1 again failed without any error. after all of there method i thought of giving a try to kingo root. i downloaded 2 apps kingo root globalv4.9.7 and kingo root v3.4, kingo root global failed to root but.... kingo root v3.4 succeeded to roo. now i have superuser app in system driectory.
but problem is that after removing system app (amazon) when i restarted the phone all the apps came back and superuser app gone. i don't know why so my request to look into this method .
i have tested this method and worked 100% and i have no intention of making fun of me. i have both the apps but don't know how to upload here
Thanks

[GUIDE] How to Update OTA Step by Step on Moto g4 plus

This guide is to help out the people who are rooted to know exactly what to do if you get an OTA notification so that there are no errors.
This guide will only work for the Systemless rooting. Guide here
The basic things for achieving OTA after rooting can be found here
Basic things to keep in mind if:
1. Still on soak - Follow this guide and come back to marshmallow and then you should be able to take the OTA.
2. If you are on Stock and rooted - Make a nandroid backup and then the next step is pretty simple, go to SuperSU app and click on the option Full Unroot and click on yes and then again yes and wait for the Phone to reboot. Once it starts back wait for the optimization of the Apps and then download the OTA and then install it. Make sure it is the Stock recovery through which you flash the OTA.
It should go through Smoothly. I have done it twice. Since Nougat doesn't support any known root method yet, so keeping a titanium backup before unrooting is preferred so that as soon as it supports root u can restore all of it back.
Happy updating!

I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.

SoNic67 said:
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
Click to expand...
Click to collapse
That's true! But it'll be just a matter of time before we get it!

SoNic67 said:
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
Click to expand...
Click to collapse
I have downgraded using my tutorial. And i told you that the firmware that i posted is official...
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961

TechBurner said:
I have downgraded using my tutorial. And i told you that the firmware that i posted is official...
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
Click to expand...
Click to collapse
I don't know but XT1643, doesn't come out of the box MPJ24.139-13.1.... it comes out with 23.1 i guess...
That guide did work perfectly!

abhi212b said:
I don't know but XT1643, doesn't come out of the box MPJ24.139-13.1.... it comes out with 23.1 i guess...
That guide did work perfectly!
Click to expand...
Click to collapse
I know that works perfectly right now, the only reason i made the tutorial on how to downgrade is because we had the same scenario for Moto g 1st gen. People got used to downgrading using the normal method, what they didnt realize was that the bootloader and gpt were not being flashed and they showed failed when you did that for the official firmware. But after a month tons of Moto g 1st gens got hard bricked because of that. Anyone who tried to downgrade from modified stock or custom rom based on Lollipop (At that time) Got their phone hard bricked. It's the same for Nougat also and is same for All cross android versions after Kitkat.
With every new update they release a new partition table and a new bootloader . The new bootloader doesnt allow you to flash the previous bootloaders over it and same for partition but for some varients of the phone the warning is not there and the older bootloader is flashed resulting in a hard brick. This is also true for Custom roms based on the official firmware (which will come) and devices in which a custom kernel has been flashed.
I am not saying trust me, i am just saying be careful .

^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.

Quick question
I have a XT1643
On stock rooted rom with elemental kernel.
Got an update notification yesterday.
I flashed the stock boot.img I found on the forum but the wifi is not working after flashing that.
what do I need to do in order to get it working and get the update?
Thanks

SoNic67 said:
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Click to expand...
Click to collapse
I agree with you on this. I am stuck with an N Bootloader and and MM firmware.
I can upgrade to an N ROM but I get FP issues (cosmetic, but still not desirable)
I cannot take an official OTA anymore because even if I downgrade to stock, I still have an N Bootloader which prevents me from taking OTA.
Unless we get a stock N rom, I guess we are stuck with this setup.
Sent from my Moto G (4) using Tapatalk

SoNic67 said:
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Click to expand...
Click to collapse
It will i guess because then again u can take an OTA to N ...

tandon.ayush said:
Quick question
I have a XT1643
On stock rooted rom with elemental kernel.
Got an update notification yesterday.
I flashed the stock boot.img I found on the forum but the wifi is not working after flashing that.
what do I need to do in order to get it working and get the update?
Thanks
Click to expand...
Click to collapse
Everything needs to be on stock! Stock boot, recovery, logo, kernel etc. then it works ! any modifications will lead to an error!