yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] marcelol:
Your MIDI56.sa.cab has problems

Not that it matters that much to some folks...but in case you have an XDA-1 /MDA/PPC Phone Edition....I can confirm the following:

1. With WM2003, you will definitely need the Camera------.cab file installed, plus the MIDI56.sa. Mind you, you will have to install the MIDI56.sa file first, and then install the Camera------.cab

2. It will use up about 600+ K of needless memory on your XDA-1 because obviously, we don't have camera's. So.....what're you to do ? Well, go to

\WINDOWS

and look for Camera.EXE ( approx 500+ K )

Then, what you can do is launch Album, and look again at the \WINDOWS directory...and you will see a bunch of bitmaps obviously ( among other things ). Now..what you're looking for is files dated from 8/20/2003 ( that's 20/8/2003, for you folks EAST of the Atlantic ). Primarily they're bitmaps that were used by the Camera application. They add up to about 50-60 K. There's probably more files associated with the Camera.exe application that you won't need, plus any references in the PPC's registry will probably need to be ferreted out.

But...once you've done that, you've actually reclaimed approximately 800 K in space. Which on a 32MB unit, is a fair bit of memory.

Enjoy !

Marcelo
[Windows Mobile Development and Hacking General] ramram:
Re: Your MIDI56.sa.cab has problems

Marcelo,

I updated the installation instructions,you needed more to read about it.

Mind you, it doesn't matter what you install first cos I had the camera and album files in ppc b4 the midi cab file so it's ok.

Actually it's taking more than you are claiming, since those files installed in the \WINDOWS you can move them to "\Storage card\Album\Album.exe" "\Storage card\Camera\Camera.exe" like I did and gain back the used space ;) , there's also a help file related to the camera it's about 56 kb you could remove it from "\WINDOWS" plus the little bitmaps. Thus you can as well fix the path in the registry for the files associations + making new shortcuts for the Album.exe,Camera.exe and by replacing them on the old ones.
[Windows Mobile Development and Hacking General] marcelol:
Excellent !!!

I have to remind people that you MUST be careful when deleting the little bitmaps...look at them inside of Album first before deleting anything.

I had to reinstall my GPRS Monitor application because I deleted one of it's bitmaps by mistake....word to the wise !!!

Also I found TONS for MIDI files ( amateur ones ) to use as ringtones....,now if there were a way to make the ringtone directory point to my storage card, that would be great !!

Here's the link

http://www.ifnimidi.com/
[Windows Mobile Development and Hacking General] ramram:
TIPS

Marcelo,

Moving the ringtones to the Storage card that was my other issue since a long time. I managed a way to do that it. Well for the first try it was successful but when the ppc turns it self off and some one calls you you’d hear the "windows default" ring :( and it remains whether you selects another ringtone. I kept a backup up on my registry to restore it back to the last status.

So if you like to share me your assistance I'd be grateful.

I'll give you tips of doing that ;) and the project from here it starts…

------------------------------------------------------------------------------------

P.S: I recommend a backup on the registry b4 applying those tips

===============================================

1- (Looping Ringtones)

This tweak works perfectly you should apply it to your ppc's:

While playing a wav or midi or a wma as the ringtone the phone has a delay of 3 seconds before repeating, now this is really annoying if you've just created that great wav,wma ringtone, spent time making it loop properly in sound editor or whatever, and then the ppc does the silly delay, well, here’s the fix...

Open the registry editor:

HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0

Select 'Values'

And modify 'Script' by removing the w3 (eg. change 'av0pw3r' to 'av0pr')

"w3" stands for "Wait 3 seconds" you can make it "w1" or "w4" or remove to make the ringtone loops ;)

===============================================

This tweak works for the first time you do it but when the ppc turn it self off the ringtone you selected won't play again :S be noticed.

2-Ringtones on SD/MMC Card

Open the registry editor:

HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0

Select 'Values'

Select 'Sound' and change the Value Data: \Storage Card\path to wav\wavname (eg. \Storage Card\Ringtones\mytone.wav)

We need here more try about this tweak and good ways to fix so ppl let’s do some tests :)

===============================================
[Windows Mobile Development and Hacking General] Biso007:
This is the registry key where all ring tones s/w is playing whenever it comes to customizing a phone ring tone ... including PZP

and that's why all these s/w keeps a "live" component in the back ground to override what Windows is updating each time.

So, PZP was designed as today plugin, so Windows will force it to update the ring tones with each system referesh ... other s/w may keep a background process DLL running or to reconnect cprog.exe to their DLL ... or even to trap the system events to cprog.exe and redirect them to their handler.

