yashsingh1/xdaforums huggingface dataset:
[Xoom General] jadkar:
That didn't work for me..... If you go and read all my posts on my original thread (don't do it ...very painful) You'll see I've been fubar for a long while now. I've been waiting for the fubar party to catch up to me :) I knew once a bunch of people suffered from my fate a fix would come about!!
[Xoom General] zone23:
Are you trying that with the new bootloader or the older one because so far only the new flash works with the new bootloader (for me anyway and only boots once). All the older images need the old bootloader (in my experience).
[Xoom General] Brenardo:
O SHINap

I got it working! Rolling Hat's walk thru. The problem for me was that I did not have the current drivers installed.... installed from motodev restarted PC and boomyow! Followed steps and I now have 3G.
[Xoom General] zone23:
Can you reboot too?
[Xoom General] hatxtrick:
Zone> not quite sure that dog will hunt.... If I go by you reasoning then I would be stuck in the same boat right now.

Background info for my device for comparison:

1: Pre ordered device via VZW 2 weeks before release & received on launch date.

2: Rooted early on, to be able to use Cisco SSL VPN hack, but found issues with certian apps, went back to stock (for awhile)

3: Over clocked w/ Tiamat 1.x, that didn't last long

4: Went back to stock (166 at the time)

5: Have been locked & stock up through the last major ver. updates.

Things that might be different in our respective environments:

Machine OS | 32/64bit: I'm running on both my boxes Win 7 pro 64 bit

Moto drivers: Just checked both machines are using 5.2.0

Xoom: std config , do not have a SD card inserted

Cheers,

Hat
[Xoom General] zone23:
Cool well it would appear in reading you post that I'm not waiting nearly long enough for it to boot up. I hope your right, trying it now.
[Xoom General] csstamatin:
thx man but it still wont see my device. have tried it in all modes, and nothin. any more hints? thx
[Xoom General] jadkar:
OK I tried Hats fix...... gotta say I got much further than normal but still stuck at Moto screen. I'm 100% certain my issues with being stuck at Moto isn't due to bad block / data during the SBF flash... I tried it twice.

Zone23 - My bootloader is v0x001045, at least that's what RSD is reporting.

I will try the earlier method of flashing the old 139 image first. I agree with Hat that you shouldn't have to go "back to go forward" but maybe there is something with the version of Bootloader as suggested???..... I'm really not sure ...but I'm stuck.

I'll report back
[Xoom General] hatxtrick:
good luck.. Let me know what happens, I can flatten my device and try to reproduce what your seeing, if need be......

Cheers,

Hat
[Xoom General] zone23:
Didn't work gave something like

linux error 0x0004 and went into RDS mode

flash boot.img from HRI39 it reboots and tries to continue.
[Xoom General] Brenardo:
Hmmmm well I am now stuck at dual core screen as well upon trying a reboot

Time to try again.
[Xoom General] jadkar:
She's back!!

Flashing the Everest 1.35 bootloader SBF and then the I39 SBF build brought her back?? Not sure why. I had the newer bootloader on the device already but it wasn't reacting good to the HLK75D build???? Maybe my bootloader was corupted somehow and I had to use the everest 1.35 bootloader first??

So tell me... by flashing the HLK75D SBF ....shouldn't that have repaired the bootloader anyway.... it seems like maybe not, but then again I'm not sure what is actually in that build. Is it possible it doesn't touch the bootloader? Maybe this is why for the I39 build someone made the everst bootloader SBF.

Do we have a new 1.45 bootloader by itself in an SBF??

Anyway, I'll let this thing upgrade to the new bootloader OTA and then try the HLK75D SBF when the OTA update completes.
[Xoom General] hatxtrick:
csstamatin > check & update your USB drivers, then reboot your box to complete the driver install....

you might want to also check or change to a different USB port.

Cheers,

Hat
[Xoom General] Brenardo:
Hat had you trie d to reboot?
[Xoom General] hatxtrick:
Cool, glad to see you device is back in the world of the living!!!!

The bootloader is a tricky thing (from tech blurbs from Moto & from info from my corporate VZW rep) it lives in two places on the device most of the bootloader lives on a protected partition, there is a small portion of the loader the lives on the user accessible partition and is flashable.

Cheers,

Hat

---------- Post added at 08:48 PM ---------- Previous post was at 08:38 PM ----------

