yashsingh1/xdaforums huggingface dataset:
[Xoom Q&A, Help & Troubleshooting] quew:
Got the same problem! Motorola (datrepair in Germany) wanted about 300€ to get my mainboard replaced... Received it back today:

In my opinion the problem is the MZ602 HLK75D image which contains new radios for LTE (baseband-2). Seems like some custom ROM I flashed in the past was built upon this release and I haven't paid enough attention...

I already tried flashing every 3G rom available (EU T-Mobile, EU, MZ600 3G), even tried to just extract the radio images but no luck at all. It seems RSD can't flash/access the baseband at all, it really seems to be completely broken :-(

The MZ600-3G sbf-image (HRI39) states: "Phone did not re-enumerate after RAM-download was sent (0x703E)"

It seems like the German/EU stock versions don't come with a radio at all, at least they are flashable without any errors through RSD lite (problem persists though). I haven't found any radio/firmware files for the Xoom neither.

The only hope I've got is for the official ICS/3G/LTE EU-upgrade to include a new radio that might be upgrading my faulty baseband(s) - unless then I/we will have to live with WiFi only :-(

Anybody got any other idea? I would really appreciate this! Thanks.
[Xoom Q&A, Help & Troubleshooting] berylz:
Thats not what I wanted to hear. DatRepair was my last hope :/

I already filled the Repairform....

Did you try the method of felipe?

Unfortunately I can't find any unofficial Europe/German stock rom thats editable like he describes in his blog.

Did you found out where fastboot get its information from?

I reviewed the code but couldn't find it

btw. heres my thread @android-hilfe.de:

.../motorola-xoom-forum/227236-radio-umts-modul.html

Sorry for my bad english ;)
[Xoom Q&A, Help & Troubleshooting] quew:
Maybe you'll be luckier than me - they seemed to check the "iswarrantyvoid" and that's it... No warranty, no actions... So I got it back without anything being done (on my own request).

Well I guess felipe's method won't work for us because unfortunately we already HAVE flashed the (wrong) rdl.bin and bp.img - so the trick might be to get the stock EU versions of that files, I just don't know if they even exist...

I have seen some strange behaviour with fastboot. After flashing another recovery the output was different but only while the fastboot session lasted! I don't know if I can reproduce it but fastboot told me it was a "MZ602" called "xoom-cdma-lte". After a reboot the above quote was given again... Strange! I don't know exactly where the information is from but the (bootloader) might be not so wrong.

Maybe all the effort isn't worth it - at least the Xoom isn't unsuable totally...

//Edit: got it!

Seems not surprising though AND kinda random, got it twice out of 5 reboots... But why?
[Xoom Q&A, Help & Troubleshooting] mynameisjon:
I'm getting this from my getvar after I used the sms/mms mod on my MZ601 running EOS 2.0..

I admit I screwed around with the radio settings by selecting "WCMDA only" in the *#*#4636#*#* menu.
[Xoom Q&A, Help & Troubleshooting] mynameisjon:
I found a solution. You can make a nandroid of your current set up.

After that download and flash to original firmware from motorola's site and relock your device. boot up and install all the OTAs as per normal. Once you're done you can unlock and restore your nandroid and 3G is back to normal.

The key is to download the OTAs from your tablet and install, 3G only worked after the 2nd patch.

The only thing is that even though 3G has returned, the getvar still returns the wrong info.
[Xoom Q&A, Help & Troubleshooting] ArakniD:
You could be right.. I've patched my device back to the original misc partition.. I'll try relocking the device and going through the motions again..

(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x303:0x5454:257
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C71004XXXXXX
(bootloader) version-baseband: N_01.83.28P
(bootloader) version-baseband-2:
(bootloader) battery-status: 97%:8.276V:0.9876A:28.25C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
all: Done
finished. total time: 0.549s

exactly which package did you go from? which UMTS build did you use?
[Xoom Q&A, Help & Troubleshooting] mynameisjon:
I used the one that listed Singapore in the region. I think it's "Build H.6.1-38-9 for Retail Other International"

The getvar still returns CDMA and MZ600 though, so it's not a TOTAL fix. 3G does work, but I'm afraid to try switching the WCDMA only switch on again. lol
[Xoom Q&A, Help & Troubleshooting] ArakniD:
some other ppl reported that this works..

when it was installing, it said "unsuccessful" I think when installing the bootlaoder ota patch..

can you dump and post your ebb partition?

/dev/block/platform/sdhci-tegra.3/by-name/ebb

;)

dd that bad boy out.. that's the boot loader..

