Database Develop

What I did to get WM61 and the new radio installed with no sd card.....

After searching for hours on all the files, procedures, etc. on the subject, here's a quick guide for the n00b's out there that want to do this... Some information i will be repeating from other places on the internet.
----------------------------------
The following Files are needed (search the forums and google to locate)
1. CheetahUnlocker.rar (http://forum.xda-developers.com/showthread.php?t=334100)
2. Treo750_OS5_2_19199WWE_STD.rar
3. Treo750Radio1.54.07.00.rar
4. RUUWrapper.zip
OK.. Now here we go
unrar the first file 'cheetahunlocker' and basically follow the instructions from the above #1 link. Two things to note: Ignore any images for Hermes and you must have .net 2.0 framework installed on the device.
when you run the unlocker, the first one worked fine for me, the second process didn't work, but that doesn't matter. also watch the screen for the unit to ask you about opening files. if you don't do it, it can time out and then you'll have to start over.
Now here is the fun part.
1. Unzip the RUUwrapper file to it's own folder.
2. unrar the CHEEIMG.nbh file from Treo750_OS5_2_19199WWE_STD.rar into the same directory of the RUUwrapper files
3. rename the CHEEIMG.nbh file to CHEEIMG_FW.nbh
4. run the RUUWrapper.exe file and it will flash the rom of the unit to WM61. **remember to watch the screen for prompting of opening files at the beginning.
5. Done with WM61. Now for the radio update. It's basically the same process as above.
6. unrar the CHEEIMG.nbh file from Treo750Radio1.54.07.00.rar and put it into the RUUwrapper directory like before.
7. rename the CHEEIMG.nbh file to CHEEIMG_FW.nbh (delete the old one first)
8. Run the RUUwapper.exe file again to flash (this time) the radio to the unit. **remember to watch the screen for prompting of opening files at the beginning.
9. All Done.
----------------------
It worked fine for me with the Treo 750 and the AT&T network..
Main places i got information from were:
http://forum.xda-developers.com/showthread.php?t=365873&page=9
http://forum.xda-developers.com/showthread.php?t=334100

Your method above just helped me escape a bootloader loop which was (apparently created) by trying to load a different custom rom after having installed hardSPL. The only precautionary measure I took was to place only one image (the same OS & Radio you used) into the RUUWrapper folder at a time and it loaded right up. Still checking and testing some things out because the bootup isn't exactly smooth as silk, and the old "TREO750-1.13-CNG" still shows up under About->Phone->Software Version, but all firmware references reflect the updates. MTTY was ineffective in my particular situation.
Now for testing the radio for reliability and battery drain,etc...
Thanks for the heads-up!

Witch one is the correct selection (see attachment)

Anybody? at least tell me where I can find information about RUUWrapper.
Well I clicked Force use safe SSPL and clicked through and I got a error message saying that it could not communicate with the 750 Error 246 check usb connection?
I read that Vista had some issues with usb connections and to download and use VistaRUU usb drivers, I installed it according to the description, still error 246 and sometimes error 202?
Any ideas?

honestly i don't remember seeing that screen you are getting. it looks like the software isn't detecting the rom you have on your phone, in which case i would use the autodetect.

Hello Eric,
If I use autodetect it says it can not detect what version I'm using "Recomend using Safe SSPL"

This was the ONLY process that worked for me. However, I did not use the Cheetah unlocker, it is unfriendly with my Vista USB connection. I used magic unlocker and then your instructions and now I running on WM 6.1..
Thanks.. great work!!

I wonder - do you have Voice Command anymore?
Just curious - I lost Voice Command when I did this upgrade. Sure, the OS runs nice, seems a little faster, but I sure do miss Voice command. I am running AT&T's Treo 750, which had Voice Command on it. Some people, on some websites, like TreoCentral said there was a 'lite' version, which did not have Voice Command, but I installed this version: Treo750_OS5_2_19199WWE_STD.rar, and that seems like the right one.
So, I wonder - do you have Voice Command anymore?

As I know it is the normal version's bug (missing the voice command).

I completed set 1, no success!
When u say add to directory what do you mean?

missing the voice command？ Oh my...

egiblock said:
After searching for hours on all the files, procedures, etc. on the subject, here's a quick guide for the n00b's out there that want to do this... Some information i will be repeating from other places on the internet.
----------------------------------
The following Files are needed (search the forums and google to locate)
1. CheetahUnlocker.rar (http://forum.xda-developers.com/showthread.php?t=334100)
2. Treo750_OS5_2_19199WWE_STD.rar
3. Treo750Radio1.54.07.00.rar
4. RUUWrapper.zip
OK.. Now here we go
unrar the first file 'cheetahunlocker' and basically follow the instructions from the above #1 link. Two things to note: Ignore any images for Hermes and you must have .net 2.0 framework installed on the device.
when you run the unlocker, the first one worked fine for me, the second process didn't work, but that doesn't matter. also watch the screen for the unit to ask you about opening files. if you don't do it, it can time out and then you'll have to start over.
Now here is the fun part.
1. Unzip the RUUwrapper file to it's own folder.
2. unrar the CHEEIMG.nbh file from Treo750_OS5_2_19199WWE_STD.rar into the same directory of the RUUwrapper files
3. rename the CHEEIMG.nbh file to CHEEIMG_FW.nbh
4. run the RUUWrapper.exe file and it will flash the rom of the unit to WM61. **remember to watch the screen for prompting of opening files at the beginning.
5. Done with WM61. Now for the radio update. It's basically the same process as above.
6. unrar the CHEEIMG.nbh file from Treo750Radio1.54.07.00.rar and put it into the RUUwrapper directory like before.
7. rename the CHEEIMG.nbh file to CHEEIMG_FW.nbh (delete the old one first)
8. Run the RUUwapper.exe file again to flash (this time) the radio to the unit. **remember to watch the screen for prompting of opening files at the beginning.
9. All Done.
----------------------
It worked fine for me with the Treo 750 and the AT&T network..
Main places i got information from were:
http://forum.xda-developers.com/showthread.php?t=365873&page=9
http://forum.xda-developers.com/showthread.php?t=334100
Click to expand...
Click to collapse
This is great and it worked for me so I'm including the files here.
WM 6.1 does have some things that need to be debuged.
I havent tried WM 6.0 but from what I read on here it seems that 6.0 is more stable.
Does any one know if this route will work for WM 6.0?
If so does any one know which file do you download?
Will this set up work with WM 6.0?
http://omnifusionhosting.net/treo750/
http://forum.ppcwarez.org/viewtopic.php?f=221&t=41062

Well, WM6.0 is more stable, for one thing I had a faster battery drain with WM6.1 than I did with 6.0.
As mentioned earlier, some missing stuff like voice command, but one thing I thought wouldn't be there was messaging. For some reason that Messaging is half annoying me.
While I'm at it, anyone know how to backup SMS messages? That Messaging app is just keeping them to itself.

[script] Generic, fully automated Deodexer (OS X, Linux... Cygwin)

This is a script that I made for my own use awhile ago because I couldn't find an OS X deodexer. I recently modified it for use with Linux, and if you're on Windows and have Cygwin, well, it works with that too.
What is it:
It's a generic deodexer, for any ROM, and theoretically for any recent phone. What do I mean by theoretically? Well, the Atrix is my first and only Android so far, but I expect to be able to use it when I get others It should work with any phone that has all its framework in /system/framework and all its apps in /system/app. Any phone that doesn't have that doesn't qualify.
How does it do it:
It uses the phone's own BOOTCLASSPATH and patches together any additional necessary dependencies from /system/framework. It then uses the phone's own files to create the deodexed frameworks and apps (via JesusFreke's baksmali/smali). All the other deodexers I've seen use canned files that have been created ahead of time, or require you to specify the proper dependencies for your phone. This is fully automated and requires almost no intervention on your part. This means you don't have to go looking for "the right" deodexed files for the new stock ROM you just flashed, or know anything about dependencies. All it asks for is Super User permission at the very start (which you need to allow and check "remember", because it will need it later).
When will it be done:
In about a half hour from when you start. At least that's how long it takes on my Core2Duo 2.53Ghz, 4GB RAM MB Pro. There are 250+ files to decompile and recompile. It's a lengthy process.
Prerequisites:
1. You must be rooted with Super User installed.
2. USB Debugging must be turned on on your phone. Settings > Applications > Development > USB Debugging.
3. You need Java on your computer, and it has to be in your path (you can test by opening a terminal (or cmd for win) and typing 'java' on the command line. If you see help for that command, you're good).
There are 3 scripts:
1. deodex.sh: This is the main deodexer script. Run this to deodex a ROM for the first time. It will do its thing, and once it tells you it's rebooting, you should be deodexed.
2. postcompile.sh: If you restore to a non-deodexed state somehow and you have run deodex.sh previously on the same ROM, you can use this to skip the lengthy compiling and just deodex with the files you already created (they will be in framework.out and app.out on your computer).
3. restore.sh: Use this to return your phone to an odexed state. Obviously, you have to have used deodex.sh to deodex first.
After running deodex.sh, you may want to zip up and save framework.out, app.out, and the system folder in the deodex folder. These contain the deodexed files and your original files for the current ROM. If you ever want to use the restore or postcompile scripts, you need these.

please help
line 15: ./bin/osx/adb: No such file or directory
Error in previous command above line 18.
Exiting.
logout

cyrux said:
please help
line 15: ./bin/osx/adb: No such file or directory
Error in previous command above line 18.
Exiting.
logout
Click to expand...
Click to collapse
Interesting, either it's saying you have no /data/tmp folder on your phone, or you're missing ./bin/predeodex.sh.
Are you able to check if your phone has a /data/tmp folder? Also, a step I forgot in the OP. Do you have USB Debugging turned on?
*edit* Okay, so I downloaded my zip from here just to be sure, and tested only the section you're having trouble on by making it quit out right after the part you error'd out on. I've verified that predeodex.sh is working, so /data/tmp must be missing on your phone?

[Q] Locating a deodexed copy of BlurEmail.apk

I've been searching through here and over on RootzWiki for a Droid 3 copy of BlurEmail.apk. I haven't successfully been able to locate the file or a dump containing the file that I'm confident will work. I am a noob and I apologize for that, hopefully this question hasn't been asked and answered a million times, though if it has I can't find it. I've been looking for the last three hours I promise, I just can't find what I'm looking for.
I have BlurEmail.apk and BlurEmail.odex that I know works on my phone out of my backup prior to installing Steel Droid. Can I deodex this myself, or am I able to just drop both of these files into /system/app and be back in business?

You would have to deodex to use in a rom that is deodexed all ready.

I had to do this as well, needed email on steel droid. Just download Monster Rom bloated, and then you can pull it out of there.

1) Obtain the Deodexed install from RootzWiki. (Or if you have a back-up, that will work too!)
2) Extract the zip file (I downloaded mine to the PC and unzipped it there).
3) Open the extracted folder, then navigate to /system/app.
4) Locate the BlurEmail.apk file (not to be confused with blur_email.apk) and copy it.
5) Paste the file to the SD card or internal storage.
6) Using a file explorer (such as Root Explorer),copy the file from where you put it and paste to the /system/app directory (you may need to mount as RW first).
7) Set the permissions to rw-r--r-- by long-pressing and selecting "Permissions" (this is if you use Root Explorer, other programs may vary). Make sure owner has Read and Write, while Group and Others have Read only.
8) Reboot phone, and enjoy!
***NOTE THIS IS NOT MY FIND. I WAS HELPED WITH SAME ISSUE. I AM NOT COPYING ANYONES HARD WORK***
thats your answer. When it says locate deodex locate the stock deodex not the deodex debloated version. Follow steps. It works. I did it. And im running sd3.
Sent from my STEEL DROID3 using XDA App