So, I think (I might be wrong too :oops: ) the trick is to build a live demon to keep updating this registry key.
[Windows Mobile Development and Hacking General] auburnham:
Necessary Files

I've been able to cut the necessary files for polyphonic ringtones down to ~570KB. Keep in mind I did this on a device with a ROM that was already cooked with supposed "support" for polyphonic ringtones, so there may be other files it is relying on. At any rate, the kitchens need to be updated with these files, because it doesn't work as-is.

There also may be ways to trim even more down, but this is what I have after many hard resets and adding/deleting files one by one. Hope it helps.

Shawn
[HTC Droid DNA] robertmoore208:
What are the requirements to port it to our phone? And if we meet those whom would we ask to get it ported? I would do it but my knowledge only goes as far as unlocking, rooting, and flashing roms. Sorry if this has been answered already. :D
[HTC Droid DNA] Bigandrewgold:
To have an 'official' rom, I would assume someone in their team would need to own a DNA.

But once cm 10.1 gets a little bit farther in development people will start building/porting all sorts of stick based roms, including pa
[HTC Droid DNA] Cdoan34:
I believe we need the IRL for any stock based roms. Its why we are stuck on sense roms for the moment.
[HTC Droid DNA] Bigandrewgold:
You do realize there's a cm 10.1 rom that's almost fully functional now. Only things not working are camera and like 1 or 2 things with bluetooth.
[HTC Droid DNA] Cdoan34:
oh i dunno. thats just what i'v heard.
[HTC Droid DNA] karn101:
What's an IRL?

Do you mean RIL?

Because that's the Radio Interface Layer. And if that's what you are referring to then it's been pretty much cracked. You should probably take a look into the Original Development forum.
[HTC Droid DNA] Cdoan34:
yea RIL is what i meant XD thanks, i'll take a look!
[HTC Droid DNA] Upstreammiami:
ril is already working and that same ril is also working on miui v5 there's 2 developers working on it .. have no idea when they are going to release it
[HTC Droid DNA] Phaded:
Ugh... Just stop

Also I thought you were switching phones?
[HTC Droid DNA] orangechoochoo:
They're holding back on it just as they're holding back on the 2.xx unlock method ;)
[HTC Droid DNA] nimrodsv:
The bottom line - as long as there is no daily driver rom for CM10.1 there wont be any rom that based on it, AKA PA, Liquidsmooth etc
[HTC Droid DNA] Phaded:
he was making a joke lol
[HTC Droid DNA] skynet11:
I'm actually looking forward to efforts to build straight AOSP for the DNA, since Paranoid Android on Nexus devices actually moved from a CM base to a straight AOSP base. Also, one of my favorite Galaxy Nexus ROMs, BAMF Paradigm, is based on straight AOSP (though I prefer the extensive feature set of AOKP on my Nexus 7 tablet).
[HTC Droid DNA] Upstreammiami:
Get off my nuts dude Jesus Christ
[HTC Droid DNA] orangechoochoo:
He needs developer support to do that, unfortunately there's none here.

Anyway, I thought you're getting a Note2?
[HTC Droid DNA] Upstreammiami:
I'm still waiting for a trade
[HTC Droid DNA] mikef:
Have you considered our partner site swappa.com/? You can use your XDA account to login there. I haven't done anything on it but I have heard good things so far.

Thank you,

mf2112

XDA Moderator
[HTC Droid DNA] Phaded:
Hahaha, +5000
[HTC Droid DNA] jamiethemorris:
I didn't know they were aosp based now. I would love pa on this phone. I always end up coming back to it on my n7. For some reason I can't use aokp based ROMs because the keyboard always crashes but aokp would be badass on our phone too.

Perhaps someone could port some of the aosp/cm based ROMs from the one over to the DNA.
[HTC Droid DNA] MustafaHadaKing:
i got pac/parnaoid android booting still some issues. lots of stuff to fix
[HTC Droid DNA] pio_masaki:
What issues? Its running fine so far for me, may be able to help each other out here. PAC I mean, not PA on its own.
[HTC Droid DNA] robertmoore208:
You are the f'n man, you rock!!!!
[HTC Droid DNA] amit_sen:
can u share ur build ?
[HTC Droid DNA] TheDanimal:
Are they both based on CM?
[HTC Droid DNA] amit_sen:
PA is based on AOSP.

