yashsingh1/xdaforums huggingface dataset:
[Streak 5 General] dwadetiu:
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. :(.. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens :(.. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
[Streak 5 General] Streak4ever:
RTFM

http://xdaforums.com/wiki/index.php?title=Dell_Streak
[Streak 5 General] dwadetiu:
Hi again guys.. and mr lordmorphous!

im following what you told him (aaivazi)..

I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.

Download the drivers from Dell. Here's the link:

http://support.euro.dell.com/support...&fileid=433681

Install them and reboot your pc.

Download MultiRecoveryFlasher from here:

http://xdaforums.com/show....php?t=1000455

Extract it to somewhere on you pc where you can find it.

Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.

Download the recovery.img for 360 (which I think you have already done)

Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.

Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)

Verify the phone displays fastboot ready

Open a command prompt on your PC

Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img

(im already here but this is what the command prompt says:

'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.)

what should i do :(?
[Streak 5 General] dwadetiu:
hi streak4ever thanks for reply.. what does RTFM means? thanks
[Streak 5 General] Strephon Alkhalikoi:
LOL

RTFM = Read The F**king (or Fine) Manual.
[Streak 5 General] dwadetiu:
sorry.. now i know the meaning of rtfm :).. thanks for the info..

---------- Post added at 05:53 AM ---------- Previous post was at 05:46 AM ----------

Hi again guys.. and mr lordmorphous!

im following what you told him (aaivazi)..

I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.

Download the drivers from Dell. Here's the link:

http://support.euro.dell.com/support...&fileid=433681

Install them and reboot your pc.

Download MultiRecoveryFlasher from here:

http://xdaforums.com/show....php?t=1000455

Extract it to somewhere on you pc where you can find it.

Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.

Download the recovery.img for 360 (which I think you have already done)

Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.

Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)

Verify the phone displays fastboot ready

Open a command prompt on your PC

Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img

(im already here but this is what the command prompt says:

'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.)

what should i do ?
[Xoom General] bathanr:
I tried to use the rooted 3.2.2 rom that was listed under development, but I could never get my wifi to connect. Now I am unable to get my 4G to work. I used to have the option to choose preferred network mode LTE/CDMA, but now that no longer shows. I am on 3.2.2 using build HLK42B.

I was wondering if someone who received their xoom back from the upgrade has the latest image I can try.
[Xoom General] hammer4203:
Tell me how to dump it. Never done it before. I am n stock 3.2.2 fresh back from the upgrade.
[Xoom General] bathanr:
I wish I knew.. I will have to research that.
[Xoom General] short/y:
I just posted an upload link over at http://xdaforums.com/showpost.php?p=18204881&postcount=13
[Xoom General] AceXMachine:
You need to flash the modded recovery, then in adb shell, run

mount /data

mkdir /data/media/Stock

dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/data/media/Stock/system.img

dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/media/Stock/boot.img

sync

Then reboot and pull the files, should be in a "Stock" folder on the internal storage.

*Thanks to solarnz for these instructions
[Xoom General] bobbydiv:
4G LTE

I got my Xoom back some time ago. I've been waiting to root it until it came back. (Really didn't want to go through it, and have to undo it just to figure out how to do it again)

I'm trying to find the official file from Moto for the HLK42B build that came back on my 4G Xoom. I'm on the Moto Dev site, but they only have up through the 3G upgrade listed. Anybody know where I can get the official file in case anything goes wrong? I want to make sure I have it, before I start.

Thanks
[Xoom General] 3_D:
Thanks Ace, it worked for me. It wasn't rooted because I imediately got and updated to HLK57D
[Xoom General] Brenardo:
Thanks for the img files. They will save many headaches for a lot of people.

It is a damn shame that Motorola will not post the updated img files though...
[Xoom General] zarkuu:
I've tried both Ace and Shorty's backups. They seem to work restore fine but I still can't get any 3G/4G data. I've tried both HLK75C and D. I've done many factory resets and cache wipes. I had VZW send me a new SIM card which they manually activated while I was on the phone with them and according to their end they can see my Xoom contacting the tower but there is no activity beyond that. I really never believed that was the problem since I was able to swap SIMs with my Bionic and the Bionic worked great with the Xoom's SIM (but not the other way around of course).

I'm still suspicious about the radio Baseband version. I am missing the second "ltedc_u_05.19.00" that I've seen in HLK75C screen shots and I don't have the option to select a network mode under Mobile network settings that I know needs to be checked. This makes me think my Xoom's hardware is ok since it is able to talk with the tower over the 4G modem for activation, however the OS software is not able to select the 4G radio for actual system use. Are the radio files built into the system or boot images? Where do the baseband versions listed in About tablet come from and how might these be backed up/restored? I've never really bothered flashing radios before so this part of the process is new to me. I'm really hoping this can be solved without having to return the device to Moto.
[Xoom General] dethrok:
This is my same exact problem. Can't seem to figure out the baseband problem.

I wonder if anyone has contacted Motorola regarding a way to flash the baseband to the LTE 4G version?
[Xoom General] Jewremy:
Hey guys. Been going through the same ****. The MEID/ESN changes with LTE upgrade. Adds a 01 or 02 to the end of the ESN. If you downgraded and took updates, it modified your baseband, taking out the LTE part of it. If you go back to HRI66 and do the CDMA activation thingy, you should be able to re-activate on 3G. Yeah, it sucks, but what else can we do? We need that OTA to re-flash the LTE baseband.
[Xoom General] hammer4203:
You can get the hlk75c which is rooted then take the hlk75d update and reroot using the universal root method. That will put you back.
[Xoom General] dethrok:
Oh, duh, it's so simple. I'll definitely be trying this when I get home from work today.

If it works - you will be my savior.

Scratch that - it didn't even reactivate my 3G.
[Xoom General] zarkuu:
I don't think that will work unless you open it up and physically remove the LTE modem. my understanding is once the LTE modem was installed the internal 3g modem is deactivated. Even if this did work it would deactivate your SIM card so you wouldn't be able to use LTE in the future without getting a new one. I had the idea to switch my currently useless Xoom data plan over to my old OG Droid and then wifi tether. I asked VZW about switching and found I *could* do this but going from a 4g device back to 3g would deactivate the SIM card and I won't be able to switch without getting a new one. Too much trouble in my opinion.

I spent about 2 hours in a Verizon store yesterday after 2 hours on the phone the previous night and eventually ended up with an RMA with Motorola. I'll be returning it to them and hopefully it will come back correct in about a week. Such a hassle when I could probably flash this myself if I had the right files but at this point I don't know what else to try.
[Xoom General] BenDug:
Can you repost link please. I am trying to get this on a Mac running OSX and I cant seem to unzip the file. Any suggestions?! PLease HELP!!!

---------- Post added at 09:22 PM ---------- Previous post was at 09:09 PM ----------

how do you unzip HLK75Csystemboot.7z on Mac OSX??? Please Help!!!
[Xoom General] Rem3Dy:
download 7zip or use winrar
[Xoom General] zone23:
This does not work I've tried it a bunch of times in different fashions. I even flashed 3.2.2 then flashed the official recovery took the next update and nothing. Actually its been said that HRI66 over rights stuff that we need. Take that with a grain of salt.
[Xoom General] Jewremy:
Yeah, it does. The radios are in the bootloader, aka mmcblk1p1, aka the ebb partition.

Theoretically, we should be able to get a dump of the post-upgrade bootloader, dd it over our borked bootloaders and have it working. Problem is, getting that dump and figuring out how to do the flash. We definitely don't want to do it in a powered up system...that leaves recovery or fastboot.
[Xoom General] zone23:
It restores your device but it will not bring back 3G/4G. If it does please tell me how because I've flashed it a few times and it did not bring back 3G.

Actually in reading your post a few times you say it yourself that its a borked bootloader. Flashing HRI66 will not fix this. If it did we would be finished and we could close this thread.
[Xoom General] kcrudup:
Hope this helps someone, then: http://dl.dropbox.com/u/12011163/hlk75D-ebb.zip

The problem I see is that the radio code has to be FLASHED to the radios- and I know there's code in the upgrade.zip that does that, plus those radio images are much bigger than the 3MB bootloader.

If you disassemble one of the ...-to-hlk75c images, it'll have the files you need and the procedure (and I think the radio images are true files, and not .p files).
[Xoom General] zarkuu:
Ok that's interesting. The md5sum matches mine so I'll have to assume that something else goes on here. Out of curiosity if you do a BP tools boot (power up normally and press both volume up and down at M) does it say "LTE radio is off"? Maybe that's normal at this point in the boot process and a red herring to this investigation.
[Xoom General] Jewremy:
Yeah. Been trying to get my bootloader to update. Bigrushdog has a file out there that updates the bootloader using Motorola's method - I've tried and no luck.

I managed to get that dump into a .sbf file - CG44 for reference - still reads as version 1045, even though you have 1050. The posted MZ602 SBF has the proper radio images. I'm thinking the new bootloader is in misc, aka mmcblk1p3. Dunno what code group that is, or what's in it. And I don't recommend using cat or dd to overwrite it. #xoom on freenode if you want to chat.
[Xoom General] scotto811:
My sad story;

1> Updated to the solarnz build after i got my xoom back with 4G and lost wifi

2> Tried going to build 1.0 to fix wifi - NO HELP

3> Unrooted and flashed back to 3.0 build and did all OTA updates - Fixed wifi, broke 3/4G

4> did this;

http://xdaforums.com/showpost.php?p=18224303&postcount=6

-NO HELP

5> Installed solarnz build 1.1 again to try and fix 3/4G - NO WIFI OR 3/4G!!!

Going to verizon tomorrow (or should i say today? It/s 415am here) to try and dupe some 18 year old into giving me a new xoom bevause "Mine never worked since i got it back" - Lets hope this works!!!

Updates to follow
[Xoom General] Jewremy:
Solarnz' build is not an upgrade. HLK42B is his, it ships back with HLK75D.

When you downgraded it overwrote your bootloader to version 1045, aka 1.45.

The bootloader you need for LTE to work is 1050, aka 1.50.

Nothing to do but wait. Going to VZ won't help.
[Xoom General] hammer4203:
How do I rip the bootloader out? I am still on 1.5.
[Xoom General] Jewremy:
Can't. We've tried. Normally, it would be dd if=/dev/block/mmcblk1p1 of=/sdcard/ebb.img

Then either a) put it into a special .zip or b) unpack a bootloader flashing .sbf, rename the dump to CG44.smg and re-pack it into the SBF.