insanity2k11 said:
I've been searching through here and over on RootzWiki for a Droid 3 copy of BlurEmail.apk. I haven't successfully been able to locate the file or a dump containing the file that I'm confident will work. I am a noob and I apologize for that, hopefully this question hasn't been asked and answered a million times, though if it has I can't find it. I've been looking for the last three hours I promise, I just can't find what I'm looking for.
I have BlurEmail.apk and BlurEmail.odex that I know works on my phone out of my backup prior to installing Steel Droid. Can I deodex this myself, or am I able to just drop both of these files into /system/app and be back in business?
Click to expand...
Click to collapse
I'm using the email.apk file taken from a Desire Z cyanogen rom, I consider it way better than blur email because I can mix the accounts and assign a custom color for every inbox.
I've just deleted the blur email and copied the email.apk in the system/app folder

jarzy00 said:
1) Obtain the Deodexed install from RootzWiki. (Or if you have a back-up, that will work too!)
2) Extract the zip file (I downloaded mine to the PC and unzipped it there).
3) Open the extracted folder, then navigate to /system/app.
4) Locate the BlurEmail.apk file (not to be confused with blur_email.apk) and copy it.
5) Paste the file to the SD card or internal storage.
6) Using a file explorer (such as Root Explorer),copy the file from where you put it and paste to the /system/app directory (you may need to mount as RW first).
7) Set the permissions to rw-r--r-- by long-pressing and selecting "Permissions" (this is if you use Root Explorer, other programs may vary). Make sure owner has Read and Write, while Group and Others have Read only.
8) Reboot phone, and enjoy!
***NOTE THIS IS NOT MY FIND. I WAS HELPED WITH SAME ISSUE. I AM NOT COPYING ANYONES HARD WORK***
thats your answer. When it says locate deodex locate the stock deodex not the deodex debloated version. Follow steps. It works. I did it. And im running sd3.
Sent from my STEEL DROID3 using XDA App
Click to expand...
Click to collapse
I had been able to locate that post you quoted for directions on how to do it, which are straight forward. I'm just having trouble finding a BlurEmail.apk, email.apk, or Messaging.apk that when used in coordination with these instructions gets me to a corporate e-mail inbox. I'll keep downloading different ROM's and trying different ones I guess until I can find one that works for me.
If I ever get to that point I'll attach it to a follow-up post so if someone finds themselves in my shoes later they can just pull that down and be set.

