yashsingh1/xdaforums huggingface dataset:
[XDA Assist] prboy1969:
You can check the link below.

[TOOL] imgRePacker (LiveSuit's & PhoenixSuit's firmware images unpacker/packer)
[Nexus 7 (2013) Q&A] SHABBYLEA:
I don't know if this is the is the correct place to post this, but here goes...

I have noted in various nexus 7 forums that quite a few people can't flash a rooted Lollipop beacause for whatever reason they have no access to a PC.

I've posted how to get around this, but I know how difficult searching forums for specific information can be.

So, if enough people out there need a step by step guide, I will post it here...
[Nexus 7 (2013) Q&A] dilfatx:
Show me how
[Nexus 7 (2013) Q&A] hobby31:
I would like to know too...
[Nexus 7 (2013) Q&A] jrsndr:
Flashing the new bootloader is the problem for me....
[Nexus 7 (2013) Q&A] kernelsandirs:
Yeah we kinda have to wait for a recovery flashable bootloader 4.04 still
[Nexus 7 (2013) Q&A] timrock:
Same here, just need to be able to flash that bootloader and I'm good from there. Thanks for the effort.
[Nexus 7 (2013) Q&A] magiconthetire:
Would love a flashable zip as well...I have no PC access but have a bl unlocked n7
[Nexus 7 (2013) Q&A] TheLeapist:
Same for me. All I need is a flashable zip for the new bootloader.
[Nexus 7 (2013) Q&A] ANGEL4RIM:
Same here.
[Nexus 7 (2013) Q&A] kernelsandirs:
in order to create a flashable bootloader.zip we need to be able to extract the bootloader-flo-flo.4.04.img file all the img utilities I tried to unpack that file give a bunch or errors

can anyone see if they are able to unpack that file with imgtool or imgRePackerRK or something?
[Nexus 7 (2013) Q&A] PsychoMcSatan:
I assume this is where I should be if I'm looking to update my rooted N7, which has no working USB port (I charge on a QI charger).

Is this promising or am I stuck on KitKat?

Thanks!
[Nexus 7 (2013) Q&A] kernelsandirs:
Well you should be able to flash to Lollipop as soon as we have a recovery flashable bootloader.zip

Some seem to have flashed the latest ROM without the 4.04 bootloader but I am not sure they still have working root and some other issues.

I have tried to extract the files needed to make the flashable bootloader but am having trouble, so it could be the reason we don't see one yet.

Someone smarter than myself in these matters may have more insight. But so far I have not heard anything from anyone else that has attempted to make a flashable bootloader for 4.04
[Nexus 7 (2013) Q&A] kernelsandirs:
I saw several posts were people did not update to 4.04 and did not seem to have any trouble, so I decided to try myself, I put a copy of the pre-rooted rom in my downloads

I made a backup, did a factory reset, installed the rom, rebooted and, installed the titanium backup on their twitter feed, restored, and everything seems to working just fine.

I am not sure what the bootloader does affect in the end as far as the running OS goes(not sure why it would affect that), I will upgrade it, if I get a flashable one, but for now I seem to be running Lollipop ok.
[Nexus 7 (2013) Q&A] Duffmantp:
I am trying ImgRePackerRK and i am getting 'unknown header formant'

im in cmd.exe. i type: Imgerpackerrk.exe bootloader-flo-flo-04.04.img

I put everything in the same folder to make the typing the syntax faster. Is that the same error you are getting?

---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------

2014.11.13 22:59:27	imgRePackerRK (v. 1.04 windows)

2014.11.13 22:59:27	(c) RedScorpio, Moscow, 2013-2014

2014.11.13 22:59:27

2014.11.13 22:59:27	Command parameters: "/log" "bootloader-flo-flo-04.04.img"

2014.11.13 22:59:27

2014.11.13 22:59:27	Run parameters:

2014.11.13 22:59:27	log = 1

2014.11.13 22:59:27	debug = 0

2014.11.13 22:59:27	quiet = 0

2014.11.13 22:59:27	mono = 0