Method B is riskier. But yeah, we've tried.
[Xoom General] TheKicKer69:
MD5 Mismatch - doesn't work
[Xoom General] scotto811:
I know..... :(

Didnt have time today, but going to see if VZ will swap it for me. It's worth a shot! :/
[Xoom General] hammer4203:
Someone needs to take hlk42b down! People keep flashing that crap and it ain't right! I swear someone thinks it's funny to point people to that build knowing it downgrades people!
[Xoom General] bobbycardwell:
I know this does not fix the bootloader issue but here is a fresh nandroid of my Xoom. Just got it back from Motorola after doing what you all did and crapped out my Xoom. Had to send it back for "repair". This is a clockmod backup. This will put you back to factory after 4G upgrade if you have not destroyed your bootloader. Good luck!

dl*dropbox*com/u/3251529/clockworkmod*zip

(replace stars * with periods . )
[Xoom General] scotto811:
THIS!!! :mad:
[Xoom General] oldblue910:
Hi everyone,

Being as I'm kinda new to the Xoom and the architecture of the radio/bootloader, I read this thread verbatim but still have a question...

Are the radio and bootloader separate partitions or are they combined. Someone mentioned the radio files are in the bootloader, so I wasn't sure what that meant exactly. For instance, on the Nexus S, you have a bootloader image and a radio image that can be flashed using fastboot (fastboot flash radio file.img, fastboot flash bootloader file.img). Is this not possible with the Xoom?

When I open up the HLK75F-from-HLK75D OTA update for MZ602, I see a 24 MB file called lte_bp_gota.img. Judging by the filename, I'm guessing that's purely the radio image, but is the bootloader in that as well somehow? When I look at the update script in the ZIP file, I see the following line:

assert(motorola.motoflash(package_extract_file("lte_bp_gota.img")));

Seems odd that Motorola would have their own radio flash utility (in lieu of something like write_raw_image which is more standard) unless they were combining the radio with something else (perhaps the bootloader?)

Can someone satisfy my ever-curious brain and shed some light on how this works?
[Xoom General] amysdadforever:
im glad this thread is not dead yet!! but can someone please help me out I've been stuck in loop holes in trying every method in getting my 4g to work. I have the bootloader to 1.5 and confirmed it through RSD ive flashed all the stock images for 3.2.2 wifi seems to work but in the status network is unknown, mobile network is unknown, service state is out of service, mdn and meid is unknown baseband is still showing unknown any ideas would be greatly appreciated!!!! Wow my first post

---------- Post added at 10:30 AM ---------- Previous post was at 10:25 AM ----------

Hey was wondering if you still have that backup would like to try if this fixes my 4g problem downgrading my xoom from 3.0

I've flashed 1.5 bootloader so hopefully by me running your backup file it might fix my problem because im running out of patience and time trying to figure this out!!!
[Xoom General] fudsak:
I was messing around with my Xoom trying to unlock/root it and accidently used an incorrect boot.img. This thread and Ace's backup saved what I thought was a bricked device. Thanks a bunch.
[HTC Sensation] johnpatcher:
Hi,

I've made my first steps with the dsixda's Android kitchen, which worked out well so far. However I've realized that the ROM will get signed during the ROM creation.

Now I'm wondering what the purpose of this is. What advantages do I get? Are there any downsides? After I've got some basic knowledge about cryptography,

I can see why OEMs are using this, but in contrast we don't have their private keys, whereas everyone downloading the kitchen can get the private key and have s-off devices anyway.

Furthermore in order for this model to work properly the public key (or some sort of root certificate) must be put on the device, so the device then can check against it. I suppose S-ON is exactly doing this, as only signed code can be executed.

So what is this ROM signing about? I've searched for reasons why to sign a ROM, but could only find instructions how to do it without any background information. What are these keys used for? I hope it is not used as root certificate in any way, so that packages signed with the publicly available private key can be installed/executed without any warning. Does it make it sense to generate a pair of keys for myself or will the private key will be included in the ROM anyway?

Best regards,

johnpatcher
[HTC Sensation] EddyOS:
Just sign it, means you don't need to know! If you don't sign it no one can flash it unless they disable signature checking
[HTC Sensation] johnpatcher:
Well, I tend to want to know what I'm doing, especially because I'm interested in cryptography and try to have security in the back of my head always ;). Basically I don't want to include some (private) keys I don't know anything about and the reason why they are needed.

