yashsingh1/xdaforums huggingface dataset:
[Xoom Q&A, Help & Troubleshooting] okantomi:
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?

When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...
[Xoom Q&A, Help & Troubleshooting] jadkar:
^^^

Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good :(

So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.

So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?

Here's some stuff I have flashed along with some links....

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

MZ600_HRI66_OEM_Image

how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html

Someone got the build img after the LTE upgrade, so I tried this....

http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html

I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.

Thanks for your time!!
[Xoom Q&A, Help & Troubleshooting] okantomi:
Well, you are flashing wildly but not well, (JK) :eek:

This thread should help you:

http://xdaforums.com/showthread.php?t=1299485

Here is a great post by Saintfyre (I think it fits the bill):

"Yeah join the FUBAR Club.

I was in the same boat as you did the same thing.

I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!

What I did to fix my situation:

-I wiped the Device and just went through Solarnz's Root Method here: http://xdaforums.com/showthread.php?t=1074979.

-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6

-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine

-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.

On Windows shift and right click the Platform-Tools folder -> Open Command Window here.

adb reboot bootloader

fastboot flash boot boot.img

fastboot flash system system.img

fastboot erase cache

fastboot reboot

After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."

From this thread:
[Xoom Q&A, Help & Troubleshooting] jadkar:
Yup.....I tried that one as well, it didn't work either.

I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??

**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.
[Xoom Q&A, Help & Troubleshooting] jadkar:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img

Questions:

- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.

- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.

Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.

Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.

recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img

recovery image from steady Hawkin (3g/4g Stock Images for HR166)

Rogue-recovery image from rogue-recovery-1.2.0

Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)

boot from AxeMachine HLK75Csystemboot

boot from AxeMachine HLK42Bsystemboot4g
[Xoom Q&A, Help & Troubleshooting] okantomi:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.

If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
[Xoom Q&A, Help & Troubleshooting] jadkar:
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.

After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.

Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....

is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.

Thanks!! John
[Xoom Q&A, Help & Troubleshooting] LesismoreTN:
I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version

ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.

We've both exhausted the experience at Xoomforum (hence our plea here:) Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):

To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.

ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.

As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.

Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)

So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot

Any help would be APPRECIATED!

P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)
[Xoom Q&A, Help & Troubleshooting] jadkar:
^^^

Thanks .... we'll see if anyone bites.... I hope so :(

As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!
[Xoom Q&A, Help & Troubleshooting] LesismoreTN:
LOL! Safe flight.
[Xoom Q&A, Help & Troubleshooting] okantomi:
Guys, you all are crazy!

I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.

If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.

Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?

Please try to follow the instructions in the following

thread before you commit mayhem on your innocent Xooms.

http://xdaforums.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.

Commands to use:

fastboot flash system system.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash userdata userdata.img

fastboot erase cache

fastboot reboot

Don't give up...good luck!
[Xoom Q&A, Help & Troubleshooting] hammer4203:
Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
[Xoom Q&A, Help & Troubleshooting] LesismoreTN:
Probably... That's half the fun! :p

Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.

Too late, mayhem already commited!

That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.

Any clues about why a successfully flashed recovery image isn't working?
[Xoom Q&A, Help & Troubleshooting] jadkar:
Lots of stuff to answer back here, please don't mind the bullet points....

from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."

- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.

- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.

- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?

Thanks!!! :)
[Xoom Q&A, Help & Troubleshooting] okantomi:
Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!

Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.

Good luck!
[Xoom Q&A, Help & Troubleshooting] hammer4203:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
[Xoom Q&A, Help & Troubleshooting] LesismoreTN:
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:

Isn't THAT what you suggested? Yes?

No

?
[Xoom Q&A, Help & Troubleshooting] jadkar:
^^Hammer....

I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.
[Xoom Q&A, Help & Troubleshooting] LesismoreTN:
Can someone lead me to the patience pool; I need a drink.
[Xoom Q&A, Help & Troubleshooting] okantomi:
If you're just trying to fix your messed up Xoom by flashing the system files you never need to relock (just something to keep in mind for the future).

Hammer is right in what he says and he's solved his problem. You may need to send the Xoom back to Moto and hope they can fix it. If you formated your partitions...

I really hope you can fix it.
[Xoom Q&A, Help & Troubleshooting] hammer4203:
I could have sworn one of the other threads said you went back to stock. That may be why your having so much trouble. Stock moto, then back to hlk75c. It seems to be the only way to get back.
[Xoom Q&A, Help & Troubleshooting] jadkar:
BTW... I think this may have been how everything got screwed up.....

