yashsingh1/xdaforums huggingface dataset:
[Xoom General] jadkar:
So a little more experimenting has revealed some more of the obvious....

- I tried to RSD flash HLK75D right after the Everest 1.35 bootloader and it wouldn't even finish. It crashed whilst trying to program the LTE module. This must mean the new bootloader is required for starting up the hardware upon boot and since I obviously didn't have that firmware the RSD flash died.

-This also explains why we can use Everest 1.35 bootloader and naturally OTA to v1.45 along the way with all the normal OTA build upgrades but CANNOT use the radio hardware. The bootloader installed is not communicating with the new gear. The new / modified radio kit needs to have bootloader v1.50 to work.

- The real mystery right now is why when we flash up through the OTA builds and then flash HLK75D the machine boots up just fine ONCE. The only theory I have is what I have been saying and that's the android OS upon first boot writes something to the 1.45 bootloader and it corrupts it so that subsequent boots fail and we get stuck in the Moto abyss :eek:
[Xoom General] dethrok:
Supposedly, I'm going to be having an "expert" call me soon. We'll see how much this expert knows.
[Xoom General] jadkar:
Hopefully you can get the bootloader ;) If the dude doesn't believe that v1.50 exists point him to that post with the screen shots!!

---------- Post added at 07:59 PM ---------- Previous post was at 07:48 PM ----------

Please do me a favor, grab yourself RSD lite 5.4.4 and hook your xoom up via USB. Boot into RSD support and start up RSD lite. on your PC you'll see your device connected in the grid. click on it and the left hand window will populate with your device's information.

Can you please tell me what version of bootloader you have? If your radios don't work I want to make sure its 1045 (1.45) or 1035 (1.35)

Thanks!!
[Xoom General] REHolt218:
I just got a call from an "Expert" from Motorola. He would not even confirm there was a problem. He said the update has not been out long enough to tell that. I assured him that even if he was not aware of it THERE IS A PROBLEM, as evidenced by several dozen people on varios forums. He asked for evidence and I pointed him to this thread. I also explained the results of testing on this thread and why we think it is the 1.5 boot loader.

After a quick look here he changed his solution from me sending my xoom for repair, to "I'll call you back after doing some more research.

Here's to Motorola providing a solution;)
[Xoom General] zone23:
Here is the experiment for Motorola:

1. Download and flash Build HRI66 both files

2. Download and flash Build HLK75D

http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard

Did it even flash? Now does it boot more than once? If so good, does 3G/4G work? If everything worked I would be shocked.

Now if it didn't how would you expect us to get from point A to point B?

We think the problem is 1.35-everest.reflash downgraded the bootloader. Even if you take the updates from HRI66 it only updates your bootloader to 1.45. From what we have seen you need 1.50 with HLK75D in order for it to work. This could be confirmed by checking into what they are flashing when they upgrade Xoom to 4G.

With all that said it is our fault that the device is broken but if we are going to develop for your device we need a way to get out of a jamb. Remembering that its this development that we do that makes this device different from the Blackberry Play Book, and HP TouchPAD. I don't think that Motorola wants their devices classified with those.
[Xoom General] hammer4203:
Yeah some experts! I stayed on the phone for 3hrs today. They said the xoom should update past 3.2 if we downgraded. The idiots did not address the fact that if the sofyware on the xoom at thr base level changed it won't see the radio. I was told to start buging the crap out of them at motodev. The xoom is suppose to update from 3.0 to 3.2.2 or whatever version it's suppose to be. So the devs said they did something and didn't. They lied to their own bosses about it. They didn't think anyone would want to play with the new 4g. What a crock!
[Xoom General] uberbyte:
I have been following this thread since the beginning and haven't posted until now. I have two xooms that aren't working and one that is. So I'm sure are ton more ppl out there that doing the same. I'm sure there is some statical value like for every one person that post another 10+ are just following and trying every suggestion.
[Xoom General] sakenfenc:
I agree

spent one hour on the phone with motorola and verizon in conference call only to be told to ship my xoom back for repair I say BS..

asked for the the update multiple times no go .... the out sourced customer support just kills me...

May be Google would fix this mess after they take over..