2014.11.13 22:59:27	md5 = 0

2014.11.13 22:59:27	rkcrc = 0

2014.11.13 22:59:27	rkaf = 0

2014.11.13 22:59:27	skip = 0

2014.11.13 22:59:27	2nd = 0

2014.11.13 22:59:27	cid = 0

2014.11.13 22:59:27	memsize = 134217728

2014.11.13 22:59:27

2014.11.13 22:59:27	==========================[ START ]==========================

2014.11.13 22:59:27

2014.11.13 22:59:27	--- Firmware unpacking ---

2014.11.13 22:59:27

2014.11.13 22:59:27	2-nd layer file unpacking

2014.11.13 22:59:27	RockChip bootloader image format detected

2014.11.13 22:59:27	"bootloader-flo-flo-04.04.img" (RockChip bootloader image) unpacking

2014.11.13 22:59:28	Image properties:

2014.11.13 22:59:28	Type	RockChip bootloader image (BOOT)

2014.11.13 22:59:28	Version	21.52

2014.11.13 22:59:28	Date	0.00.21

2014.11.13 22:59:28	Time	61:00:115

2014.11.13 22:59:28	ChipID	0x00316c62

2014.11.13 22:59:28	Code(?)	0x02000000

2014.11.13 22:59:28

2014.11.13 22:59:28	.ERROR.	Unknown header format

2014.11.13 22:59:28

2014.11.13 22:59:28	==========================[ STOP ]==========================

Here is the full description
[Nexus 7 (2013) Q&A] Q8-V08:
You can extract the factory image tar gunzip with https://play.google.com/store/apps/details?id=com.rarlab.rar&hl=en

it's alot easier then using windows tools.

Flashify allows you to flash boot and recovery images, I don't see why a extra option couldn't be added for flashing the bootloader also.

If you knew which block the bootloader was stored you could flash it with a terminal emulator also.

The only one I know is

dd if=system.img of=/dev/block/mmcblk0p22

root@flo:/ # cat /proc/partitions

major minor #blocks name

7 0 34335 loop0

179 0 15388672 mmcblk0

179 1 87536 mmcblk0p1

179 2 3072 mmcblk0p2

179 3 3072 mmcblk0p3

179 4 15000 mmcblk0p4

179 5 780 mmcblk0p5

179 6 780 mmcblk0p6

179 7 780 mmcblk0p7

179 8 3072 mmcblk0p8

179 9 1500 mmcblk0p9

179 10 1500 mmcblk0p10

179 11 2048 mmcblk0p11

179 12 5120 mmcblk0p12

179 13 512 mmcblk0p13

179 14 16384 mmcblk0p14

179 15 512 mmcblk0p15

179 16 1 mmcblk0p16

179 17 1500 mmcblk0p17

179 18 2048 mmcblk0p18

179 19 5120 mmcblk0p19

179 20 512 mmcblk0p20

179 21 512 mmcblk0p21

179 22 860160 mmcblk0p22

179 23 573440 mmcblk0p23

179 24 1024 mmcblk0p24

179 25 10240 mmcblk0p25

179 26 8 mmcblk0p26

179 27 8 mmcblk0p27

179 28 1 mmcblk0p28

179 29 32 mmcblk0p29

179 30 13029359 mmcblk0p30

254 0 34335 dm-0

root@flo:/ #
[Nexus 7 (2013) Q&A] PsychoMcSatan:
So it looks like we have the bootloader here: http://xdaforums.com/showpost.php?p=56737284&postcount=12

But I want to make sure I do things in the right order. I have no USB port on my rooted N7 (2013). So I thought I'd go ahead and flash the ROM via TWRP as people have had success with the old bootloader. After that I can flash the bootloader to be nice and up to date? Will that mean I lose root at that point? If so, how do I reroot over WIFI?