Okay, finally found what I needed to get back working with corporate e-mail. I can't attach to this post unfortunately, nor am I allowed to post links in a post so... I'm throwing this archive up on one of my boxes so if someone else needs it they can maybe find it faster than I did.
www . gcpsite . com / corporate-email-fix.rar

insanity2k11 said:
Okay, finally found what I needed to get back working with corporate e-mail. I can't attach to this post unfortunately, nor am I allowed to post links in a post so... I'm throwing this archive up on one of my boxes so if someone else needs it they can maybe find it faster than I did.
www . gcpsite . com / corporate-email-fix.rar
Click to expand...
Click to collapse
thank you!

I had the same issue. I found Mail Droid in the market to be better than anything I've used prior.
Sent from my DROID3 using XDA App

insanity2k11 said:
Okay, finally found what I needed to get back working with corporate e-mail. I can't attach to this post unfortunately, nor am I allowed to post links in a post so... I'm throwing this archive up on one of my boxes so if someone else needs it they can maybe find it faster than I did.
www . gcpsite . com / corporate-email-fix.rar
Click to expand...
Click to collapse
this link is no longer valid. does anyone have a good one for this file??

[Q] How to enable mass storage in CM 10.1 ?

Does anyone know how to enable USB Mass Storage on our phones under CM10.1? I've searched around and found this thread. But since I'm not familiar with changing build.prop I don't dare to do it myself. There are some CWM .zip files around to enable it, but they are on other phone's forums and I'm sure they just replace/change the build.prop so it's definitely not a good idea to flash those on a different phone than the ones they were intended for....
Long story short, does anyone know how to enable it on ours?
TIA!

