yashsingh1/xdaforums huggingface dataset:
[Droid Ultra General] spiral777:
thank you kent for the fxz! worked great! i was playing around trying to get LTE working but had no success...HSPA+ on tmobile is fine here in chicago...the LTE data is very fast too but calls and txts havent worked yet...so after seeing so many people update without any issues i figured id give it a try and update to 19.6.3

ill play around with it throughout the day and post back if LTE is working on tmobile...fxz was fine though and twrp installed supersu

edit: i disabled xposed before fxz but i for got to unfreeze my frozen apps...still had no problems and all of my apps were still frozen
[Droid Ultra General] NWKENT:
Awesome my friend..glad and honored to help out..I hope you smooth out your text and voice issues..

Sent from my 4.3_14.14.14

(Unlocked) XT1028 Moto G

http://waynekent.com/page6.html
[Droid Ultra General] kitcostantino:
NWKENT, will the reverting fxzs work for 4.4 4? been on it for a couple of days. usb otg wprks (for my purposes), but i am itching to go back to jb.
[Droid Ultra General] NWKENT:
Sir..I personally haven't tried it, due to lack of time to do so..But..I have read at least twice, that once on 4.4.4 one cannot revert back..

Sent from my:

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Droid Ultra General] kitcostantino:
ah, well, that is allright. i never took the plunge back to 12.15.15 from 4.4 (19.5.3) but i just wanted to rule it out as a possibility. i switched back to skiwongs carbon 5.25 build. all seems okay, but nothing will ever compare to the battery life i had on stock 12.7.7. thank you, sir!!!
[Droid Ultra General] NWKENT:
Confirmed..XT1080M cannot revert back from 4.4.4_21.11.21 to any previous OS..just bootloops..flashed stock KK and JB without success..a new OS version that is more secure than ever before certainly causes problems..but..I'm no Dev..lol

:(

Sent from my 4.4.3_21.23.4

(Unlocked) XT1045 Moto G 4G LTE

http://waynekent.com/page6.html
[Droid Ultra General] kitcostantino:
Ha ha. Thank you for taking the plunge for us, man. I really wouldnt mind stock 4.4.4 if i could theme and tweak stock. Gravity box and HkTheme manager are a strong almost, but i really want to theme it red and black *completely* and make baked in toggles w/o depending on stock quicksettings or a third party app. I am glad to see what GB and xposed do for people that are bl locked, i just wish moto stock was themable with a theme chooser theme. maybe one day. Carbon is great, for now, though. maybe i will finally break down and find a proper theming setup for mac. thank you again for your contributions to the maxx community, friend.
[Droid Ultra General] NWKENT:
Absolutely friend..sorry I couldn't help with good news..

This new 4.4.4 OS has corrected some issues for sure..(example) OTG-USB support now available, and other "stuff"..but..if you are Rooted..be sure and " freeze" the OTA..because, as we found out, no reverting back once on 4.4.4 at this time..I have read where, MAYBE , a few have managed to keep Root over into 4.4.4 but I don't know that for a fact..all my "stuff" is unlocked..

I do a lot of "stock" flashing and testing..and tried (many) different procedures to revert to KK 4.4 and JB 4.2.2 and flashed completed..but during animation boot, would run endlessly, (aka) bootlooping..also flashed different "recoveries"..with no good results..

:(

BTW..Xposed and Gravity Box run flawlessly on this new 4.4.4_21.11.21

Sent from my:

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Droid Ultra General] Topsnake:
What are we trying to accomplish here? Reverting back to JB or 19.5.3 is rather easy.
[Droid Ultra General] NWKENT:
Trying to revert from KK 4.4.4_21.11.21 to KK 4.4 (or) JB 4.2.2

Sent from my:

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Droid Ultra General] Topsnake:
Unlocked bootloaders correct?
[Droid Ultra General] NWKENT:
Absolutely..

Sent from my:

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Droid Ultra General] Topsnake:
I assume you have both fxzs already downloaded?
[Droid Ultra General] NWKENT:
Yes..I have JB 4.2.2 (and) KK 4.4_19.6.3 (and) KK 4.4_19.5.3

Sent from my:

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Droid Ultra General] Topsnake:
Ok let me test a bit and I'll get back to you
[Droid Ultra General] NWKENT:
Yes Sir..