Thanks!
[Nexus 7 (2013) Q&A] kernelsandirs:
If you flash the rom from http://xdaforums.com/nexus-7-2013/development/rom-factory-stock-rooted-rom-lrx21p-t2938161 it is pre rooted i just downloaded it to my device, rebooted to twrp, made a backup, factory reset, install that rom and rebooted. Worked great. Also Eksasol posted the recovery flashable bootloader here

http://xdaforums.com/nexus-7-2013/general/flashable-factory-image-zips-android-5-t2939599/ get the bootloader one from the link. thanks [MENTION=2168379]eksasol[/MENTION]
[Nexus 7 (2013) Q&A] SHABBYLEA:
I've just discovered where my original post was moved to.

So if anyone still wants to know how to get lollipop without the latest bootloader, let me know.

I assume after a couple of weeks this has been solved, but if not...

Cheers...
[Nexus 7 (2013) Q&A] AnkeshReborn:
This was a great trouble for me back then,hell I didn't discovered your thread that time and I'd had to beg for a PC,I sold my PC some months ago!

Thanks @Q8-VO8 liked the trick!
[Verizon Samsung Galaxy S III] Nightfallxx:
how do I install this back to my phone properly? I am on CM11 and I have added back the apk but when I open the app it tells me this.

Caller Name ID is not yet activated. Please try again later.
[Verizon Samsung Galaxy S III] ShapesBlue:
Your referring to the caller ID name app from VZW?

From my CM11 S3
[Droid Ultra General] bluebloomers:
So with the second gen moto G and X starting to get lollipop, how much longer do you guys think untill we start seeing our soak tests?
[Droid Ultra General] jmaclean62:
Is the Verizon Moto X and G getting the update or just the gsm version? If the Verizon Moto X is getting it, then it shouldn't too much longer for us. maybe a few weeks I would guess.
[Droid Ultra General] bigv5150:
Nope just unlocked gsm versions. I'm thinking January if moto keeps with their quick updates like last year.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] pijes:
verizon probably needs some time to prepare the bloatwares
[Droid Ultra General] Johnny Wong:
Let's hope xposed will be compatible with ART by then. Who knows, maybe a Lollipop based AOSP ROM will be released before Verizon's. Either way, not in a big hurry since my phone is pretty much running all Lollipop Gapps. The only thing not updated is the dialer.
[Droid Ultra General] spiral777:
droid maxx will probably get the update in about a week or two...werent the 2013 droids the first to get 4.4.4? even before nexus if i remember right...

either way im really loving an improved battery and LTE on T-mobile on my droid maxx after the su5 23.3.24 update :)
[Droid Ultra General] doogald:
My guess is that the 2013 Droids won't see Lollipop until 2015. Motorola will want to update the 2014 Moto X, the 2014 Moto G, and the 2013 Moto X, maybe the 2013 Moto G and E, and Verizon will want to update the Turbo, before both get around to the Ultra/Maxx/Mini. The 2012 Droids (Razr M and Razr HD series) got a KitKat update in May. Hopefully the update will get to the 2013 Droids before next May, but I think we still have to wait for those other phones to be updated first.
[Droid Ultra General] hayze:
In depth review of Lollipop: http://arstechnica.com/gadgets/2014/11/android-5-0-lollipop-thoroughly-reviewed/
[Droid Ultra General] bwheelies:
Based on Nexus reviews(6) Lollipop has integrated Google Now with hot word detection so the Moto Assist app will be obsolete. It also means much quicker operation without the extra app handing off data to Google Now.
[Droid Ultra General] doogald:
At the expense of more battery drain. I think I'll stick with touchless controls/Moto Voice and its use of the low power processor. (The assist app announces text messages and voice calls while you're driving, so I think you mean Moto Voice...)
[Droid Ultra General] Crwolv:
well I don't know about your phone but my droid Maxx runs faster with a cyst it gets to Google faster and Google runs faster than going straight from Google yeah may be weird but it does
[Droid Ultra General] nicotheandroidguy:
Motorola says the update is ready just waiting for carrier approval. Hopefully this means they will soak test soon.
[Droid Ultra General] jaydotelloh:
Huh? Haven't seen this news yet. Do you have a source?
[Droid Ultra General] nicotheandroidguy:
Yeah it says pending partner (Verizon) support. https://motorola-global-portal.cust...iZHltTzNmOW0iLCJzZXNzaW9uSUQiOiJ5VU5uM2Y5bSJ9
[Droid Ultra General] s_u_n:
http://motorola-blog.blogspot.in/201...inkId=12303485