Keep up the good work ..:)
[Xoom General] despich:
Yes its possible, I was in exactly your shoes 2 days ago. Look at my earlier posts in this forum for how to fix. Basically Don't use the 75d sbf to fix. Use the axemachine 75c boot.img and system.img them put on the 75d patch.

I was on tachi kernel and now I am on stock kernel with 75d. Just don't put on anything earlier with rsd or you will jack your bootloader and your device like so many others in this forum have.
[Xoom General] REHolt218:
I never used RSD and still have the same problem. I tried to fix it with Axemachine 75cbut only managed to get wifi without 3g/4g.

At this point I would stay with what you've got until this settles out some. Hopefully within the next few days we will get the update we need.
[Xoom General] jadkar:
So far this may be the best lead we have so far. Did they give you at case# so you at least have something to follow up on if they don't call you back??
[Xoom General] Brenardo:
I really don't understand why we can get HLK75D to boot up and run (with 3G/4G) without the updated bootloader. What happens after the reboot that causes the hang up!
[Xoom General] REHolt218:
I have HLK75D running on my Xoom right now, I just don't have 3g/4g. HLK75D seems to be very stable and runs well. I have even added Tachi 2.1 and am overclocking to 1.6.
[Xoom General] Brenardo:
................
[Xoom General] jadkar:
I do too..... just no radio. The bootloader v1.50 must turn on / initialize the radio hardware first before it starts the OS. I'm currently running the Everest 1.35 bootloader. I want the damn v1.50 so I can get my wireless working (since I'm still paying for it)

Certain apps are not working though, the new icon for the market says it's not installed. Also, my regular marketplace app keeps FC'ing on me.
[Xoom General] zone23:
Its too bad this isn't an adult forum because I got a lot of F bombs to drop.

As long as it is taking for them to even realize we have an issue I could have sent it back. Here is an idea is it possible for you to post the number you are calling? Posting the number will get a lot of members and lurkers to start calling Motorola.

Here's my question:

Is it really that hard to get us a flashable bootloader? Those asses will spend more time dicking around just make the damn thing and we can all get on with our lives.
[Xoom General] craigcrawford1988:
Edit: Never mind.
[Xoom General] Brenardo:
This is exactly right! I am very unimpressed with Moto's bull right now. The fact my radios are not working is only compounded by the fact that while in the upgrade process the front glass panel on the underside now has a fingerprint on it...

Motor is flirting with disaster... I am pretty sure many people will no longer deal with Moto due to the excessive delay for the upgrade and now this ****... It is obvious the ball has been dropped, and for me I am not sure they will ever be able to pick it back u

The only thing that can save Moto now is Googorla
[Xoom General] Brenardo:
This is funny. : )
[Xoom General] hammer4203:
Ok just say all I want is the bootloader. It's unlocked. How the crap do I pull that? It has to be the portion that has the logo, rsd, fastboot. The rest is boot, recovery system, etc. It's like the bios in your pc. I thought we were past that kind of loading of a system. I can pull everything else, but that.
[Xoom General] Brenardo:
I was messing around and wiped the logo.bin with

fastboot erase logo.bin

I saw some text while reflashing the 75D build I am not sure what all was included but it seemed pretty informative
[Xoom General] jadkar:
I'm starting to think the bootloader is encrypted so that once the bin file is turned into an SBF and flashed that's it. We can't pull the code off. The boot.img that people have been pulling is not the bootloader.
[Xoom General] zone23:
Exactly the bootloader and the boot.img are not the same thing. Its been posted that the bootloader is on two partitions one is encrypted the other isn't. I believe what happens is when you flash the bootloader the devices runs a program that loads it on the device. It needs to be done exactly right or we all end up with unfixable (without a special cable) bricks.

So far we have two options:

1 send your device back and have them fix it