Sent from my:

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Droid Ultra General] Topsnake:
Looks like your right kent. Possibly incompatible with the new boot loader
[Droid Ultra General] NWKENT:
Yeh..I worked with the issue maybe three hours the other day, many different approaches, many different recoveries..could flash successful..but during boot animation..would continuously loop..

Thanks for your assistance and time with this..

:)

Sent from my:

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Droid Ultra General] hayze:
Were you trying to just flash the system image, or did you flash older boot as well?
[Droid Ultra General] NWKENT:
I flashed complete FXZ, all img files, same as one would as a complete OS flash, each flash attempt completed, but during boot, would have a boot animation loop..I also erased data/cache each attempt..I flashed 4.4_19.5.3 (and) 4.4_19.6.3 << the stock recoveries flashed fine, and could get into stock recovery with each OS version..but always bootlooped..no matter how I flashed..I was using modified FXZ's, flashing with RSDLite using "fastboot" and "mfastboot".. couldn't revert from 4.4.4_21.11.21 to any other OS..

Sent from my:

4.4.4_21.11.21 (Unlocked)

XT1080M Droid Maxx #2

http://waynekent.com/page6.html
[Droid Ultra General] jphillips.hd88:
I was on 4.4.4 21.11.21 and was messing around with the dialer and got a system error msg I couldn't get out of. I didn't have my computer at the time and didn't want to be without my phone the rest of the day, so I booted to TWRP and restored and old backup. It took and brought me back to 4.4. 19.5.3. Sort of. When I got back to my computer I attempted to fastboot the 4.4 19.5.3 XML. I did get the downgrade error msg on the gpt and the motoboot, but the rest flashed allowing me to get enough back to stock to get the OTA's up to 4.4.4 21.11.21. So it looks as if the partition and motoboot img don't downgrade but will still allow OTA's and factory reset.
[Droid Ultra General] deduct:
im back baby!

Wanted to say thank you for this sir. I am back on 4.2 and my battery is already much improved. Plus i am able to use some xposed modules that i couldnt use on kk. Thanks again!
[Droid Ultra General] chuck864:
Battery life update

Only 1.5 hours screen time but still sooo much better than before I downgraded.
[Droid Ultra General] bigguy0691:
Hi fellas,

I have a boot loader unlocked MAXX on 4.4 19.6.3 want to update but am concerned about 2 things..

1. Will I be able to revert back to 4.4 19.6.3 after I update to the latest OTA version?

2. I believe I read that Xposed does not work (or stick after reboot) on the latest updates 6-7 and 6-7.2. Not sure if that is true.

Thanks in advance for the knowledge.
[Droid Ultra General] kitcostantino:
I thought i had already answered this. guess i never posted. ;) Q1: No. but the latest OTA version is great as long as you have an unlocked bootloader. 2) im on SU 6-7.2 and have zero issues with xposed on reboot. this runs amazingly compared to earlier Droid Maxx stock software. SU 6-7.2 is a fine update. it only sucks for those that do not have unlocked bootloaders. I used xposed 2.7 experimental. HK theme manager works well with older themes. im about to go back to Dirty Unicorns obake builds. Those are awesome. Well, unless Moto features aside from Active Display are a must-have. i use Dynamic Notifications 2.9.1 to replace Active Display when on cm12 based roms. Hope this all helps man. ;) any ? just lmk or pm.
[Droid Ultra General] rowland007:
You're right. I would just like to have the bloat plus Miracast and Droid Zap taken out.
[Droid Ultra General] arcanexvi:
Droid Zap can be disabled so that it no longer uses resources and screen mirroring doesn't use anything unless it's active... almost all of the bloat can be disabled. It still confuses me as to why people want the whole app gone. It's not like you recover that space as usable for storage. The storage partition and system partition are not interchangeable and are fixed in size. If you don't want to see the icon under disabled apps for some reason, just root and delete them from the /system/app folder. Just don't go in thinking that you're going to get more storage space or better performance than just disabling/deleting the app.
[Droid Ultra General] Gundabolu SC:
MOTO X SAFE STRAP

We can definitely be expecting one for the Maxx/Ultra/Mini soon! :fingers-crossed::victory:

Let the custom ROMs begin!!! :good:
[Droid Ultra General] reggie14:
Are there enough folks getting the Droid Maxx Developer Edition that it will get some some ROMs without resorting to Safe Strap? I've been waiting to see if a developer community forms, and so far it's not looking good.