Moto Maxx now has a soak test for Lollipop. So, Turbo should be next and then we can get it on the Maxx.
[Droid Ultra General] jdawg334:
May not be so soon according to this. If I understand correctly that the Droid Ultra/Maxx has the same processor as the 2013 Moto X but someone correct me if I am wrong on that.

Tweet link

https://twitter.com/MotorolaSupport/status/564881795767095298

Story

http://www.androidpit.com/moto-e-and-moto-maxx-android-lollipop-update-incoming
[Droid Ultra General] fix-this!:
Id sure like to know where the lollipop update is for the droid maxx, mini and ultra.
[Droid Ultra General] romma1:
Or "If" it is... ;) Seriously, at this point I am hoping that they do make us wait till 5.1.. With the reports of fixes and improvements, it will be worth it...

Here is my theory why: Our phones are reaching the outer edges of carrier,OEM and Google support. If we get 5.0, 5.01 or 5.02,,, we may not see another update beyond that. We could be stuck with whatever they give us for good. I am checking like everyone else for the update, but aside from my own personal desire for instant gratification, I believe we may be better off to not get it with a shot at 5.1...

This is very difficult for me since this is the first Android device I have had with no unlocked bootloader or root. But the phone still rocks pretty hard.
[Droid Ultra General] doogald:
Seriously, it's not coming until after the Droid Turbo, and almost certainly after the 2013 moto x on Verizon. Neither phone is even in a soak test right now.

Last year the 2012 Droids got KitKat in may. I'd say that's the earliest the Maxx gets Lollipop this year.
[Droid Ultra General] fix-this!:
not positive we will even get it tbh. glad this isn't my personal device, just a work phone.
[Droid Ultra General] doogald:
Moto has made it clear that the 2013 Droid are getting lollipop. No timing promised - they never do - but, like I said, there are newer phones still in the pipeline without it.
[Droid Ultra General] pijes:
1. We will definitely get lollipop after Turbo

2. It was reported that the X8 custom setup in 2013 models (moto x, mini, ultra, maxx) is causing some issues with lollipop

1+2 = probably not getting it in the first quarter. I have no issues with KitKat so I can wait.
[Droid Ultra General] doogald:
It looks like the original Moto X is getting lollipop soon. See https://plus.google.com/110587026141482969464/posts/NDYt15d7CxD comment number 4.
[Droid Ultra General] bigv5150:
I don't what your reading but nowhere does it say first gen x is getting 5.0 anytime soon. That is a thread for at&t motox 2nd gen. I doubt any 2013 phones get lollipop before turbo.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] doogald:
Like I said, read the fourth comment in that thread, also from Luciano Carvalho of Motorola.

"1st gen Moto X is progressing. You should see news about it in the near future."

I agree that it shouldn't beat the turbo, but it could. Some of last year's Moto G beat the turbo.