but it could have been whinging about not being able to boot my little mbm6600 chip... it'll get into bootloader mode, but not show the usb device for the modem..
[Xoom Q&A, Help & Troubleshooting] mynameisjon:
I'm not too sure how to dump that, any chance you can point me in the right direction?

As for DD, considering I'm not even familiar with what it is, and reading solarnz (was it solarnz?) comment on it being dangerous, I don't think I want to be fiddling with that. :eek:
[Xoom Q&A, Help & Troubleshooting] ArakniD:
ye doing a dd with the output going to the dev block devices can be dangerous..

i may just leave this xoom as 3g and be done with it.. failed rooting :) never stuffed up a phone/pc/laptop mod so bad!
[Xoom Q&A, Help & Troubleshooting] berylz:
Hey guys...

In the hope that the repair service in germany would replace my xoom mainboard, I locked the bootloader like andlommy described.

But I hadn't much luck :/

They returned it without doing anything, saying it has unofficial software installed (reflashed the official stock rom....)

So, don't lock your bootloader, at least in germany!

Does somebody know if theres a way to re-enable fastboot commands?
[Xoom Q&A, Help & Troubleshooting] quew:
Not working for me in Germany... Tried to install the Singapore SBF and stock Motorola images - no luck at all. I'm accepting that there's no 3G for me anymore...
[Xoom Q&A, Help & Troubleshooting] thenemis:
have you try rdslite + full .sbf image ?

http://sbf.droid-developers.org/everest/list.php
[Xoom Q&A, Help & Troubleshooting] quew:
Several times - no luck at all
[Xoom Q&A, Help & Troubleshooting] thenemis:
mz601 baseband flashable on CWM rogue 1.5.0 :

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

flash recovery. reboot, flash baseband.

hope it fix
[Xoom Q&A, Help & Troubleshooting] kevlarman:
Didn't work for me. :(
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
I've never run in to this before and the other guys might have a better idea but it sounds like you need to repartition. There is a check box in Odin to do it. I don't think that you need the pit file unless that is hosed too... It looks OK from your Heimdall output. I would try going through AdamOutler's unbrickable mod post and when you get to the Odin flash check the repartition box in odin...

Or have you tryed that?
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Ok, I got in this situation few times. The problem comes when you compile a kernel with wrong vermagic and init tries to load samsung propietary modules. Sometimes when it happens, the partition table of your internnal storage gets corrupt. Repartition with Odin using a PIT file won't help.

You need to manually repartition your internal storage. To do this:

1. Make sure you can enter to a shell with adb shell command. If not, try Entropy512 kernel. The device will stay with Samsung logo, but you should be able to get in a console.

2. Ask someone with a working device to give you a working partition table. To do this, you need to do:

fdisk /dev/block/mmcblk0

Then, press u, enter, press p, enter. This should give you a output like this:

# partition table of /dev/mmcblk0
unit: sectors

/dev/mmcblk0p1 : start= 64, size= 15515584, Id= 5
/dev/mmcblk0p2 : start= 0, size= 0, Id= 0
/dev/mmcblk0p3 : start= 0, size= 0, Id= 0
/dev/mmcblk0p4 : start= 0, size= 0, Id= 0
/dev/mmcblk0p5 : start= 128, size= 512, Id=83
/dev/mmcblk0p6 : start= 704, size= 512, Id=83
/dev/mmcblk0p7 : start= 1280, size= 2560, Id=83
/dev/mmcblk0p8 : start= 3904, size= 2560, Id=83
/dev/mmcblk0p9 : start= 6528, size= 10240, Id=83
/dev/mmcblk0p10: start= 16832, size= 20480, Id=83
/dev/mmcblk0p11: start= 37376, size= 15360, Id=83
/dev/mmcblk0p12: start= 52800, size= 15360, Id=83
/dev/mmcblk0p13: start= 68224, size= 593920, Id=83
/dev/mmcblk0p14: start= 662208, size= 274432, Id=83
/dev/mmcblk0p15: start= 936704, size= 131072, Id=83
/dev/mmcblk0p16: start= 1067840, size= 3940352, Id=83
/dev/mmcblk0p17: start= 5008256, size= 10504192, Id=83

This output is from my YP-G70 international 8G. Don't know if it's exactly the same for US version.

3. Then:

adb shell
fdisk /dev/block/mmcblk0

Press u, enter, press p, enter. This should print your faulty partition table. My guess is the last partition will have incorrect size. Delete that one with d. Then, create the rest of partitions with n. Make sure you enter the right starting sector, and the right size (ex. for mmcblk0p12, enter "52800" and "+15360").

Finally, write the partition table with w.