2 wait..
[Xoom General] jadkar:
3. .... Use this as an excuse to buy Glaxay Tab 10.1
[Xoom General] zone23:
No doubt because after all this I will not buy another Motorola product of any kind nor will I recommend one.
[Xoom General] hammer4203:
It's not encrypted. It's unlocked when you oem unlock. Its just not in the boot img anymore. Tgat's why we are having so much if an issue. Just like the bios it will boot without the img files to rsd. It is that portion that is carrying the baseband. I would say that a fresh xoom just built has nothing on it. Use the special cable to load the rsd with baseband and now you can create any img you want so long as you identify the right info in that section. If you change it it won't boot past the rsd mode. So that partition is writable, but only in one way and they left that out of the downloaded sbf. So if we did not downgrade we could use the sbf to return to stock, just not change that bootloader. I know there is a way to get that off, but I can't find anything but the stuff from 2009 back for phones. Moto just seems to not want to share that file now. Or they just don't care. Then again they may just not be clear on the problem yet.
[Xoom General] dethrok:
Well, for one, I am glad I just got my Xoom back up and running with full connectivity. I didn't want to have to find a way to put my data plan on hold until Moto releases a fix, that is, if they do.

I just have to be careful to not mistakenly turn it off or reboot, or I'll have to flash everything all over again. :(
[Xoom General] zone23:
Actually you just call them and say I want to suspend data without billing. The key is "without billing" otherwise they will just turn off your data and keep charging. Does that sound stupid to anyone else?
[Xoom General] jadkar:
nah, Verizon is synonymous with stupidity so this sounds just about right :)
[Xoom General] zone23:
On a device that has nothing but data, if you suspend it what are they billing you for? Thats what I told the lady anyway.
[Xoom General] dethrok:
Someone over on the Moto forum posted a copy of, what they believe to be, their v1.50 bootloader.

https://supportforums.motorola.com/message/490360#490360
[Xoom General] tonesto7:
That files appears to be similar in size and in contents...

Could someone describe to me what DD' in recovery means?

---------- Post added at 02:59 PM ---------- Previous post was at 02:56 PM ----------

Hmm... I ran a "fc bootloader.bin hlk75D-ebb"

it returned no differences encountered... So it appears to be the 1.45BL
[Xoom General] jadkar:
HHMMM.... well he said when he goes home he will check his BL as he wasn't sure of the version he had.

Here's the thing though, I have no idea how he (kcrudup) pulled that. I'm not versed in the process / commands. However if it was super easy for him to do it why don't we just ask Hatrix?? He has the 1.50 BL on his device??
[Xoom General] dethrok:
Also, Matt finally replied.

Awesome generic response, but maybe now someone with some knowledge will see it.
[Xoom General] Brenardo:
Did I mention I don't really care for Matt?
[Xoom General] dethrok:
I noticed after reading the thread about Moto not posting .IMG files anymore.
[Xoom General] hammer4203:
I sent matt a pm ask him to talk to the dev dept because they have no way to be contacted listed. That's what moto asked me to do. If it is easy to pull the 1.5, I can pull it. I just can't find the instructions to do it.
[Xoom General] zone23:
Well this certainly doesn't hurt the more people we get involved the more likely we are to achieve our primary goal.
[Xoom General] howlinwolf:
Hey as an update to the Motorola Support forum threads; it seems that Matt the moderator has finally looked at the posts. As of right now all he is saying is that they are looking into it and going to try and straighten things out. I hope so...
[Xoom General] REHolt218:
I finally got a call back from Motorola support. The guy talked like he had a mouthfull of rocks. I could barely understand him. Basically from what I could figure out the response was "you can send your xoom in to us for repair OR you can go to developers.Motorola.com and download the system files and load it yourself". When I asked him if they had posted the correct files he's said "I don't know you'll have to ask the developers ".

I'm not sure how any of that was supposed to be helpful. Especially since there is no contact information on the developers site. I hope someone else has better luck than me.
[Xoom General] hammer4203:
Matt finally understands what is going on. He didn't know people were downgrading to the 3.0. He has passed the info on to the dev dept. If you didn't downgrade then the sbf will unroot you back to stock after the lte radio was put in. They didn't know people would try that. That's funny. But he said they are working on it. This is what happens when you put in an intersection and leave out the stop signs.
[Xoom General] jadkar:
Yeah, So I spoke to him via email and I recieved the same response. I explained to him what I did. However I said others may have done something similar. I actually don't know how everyone else ended up in the same boat so I didn't want to assume too much.