I don't see any point in the signing, beside some basic verification whether the ROM is damaged. Every harmful change done by someone on purpose will also change the included private key, so basic hash functions would also do the job and would be a lot more efficient. So I think there must be a better reason for this public-key crypto. Any clues?
[Windows Phone 7 Development and Hacking] Knochen1981:
Hi,

here in Germany there is no Marketplace for Podcasts and podcast streaming.

I found a way to add Podcasts on your Device in non US Countries using WP7 Root Tools (So Samsung Only ATM)

Simply browse the registry under Local Machine/Software/Microsoft/Zune/Settings

There u find a String called XUID locale

change it to EN-US and exit Root Tools.

Open up Marketplace and go into Podcasts add the Podcasts u want to, configure them and leave Marketplace.

Change back the XUID via Root Tools and go into Music Hub.

Your added Podcasts are under Podcasts. U can still stream or download or change settings for them. To stream press the marketplace section and the the play button before the Episode.

For Custom Background images u have to work more and be patient :)

Open up Music & Video Hub

go into every artist an let the pic beeing downloaded.

In my case all those pic have been low low res :)

The Pics will get stored under My Documents/Zune/Content/0800

02/art is for collection

08/art is for the Artists under the new section

In these folders there are pics called

3a.jpg

3b.jpg