Now, enter in download mode and flash a kernel that you know is working (you can also dump it to the right partition (dd if=<unpacked zImage> of=/dev/block/mmcblk0p11). If the device doesn't reboot, you should reflash a stock kernel and do a factory reset in stock android recovery.
[Samsung Galaxy Player 4.0, 5.0] exodus454:
Thanks, that might be really helpful!! I'll give it a go. Meticulus, I've already tried alllll that like 20 times already.

I can still ADB in with no problem whatsoever, manual partitioning seems like the only thing I haven't tried so far. I also have a feeling that the partition tables for US/INTL are different.. I really borked it eh?

Anyone with a US 5.0 wanna post the output of

fdisk /dev/block/mmcblk0 please?
[Samsung Galaxy Player 4.0, 5.0] dgk164cpehs1:
*Warning you are doing this on your own behalf I am not responsible if something goes wrong with your device or anything when you are going through this process*

THIS PROCESS WORKED FOR ME

You are going to have to do a factory restore * I kept all of my device data and sd data i just had to re-install the apks*

hmm

have you tried doing the unbrickable mod on a unbuntu i was on a hard brick state in which the device hadn't turned on at all but i got it to work.

Maybe this can help

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

I followed the first steps before creating the virtual machine

make sure you have unbuntu on windows if you have windows of course, then try installing java for linux on unbutu so you can open up the unbrickable mod, make sure you have device plugged in and it should say spc110 detected or at least something like that then start the unbricking you should see a downloading sign. Note: if you don't see a downloading sign on the galaxy player and computer you should unplug the galaxy player and restart the unbrickable mod don't plug the galaxy player in immediately, plug the galaxy player in when you are ready and as soon as you see spc110 detected quickly click unbrick button and it should say downloading *this must be done quickly in order to get a downloading reading* wait 5 min and then shut down unbuntu and open up windows i did this and the galaxy player stayed in download mode. unzip the bootloaders attachment from the link above. Make sure you have kies installed on windows with all of the proper samsung drivers. Next open up odin and click pit select galaxyplayerpart.pit from the bootloaders folder, click bootloader afterwards and select galaxyplayerdownloadmodeonly.tar from the bootloaders folder and click start on odin. wait until it is complete it should say something like pass. Re-open odin and click bootloader open up galaxyplayerbootloaders.tar from the bootloaders folder and click start on odin. your device should restart and go into recovery mode now this is important you have to do wipe data and wipe/clear cache options then do factory reset and select the reboot device option and there you go. your galaxy should reboot and you will have to go through set up again and you will have to reinstall your apks your data should still be there though.

Thanks AdamOutler and all of the members on this page http://xdaforums.com/showthread.php?t=1386669
[Samsung Galaxy Player 4.0, 5.0] exodus454:
Thanks, but I tried all that already to no avail.. flashing the new PIT file makes no difference. I will say though, I did find myself using the Unbrickable Mod and it's turned out to be a lifesaver!

What version of the SGP do you have, btw?
[Samsung Galaxy Player 4.0, 5.0] rumirand:
There is another method, but use it only if the method above doesn't work:

Get a full dd dump of another US device, that was the method I used to get back to life my player: take a look here.
[Samsung Galaxy Player 4.0, 5.0] exodus454:
AWESOME!!

Just manually repartitioned it and I'm back in business. Thanks so much! Turns out the international partition table is pretty close to the US one. The last partition was indeed really screwed up. Fixed that, flashed a new bootloader and ROM and it finally let me restore my nandroid backup!
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Just share the partition table and mark it as solved, please.
[Samsung Galaxy Player 4.0, 5.0] dgk164cpehs1:
yea i have galaxy player 5.0 us version
[Samsung Galaxy Player 4.0, 5.0] exodus454:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 64 15515647 7757792 5 Extended
/dev/block/mmcblk0p5 128 639 256 83 Linux
/dev/block/mmcblk0p6 704 1215 256 83 Linux
/dev/block/mmcblk0p7 1280 3839 1280 83 Linux
/dev/block/mmcblk0p8 3904 6463 1280 83 Linux
/dev/block/mmcblk0p9 6528 16767 5120 83 Linux
/dev/block/mmcblk0p10 16832 37311 10240 83 Linux
/dev/block/mmcblk0p11 37376 52735 7680 83 Linux
/dev/block/mmcblk0p12 52800 68160 7680+ 83 Linux
/dev/block/mmcblk0p13 68224 662144 296960+ 83 Linux
/dev/block/mmcblk0p14 662208 936640 137216+ 83 Linux
/dev/block/mmcblk0p15 936704 1067776 65536+ 83 Linux
/dev/block/mmcblk0p16 1067840 5008192 1970176+ 83 Linux
/dev/block/mmcblk0p17 5008256 15512448 5252096+ 83 Linux

There's my partition table.. no idea if it's spot-on for what the stock table was but it works without issue. I didn't recreate the missing zeroed partitions (2-4) either.
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
1) Heimdall's dump-pit will report partitions as EXT4 even when they are RFS