Obviously no promises but strongly hinting the Moto X, with the same hardware as the 2013 Droids, is getting closer.
[Droid Ultra General] Kittimasak:
Some Moto X are getting the updates, so I would imagine our phones getting it soon.
[Droid Ultra General] romma1:
Hoping so, I was hoping to wait a while and get 5.1... If we get 5.0.2, I doubt we'll ever see the 5.1
[Droid Ultra General] bigv5150:
5.1 is mainly a bug fix so pushing it to us would be easy. 5.0 working with our chip set was the issue. That has been resolved so I would imagine we will get updates until 5.0 is stable.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] Topsnake:
Man I'm glad I have the nexus now [MENTION=3462404]bigv5150[/MENTION]
[Droid Ultra General] bigv5150:
I was wondering why I haven't heard from you lately. I was going to get the turbo but gave it to my wife. I'm waiting for the 2015 droids to see what's new. To be honest after messing with the turbo it was not even close to enough of an upgrade to lose unlocked BL and root on my maxx.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] Topsnake:
Nexus 6 is your answer. Its so nice just flashing direct from google. Unlocked BL of course.
[Droid Ultra General] bigv5150:
Its just to damn big if it was 5.5 or below I would have been all over it. I am excited to see what is coming down the pike this year.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] kimical:
Lollipop update as began to rolle out for droid turbo... Very soon de will get it four our devices. Some guys that are members of motorola network feedback have received a soak update of lollipop for droid ultra
[Droid Ultra General] romma1:
I cannot find anything about a current soak test for the Ultra, Droid Maxx or Mini.. Where are you seeing this info kimical?
[Droid Ultra General] kimical:
ytb.com/watch?v=9PgQOAP4Ubs
[Droid Ultra General] doogald:
Look at 0:26 in, at the "About phone" screen. The phone says it's a Moto Maxx, hardware sku is XT1225 (which is the Moto Maxx - the Turbo is XT1224). The Moto Maxx has had Lollipop for a while.

When a soak test invite goes out for the Turbo, it'll be all over places like Android Central and Droid Life within minutes. There is no soak test yet.
[Droid Ultra General] romma1:
Yup, and the Moto Maxx and Droid Maxx are two different animals..
[Droid Ultra General] romma1:
In case anyone wants the latest info, here is David Schuster's (Motorola Mobility)reply to my asking about the 2013 Droid line up with regards to Lollipop: David Schuster

12:10 PM+

https://plus.google.com/+DavidSchuster/posts

Scott.... with respect the 2013 DROID Ultra family of devices... we are running into some "partner support" issues for the Lollipop upgrade. We are actively trying to work through these issue and I will update you guys as soon as I have more information. Sorry about not having clearer direction for you but my hands are a little tied at the moment until we work through the issue with our partner.﻿

---------- Post added at 03:22 PM ---------- Previous post was at 03:21 PM ----------

So Verizon is the culprit who is once again "humping us"...
[Droid Ultra General] s_u_n:
Thanks for sharing.

There is not much activity in the Droid Ultra sub-forum on XDA or other sites.

The special chipset used by Motorola has deterred the developers to work on this and the Moto X, I suppose.

There are some insider news (unconfirmed, of course), that we might get 5.1 directly instead of 5.0, since 5.1 brings in VoLTE (or something similar) out of the box and that somehow conflicts with the VoLTE that Verizon was so fond of bringing into 4.4.4 earlier.

So, perhaps that is also where the tussle is between VZ and Moto.

I have a feeling that this 5.1 might be the last that we could see officially from VZ for this phone. But as an owner I hope I am wrong.
[Droid Ultra General] romma1:
At this point I will be ecstatic to see 5.1 with zero expectation of anything beyond. We may get a lower version of LP, or with all the silence from Verizon we may get nothing beyond where we are now. Verizon did this to me with my Incredible 2, and they have a lengthy track record of this pattern with other phones. It is what it is.
[Droid Ultra General] bigv5150:
Well it has been said the moto x 2013 is getting 5.1. So I see no reason why we wouldn't they are the same phone. Also I could careless if we get an update beyond 5.1. This phone will be gone come November. I skipped the turbo because not enough of an upgrade from my maxx and can't unlock the boot loader. Got the turbo for my wife huge upgrade from her RAZR m. I hope the next droid has a de like the maxx did.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] doogald:
Well, I would hope that Verizon is putting them off until they get the Turbo updated. I can't believe that they are going to let the Maxx get updated while the newer phone sits on KitKat. Honestly, the Maxx is fine on KitKat. I have a hard time believing that Lollipop will bring much better performance or functionality. Some things look nice - better option toggles in the notification shade, some bug fixes, but the Maxx on KitKat isn't holding me back at all. I'd love to get it, but can live without it.