Update on the process:
I was able to edit the build.prop according to the instructions, but that alone doesn't seem to do anything.
So I decided to try the next step, but where it tells me to do the changes below I wasn't sure what to do.
Thom75 said:
in framework-res.apk/res/xml/storage_list.xml
where oryginal line look like this:
Code:
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:maxFileSize="4096" />
after change look like this:
Code:
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:allowMassStorage="true" android:maxFileSize="4096" />
Click to expand...
Click to collapse
I was able to find the framework-res.apk file, copied to my computer and tried to open it with an XML editor... looked too complicated so I left it alone.
Does anyone know how to mess with that?

Open the .apk file with WinRar
-Drag the file you want to edit on your computer
-Edit the file on your computer
-Delete the old file in Winrar from the apk file
-Put the new file from your computer back in Winrar and save the "new" apk file
-Put the new .apk file on your smartphone
Before you install the new .apk file take a Root Explorer and look at the permissions of the old .apk file and set this permission on the new once...
I hope i could help you

Sivvis said:
Open the .apk file with WinRar
-Drag the file you want to edit on your computer
-Edit the file on your computer
-Delete the old file in Winrar from the apk file
-Put the new file from your computer back in Winrar and save the "new" apk file
-Put the new .apk file on your smartphone
Before you install the new .apk file take a Root Explorer and look at the permissions of the old .apk file and set this permission on the new once...
I hope i could help you
Click to expand...
Click to collapse
Thank you very much for your help! I didn't know apk files were just a compressed library of other files.
Now I am stuck trying to edit the "storage_list.xml" file... I tried to open with a few different xml editors, but could not get clean text like the example before. Any sugestions?
I attached the file below:

Apoena said:
Now I am stuck trying to edit the "storage_list.xml" file... I tried to open with a few different xml editors, but could not get clean text like the example before. Any sugestions?
Click to expand...
Click to collapse
Well, how about decompiling the .apk file with APK Tools instead of just opening it with WinRar? :laugh:
Yes, now I get a clean, editable, decompiled xml file.
I'll try editing both when I get home tonight and will post the results.

I guess this is a problem because of the emulated layout. There is a trick with setprop sys.usb.storage.config mass_storage but it does not work.
Keep me informed if you find something valuable (i'm on original CM10.1, latest nightly 0423 actualy).

Ok, here's the update from last night:
I started over since I flashed the nightly, which is good so I restarted with a clean slate.
- Edited build.prop - OK
- Copied framework-res.apk to my computer
- Decompiled framework-res.apk
- Edited storage_list.xml
- Recompiled framework-res.apk with new storage_list.xml
- Copied framework-res.apk back to my phone
- Deleted original framework-res.apk
- ...... instant restart & bootloop before I could paste the new framework-res.apk in its place
No big deal, just restored a nandroid backup I made before messing with anything and I'm back in business.
Apparently you can't mess with the framework-res.apk while your phone is on (with the OS running)... so now I need to research the right way to push/pull these files from ADB while on CWM recovery. I appreciate if someone could point me in the right direction since I'll be busy at work today.
To be honest, my gut feeling tells me that this is not going to work anyway. But look at what I learned so far... two days ago I wouldn't even think of compiling/decompiling anything... this is what XDA is all about, right?

Imho, the framework_res.apk and various tricks are all enabling or disabling a sys.usb.storage.config key. I'm not understanding nor finding informations about CM10.1 emulated layout, and if there are any reasons to forbid mass storage (because, yes, it seems it is disabled because it is not compatible).
This is something i have hard time with. On Android, you have tons of improvement for rom or kernel XY, but generally undocumented. If you apply this 'per device', the information is very fragmented and difficult to grab.
I was looking for a simple brief on base MTD partitions layout for LG P880, it seems the only way to have this is to dig KDZ files. Perhaps a Wiki would help the wannabe contributers like me to start ?

Any Solution For This Problem ??? I Can't Transfer Any Files To My O4X , What's The Point Of Cyanogenmod Then ??????????????

Nooby305 said:
Any Solution For This Problem ??? I Can't Transfer Any Files To My O4X , What's The Point Of Cyanogenmod Then ??????????????
Click to expand...
Click to collapse
Flash the latest nightly. MTP is working and you cab transfer files that way.
Sent from my tree using a ladder

effectively, if you are flashing for USM, you should stay on LG stock.

I know that the topic got a little old but I'd like to refresh it since more people (e.g. Ubuntu users) could be interested in enabling Mass Storage.
What I've done is:
1) pulled /system/framework/framework-res.apk
2) decompiled it with APKtool
3) added
Code:
android:allowMassStorage="true"
in storage_list.xml
4) builded a new apk
then I've rebooted my phone into recovery and (@Apoena you may be interested in it - there is a possibility to access /system through adb connected with phone in recovery mode) pushed the new framework-res.apk. I've also changed the entry in build.prop to
Code:
persist.sys.usb.config=mass_storage,adb
Everything seemed fine until I've tried to reboot the phone: instead of CM boot logo I got a black screen. Anybody has an idea what went wrong (maybe something during recompilation of the apk)?
And of course sorry for any language mistakes, I'm not a native speaker