http://xdaforums.com/showpost.php?p=14966182&postcount=20

A lot to think about now but after I unlocked the device (right before it dies) I did take a stroll into recovery and I tried to load a backup image from the SD card. I wonder if I inadvertently blew out this "NAND" memory.

If so it's funny nobody mentioned this before. Is there any way to recover from this? Can the NAND memory be written to?

Thanks,
[Xoom Q&A, Help & Troubleshooting] okantomi:
You can save a nandroid backup to the internal sdcard and even flash from it in certain versions of cwm recovery but not the solarnz version R4c, which only reads from/writes backups to the external sdcard. I actually did mention that you might be screwed if you formatted your internal storage.I wish you the best.Good luck...I really mean that.
[Xoom Q&A, Help & Troubleshooting] hammer4203:
Just call motor and tell them your xoom quit working.....blame it on the upgrade! Tell them it's been acting funny ever since you got it back. They will flash it back and test it. There is also a different cable you can get that looks just like the USB cable that you hook to the PC. It's wired differently for PC to xoom( or any motor device w/micro USB) flashing of the system. That's how they cash them to begin with.
[Xoom Q&A, Help & Troubleshooting] okantomi:
I bought that factory programming cable from Black Hat, but luckily haven't had to use it yet.
[Xoom Q&A, Help & Troubleshooting] dustywilson:
Me too, me too...

I have this exact same problem. All I did was oem unlock and immediately afterward it simply is stuck at the logo. Fastboot works and so does RSDLite (though neither have fixed the problem). Booting and recovery both fail.

I'm guessing the problem has something to do with the partition table. I'm assuming that RSD doesn't rebuild the partition table.

In case someone figures this one out, I'm certainly interested. If anyone has any ideas not yet stated, let me know and I'll give it a shot.
[Xoom Q&A, Help & Troubleshooting] jadkar:
Hey buddy...the party moved over tho this thread. Stop on by and join the multitude who now have the same issue..... http://xdaforums.com/showthread.php?t=1309562
[Windows Phone 7 Development and Hacking] VoodooKing:
Hi guys.

Many of us really appreciate your work bringing us tools to dig around and play with the internals of our phones. However now with many tools on the phone, it's starting to get a little difficult to jump around the different tools using the jumplist. "SamsungTools and Samsung Registry" are in S, "Interop Unlock" is in "I", "WP7 Root Tools" is in "W" and so on and so forth. You get the idea.

I'd like to suggest to devs to prefix '...' in front of their app names so that when the program is installed, it appears right at the top in the # jumplist.

Just a suggestion.

Regards and thanks for all the hardwork!
[Windows Phone 7 Development and Hacking] sensboston:
You can do it by yourself, editing WMAppManifest.xml in xap. Change <App Title="whatever you want"
[Windows Phone 7 Development and Hacking] GoodDayToDie:
Ideally, of course, we could create our own "Homebrew Hub" or some such. I don't think anybody has figured out how to do that, though - even TouchXperience, in the version that I saw, could only start native apps, not third-party ones (sideloaded or otherwise).
[Windows Phone 7 Development and Hacking] ryotgz:
That would be awesome.
[Windows Phone 7 General] chuwi1978:
Hi

I'm having a problem using Mango on a brand new HTC RADAR. I've configured a twitter account. I can post messages, read people messages from PEOPLE HUB but I cannot read twitter notifications on "Me" tile.

I tried to re-create account, rester phone, but nothings works. I've read thats some people re-link twitter account on windows live website but I cannot find where is it

"Me" tile notification sections only show Facebook notifications which work great but no twitter :-(

Are you having such problems?

thx in advance!
[Windows Phone 7 General] Peew971:
You're notified in the Me hub only if you're mentioned in a tweet, not just for new tweets. Could be your issue.
[Windows Phone 7 General] chuwi1978:
thx peew971

this is exactly my problem, i cannot see my mentions/replies
[Windows Phone 7 General] efjay:
Have you checked your actual twitter account to confirm the permissions for the WP twitter access? Try removing it from there then try readding on the phone.
[Nexus S Q&A, Help & Troubleshooting] piax:
hey guys!

i have a droid x, but before anyone *facepalms*

im here on behalf of a friend who has the nexus and asked me to do some rom research

i cant for the love of android get into his device

maybe since i dont have it

but i can work my way around the droid x ;)

so i thought id ask the people who knew the device =]