PAC is based on CM.
[HTC Droid DNA] TheDanimal:
Is the radio working? Your screenshot doesn't show any signal bars.
[HTC Droid DNA] Bigandrewgold:
I would think its working, or it won't be hard to get working, because cm 10.1 has working data.
[HTC Droid DNA] TheDanimal:
Right. On my AOKP build the radio didn't quite work right on the initial boot but after power cycling it worked fine.
[HTC Droid DNA] t1gartist:
regarding miui i pulled off until 4.2.2 version comes out to many issues with the booting. after several and i mean several trails i got one time of optimizing apps made it 3 apps then shutdown and bootlooped and yet to get back so i wanna wait but for now im working on a asop build hope it goes better then miui lol
[HTC Droid DNA] pio_masaki:
I didn't have my sim card in it, while I was testing I had my gnex in use instead. Radio works fine.

Tapatalked from my HTC DNA - PAC v22.1.1
[HTC Droid DNA] SHANENATAS:
I rooted my Galaxy S player 5.0 and love it with Paranoid Android. A little buggy with a few things but overall Grrreat!!!
[HTC Droid DNA] vbanagas:
I believe it's only a matter of time before we see a build considering CM10.1, AOKP and PAC ROMs are already out there and close to being fully functional.
[One (M7) Q&A, Help & Troubleshooting] stran0014:
*small rant, question's in bold*

Forreal tho I'm on jellybean 4.1.2 build version 1.26.502.10 and boomsound is loud as hell.

I been playing around with custom kernels and roms and noticed that the newest update (build 1.29) reduces the max volume noticeably.

..Reading around the forums confirmed this also.

For comparison, 1 click up from mute on 1.26= 3 clicks up from mute on 1.29

Has anybody figured out what the changes are that HTC implemented that causes this?

I read another post somewhere in the elementalx forum that HTC said these speakers are capable of 93db! So why can't be have that?

Hell one of the main reasons why I got this phone was because of the amplified dual stereo speakers, if I want to blow them then let me but best be assured I'm gonna be jamming until they go.

I hope there's some dev out there working on making this phone's speakers reach their limits for us. I'm gonna be staying on 1.26 for awhile and enjoy my loud volume. I'll be definitely keeping a backup saved in case I decided one day that some rom's tweaks and stuff is a better tradeoff than louder volume.

*end rant* But seriously tho.. Can I haz even louder volume plox? Lol
[One (M7) Q&A, Help & Troubleshooting] Blue1k:
This is a kernel issue already addressed due to released source not being complete. Hopefully will be fixed soon!!
[One (M7) Q&A, Help & Troubleshooting] stran0014:
Hopefully! And here's to hoping that a dev 1ups HTC and creates a tweak that unleashes the amped speaker's full potential!
[LG Thrill 4G] shamike0820:
I have rooted my lg thrill using ClockworkMod Recovery v5.8.4.3 a while back.I noticed the battery would drain fast.So I wiped the data on the phone thinking that would help I did not make a back up.When the phone booted back up i see the lg logo then it takes me straight into cwm. So I downloaded a rom to put on there.It said the rom installed. But when I reboot again I see the same thing lg logo then cwm.Is there any thing I can do now or is it like a concrete brick?

I also tried to install omap drivers and couldn't get them installed. Please help
[LG Thrill 4G] pete3000:
http://xdaforums.com/showpost.php?p=39693262&postcount=9
[Galaxy Note 10.1 Original Development] Ralekdev:
This unlock was basically identical to the second Galaxy Note 2 unlock except I had to add a few more tweaks because we're shoving a modified N8010 bootloader onto the i925.
[Galaxy Note 10.1 Original Development] BeansTown106:
great work guys as usual! you guys never cease to amaze me :)
[Galaxy Note 10.1 Original Development] JasonGeiger:
Does this install the same TWRP version as Dees-Troy is working on in this forum? Just curious because that one is pretty rough with touch issues and it would be great to have a more functional one. I have the 8013...

Sent from my note 2
[Galaxy Note 10.1 Original Development] pro_b:
I have the U.S. Cellular i925u. Is there anyway to get this to work. I'm not interested in keeping the 4g capability. I'm ok with using WiFi only. I tried using the Casual install but it failed.
[Galaxy Note 10.1 Original Development] AdamOutler:
This was packaged from the TWRP nightly released last night.

CASUAL will let you root, but it won't install files that will damage your device. Even if it would, it's a bad idea. This is an IROM unlock, intended for Verizon devices only. IROM unlock means you can flash anything you want including files that destory your device.

