yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] sorg:
For successful flash in Odin, modem and non-hlos parts should be signed by samsung. Signature is at the end of file. But if you dump these parts from device, they will be padded by zeroes to the partition size.

So, after dumping, you need to cut padded zeroes from the "tail". Just start to look the first non-zero byte from the end of dump. And then cut after that byte.

And then you will have valid modem and non-hlos parts. You can TAR them and then flash through Odin.

I highly don't recommend to flash those sbl, aboot, rpm, tz parts. Although they are signed (and will require procedure i've described above), the risk of brick is very high if somehow you flash non-compatible to each other one of these parts.

So, dump them and keep in the safe place for some emergency case, but don't flash them neither separately nor as whole firmware package.

It's ok to flash these parts if you get them inside new OFFICIAL firmware from Samsung server, but avoid to flash them from any dumped firmware.
[Galaxy S 4 Q&A, Help & Troubleshooting] MJHawaii:
Solved Done close thread
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] sanchit0403:
this not a question i just want to request the developer's that please port cm9 for galaxy y if u guys can port cm7 then u guys can also port cm9 i don't have much knowledge about porting but i and i think other xda guys will help in contribution for making cm9 please xda developers now its time for cm9.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] aniket.lamba:
Lol come on man! Most of the devs here are school/college students.They also have study for their exams and have a personal life also.Recently CM7 is ported,why don't you use it! :sly:
[Galaxy S 4 Q&A, Help & Troubleshooting] chintz24:
I need to know that after rooting do I need to do a full wipe on every update?

Also those who have rooted, after rooting are you'll sensors and everything working properly
[Galaxy S 4 Q&A, Help & Troubleshooting] qazmed:
Firstly rooting doesnt hurt device or slowdown in any way

2ndly see when u root u dnt get ota updates but u cud flash them thru odin and when u flash no need to wipe and u dnt loose any data for more guidance refer to samersh72 guide on the general thread by the name how to unroot and unbrick your s4

hit thanks button if helped
[Galaxy S 4 Q&A, Help & Troubleshooting] HS™:
1, No neet to reset after rotting

2, everything works as its suppose to except OTA updates
[Galaxy S 4 Q&A, Help & Troubleshooting] chintz24:
Thanks answered ny question
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] pbpatel1981:
which is new baseband? and what are the different UCUAMDB vs UCUAMDL
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jeffreii:
MDB was the firmware the device was released with.

MDL was the update that came a few weeks later.

MF3 is the current version which breaks the old root/recovery/bootloader exploits.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] ahfu25:
What did the mdl update bring to the table that makes it better than mdb?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Senior Member:
Nothing, really. It's more of a location-based thing, and which one works better for who and where.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] chocodough:
Actually to be more precise, it wasn't the MF3 baseband that broke root/recovery/bootloader.....it was the ROM itself that did.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jeffreii:
I never said it was the baseband! You can flash the modem (aka baseband) for MF3 and be fine. It was actually the update to the bootloader that blew the qfuse.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] athens71:
The new AT&T Baseband version is I337 UCMA MF3.

Not sure about the differences above.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RockRatt:
When it says "Baseband" that ONLY means the modem (radio) that is installed.

View attachment 2173127

Now as far as being able to flash certain Roms that SAY you need to be on "MDL" baseband they are ACTUALLY referring to the FIRMWARE VERSION with THE BOOTLOADER that goes with that firmware and NOT the modem (baseband/radio) being used.

So for instance you can see MY BASEBAND above is "MDL" but my ACTUAL FIRMWARE is still on "MDB" bootloaders. So if I want to flash those Roms that say they require MDL, I would actually need to flash the BOOTLOADER that comes with the MDL firmware to be able to run those Roms. I understand where the confusion comes from on those Roms. BUT if they said you need to be on MDL BOOTLOADERS to be able to flash this ROM you would have others confused about HOW TO FLASH BOOTLOADERS and the riskyness of flashing bootloaders that CAN HAPPEN if someone doesn't understand what they are doing 100%

Sent from My Spiderman Themed I337
[Sony Xperia Z Ultra] zylor:
Open source download for Xperia™ Z Ultra (C6802) (Jelly Bean); software version 14.1.B.0.461.

Sources can be downloaded here:

http://developer.sonymobile.com/dow...s/open-source-archive-for-build-14-1-b-0-461/
[Sony Xperia Z Ultra] sev7en:
Hi,

thanks looking forward for the latest 471 because I can't get it via PC Companion.

Regards
[Sony Xperia Z Ultra] zylor:
Thanks for moving to the correct section :)
[Samsung Galaxy Nexus] myxor:
Hello,

i am just thinking i bricked my Galaxy Nexus.