2) Heimdall tends not to like flashing US 5.0s - gotta use Odin
[Samsung Galaxy Player 4.0, 5.0] Meticulus:
Out put from mine

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 969728 7757792 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 41384 296960 83 Linux
/dev/block/mmcblk0p14 41389 58540 137216 83 Linux
/dev/block/mmcblk0p15 58545 66736 65536 83 Linux
/dev/block/mmcblk0p16 66741 313012 1970176 83 Linux
/dev/block/mmcblk0p17 313017 969528 5252096 83 Linux
[Samsung Galaxy Player 4.0, 5.0] sjefket:
Removed :) started my own topic!
[Samsung Galaxy Player 4.0, 5.0] zaphod666:
Bumping this to ask if anyone has the partition table output for the 4.0 USA 8G. I am in a similar bind and I cant seem to find the 4.0's table anywhere...
[Samsung Galaxy Player 4.0, 5.0] Promethyl:
Bump, need this too.
[Samsung Galaxy Player 4.0, 5.0] t0m4s_g1l:
Hi. i have softbricked device too but mine is YP-G1 4.0 INTL and i cant find partition table for mine to repair my player. i have done all with odin pit file and full restore tar.md5 and i have no luck. i can acces download mode and stock recovery. can some help me with this?
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
try looking here: http://xdaforums.com/showthread.php?t=1531850
[Samsung Galaxy Player 4.0, 5.0] t0m4s_g1l:
Thanks but i did all that and doesnt work.... as i said when it boot up all apps fail and nothing work sorry my english u can look my post and see what is happening. i think i need to do repair partitions with adb like man in this post.

http://xdaforums.com/showthread.php?p=42010368#post42010368

Thanks for help
[Samsung Galaxy Player 4.0, 5.0] JimiGEE:
Could you shed a little more light on this...I have done so much already so this looks like rocket science to me!
[Off-topic] ajam100:
Does anybody have or know where I can find the Black Berry "Screen Muncher" sound? I saw a friend with the app and once I heard that noise, I instantaneously wanted it as my notification ringtone!
[Off-topic] LordManhattan:
Found it on Zedge, but it's very short. The only thing you can do is browsing YouTube, find a video with good quality sound, download it and extract the audio.
[Droid 2 General] chessknt87:
I am trying to get my phone back to factory default so i can update to GB (and from there to a ROM) but cannot seem to find the appropriate SBF to do so. I was running an old version of Liberty and tried to use Clockwork to reset to a factory default via data wipe, but when I did that I still see the liberty boot screen every time it loads and the OTA update fails to install every time. Right now (after using restore) my phone is using Version.2.2.20.A955.verizon.en.US.

Thank you very much in advance for any help.
[Droid 2 General] Albinoman:
You cannot use the official gb update.zip's if you're already on gb. Use the sbf on this site.

http://wiki.cyanogenmod.com/wiki/motorola_Droid_2:_Full_Update_Guide
[Droid 2 General] chessknt87:
I will give that SBF a try when I get back to my home comp, but I just wanted to note that the phone is running froyo, not GB. I couldn't figure out how to update it to gingerbread within the framework of my old liberty ROM so that is whan I tried to restore it to default (and apparently failed since the liberty screen still flashes on boot despite it having the factory version displayed under phone settings). Even in default though it is unable to update using OTA.
[Desire HD General] zunaedsaki:
Sense 3.0 is very good specially GPS lock up is very quick.thanks to HTC
[General Questions and Answers] ugin4xda:
Does anybody encountered this?

2 week ago, I bought tmobile hd2 us. The phone storage was 650 mb when I first run the phone using stock rom. I install some aplication. storage is still the same. But when I run and played pangya. Phone hunged then I soft reset. The phone has reverted to factory. but I check the phone storage. The storage was 300 mb. Then I run another application. then it hunged again. I again factory reset the phone. then boots. I checked the storage. It had 110 mb.

Then, I installed an energy rom. Phone storage was 710 mb. I used the phone to browse the net for 3 hours. Again my phone hunged. When I checked the storage, went dowm to 300 mb.

Is this the result of the storage not formated correctly that is why the phone behaves that way?