Please help, I can't deodex services.jar

SOLVED! (Solution below)
Alright, so I tried everything I could, and spent almost my day trying to fix this. First of all what I did so far (it's maybe not the right method, so I let you know):
- Tried smali patcher
- Deodex error
- Google for hours, find a solution
- Search for /system folder, couldn't find NOWHERE, even with ES file explorer (root was checked)
- Downloaded "File explorer root browser"
(it's when the interesting part begins)
- Found system folder, copied to the storage, but somehow it didn't copy everything, only the apps an 2 empty folders
- So I copied the framework folder too into the system, and the build.prop
- Connecting phone, the folder is not even there
- Opened TWRP, because I read that I have to use that too, file manager, found the folders, copied them there into ANOTHER folder, and somehow it was there when I checked from the PC
- Finally finishing the deodexing, everything was okay, smali-blaksmali browsed etc.
- Opening smali patcher again, trying to browse services.jar, and of course it wasn't there, somehow it didn't copy that one (but I believe everything else was there)
- Searching for it via TWRP, copy-paste, PC, copy-paste into the framework, deodexer, bootclasspath not found
- I thought it's because the other files already deodexed, so I copied them from the phone again, put services.jar into the right folder, deodexing, done.
- Browsing in smali patcher, click on Path jar, I was so happy, I thought it's over, I did it, I'm the king.....
- "Target JAR must be deodexed"
- (UPDATE) I was able to copy the system folder properly with TWRP, deodexed, now smali patcher says "Mock location class not found".
Sorry for the long post, but I thought I share every information. I'm really sad. And really desperate. I read this forum too for help, and saw some really helpful people, I really hope someone can help me too.
For the TWRP part, I read about some adb sideload, read a llllot of things about it, but all of them was about copying files TO the phone, not FROM it, that's why I did it like this.
So again please help, because at this point I really don't know what to do.
As the device: Android version 7.0, Xiaomi redmi note 4.
Deodexer version 1.6, smali patcher 0.3.7 and 0.4.0
Solution
So apparently I'm blind. First of all I did everything by a reddit guide named "[mini Guide] [Android] [ROOT] Smalli Patcher: Deodexing services.jar "
It didn't really help, and even if I read some comments, I missed the most important to me, the comment of ajdroid270, who linked the correct, deodexed files to the phones Redmi note 4 (MIUI 10 - 8.12.20) and OnePlus 6T with 9.0.11 version. So if you have one of these devices, just simply download the files he mentioned, copy them to your phone, and flash with magisk. If not but you're stuck... well... praying helps sometimes.