37.jpg

5a.jpg

and more

So u have to know wich pic belongs to wich artist.

Here is how.

Play a song from the Artist u want to change the picture

In root tools check the registry under

Current User/Software/Microsoft/Zune/MusicVideoHub

there is the path to the image from the Artist.

Lets say its 3a.jpg

Create an Artist Pic on your PC.

Resolution 960x800 looks best for me.

Use jpg Quality 9 in Photoshop to keep performance of the Zune Hub

Now download Filedeployer from Heathcliff and create the following folder on your PC

XX-XX-XX-XX-My Documents

in there create a few more folders

Zune/Content/0800/02/art

Follow the Tutorial in this Thread

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

and deploy the xap.

You have to do this for every artist pic but you can deploy them all in one filedeployer.xap

U can even add Pics to artists that doesnt have one, u just have to find out wich id the artist has on your device.

To do this create a dummy picture calle 10.jpg and deploy it to the zune content 0800 folder

Zune sets ID in sync Order (always letters first like 3a-3f then Numbers from 30-39)

Example

If you sync like this

1.Alice in Chains

.

.

5.Danko Jones

.

7.Tricky Woo

then Zune will set

1 to 3a

5 to 3e

7 to 30

Lets say all Artist between 1 and 5 doesnt have an Artist pic and the folder only contains 3a.jpg, 3e.jpg and 30.jpg