You don't need this if you can flash custom kernels and ROMs. We have taken down all defenses here. If the U.S. Cellular version is locked down and you cant flash kernels/ROMs without it, I can release a new, updated version.
[Galaxy Note 10.1 Original Development] Spectredroid:
This is so awesome man. Great stuff, beans is right, you guys really never cease to amaze. Now I need jellybeans Rom on my jail broken note 10.1. Ahem..................... I think we know who I'm talking to. :p
[Galaxy Note 10.1 Original Development] pro_b:
Thanks Sir. The U.S. Cellular version is locked down like the Verizon version as far as I can tell. Since the US Carriers decided to do the same crap with the bootloaders. I have root using framaroot but I'm unable to install a recovery or flash a kernel.
[Galaxy Note 10.1 Original Development] AdamOutler:
Hit me up on an email with the output of terminal emulator command "cat /system/build.prop"
[Galaxy Note 10.1 Original Development] rspong:
Update: rebooted windows 8 and the install went through fine.
[Galaxy Note 10.1 Original Development] drozek:
Adam,

So here is what I am seeing, see the pictures attached
[Galaxy Note 10.1 Original Development] AdamOutler:
Alright guys. I'm uploading two new packages....

The first one is the latest copy of the Take Note Verizon jailbreak. It includes a modified Recovery by Dees_Troy. Our Note 10.1's are different than the other ones.

Differences: The partition structure is totally different. The kernels are totally different. This means you will soft-brick your device by flashing anything in these forums involving a recovery or a kernel other than this one. That being said..... It may be a good idea to get a separate forum. If you are interested, please start a *NEW THREAD* in General forums listing all the i925 specific threads which could be moved.

Alright. For the second part, I'm uploading a Rooted back-to-stock which I packaged from my own device before unlocking it and flashing stuff. Here's the technique used. http://xdaforums.com/showthread.php?t=2082951 . This file is large so it will be a while before it's uploaded. The files included are basically everything needed to safely get back from a custom ROM and be rooted stock again.

Files included: boot.img, hidden.img, modem.bin, param.bin, recovery.img, system.img

We don't have a way to remove the modified system status currently. There is no completely back to stock.
[Galaxy Note 10.1 Original Development] drozek:
Looking forward to trying this
[Galaxy Note 10.1 Original Development] DJsCrIBbLe:
So does N8010 boot loader mean N8010 ROMs or no...
[Galaxy Note 10.1 Original Development] AdamOutler:
no. The hardware is different. The bootloaders are similar. You need a different kernel

As a note: Never flash an N8010 bootloader. this is a SPECIAL bootloader based on the N8010 bootloader. Just pretend it has nothing to do with N8010. For all practical purposes, this is an I925 bootloader we crafted out of an N8010 because we didn't have a i925 to work with.
[Galaxy Note 10.1 Original Development] DJsCrIBbLe:
Ok thanks, mostly just curious as i own the N8013 but considered the verizon version or selling and getting the unlocked international.
[Galaxy Note 10.1 Original Development] *Madmoose*:
Thanks a ton Adam! Worked perfectly.

So if I have this correctly, we will be running stock until we get a dev to start working on our variant? I would assume that the other roms wouldn't install correctly with the partitions being different correct?
[Galaxy Note 10.1 Original Development] AdamOutler:
Yeah... don't flash nothin' or you will die. :). We need a ROM dev.
[Galaxy Note 10.1 Original Development] Snarlster:
Great work Adam, almost sent you a PM begging you to take this project on about 6 weeks ago... thanks!

But I had some problem as I ran the script, it stopped after it had rebooted and was stuck in Download Mode and asked me for my XDA username for some pastebin. The last information in that pastebin was:

After unpluging and holding the power down for a few secs it rebooted as usually, but I dont know if it completed or not... how do I know if the bootloader got unlocked?

If you would like to see the pastebin then I'd be glad to be able to help, just let me know.

Thanks again,
[Galaxy Note 10.1 Original Development] AdamOutler:
Use a different usb cable and port on your computer. There is a problem with the communications.
[Galaxy Note 10.1 Original Development] sednafx:
I am getting the same error. Can't even download the PIT file.
[Galaxy Note 10.1 Original Development] sednafx:
[MENTION=3682533]AdamOutler[/MENTION] Few questions:

Do you still need an image of the patched bootloader and do you have time to work on finding a fix? If so, I can root this weekend and dump the patched bootloader. Lastly will you let me know the full command I need to run in the terminal emulator?