yep, I reloaded all my apks via MyBackup pro wich requires reboots after the application & data jobs.

Plus I had to "emergency" power down during a meeting today, when an email alert (from my wife) triggered and I couldn't silence it.

Noting like 'Timberlake's' "sexy back" to make a room full of techs bust out in chaotic laughter.... I'm going to be pwned for life now........ :-)
[Xoom General] jadkar:
ROFL!!!!!! She's back with HLK75D !!

Going all the way back and using the everest bootloader got me into Android (first time in a week).. Then I let it OTA update until the bootloader was up to 1.45. Once she looked good with the new bootloader I SBF flashed HLK75D.

BTW...My RSD issues were fixed due to me now using RSD 5.4.4 rather than 4.9

Anyway... I'm done for now. Later on I'll do the universal root. Get Ti working and try and get some of my apps back.

Thanks everyone for the help ..... and for those of you who are still trying to get your xoos back....Good Luck...don't give up!!
[Xoom General] csstamatin:
Thx Hat, but no luck, i normally run linux and have window 7 as a backup. tried just about everything. let me know what else u can think of.
[Xoom General] jadkar:
So I guess I spoke to soon......

Add this to the list of wierd stuff. Everything was working fine. I am navigating a totally stock xoom and the message comes up saying 4G SIM card detected do you want to switch to LTE/CDMA . You know, the message that we all know... I was looking for this to happen. I say YES. Then I navigate some more and decide to do a reboot.....and.....

back to frozen at the Moto screen!!! Explain that one!!
[Xoom General] dethrok:
Yup. The same problem all of us are having. We can flash into HLK75D once, then once you reboot, you're screwed.

Just like I did (again). I was just checking to see if it would freeze, and of course, it did.
[Xoom General] zone23:
Ya your really screwed because you can't power off the device you got to keep messing with it until you get back to where you were. Sucks I had to drive how with it stuck in that screen. the good news is you can flash back to recovery-Tiamat-R4c-100611-1150-cwm.img using

fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img

and flash a custom ROM make sure to wipe.

Its all in the bootloader I think Moto needs to provide us with a RSD bootloader image to flash as well.
[Xoom General] jadkar:
So here's the logical deduction....... if we all had the 3G verizon device and we sent in for the upgrade than..... maybe we don't really have a MZ602!! Maybe when we flash the MZ602 it's not really made for our device and its screwing something up. Remeber Verizon is selling a 4g/LTE device right now and THAT'S the MZ602, not an upgraded one like ours. Our device is still a MZ600 (just my best guess)

So this is what I am doing.... loading the everest bootloader 1.35, returning to I39 build and letting the thing upgrade to the 1.45 bootloader. Once all the OTS upgrades are done I will flash the AceXmachine HLK75C image. I believe this is the image our device came with when shipped back from Moto.

I'll let everyone know how it goes
[Xoom General] hammer4203:
Maybe try once it's booted to hlk75d a factory reset. See if it will do that and maybe it will stick. I reset mine b4 the upgrade, but when it came back I had to do a factory reset again.
[Xoom General] jadkar:
Its what Zone23 said and what I have been thinking a long time now..... its the bootloader. I'm guessing the bootloader for the MZ602 is different in some way and the first time we load the MZ602 image the android OS comes up but it's too late because it has already overwritten or changed something in the 1.45 bootloader. Therefore when the machine reboots the bootloader will not let the device move forward cause its been modified.

I don't think a system reset will do anything, I believe the bootloader has already been messed up from the OS load.

We need a stand alone bootloader flash.
[Xoom General] hammer4203:
I called moto and yes the xoom upgrade does make it MZ602. The 600 has been discontinued unless you opt out of getting the upgrade. I think there is something we are missing that makes it stick for you guys. Most everyone has had to go into recovery and clear everything when doing an update when rooted. Wonder why. I am waiting for an email as to exactly how we need to load this file. I will let you know as soon as I get it.
[Xoom General] hatxtrick:
Thanks for the update Hammer!

Cheers,
[Xoom General] jadkar:
Yes, thanks Hammer..... regardless of what happens right now I think huge progress was made here today and tonight because it seems like many us of are able to duplicate the problem and at least we know we can get the devices back from the "stuck" state where we were.

I'll await further word if my latest attempt doesn't work.
[Xoom General] hatxtrick:
As promised, I’ve created a couple of walk-through videos:

1: A brief demo of the “stuck” at Moto boot screen:

I reproduced the issue and demonstrate how to navigate through it.

Link:

http://youtu.be/W7VRtb1szi8

2: Complete walk-through of how to erase and reload your Moto Xoom MZ600 w/LTE 4G to the new HLK75D SBF image.

Links:

Part1: http://youtu.be/utCgD13yMg4 Part2: http://youtu.be/tJya_YAM8ag

Hope this helps,

Cheers,

Hat
[Xoom General] jadkar:
Watched the video...very...cool.... thanks!!! Please read below carefully.... I really think this is what is happening!!

After following your videos (which I did before anyway) I'm still stuck, however hearing you go through this was key!! and it seems to confirm thoughts about the bootloader. You said in Vid00002 Part 1 (while in RSD) that you have bootloader 1050 which I believe is ver. 1.50. The below is what I think is true.....

Flashing Everest bootloader SBF = 1.35 (1035)

Let it OTA will get you to bootloader = 1.45 (1045) this is what I think most of us now have, (check in RSD.)

You have (Hatxtrick) = 1.50 (1050) and this probably came from Verizon after the upgrade.

We need bootloader 1.50 for this HLK75D SBF to work.

I bet if you flash Everest SBF 1.35 bootloader you will not be able to recover and be in the pit with us. Not saying you should try this (unless you want to be a champ and confirm for us).

Below are some supporting photos. 1st photo is my buddy's Xoom, he has the 4G upgrade and never touches his machine. Look at his bootloader version.

Next photo is mine after I FUBAR'd it. Most like everyone that is stuck has this bootloader.

*Notice how even though I flashed MZ602 it still says MZ600.

** Looking for Hammer to have some good news today from Motorola about a new bootloader!!

Thanks again Hat!!..... making videos is a long (and sometime boring) process.

-John
[Xoom General] hammer4203:
I'm hoping for that myself. Seems motorola forgot that the instructions they list are for fastboot and not rsd. That's typical if engineers though. I requested the app needed and procedure to properly load the sbf.
[Xoom General] zone23:
This is what i've been saying. You can go back the HRI39 and download the bootloader update OTA. Then flash the SBF image HKL75D but once you flash back to HKL75D it gets stuck at the dual core screen.

Like right now I flashed HRI39 and have the updated bootloader. But if I flash HKL75D it will only boot once.
[Xoom General] jadkar:
On a side note..... I told everyone last night I would try another method ... the "go back to old bootloader and work our way up using OTA, etc ,etc, etc".

Then I would try AceXMachines HLK75C boot.img & system.img??

Well, I did this and I got something else. I was able to get into the Xoom but I had a problem that another group of people have....... Xoom working perfect but no 3G/4G. All I had is wireless :(

So now I have duplicated both scenarios..... Us with the "stuck at Moto" and other users with newest 4G upgrade but non-working 3G/4G.

-John

---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------

Well.. lets start being careful when saying "updated" (for the forums sake). Lets refer to the version. You most likly have what all of us have (except Hat) version 1.45.

If you had the newest "updated bootloader" it would be like Hat's (or my buddy's) and be v.1.50.

---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------

Is it possible to just ask them for the SBF file forthe newest bootloader? I'm just afraid that what you will now get is the same SBF that we have with pretty instructions.

* Just thinking like an "Engineer", like you joked..... I happen to be a Windows Server Engineer ;)
[Xoom General] zone23:
So far nothing works. So I'm at 3.2 with the 1.5 waiting for Moto to actually help us out.
[Xoom General] Brenardo:
So Zone the only way to get past the stuck dual core screen is to flash a Custom ROM?

I assume so because I flashed HRI66 imgs and that didn't get me anywhere. I am still stuck in the mud.

EDIT: I just flashed Tiamat R4C recovery and I am unable to get into the recovery to flash a ROM.
[Xoom General] jadkar:
Bernardo - Do this to get where we are :) When replying answer YES or NO to the steps I list below so we can tell where you are.....

- Obtain RSD Lite 5.4.4 with USB cable (use your normal moto USB cable that came with your device for now)

- Get your machine into Fastboot (volume up while booting) and run the following commands in order

- Fastboot erase boot

- Fastboot erase system

- Fastboot -w (overkill but do it :) )

- Fastboot oem lock (follow prompts)