Copy your dummy file to this folder and rename it to 3b.jpg

Then Check the Artists synced after Alice in Chains.

If you found it write down id and artist.

Then rename to 3c.jpg and again check all Artists synced

between 3b and 3e.

Its a lot of work but you will have high quality backgrounds even on your lockscreen :)

Sorry for my Bad english :)
[Windows Phone 7 Development and Hacking] clfosk:
This is awesome. Some of the backgrounds Zune has on file are horrible quality and it looks really bad. I'll have to try this. Thank you.
[Windows Phone 7 Development and Hacking] tomhop:
Update on artist background

Thanks for the tutorial. It's really helpful. I decided to try and fill in the gaps in my collection and update a couple. A word of warning - it's a really time consuming endeavour and you probably have many more artists than you think.

I found a couple of differences (and builds) on the original article.

1. My 800 folder (where the backgrounds live) had two subfolders (15 and 16 in my case), both of which contained background files.

2. Mine were all of the format xx_bg_art.jpg the first two 'x's can be anything 0-9 and a-f (hex)

3. Mine exhibited virtually no recognisable pattern to fill the gaps. However I did come up with a ruse to find them. Using a file renamer, take a blank image and make 100s of copies and rename them to cover all the options 00_bg_art.jpg through to ff_bg_art.jpg. Dump these all on the phone (using the technique described above which is easier than it sounds) in all the folders that you have - you can figure this out using explorer in root tools. You'll be able to then read off background name for all artists using root tools and looking at the current background - again as described above. You then remake your set and copy them across (they will overwrite the dummy files).

(NB, there's currently no easy way to delete them again so keep the blanks really small).

I didn't do this but an even easier way to do (3) would be to include the file name in the image (perhaps using scripting in photoshop). These could then be read directly off the screen.

Oh, and before you do upload your batch to your phone, take out any where there already is an image downloaded, which you want to keep.

HTH.

Tom
[Windows Phone 7 Development and Hacking] Knochen1981:
UPS you are right.

They are called xx_bg_art.

As I wrote, the pattern is the sync order not alphabetical.

So when U sync Led Zeppelin and then Bad Religion it will give led zeppelin the lower id.

Anyways I think its worth the time cause the Zune Mplace pics are so annoying low red.
[Windows Phone 7 Development and Hacking] GoodDayToDie:
FWIW, the registry change (changing the locale) is possible on HTC and LG phones as well as Samsung, no problem.

The filesystem access is also possible on HTC phones, if you don't have the latest HTC update (because that update blocks the HTC filesystem acces DLLs used by TouchXplorer and such).