But first i will describe what happened:

My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.

After arriving home i tried to fix that by removing the battery and give it a few minutes.

But my device was stuck in a bootloop after that.

I tried to reflash ROM and RADIO few times but nothing helped.

I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.

So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.

When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.

I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.

Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.

Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.

Any suggestions how to continue or just rescue my files from the "sdcard" ?
[Samsung Galaxy Nexus] beekay201:
Drop the toolkit, learn how to do it proper or stop flashing stuff before you hurt your device.
[Samsung Galaxy Nexus] myxor:
I guess it's already to late :(

I just tried to install the CWM Recovery via fastboot

But when i select Recovery from the bootloader menu i only get the charging battery icon.

Anything i can do?
[Samsung Galaxy Nexus] iLeopard:
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
[Samsung Galaxy Nexus] myxor:
Thank you for your advices but the results are not what i hoped for:

After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:

sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...

finished. total time: 126.458s
Press any key to exit...

the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
[Samsung Galaxy Nexus] wisefreakz:
Was this issued using flash-all.bat?
[Samsung Galaxy Nexus] beekay201:
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:

- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.

fastboot erase partition_name
fastboot format partition_name

Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.

fastboot flash partition /path/to/filename.img

- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.

Anyways, if you return to the bootloader, and try to

fastboot boot /path/to/cwm_or_twrp.img

What does it do? Can you use your custom recovery now?
[Samsung Galaxy Nexus] myxor:
I ran through the linked post and erased + formated all possible partitions.

Is it normal that o can not format some partitions like the recovery partition?

>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s

:confused:

After that i flashed the partitions once by once per

fastboot flash partitions /path/file.img

with the files from the factory image.

Sadly no boot possible.

Then i tried to boot my recovery by

fastboot boot /path/to/cwm_or_twrp.img

but it happens the same as before:

after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.

After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".

This stays the same after flashing a recovery image via fastboot :crying:
[Samsung Galaxy Nexus] beekay201:
Use omapflash to restore your bootloader. See this thread's post with useful links. http://xdaforums.com/showthread.php?t=1812959
[Samsung Galaxy Nexus] myxor:
I sent in the device to the repair and got it back a few days ago.

Some "broken parts" were changed and i got a new battery.

Now my Galaxy Nexus works again like a charm :)

Don't really know what parts were broken but it seemed that it was a hardware failure.

Thanks to everyone who helped! :good:
[Xperia Z General] weijai:
Download through Sony PC Companion

:) Smoother Boot animation

:) Efficient RAM management, 1784 MB RAM available for usage

:) Home launcher is smoother

:) New UI for Update Center

:) Album app now seems to be a little slower to load photos

:) 3G Signal strength improved

:) Touch response is improved a lot

:) Sleep and Wake times improved

:) Camera Image quality in dark improved

:) Changes in car mode app

:) High resolution image is captured in normal mode with HDR off. ( Around 2.8 MB )

:) No screen flickering

:) No unusual battery reading bug
[Xperia Z General] beni8978:
Thread arleady opened.
[Xperia Z General] nhoc_huhu:
Where link???? Or it is firmware 10.3.1.A.0.244
[Xperia Z General] weijai:
Yes it is firmware 10.3.1.A.0.244

1. Download Sony Companion

2. Update via Sony Companion (Software Update)
[Xperia Z General] hush66:
Already reported days ago and there are many threads in the General section (like this).
[Xperia Z General] weijai:
excitement above all... then miss it completely. thanks
[Xperia Z General] weijai:
For those who get an error "sony update engine failure (error 2003)" during update process,

please RELOCK your bootloader. TQ.

http://xdaforums.com/showthread.php?t=2191907
[Xperia Z General] deadlyheart4u:
Where is this update I have checked for this over the device as well as On Mac, with Sony bridge.

Someone popup with some ideas.
[Xperia Z General] hush66:
For unlocked bootloaders, they would need to use Sony flashtool to update.
[Xperia Z General] weijai:
Check this out:

Download .ftf: http://fs2.filegir.com/xperian/C6603_10.3.1.A.0.244_Generic_CE.ftf
[Xperia Z General] weijai:
For more informations about FLASH TOOLS, check this thread:

http://xdaforums.com/showthread.php?t=2335555
[Xperia Z General] exekias:
If you are rooted then change your build prop to make the update service think you are a difference version pick any of these region codes

fIf you are not rooted, wait
[Xperia Z General] deadlyheart4u:
I am from india, my phone is rooted, what changes shall i make to get these changes i am currently on .423

---------- Post added at 08:32 AM ---------- Previous post was at 07:54 AM ----------