Anyway. Thanks to the maker of energy rom I used. very fast indeed.

I might as well experiment my phone further.

Does anyone encountered this to their hd?

To those who have used hd2 before. What is the nominal phone storage for both stock and custom rom used?
[Samsung Galaxy Nexus] nexx892:
I keep trying but initrd keeps not working :(
[Eee Pad Transformer General] waywardfrantz:
So I've dropped my tablet a few times, and it frequently caught on the audio cord. So now the audio port doesnt work...

considering the teardown http://xdaforums.com/showthread.php?t=1109928 do you think it would be reasonable to resolder this? I can't make much out in the pictures, but it looked like there could be several connections between a chip with the 3.5mm jack on it and the motherboard or something.
[Eee Pad Transformer General] ckoadiyn:
I'm looking in to fixing my jack as well lol
[Galaxy Tab General] ®AndroidDoctor®:
i was restoring my backup rom and i went to reboot but it stays at the samsung galaxy splash screen. so then i tried to reboot in to recovery and it wont let me or its not there. so after that i boot into download mode and my computer doesnt even see the tablet plugged into it. i tried using the drivers in the safe stock zip but its a fail...do i need adb to be installed on my computer to use the download mode...how do i bring my tablet back pls help
[Galaxy Tab General] burhanistan:
Have a look here for unbricking methods:

http://xdaforums.com/showthread.php?t=1133590
[Galaxy Tab General] rkmj:
There is one method that that thread neglects to mention: OneClick Unbrick. I've used it before on my softbricked, (you have a softbrick,) tablets. You can find all the information for OneClick Unbrick here. Good Luck!
[Optimus One, P500, V General] cobra4014:
Okay, I have set up Lupo's CM9 Beta 1 on the new baseband. I have looked up APN's for data and entered all that I have found, but it dosen't seem to save afterwards. I can text and call to my hearts content, but I can't get data to work for the life of me. I was wondering if anyone has managed to get data working on ICS + V20 Baseband, on the Optimus T (on T-Mobile)

I know I'm new, but I preformed searches on here and on the main page for Lupo's ROM, but I have yet to find a mention of the Optimus T. The only ROM I have used with working data on the v20 baseband is Ciaox's OpenOptimus Gingerbread.

Any help? Thanks in advance!
[Optimus One, P500, V General] cobra4014:
*Bump* Please help me!
[Optimus One, P500, V General] ccdreadcc:
switch back to open optimus..
[Optimus One, P500, V General] Kaerper:
That's a bug. You have to wait for a fix.
[Optimus One, P500, V General] Arjen:
Probably you are the owner of one of the sims CM7/9 cannot cope with for now.

It's a known bug but cannot tell you when it will be solved.

Better post this bug at Cyanogenmod-forum.
[AT&T Samsung Galaxy S II SGH-I777] SquidLord:
So I know what it does and what it's speculated to be used for [warranty and such], but is there any other reason I should care about increasing the number on the flash counter? Or is warranty the only reason to avoid increasing it?
[AT&T Samsung Galaxy S II SGH-I777] Miami_Son:
Easily answered by reading the related Sticky in General.
[AT&T Samsung Galaxy S II SGH-I777] SquidLord:
Just lead me back to warranty and the yellow triangle. There's no mention of any other issues with the flash counter, which is what I'm curious about. I'd just like a confirmation.
[AT&T Samsung Galaxy S II SGH-I777] getbuzzin:
Yes
[AT&T Samsung Galaxy S II SGH-I777] SquidLord:
Such as? This is the kind of info I couldn't find...
[AT&T Samsung Galaxy S II SGH-I777] Miami_Son:
You should have posted in that sticky so A) other interested people might see it and answer you, B) other interested people might see the answer, and C) all interested parties would be able to do both in one place.
[Galaxy Note GT-N7000 General] mintu123:
just got my note from italy.updated to latest firmware.everything seems to work.

Only problem with games.seems like some.sensors are not working.i tried asplant hd no control by tilting the device.also played airpanguins same issue no control.can someone tell me

Whats going on with device.

Thanks
[Galaxy Note GT-N7000 General] rogconnect:
There are Nothing wrong with the device!

You need to do some setting on your GAME's control to enable the functions! DUDE...
[Galaxy Note GT-N7000 General] mintu123:
I had samsung infuse for 6 months.played all them ganes without any settings.i just goigle gyro sensor issue.its a ****ing samsung problem with some devices.gyro sensor wont calibrate.
[Galaxy Note GT-N7000 General] dr.ketan:
open asphalt - option - control

control A working fine o my Note