can you guys/gals tell me how exactly to get his device onto stock or another rom?

and stupid question i found out theres no sbf file for samsung devices?

(quick story he bought the device from a boost mobile carrier and had them flash over roms but they charged $20 every time he wanted to flash over a new rom)

thanks in advance =]
[Android Q&A, Help & Troubleshooting] es0teric:
Is there any latest andriod firmware like SIRI?
[Android Q&A, Help & Troubleshooting] Theonew:
SIRI is not a firmware :p.
[Android Q&A, Help & Troubleshooting] es0teric:
Oh, is there any apps like SIRI? :D
[Android Q&A, Help & Troubleshooting] TechSilver13:
IOS5 is ur best bet. Closest thing to what u r asking for.
[Android Q&A, Help & Troubleshooting] Theonew:
He is obviously talking about it for android.

---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------

Not really. Just voice search apps (e.g Voice Search) but none that is so interactive (at the moment...). Check out this thread (it may get somewhere): http://xdaforums.com/showthread.php?t=1299387 .
[Android Q&A, Help & Troubleshooting] genisis7:
try iris:D
[Android Q&A, Help & Troubleshooting] Theonew:
Good one. Thought it was a joke, but then I searched for it and actually found it.

OP - You could try it. Here's the link: https://market.android.com/details?...?t=W251bGwsMSwxLDEsImNvbS5kZXhldHJhLmlyaXMiXQ.
[Android Q&A, Help & Troubleshooting] monkeytown:
samsung should come up with something in no time, they like apple stuff
[Android Q&A, Help & Troubleshooting] baseballfanz:
http://www.wnem.com/story/15745428/website-provides-fake-girlfriend

:D
[Android Q&A, Help & Troubleshooting] es0teric:
Current I'm using speaktoit assistant.

A program similiar to SIRI and I think it's better than IRIS.

You can try by downloading it at the android market app.
[Galaxy S II Q&A, Help & Troubleshooting] suhail_kapoor:
Hi All,

First thanks for hosting this forum and contributing. I am an android noob and have recently got a samsung galaxy sii on a contract with t-mobile uk.

after reading through forums i have managed to root the device using odin and insecure kernel and then unlocked it using the galaxy s unlock from market.

The device came with stock 2.3.3 and I want to update but stay on stock roms as they offer best battery life. I have seen the latest firmware available is XWKI8.

All i need to understand is can i upgrade to XWKI8 using the firmware from official firmware xda forums and will i loose my unlock when i do so ?

If yes will the aforementioned galaxy s unlock app be able to unlock it again ?

Many Thanks for your help. I have read so many forum posts now but as a beginner cant get my head around it.

Regards
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
Rules question = Q&A

he device came with stock 2.3.3 and I want to update but stay on stock roms as they offer best battery life. I have seen the latest firmware available is XWKI8.

Correct .

All i need to understand is can i upgrade to XWKI8 using the firmware from official firmware xda forums and will i loose my unlock when i do so ?

No it should remain unlocked .

jje
[Galaxy S II Q&A, Help & Troubleshooting] suhail_kapoor:
Thanks for your reply, I am now officially confused ... :(

Read the following at android devices .com "The best part of this firmware is that anyone with their Samsung Galaxy S2 GT I9100 handset can proceed to apply the update of this XWKI8 irrespective of the current firmware, the only condition being is that this phone should not be a network locked device. "

I know my device is now network unlocked but it wasn't originally will that matter ? Sorry if i sound like a stupid chap, just worried don't wanna screw my phone.
[Galaxy S II Q&A, Help & Troubleshooting] ixon2001:
Your mobile will remain unlocked no matter which firmware you flash.
[Galaxy S II Q&A, Help & Troubleshooting] skimminstones:
kinda answered your own question there dude, your phone isnt network locked anymore so you can install it fine
[Galaxy S II Q&A, Help & Troubleshooting] bruflot:
Off topic: Stock ROM/Kernel doesn't really have the greatest battery life. Jeffreys SpeedFrey 4.0 kernel is said to be released today, and has AWESOME battery life!
[Galaxy S II Q&A, Help & Troubleshooting] skimminstones:
How do you know if its only been released today?
[Galaxy S II Q&A, Help & Troubleshooting] bruflot:
The old thread/versions got closed/deleted since the author didn't provide the source. And on his twitter he said its returning today :P
[Galaxy S II Q&A, Help & Troubleshooting] suhail_kapoor:
Thanks All .. ill get the update soon