THANK YOU!!
[Galaxy Note 10.1 Original Development] addictivepixels:
Were you unable to unbrick your tablet?
[Galaxy Note 10.1 Original Development] sednafx:
I never bricked mine. I just have been lurking for a while now. Been running stock/unrooted/unjailbroke since my chick decided "oh cool an update". <facepalm>. I am no dev but I think the update broke the use of heimdall. Hopefully if with the stock recovery and bootloader the devs can find a fix. I am willing to dump what's needed.
[Galaxy Note 10.1 Original Development] addictivepixels:
Ah, well crap.

I'm stuck in download mode, hopefully one day an ODIN image will surface. [MENTION=3682533]AdamOutler[/MENTION], if you can resurrect it I'll love you for-ev-var...
[Galaxy Note 10.1 Original Development] sednafx:
You should be able to make an odin tar from the images Sbrissen posted. Google "how to create Odin image"
[Galaxy Note 10.1 Original Development] addictivepixels:
Holy crap balls... I don't know why I didn't think of that.

I'm an idiot.

Thank you!
[Galaxy Note 10.1 Original Development] sbrissen:
Just use the system and boot though ( and recovery if necessary), don't flash the boot loader.
[Galaxy Note 10.1 Original Development] addictivepixels:
I'm not sure what I'm doing wrong. I created the tar file via http://xdaforums.com/showthread.php?t=926546 but when I go to flash it, odin crashes.

I feel like I'm so close to unbricking my tablet lol :(

---------- Post added at 09:48 PM ---------- Previous post was at 09:33 PM ----------

Got a working image, but odin fails...

<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

------------------

Edit: Tried a different copy of odin:

<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Enter CS for MD5..
<ID:0/005> Check MD5.. Do not unplug the cable..
<ID:0/005> Please wait..
<ID:0/005> Checking MD5 finished Sucessfully..
<ID:0/005> Leave CS..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
[Galaxy Note 10.1 Original Development] sednafx:
^ did you remember to rename the images prior to making the tar.
[Galaxy Note 10.1 Original Development] needoZ:
I have bricked my Note 10.1 the same way.

What I did was root it via Kingo then I ran Casual. Causal did not work due to a Heimdal error. I have ODIN access but that is all. But every thing I attempt to flash with ODIN I get NAND Write FAIL.

Here is the log of CASUAL: http://pastebin.com/bfhvvTWx
[Galaxy Note 10.1 Original Development] tetaganda:
hello everyone!

Please help me. Im trying to figure out why i cant use the Casual. First, i still have the root that i had using Framaroot. How do i know if my software was updated via OTA? I dont remember accidentally updating it. Is there a way i can check it?

Second, when i run casual, it goes through the rooting and of course tells me that i already have frodo root. then it eventually gives me an error that the casual is not compatible with my device. But it is a galaxy note 10.1 LTE verizon.

Hope someone can give me some light.

thanks!
[Galaxy Note 10.1 Original Development] sednafx:
I have the latest update. Under settings>about>build number = JZ054K.I925VRAMH2. Don't know if that helps.
[Galaxy Note 10.1 Original Development] addictivepixels:
Yeah - I found another image someone else made and it gave the save result.
[Galaxy Note 10.1 Original Development] needoZ:
DO NOT RUN CASUAL AGAINST THE LATEST OTA, EVEN IF ROOTED!!!

I was lucky and my i925 was still under warranty. I took it in to the Samsung Repair Center and they could not flash the device, they had to replace the motherboard, and then flash the tablet.
[Galaxy Note 10.1 Original Development] WorldOfJohnboy:
Can't get root

Just purchased a Samsung Note 10.1, Model # SCH-I925 from Verizon. The Android version is 4.1.2, baseband version I925VRAMH2, Hardware version I925.03.

Tried running CASUAL and chose "FRODO" on the tablet in Framaroot, and I get the error "Failed :( Try another exploit if available."

I also tried Kingo as someone else suggested and it won't get past the Driver install (keeps looping between installing driver, Disconnect Device to continue installing driver, and waiting to connect to device).

Any hope for me? I really only want root access (Titanium Backup), but would take what CASUAL gives me.
[Galaxy Note 10.1 Original Development] sednafx:
Kingo worked fine for me using an old Windows xp laptop. I didn't install any drivers. Just make sure usb debugging is checked under settings. DO NOT RUN CASUAL AFTER YOU ROOT. YOU CAN BRICK YOUR DEVICE.