Anyone update
[Xperia Z General] weijai:
Just download .ftf file then flash it using flash tools.
[Xperia Z General] akshay811:
Is this 4.3
[Xperia Z General] SuperHanss:
Nope it's still 4.2.2
[Xperia Z General] Alhaddad:
Is this thread still opened? It makes some confusion.. At least edit the title and include the version number
[Xperia Z General] Jonathan2677:
How about it,can we even count how many threads there is for 244 from like three days ago, then this pops up new,lol
[Xperia Z General] adaa:
I think this is one of the best updates from Sony so far.. I feel a big difference.. Screen white fadeness is gone plus its very smooth overall.. Does anyonelse agree?
[Xperia Z General] joke19:
Not more funny from Sony. The SP wait now long time for a update.

Gesendet von meinem Xperia SP
[Xperia Z General] ImAnurag:
Those who get an error like this , i suggest you turn off your antivirus and its firewall it will work definitely...It works for my always...
[Xperia Z General] :
Its terrible firmware again.... Waiting for 4.3 if we going to have it HURRY UP SONY.... Freaking UK unbranded still on .434 It may the same case as with xperia s. In that case it will be my last sony device for sure.:rolleyes:
[Xperia Z General] warface:
If only there was a way for you to flash the update yourself.

Some sort of flashtool....

If only.....

Sent from my Nexus 7
[Xperia Z General] Ereckson:
True if only..

[MENTION=1191647]donottouch[/MENTION]. Ohh wait someone here has answered your prayers. Your one lucky dude man... People here have taken the trouble and bandwidth just not to see guys like u not cry. So Stop cribbing and start flashing. It's safe and efficient, plus you won't have to whine... Cheers.. And pls don't get offended by my sarcastically rude nature.
[Xperia Z General] egzthunder1:
Thread moved to general and closed as there are several threads of this kind, for this build, available already.
[RAZR HD General] al2fast:
So, I was having some problems, my phone was only rooted, not unlocked. OK a LOT of problems after the latest update with my phone freezing and rebooting. Wiping cache and factory data resets didn't work. Did a data reset and didn't install a single app or widget and still locked up and reset after using it for a couple minutes. I used the droid utility 1.21 by mattlgroff to go back to the 9.20.1, rooted, and then took the factory OTA again and still lockup and reboot machine.

So, called Verizon, told them what I did (minus the mattlgroff utility), and they sent out a replacement to me, 1 year warranty on the phone. I bought the phone from Best Buy, they told me they couldn't do anything unless I got their goon squad warranty. Call to Verizon was fast and painless.

The replacement showed up today, and this is how it was equipped:

9.16.9.xt926

4.1.2

radio 100730.081.64.09P

Kernel 3.0.31-ge491d6d 4/5/13

build 9.8.1Q-62_VQW_MR-4

build date 4/5/13

Had a sticker on the back with the IMEI and software version and a date of 7/18/13.

Good news for me is I was unable to unlock the bootloader on this one because I was a dummy and didn't unlock the bootloader on my last one. So, now I'm back to 9.20.1, rooted, unlocked, and got CWM installed. Now it's time to pick a ROM and start flashing as soon as my new SD Card shows up seeing as I lost everything I had backed up on my SD Card because it died on me out of the blue on Sat, GRRRRRRRRRRRRRR.

If you're having issues with the updates, give Verizon a call and get yourself a replacement. Good chance you can get one that is still able to be modified!
[Verizon Samsung Galaxy S III] jayyskittles:
So, I have decided to build my first ROM from SOURCE :DD But, I really like the Halo feature.. is there anyway to add that to my CM 10.1 repo?
[Nexus 4 Q&A, Help & Troubleshooting] iNOMAD:
I am new to Android, I recently migrated from the iPhone, and am enjoying my Nexus 4 very much.

My Nexus would be nearly perfect, if I did not regularly experience an audio playback glitch.

Randomly, audio playback pauses. The audio sometimes pauses after just 2 minutes of listening, and at other times occurs after 10-15+ minutes of listening... with the screen off. The audio pauses when using any of my multiple pairs of headphones, and even via Bluetooth streaming audio. I believe the issue has also occurred when using the built-in speaker. The audio pauses when streaming via wifi networks and AT&T 3G.

The audio pauses when using the following music apps: Google Play Music, Spotify, SiriusXM, Beyond Pod.

Sometimes the audio resumes when I press the power button. Sometimes I have to unlock the device and the audio resumes. Sometimes I have to press "play" again from the App.

I would love to be able to play uninterrupted audio from my Nexus.

Note: The issue occurred on 4.2.2, and still persists on 4.3.

I have searched for a solution many times, in multiple sources, but have been unsuccessful. Does anybody have any suggestions?