Hopefully the phone gets the update, though, before my upgrade date in late August.
[Droid Ultra General] bigv5150:
Well if you remember correctly the RAZR line was updated to kk before the maxx and ultra. I don't see that happening here but you never know.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] romma1:
Not to sound too pessimistic (hopefully), I just wouldn't put it past Big Red to leave us stuck on KK. I figured once they started soaking the Moto X 2013, there would be some news for us seeing how we have the same type of modified hardware. Again, I hope that I am wrong.

Is there anyone good at organizing protests to carriers for a petition if it will help nudge VZW?
[Droid Ultra General] doogald:
Not quite. The Ultra/Maxx/Mini got 4.4 in December 2013/January 2014. The Razr HD/Razr Maxx HD/Razr M got 4.4.2 in May 2014. The Ultra/Maxx/Mini then got an update to 4.4.4 in July 2014. So, the Ultra line had KitKat before the 2012 Droids, but it did have some bugs and it was a PITA that it took Verizon so long to update it past 4.4.
[Droid Ultra General] bigv5150:
My bad thought they got it first. I think there was talk about them getting it before us but it was so long ago can't remember. That seems to be happening more and more to me. Lol

sent from "my kungfu is stronger then yours" XT1080

---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------

Well if they do upgrade the moto x and not us if you have an unlocked boot loader I believe we will be able to finagle it to work on the maxx. Topsnake did it with kk and I ran the moto x build on my maxx.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] bankai_droid:
Just check Motorola's upgrade page. Still no news and haven't seen anyone in the US get the soak yet either.
[Droid Ultra General] fix-this!:
im thinking the s4 pro is a problematic cpu with lollipop and moto cannot fix it for some reason. not sure why as the moto e and g have it. im almost positive we will not get 5.0 on this device. whether its motos fault or verizon im glad this mini isn't my personal device.
[Droid Ultra General] bigv5150:
They have stated the chip set is the issue. Well I didn't pick the chip set moto did and they need to make good on their promise to upgrade this phone. Its not our fault they can't make it work.

sent from "my kungfu is stronger then yours" XT1080
[Droid Ultra General] doogald:
They've already posted that they have a 5.1 build going for the 2013 Moto X.

See this post: https://plus.google.com/+DavidSchuster/posts/cV4vDyyMmw2

Also, from the comments (toward the bottom):

"Partner support" = Verizon. Motorola is working on it, it looks like Verizon is holding them up for some reason, we will get it, who knows when - but it's coming.

If you want a device that gets updates fast from now on, DON'T BUY A DROID.
[Droid Ultra General] s_u_n:
Qualcomm, Verizon and Motorola - they all need to sort this out together. Sometimes the priorities may not match.
[Droid Ultra General] frank9525:
Droid Ultra xt1018 lollipop

someone can tell me about cm12.1 for ultra droid or wait the update via OTA
[Droid Ultra General] 1806:
CM12.1 works FINE, use TWRP2.8.4.0 and CM12.1obake
[Droid Ultra General] MArtyChubbs:
Moto X is getting 5.1 in a few weeks and we'll get it shortly after if not before....
[Droid Ultra General] doogald:
I don't think there is even an infinitesimal chance that the Droid Maxx gets Lollipop before the 2013 Moto X. And it's not getting it before the Droid Turbo, either. It's going to be at least a couple of months at best, I think - probably longer.
[Droid Ultra General] MArtyChubbs:
Hope not... The phones are sooo similar
[Droid Ultra General] Jaocagomez:
if verizons moto x gets it i dont see no reason to droid maxx to not get it too.
[Droid Ultra General] fix-this!:
I dont think the ultra and mini will get lollipop at all.
[Droid Ultra General] kcipopnevets:
Don't be so negative! Motorola has to support us. We're in the queue. They've really changed from their Droid X2 and Atrix days.
[Droid Ultra General] ratman6161:
Motorola's update site says they will "pending partner support" just like the Maxx.
[Droid Ultra General] morphius2036:
Just got my survey for another Moro Verizon SOAK...not sure if any Lollipop is involved but we will see.