- Let the machine reboot and it should go right to RSD support (if you did the above)

- Launch RSD lite 5.4.4 from your desktop and flash the files in the HRI39 SBF file from Legion. (It's around here somewhere). Flash in the follwoing order.

- Flash SBF "Everest bootloader" first, its the small file. (This will get you the old v1.35 bootloader)

- Flash the large VZW Sbf, this is the actual build.

The above will get you to the HRI39 build using the old v1.35 bootloader and the machine should boot up, the whole process takes a about 10-12 minutes and you will see the device bounce a couple times. When it boots up you may not have 3g and will need to connect to the internet via wireless. So do this and let the machine run through all the OTA updates. Eventually one of those updates will update the bootloader to v1.45.

** From this state you could actually stop although you won't be on the latest build version and may not have your radio working. Once you have this bootloader (v1.45) though you could flash from RSD the new HLK75D image that we have been talking about...... but if you do your device will work awesome....until you reboot.

We need the bootloader v1.50 for HLK75D to work.

A lot of typing here but follow the first SBF flashing steps I listed to at least get you to a "booting device".

Let us know how that works.

***** Forget it ...... if you were at the motoscreen but was able to flash and then get into recovery then you were at a better place then any of us anyway and really didn't need to go through our crazy process. Most of us were not even able to get to recovery!!
[Xoom General] zone23:
Just to answer your question I think (its hard to remember I've tried so many things) you can flash the HRI39 boot.img and it will boot but 3G/4G wont work of course.

My suggestion at this time is to flash the HRI39 via fastboot do the updates and wait it out.
[Xoom General] dethrok:
I've been blowing up Motorola's e-mail to see if they can provide any kind of solution to our bootloader problem.

The live chat support obviously isn't very helpful. Maybe they'll pass my e-mail to someone who knows what they're doing, aside from knowing how to search a knowledge database.

I also rebooted last night just to see what would happen. Of course, I got stuck at the boot screen, so I had to follow all the steps again to get back to working order.
[Xoom General] zone23:
Its been a nightmare I truly worked on this for about 12 hours yesterday and could not get any combination to work. Now I may not be the brightest bulb on XDA but I know enough to say that it shouldn't be this hard. Something is wrong with the file Moto provided. I think they are just messing with us.
[Xoom General] jadkar:
I sent them an email as well trying to utilize my work credentials and saying this is interupting a large POC implementation I'm involved in. In reality I am working on some current solutions utilizing Android .....but at another gig..... all the same :)

---------- Post added at 09:19 AM ---------- Previous post was at 09:18 AM ----------

Just need Bootloader v1.50 ... that's all

Can't someone extract this from they're device??? The everest_bootloader got into the wild some how??
[Xoom General] zone23:
Well I have the 1.5 (I think) but the problem remains if you flash HKL75 it will only boot one time. The file breaks something and I have know way of know what.
[Xoom General] jadkar:
I don't thnk you do.

Please check for us..... use RSD lite and don't flash anything. Just click your discovered device and it will populate the left hand box showing you your bootloader. If you confirm you have 1.45 than we know for sure its a bootloader version issue. Look at my post with the screen shots a couple pages back. Read that whole post ..... I put some good stuff in there which I believe explains it.
[Xoom General] Brenardo:
Device booted into HRI66. I was being stupid and did not flash the old bootloader... DUH!

Thanks guys.
[Xoom General] zone23:
it says "Bootloader Version: v0x001045" I assume thats 1.45 since no combination makes 1.5. So reality is we can do anything until we get updated bootloader. So you are correct, but you knew that already didnt ya.
[Xoom General] KidJoe:
newbie question... Is the bootloader in the boot.img?

if so can this help?? -> http://xdaforums.com/showpost.php?p=18224303&postcount=6
[Xoom General] zone23:
Nope that wont help. Thanks though.
[Xoom General] jadkar:
You got it Buddy!!! We need bootloader v1.50

So as I said before..... can we get one of these XDA Jedi masters out of their Tower of Power and throw us a bone ;) I'm sure one of these guys can extract the 1.50 bootloader :)

I know they don't answer PMs but does someone have like a XDA Bat Man spotlight we can shine in the night sky!!
[Xoom General] zone23:
One of us could PM solarnz and see if it can be done. While we wait for Motorola.

edit:

Motorola must load 1.5 at the factory when the update the device. They must have the file if the people from Manpower can do it we should be able to. Wonder why they are holding out on us. Guess I'm just thinking out loud.
[Xoom General] howlinwolf:
Normally don't post, but I have started a thread over at Motorola's Unlocked forum hoping that the Moderator Matt can somehow post instructions or the boot file. I believe hammer and dethrok have also posted in there. If this Matt character posts anything helpful I will immediately post it in here. thanks everyone for the insightful posts.
[Xoom General] zone23:
Thanks I'm sure Motorola new we needed the bootloader when they posted that file. They know a lot more about it then we do (no disrespect). Where did they think we were going to get it from? Maybe they didn't think we would over right the bootloader that came back from the factory, but some how we did. Also I don't think everyone did just some of use. If you have the 1.5 then you should have no problems restoring.
[Xoom General] Brenardo:
Matt over at the Moto site has some kinda pull... I have always thought he was a bit spiteful but he normally comes thru in a pinch.

Lets hope that the powers that be can help us out much sooner than later.
[Xoom General] howlinwolf:
Yea he does seem to have some pull. If I remember correctly someone post over there about images not being released anymore and at first he said they wouldn't be, but then he said he was looking into it. so, maybe he can work out something again. And no disrespect taken zone, I normally don't post because I know people here have way more knowledge than me, which I am grateful for. Thanks.
[Xoom General] Brenardo:
Zone I just caught myself confusing you with a "true" Dev again... ;)
[Xoom General] zone23:
I just play one on TV..
[Xoom General] jadkar:
Not sure if they knew it or not. I mean "somebody" most have known but it maybe a case of "one hand not talking to the other". I mean that whole download page doesn't seem to have been proofed by anyone who actually knows how to work with the device. If you look at the instructions they list the fastboot process and it looks like its taken directly from XDA :) Meanwhile the files they give you are SBF for use with RSD Lite. Nobody ever mentioned on that page the specific version of RSD to use either (which stumped me for a day) and then there is not even links to where to get RSD.