Or, is it simply that until Motorola puts out a 4.3 ROM (for, say, the Moto X) they don't really have much to do?
[Droid Ultra General] mbh87:
should work fine now and shouldnt need a separate SS.
[Droid Ultra General] arcanexvi:
Moto X roms work fine. Just need to enable capacitive keys.
[Droid Ultra General] reggie14:
Sure, that's what I understand. But first, there really aren't any Moto X ROMs either, despite it being bootloader unlocked and having the sources available. I guess it shouldn't be overly surprising- most of the early ROMs for other phones were just variations on stock Android.

Second of all, while it shouldn't be too much port to port over a Moto X ROM, it's still more than I know how to do. I'm starting to wonder if anyone will bother, particularly with the Safe Strap route working with more devices.
[Droid Ultra General] LunaticSerenade:
Kernel source was recently released also. Give it some time.

Sent from my Carbon XT926
[Droid Ultra General] rowland007:
Droid Maxx's source and bootloader is unlocked too. I'm sure someone will develop directly for it.
[Droid Ultra General] reggie14:
The Maxx doesn't have an unlockable bootloader. There's a Developer Edition with an unlockable bootloader, but only a relatively small percentage of users will pay for the full $650 for it.

I suspect you're right, though. Someone will eventually port Android 4.3 to it.
[Droid Ultra General] LunaticSerenade:
I imagine that, much like the last generation, kernels and the like will work across devices.

Sent from my XT1080
[Droid Ultra General] Gundabolu SC:
Android 4.3 needn't be ported, its already there...!! U can flash the Moto X's 4.3 leak on the Maxx/Ultra if u have an unlocked bootloader n it works great, just that the capacitive buttons don't work... N probably Safestrap would make the same possible on locked bootloaders too!! :D
[Droid Ultra General] arcanexvi:
The kernel will be an issue for locked bootloaders
[Droid Ultra General] Blade765:
Well, from the little bit of messing around I did with my Consumer Maxx (Locked Bootloader), the key that it requires to unlonk the BL is 64 characters long. I wonder if there is a way we could figure out how Moto creates these keys by looking at a developers edition Unlock Token and the key Moto generates and sends.

Or if there is a way to make motorola's servers think that our Maxx's are Sprint Moto x's, since they are unlockable via the site anyway. Just thinking out loud really.

When I plugged just any 64 digit code in an performed fastboot oem unlockk "unlock code", it reported success on the computer, but remained locked on the phone itself.

Again, this was all from maybe 20-30 minutes of messing around in fastboot.
[Droid Ultra General] arcanexvi:
The IMEIs are flagged so other than brute forcing a code with near infinite possibilities... Unlock codes are 20 letters and numbers. Never happen. It's 1.336749x10^31. Keep trying with your random guesses though. :P
[Droid Ultra General] tucstwo:
Done

Personally, I'm tired of this game VZW and Moto (their pawn) are playing with everyone. With their bootloaders and security and going out of their way to keep everyone out of their own devices.

I'm done. My next device (err last few too except the exploited Razr HD) will be factory unlocked and if VZW doesn't want to come with me or participate, so be it. That's their loss...sure, little ole me...I'm negligible, but still, I'm gonna live on my principles. I guess I alone will force VZW to lose 6 cents a year. Oh well. Better off in my pocket and enjoying myself.
[Droid Ultra General] Blade765:
I didn't mean I was just plugging in random numbers abs letters hoping one would work, I was just trying to see exactly what it was the phone was actually looking for in order to unlock. If I'm not mistaken though, don't we actually have the ability to change imei's (this being one way people make their phone work on other carriers) I could be wrong, and probably am. I just didn't want you guys thinking I was trying to unlock my bout loader by just throwing **** to the wall and seeing what stuck. Lol.
[Droid Ultra General] arcanexvi:
I don't think the code generated by get unlock data will change if you change your IMEI but go ahead and try it. If it does you might win :P
[Droid Ultra General] sean67854:
This is probably a noob question but does disabling superuser in the SuperSU setting temporarily unroot in the same way it does on a GNex?
[Droid Ultra General] rowland007:
It doesn't unroot it. You just loose access management of the SU binary.
[Droid Ultra General] bigguy0691:
Thank you I really appreciate the education. Guess there would be no need to go back to 4.4 after updating?
[Droid Ultra General] kitcostantino:
no need at all, man. the only reason people freaked out when 4.4 came out was the inability to revert. there literally is no need to if yoi are bl unlocked. in the Droid Ultra android dev section, you will find a patched TWRP Recovery that has not failed me yet at all. its 2.8.4 and I think skrillax made it. its great. for those stuck on stock, it sucks. you, sir, are in am advantageous position.
[Droid Ultra General] TEPEM:
Hi there guys! I have just received a new Motorola XT1080 Maxx Developer Edition (dated to December 2013). It runs 4.2.2 and has an unlocked bootloader with factory recovery and stock:

- System Version 12.7.7.obake-maxx_verizon.Verizon.en.US

- Baseband MSM8960PRO_BP_2323.011.75.00R

- Build Number 12.9.0Q2.X-160-OBK_TA-14-7

If any of developers possibly require dumps from this or generally anything - please let me know before I root, install custom recovery and start flashing custom ROMs.

And 2 questions to everyone:

- what is the best custom recovery one may advise? (it's desirably for it to have a root incorporated.)

- what is the best ROM one may suggest?

Happy Thanksgiving!
[Droid Ultra General] kitcostantino:
dude, sounds crazy, but my xt1080mDEV lasted over two full days on that exact firmware. if it were me, id do nothing aside from unlock the bootloader and flash TWRP. that is the best sw and battery i have ever seen on a phone. (and i have a Turbo).

this is what i did when i got my DEV maxx.

http://xdaforums.com/showthread.php?t=2452152&page=46

i dont know if the newer version of TWRP by skrillax_cz will work on that firmware, but that is what i use on mine. http://xdaforums.com/droid-ultra/development/twrp-2-8-4-0-droid-mini-ultra-maxx-t3012851

again, though, i would stay on that version given the option. ;)
[Droid Ultra General] TEPEM:
hi man. It's a sad story with my phone I hope someone can really help. You know that I have a new XT1080MDEV phone running 4.2.2

- System Version 12.7.7.obake-maxx_verizon.Verizon.en.US

- Baseband MSM8960PRO_BP_2323.011.75.00R

- Build Number 12.9.0Q2.X-160-OBK_TA-14-7

It was bootloader unlocked but with a stock reovery and unrooted. I can only operate with fastboot so I took

DevFAQ_twrp-2.6.3.1-ghost-4.4.img recovery and flashed it by issuing "moto-fastboot flash recovery DevFAQ_twrp-2.6.3.1-ghost-4.4.img" command while in fastboot mode.

It worked out like a charm: it flashed and also offered to install SuperSU after 1st start so I rooted and was playing with phone for a while. The phone was on Wifi without SIM and I never customized system - rather installed few apps and played Asphalt. I turned it off and on few times and did a full backup with TWRP.

Then I left my phone on and unattended for 15 mins maybe and when I was back I discovered that it shows standard boot message "Warning Unlocked Recovery....etc" but after hanging a bit it does not show droid splashscreen and boot but turns black a shows "Warning Unlocked Recovery....etc" message again.

So I got this bootloop with no possibility to even power off the phone. By holding Power and Volume Down buttons for 10 seconds and releasing them I am able to get into fastboot mode. I tried "Normal Powerup", [B]"Factory"[/B], "Recovery" and "BP Tools" - all result in the same bootloop. "Barcodes" shows IMEI SV and PV info but it's of no help. I tried flashing philz_touch_6.19.3-xt1060.img recovery - still this bootloop.

When I tried relashing TWRP and booted into recovery it displayed a broken TWRP splashscreen like with artifacts but then went into bootloop again.