Thank you in advance.
[MDA II, XDA II, 2060 ROM Development] veepee78:
Subject says it all, in case you missed it :shock: :

Does WM2005 have MP3 ringtone support?
[MDA II, XDA II, 2060 ROM Development] johnz:
yes, it has mp3 ringtone support

i copy song.mp3 to root of storage card/storage/extrom or to My Documents and i can set it as ringtone
[MDA II, XDA II, 2060 ROM Development] eFiend:
Every device that have Windows Media Player 10 have mp3 support.
[MDA II, XDA II, 2060 ROM Development] tonyflow:
I have WM2k5 on my XDA, and cant add an MP3 ringtone?
[MDA II, XDA II, 2060 ROM Development] veepee78:
Come'on guys, try to decide. MP3 or not? :D

Which versions of WM2005 do you have?

How about alert sounds and other voices? Are there possibility for MP3?

Hate that MS policy to push their own formats instead of mainstream..
[MDA II, XDA II, 2060 ROM Development] alpacino:
I can't use MP3 as ringtone (with media player 10)

Subj

But I really wanna use MP3 :)
[MDA II, XDA II, 2060 ROM Development] kdodd:
mp3 works ok for me added in root of sd card
[MDA II, XDA II, 2060 ROM Development] eFiend:
Well from settings>System> Add ring tone you can assain mp3 tone for ring tone and alarm tone. Now I'll cut so of my mp3's and I'll make myself mp3 ring tone.
[MDA II, XDA II, 2060 ROM Development] steelorange:
or you can manually put MP3 files in the \Windows\Rings directory of your device :wink:
[MDA II, XDA II, 2060 ROM Development] kdodd:
if u add em to the windows/rings folder then that takes up memory on ur xda, i found that just by having them in the root of the sd card that they appeared in the available ringtones section of phone/options.

so i didnt need to add them, so u can add upto 1 gb of mp3 :)

this was with 1.501 96 2005 btw
[MDA II, XDA II, 2060 ROM Development] alpacino:
guys sorry

I've missed my forum - for blue angel platfrom there are some troubles. you can't choose mp3 from "add ring tone" even after all latest update (WM10)
[Android Q&A, Help & Troubleshooting] RaiderDuck:
The NFL app now will not run on rooted phones (per both Android Central and my own experience). If anyone could fix this, I'd be MUCH appreciative. Thanks!
[Android Q&A, Help & Troubleshooting] SayWhat10:
Why, what can rooted phones do that the NFL doesn't want us to?
[Android Q&A, Help & Troubleshooting] RaiderDuck:
Excellent question, and one that a few hundred people on the Google Play Store are asking when leaving one-star reviews.
[Android Q&A, Help & Troubleshooting] mulletcutter:
NFL.com app is pretty worthless, as long with NFL.com website on androids.
[Android Q&A, Help & Troubleshooting] nrfitchett4:
The Verizon version gives you live broadcasts which is why it's worth it to us
[Android Q&A, Help & Troubleshooting] SayWhat10:
Audio or video?
[Android Q&A, Help & Troubleshooting] nrfitchett4:
We get video for mnf, snf, and thursday games and radio broadcasts for both teams for all games

Not a bad deal is they would leave root users alone. Giving it a week then I will cancel if the community hasn't figured it out.
[Android Q&A, Help & Troubleshooting] SayWhat10:
Cancel? You have to pay for nfl app on Verizon?
[Android Q&A, Help & Troubleshooting] Sackboy193:
Try this!

https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot
[Android Q&A, Help & Troubleshooting] CNexus:
Block removed. Enjoy!

http://xdaforums.com/showthread.php?t=2395333
[Sprint LG Optimus G] Okazar:
I just got the LG optimus g e973 and before the rooting and bootlock unlocking i was able to get into the hidden menu by pressing 3845#*973#. Now when i try to get into the menu again the only line that appears is "null"

You can press it / hold onto it but nothing happens.

Did the process remove my hidden menu?

Would i be able to get into it with another program if thats the case?
[Sprint LG Optimus G] engine95:
Our Sprint phones are 970. So try 3845#*970. I have no idea how you made 973 work. Unless you are not on Sprint, and are on the International. I think that's the 973, which is another forum.
[Sprint LG Optimus G] Okazar:
Ahh thats correct. Im in the wrong forums. The phone is 973(Canada). ..nonetheless i believe my problem is an OS related problem.

Like i said before I was able to get into the RF status menu but upon changing the buildprop ( to fix wifi stick problems), bootload and root Im not able to get the menu again
[Sprint LG Optimus G] engine95:
I think there is a thread here about the hidden menu. I think autoprime made it but I'm not sure. I can't help with this either, sorry.