For me, basically when I got the machine back from LTE upgrade I needed some applications and such that I was developing for a customer so I thought .... real easy ... just apply some backup .imgs I have from before the upgrade. This put back the last build before HLK75D which is obviously not compatible with BL 1.5. I didn't know what happened and sat for a couple days in limbo. At this point if I had the Moto HLK75D image I would have just put that back but remember Moto didn't get us the image until October 17th. So as I was stuck and I decided to flash the Everest 1.35 & HRI39. THIS STEP IS WHAT SCREWED ME. We all now know once we downgrade we are stuck here :( In "no radio pre-HLK75D land" :eek:

Fact is none of us would have done this if we knew the BL was modified. This seems like common knowledge for Moto engineers but for me at least I had no idea the machine was going from MZ600 to MZ602 with a new bootloader. It would have been nice for a piece of information to have been included in the packaging that said *** Do not load any images intended for a 3G / WiFi device onto your LTE XOOM as they are not compatible**

I just hope they will get us the bootloader. In all honesty I'm worried they will tell us "no dice" as its not their problem we messed with the BL. They supply us build images but I don't think they ever intend for people to be flashing the BLs. This seems very short sighted but still it may be their policy. Let's hope they realize that not supplying the bootloader in the long run may hurt them rather do any good. I know for myself if my client can't be sure that this Xoom can be brought back easily from any condition then they are not going to move forward and give this device with custom applications loaded to a bunch of traders :( They want something that can be completely repairable onsite, they don't care what version BL is on it.
[Xoom General] Brenardo:
I think that the bootloader engineers get hard ons because they have figured out how to really lock the users out. I am also worried that they may tell us to chuck rocks...

If Moto does not help us out here.

I will campaign my ass off to everyone possible not to buy Moto products...
[Xoom General] zone23:
Honestly I dont know how it all got started and when I down graded my bootloader, I just don't remember. Regardless that is were we are. I never blamed Moto for that it was our own faults. Just asking for a little help is all.
[Xoom General] REHolt218:
Sorry I missed this earlier. I did confirm that I am on bootloader version 1.45.

---------- Post added at 08:24 AM ---------- Previous post was at 08:19 AM ----------

i had a though; since our main problem seems to be that bootloader version 1.5 apparently turns on the radio and we are all missing ver 1.5, would it not be possible for one one the smart guy developers to write a utility that would turn them on?:confused:

Just a thought:D
[Xoom General] hammer4203:
If someone new how to rip it off the xoom I am still on 1.5. I never downgraded. How do I get it off? I can get the boot, system, recovery, data, & cache images. All we need is the part that boots the xoom before the boot image. They use to rip the bootloader from the phones. How?
[Xoom General] kurttrail:
The Xoom was sold as unlockable, but it seems this bootloader is still lock from us, and if Motorola doesn't provide access to our bootloaders, they will prove that they sold us a tablet that cannot be completely unlocked for those of us who got the LTE card we were also promised at the time of sale.

I kinda hope they don't provide the bootloader because I'd love to sue Motorola with such a slam-dunk of a case.
[Xoom General] hammer4203:
Can I read the data for that baseband and write it by hand? Then pack it into an sbf?
[Xoom General] Brenardo:
I don't believe it is locked... I believe it is unavailable... this lawsuit is far from "slam dunk"...
[Xoom General] zone23:
I got no interest in a lawsuit I just want my Xoom fixed. Thats all i'm gonna say about that.

Also as stated above the device is not locked if it was I would not have been able to screw it up.
[Xoom General] hammer4203:
At least for now you can flash rhe sbf and use your xoom as long as you leave it turned on. When I get off work I'm going to see if I can get around and copy the dev folder with the contents. Maybe we can paste it in!
[Xoom General] Brenardo:
Just to state the obvious....

This Sucks Ass... damn
[Xoom General] zone23:
Sorry thats not going to help.
[Xoom General] sakenfenc:
Ck

The HLK75D download is still available at the motodev site.. it seems that this Matt.

guy has no pull, although he suggested that he would pull it. we need a better contact!!!!
[Xoom General] Brenardo:
I don't think anything is wrong with the SBF as long as you have the 1.5 bootloader.
[Xoom General] zone23:
Correct it is just those of us who screwed up our bootloader.
[Xoom General] sakenfenc:
I agree

If downgrading is not recommended then it should have been mentioned by Motorola

rather than encouraged by the instructions on the Motodev site .

They provided theses files so one can lock and return the Xoom to stock.

I believe they will include a bootloader in the SBF now that they know it is needed to rebuild back to stock.
[Xoom General] jadkar:
Guys - I have faith that Motorola will do the right thing for us but unfortunately these things take some time.

I think we collectively need to stop with the "lawsuit" comments as well as publically speaking out against Matt. So far this is the only guy who even IM'd me. I think Matt will do all that he can within his power. In general insults and empty threats are no way to diplomatically get what we desire.

If we want to be constructive we can list the things Motorola did that didn't help us make the correct decisions with our Xooms when we received them back. For one, I mentioned earlier there should have been an "Important! Read this!" message inside our box warning us that the version of our tablet has changed to MZ602 and that earlier software will not be compatible. without some education regarding this they should have expected the outcome they are seeing now.

In any event we have three options I see right now.

- hold tight and wait for Motorolato address this

- enlist somebody to try and pull down the actual v1.50 bootloader from a working MZ602 and get this turned into a flash-able SBF file. (May not be possible)

- send it into Motorola to get re-flashed. (My client will not accept this solution and will no doubt go with another vendor).

- John
[Xoom General] zone23:
im gonna just flash my rom suspend my services and wait. Motorola will help use out eventually.
[Xoom General] hammer4203:
Or send it in. I mean turn around time seems to be really quick. But hopefully Monday it will be fixed.
[Xoom General] kurttrail:
You have faith in Motorola?

7 months to install a friggin' mini-pcie card.

Motorola's changes the type of restore image, for 4g, that requires a leaked program to use, then they gave the wrong instructions on how to flash this image, and they didn't even take the time to post the MD5 sum!

Oh, not to mention that the restore image they provided wasn't a complete image to begin with!

Are you really buying the BS that they never thought that the upgraded 4g Xooms would need a complete restore image? If so, I got some land in Florida you might be interested in.

Luckily for me, I don't deal in faith when it comes to businesses. I left mine stock and waited to hear what problems arose first.

You do realize that your Xoom is screwed up right now, because you trusted Motorola's restore image, right?

Sent from my Bolt
[Xoom General] hammer4203:
You could have left it locked. You could have not rooted. Maybe not put an untested kernel on it. Moto will post the imgs, just get some coffee and relax already. I almost downgraded, but I saw the post that said they lost their radio. That was before this sbf file was up.
[Xoom General] REHolt218:
Problem is that mine came back from the factory upgrade BROKEN! It would not even boot. When I finally did get it to boot the wifi didn't work. I didn't put an "untested kernel" on it. I used the ota update that Motorola/Google pushed to my Xoom expecting that it should fix my problem. What I got was working wifi but no 3g/4g.

Of course that is better than only having 3g/4g and no wifi since I only have a 1Gig plan, but what I expected to get was a device that works like it is suppooaed to.
[Xoom General] i_am_the_one:
If yours came back broken, why didn't you contact moto and let them fix it?
[Xoom General] kurttrail:
How can you be sure they'll provide the images?

Most of the people having problems with this sbf have clearly unlocked their Xoom and voided their warranty, and flashed images not intended for their model of Xoom. And the sbf works for those of us that haven't flashed an image not intended for the MZ602 model of Xoom.

And Matt is quite notorious for saying, "I'll look into this, and get back to you," and never getting back with an answer or solution.

Good luck, I hope it works out for all, but remember you're dealing with a company willing to lie and blame their partners for locked bootloaders, like Verizon, when Verizon has tons of phones from other manufacturers that are unlockable.

Sent from my Bolt
[Xoom General] stevefxp:
All,

Not sure what I can do to help but I have a rooted Xoom with the 1.5 bootloader. All I did was root it when I got it back from Moto with the LTE upgrade. Is there anything you would like me to try?

Steve
[Xoom General] kurttrail:
One more thing, ever wonder why Motorola didn't give a complete image?

Yeah, incompetence is one explanation, but there is so much incompetence surrounding this that it can hardly be coincidental.

Like laptop manufacturers locking wwan slots to only work with certain wwan cards via the BIOS, I suspect that this is Motorola's way of locking the mini-pcie slot to only work with their approved LTE radio card. I suspect that this is an undocumented hardware lock.

Sent from my Bolt