I just think the download page is like a "hobby" for some people at Moto. Lets face it they don't have that much of an audience for this stuff so their resources are most likely spent in other areas of their business.
[Xoom General] hammer4203:
Moto is telling me that if you downgraded it should update if the sim and radio are in over wifi. They must be on crack over there!
[Xoom General] dethrok:
Did they tell you that over the phone or with an automated e-mail response?

If it was the former, I would have just laughed at them and hung up.
[Xoom General] zone23:
Someone with access over at the Moto should just start a thread and call it something like

Bootloader 1.5

We believe this version of the bootloader is necessary to use HLK75D image. Otherwise the device will freeze at the Dual Core screen after a reboot. Can someone at Motorola confirm this and possibly provide the necessary bootloader image. The device currently only updates to 1.45 OTA. Sorry for the inconvenience.
[Xoom General] jadkar:
Sure it upgrades over wireless... they are right BUT it only updates to v1.45. We need 1.50 :( I agree with the drug suggestion ;)
[Xoom General] dethrok:
https://supportforums.motorola.com/thread/60221
[Xoom General] zone23:
Nice I think that is really the question we are asking and is very direct.
[Xoom General] sakenfenc:
Ck

stuck in Moto boot screen no matter what image I flash , tried HR139, and HR166 no go. any help would be great..
[Xoom General] jadkar:
Cool...I posted basically the same question on the developers forum....I don't even know what forum this is but I got here from the software download page :cool: It might be just "app development" however maybe we'll get lucky.

http://community.developer.motorola...r-1-50-needed-for-using-HLK75D-SBF/td-p/19789
[Xoom General] craigcrawford1988:
Rather than flashing it and rebooting it, can't you guys flash it and dump the entire system (including boot.img, etc)?

That way we can have something to work with.
[Xoom General] dethrok:
I think I posted something in that category the other day and it got removed due to not having to do with application development.

Hopefully they leave yours up so it gets some attention.
[Xoom General] zone23:
We have the system we need a compatible bootloader (aka 1.5).
[Xoom General] jadkar:
In the spirit of being positive ..... I have learned more in one week with a dead device than I have in the two years I have been here "reading guides".

Sometimes you gotta get dirty with this stuff to truly "learn it"
[Xoom General] zone23:
Its true you learn a lot about the side of the device people rarely pay attention too. I have to give Moto credit on there design because I haven't bricked it yet.