Now I have no idea what to do - I left phone hooked to USB in the fastboot mode (this way it's charging at least) - could you please suggest what would be the correct and most painless way out for me?

My idea now is to reflash stock recovery with the fastboot and I was looking around in a search for stock 4.2.2 XT1080 recovery but I failed to find any working links.

Also I wondered if I flash recovery in a correct way. I never issued "moto-fastboot erase recovery" command - I mean I tried it once but it showed "Erase Failed......" so I was just flashing it every time anew - not sure if this is correct, but this is the only option for me.

Many thanks in advance and any assitance is indeed much appreciated!

P.S. I attach how my fastboot screen looks like just in case.
[Droid Ultra General] kitcostantino:
Okay. Let's get ya back up and running. Idk what could have happened to make it soft brick like that. But its easy to fix. When you are in the bootloader (fastboot mode) volume down highlights, vol up selects. If you highlight recovery, press vol up and you don't get to recovery, recovery is bad for whatever reason. Honestly, I'd look around for a different recovery hashcode made the 2.6.3.1 that you should be using. I'll dig for a link in a moment. Reflash recovery (I presume the backup you made was in TWRP) and restore it if you can. [MENTION=3333955]NWKENT[/MENTION] 's links on his personal page are all gone, so I can't find the exact fxz you need at the moment, if we cannot recover you from where you're at and you )as I would) want to stay on 12.7.7 or 12.15.15 (same thing pretty much) worst case scenario, you may have to fxz newer firmware. I honestly am baffled at this bootloop, but it's probably something simple. Brb.

---------- Post added at 10:18 AM ---------- Previous post was at 09:56 AM ----------

https://docs.google.com/file/d/0B8Wgm9kaCVhFaTFnbEJUdzg3YTg/edit?pli=1

---------- Post added at 10:24 AM ---------- Previous post was at 10:18 AM ----------

http://xdaforums.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
[Droid Ultra General] TEPEM:
kitcostantino, many thanks, man - you are the only one who replied to me so far.

First let me start with some observations. As I said I left the phone hooked to the USB overnight but today in the noon I discovered that in fastboot it shows "Battery Low" so it was weird to me because previousy when on USB it was sayng "Battery: OK (Charging)" so I was under impression that it was charging all that time. I presumed that USB was not providing sufficient force of the electric current so I took original Motorola charging socket which is 1.1 A output and plugged the phone. What is the most weird thing it kept showing "Battery Low" and nothing about the fact it (?)was(?) charging. Phone stayed like that for a couple of hours when I decided to hook it back to USB - guess what: as soon as it got back on USB it started showing "Battery: OK (Charging)" again.

Now about this bootloop. Reflashing recoveries does not help. Here's the list of what I tried with no luck so far:

- openrecovery-twrp-2.8.4.0-obake.img

- philz_touch_6.19.3-xt1060.img

- twrp-2.6.3.1-ghost-4.4.img

- stock recovery (stock one taken from VZW-4.2.2-SU1-15-3-release-keys.xml.zip FW)

After all those runabouts with recoveries I caught myself thinking that it all looks like it's not a recovery which is "broken" - but rather a boot. I mean since it does not boot into the system that means that the recovery does not much matter in such a case, right?

So my thought right now is to take boot.img from VZW-4.2.2-SU1-15-3-release-keys.xml.zip stock FW (from here) and flash it in fasboot to see if that helps. What do you think?

You also shared a link to Blur_Version.12.7.7.obake-maxx_verizon.Verizon.en.US.zip FW (around 139 Mb) but I see big difference compared to the one I found (mentioned above) which is roughly 750 Mb - could you please explain what is the difference then between these two? I can say that the bigger one - VZW-4.2.2-SU1-15-3-release-keys.xml.zip is CFC - i.e. it has the XML file with extra lines to erase the cache, userdata, clogo, etc, where the 1FF does not.

I definitely need explanation whether each of those can be flashed with RSD or not and what would be the procedure - link to a guide would work perfectly. But again, I need to know if these 2 FWs can be flashed in the same way by RSD or by what if not. This is something I want to set a bit aside as a last resort.

As I already mentioned I want to try flashing boot.img first in order not to loose all apps and config - really not too much but still.

Many thanks for your assistance and help again. Will be waiting for your suggestion advise.
[Droid Ultra General] TEPEM:
kitcostantino, I have just tried flashing boot.img (from VZW-4.2.2-SU1-15-3-release-keys.xml.zip FW) - no results. It is the same bootloop.

So I presume I have the only option to falsh the whole firmware with RSD - I think I choose VZW-4.2.2-SU1-15-3-release-keys.xml.zip - could you please guide me in what regards driver installation?

- where do I get Drivers from?

- do I install Drivers 1st or RSD or it does not matter?

- do I install drivers when phone is hooked to USB (only fastboot mode in my case) or without phone connected?

I will gladly appreciate any help here because I have never flashed new android Motorolas with RSD before.

Thanks!
[Droid Ultra General] teerout:
tepem, you should be able to find everything you need from motorolas website. https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth

look at the right hand side to request factory image.