Related
SuperJustKitchen v0.7 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
For more information on the kitchen, please read: http://forum.xda-developers.com/showthread.php?p=4288668
Word of warning:
None of the new EXT's have been tested and fixed for the Herald, Opal, Hermes AND Artemis. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here.)
howdy,
i just gave it a shot, downloaded all files and wanted to look into it but it seems i have to look somewhat deeper to just set the kitchen up...it doesnt work following your walkthrough guide...
so for now the impression left behind is:
nice homepage
frustrating setup..for a time pressed person
greetz
Sorry, that's because the setup has changed a lot since I first started the kitchen for the Herald.
It's pretty simple.
Create a folder in your C drive and name it Kitchens.
Within that folder create a folder called SuperJustKitchen.
Dump the contents of the the main files into this.
Go into the Working_Directory and dump the contents of the other 7z files.
I'll probably be making an auto install pretty soon.
Android NBHCREATOR [v0.3] on Ubuntu. FROYO SUPPORT & ADVANCED SETTINGS [July-29-2010]
NBHCreator v 0.3
NBHCreator makes the nbh file for flashing android to nand.
This utility works for Vogue, Polaris and Kaiser.
Currently supporting Donut, Eclair and Froyo
Prerequisites:
1. you need to be running Ubuntu (other Debian distros may work, give it a try) NBHCreator v2.0 will be cross-platform
2. you need to have wine installed ( I am using v1.1.42)
Make sure to "Completely" uninstall previous versions before installing newer versions.
Directions as follows:
a. select the zImage you wish to make an nbh for... try one from here:Working Kaiser GPS!! or here:DZO
b. change parameters to your liking...
c. click on the "compile" button...
d. select output folder.
and Flash Away...
Please Search for how to flash if you don't know how.
that being said...
I welcome any and all criticisms of this program
and I would appreciate any advice, suggestions, questions or comments.
Version 0.3b
-Fixed Window issues.
-For now...do not save output to a FOLDER on the Desktop.
-DOES NOT WORK YET WITH 2.6.32 ZIMAGES
Version 0.3 (07-29-2010)
-Now Supporting Froyo
-New Advanced Settings for things like Clock speed and Memory.
-Added a Date Stamp option for output filename.
-Removed internal Error checking[/B]
-This version has window issues with the xfce desktop environment. fixed in 0.3b
Version 0.2b (07-01-2010)
-Fixed false errors when creating for Vogue and Polaris
Version 0.2 (06-15-2010)
- Added ability to select zImage with name extentions ie... "zImage-12-06-10"
- Output filename now refects device type ie... "VOGUIMG, POLAIMG and KAISIMG"
- Added some error checking to make sure nbh was built correctly
- misc internal code fixes.
-False Error messages are popping up for vogue and polaris. Resulting nbh should still be usable. Fixed in 0.2b.
Version 0.1 (06-09-2010)
- should work for Kaiser, Vogue and Polaris
- Device specific options
- Settings for hw3d (donut/eclair)
- Settings for Resolution 240x320, 320x428, 320x480
- Settings for Panel Type 1, 2, 3
- Settings for Battery Capacity
- Settings for ppp.nostart (Data)
- May not work with loser's editor (let me know...)
- more options to come
- NBHs are all being named KAISIMG.NBH will be fixed in v0.2
Honestly? I think it rocks, since I'm to lazy to build my own NBH's
I see the similarities, and also the differences, and I think you should continue development personally, it's a different approach, and I can see the possibility to add to it by being able to include boot splashes perhaps, or edited initrd/zimage combinations for instance.
So yeah, keep at it
Yep, sounds like a great idea. A nbh editor is good for beginners, but it would be nice to be able to build your own. Could open up a lot of opportunities for customization.
Just make a Windows and a Mac port as well, for the future.
ok....so far progress is going along very well. I have this functioning on my setup
but I still have to work out making it transferable to other computers.
while I work on this, are there any additions that you would like to see added.
I will see if I can squeeze any changes into the beta release.
What language and GUI toolkit are you using?
It would be fairly portable if written in Python with GTK or Tk.
I am using gambas2 in ubuntu.
I am still trying to port my visual basic knowledge to gambas. it doesn't all function the same.
I have minimal experience in Python. but if you know any good tips I am all open for suggestions.
Now available for testing
really???? no feedback at all???
I have to get around to install Ubuntu, and I don't have the hard disk space for it just yet. Been meaning to go buy a terabyte hard drive to dual boot.
got sources or anything like that so I can haz on gentoo?
currently attempting to break open the deb, will fall back to a vm in worst case.
Edit: As I expected, I found the solution right after posting. Run NBHCreator.gambas from /usr/bin
I'm fairly new to Ubuntu and I've never use Wine before so can't work out how to get this running
The package installed, along with it's dependencies. Now what? How do I run it?
Sorry if this is basic stuff...
richard.
Working ok here. Still need to flash it onto my Kaiser - will report back if I find any problems.
Thank - this is a handy little tool
Edit: Hmm, output file only 4.8K so something is not right. Probably down to me so I'll keep playing.
richard_s said:
Edit: As I expected, I found the solution right after posting. Run NBHCreator.gambas from /usr/bin
richard.
Click to expand...
Click to collapse
The install deb should have created a 'start menu' item under /Applications/Other/NBHCreator
that is confirmed under the default Ubuntu window manager 'Gnome'
however I have not tested it in KDE or any other non-gnome window manager.
what window manager are you using?
poly_poly-man said:
got sources or anything like that so I can haz on gentoo?
currently attempting to break open the deb, will fall back to a vm in worst case.
Click to expand...
Click to collapse
let me know if you get it. I don't have the source available at the moment. it's on my wife's computer.
richard_s said:
Working ok here. Still need to flash it onto my Kaiser - will report back if I find any problems.
Thank - this is a handy little tool
Edit: Hmm, output file only 4.8K so something is not right. Probably down to me so I'll keep playing.
Click to expand...
Click to collapse
the resulting nbh must be 3M
DON'T FLASH IF IT ISN'T 3M.
make sure the zImage file is named 'zImage' and not somthing like 'zImage-12-06-10'
I am fixing the next version to allow different names for zImage.
mnjm9b said:
the resulting nbh must be 3M
DON'T FLASH IF IT ISN'T 3M.
make sure the zImage file is named 'zImage' and not somthing like 'zImage-12-06-10'
I am fixing the next version to allow different names for zImage.
Click to expand...
Click to collapse
No - I won't be flashing it! The file name is definitely just 'zImage'. Oh well I'll wait for the next version and try again.
richard_s said:
No - I won't be flashing it! The file name is definitely just 'zImage'. Oh well I'll wait for the next version and try again.
Click to expand...
Click to collapse
I haven't built in a error log into the program but could you run
the NBHCreator.gambas in a terminal and post the output.
what device are you building for and what are your settings?
After restarting Ubuntu your program it is all working as expected. Sorry about that - I should have thought to try that first
yeah, had to throw it into a virtual machine. Nice tool, though.
If someone describes the process in great detail (including the binary formats and all that), I can make a slightly more portable version, if you'd like.
I will be releasing a more cross-platform version after I work out all the bugs.
Keeping it ubuntu for now keeps the distribution of a crappy program to a minimal.
on that note... V0.2 will be out very shortly.
this will address
-input filename variations ie.. 'zImage-12-06-10'
-output filename specific to correct device ie.. 'VOGUIMG,POLAIMG and KAISIMG'
-error checking
-misc fixes
Update:
Fixed kaiser and polaris version info for NBH
Fixed issue where if a source code pull failed, any later attempts would fail as well
Fixed issue with updating bootenv
It's my first meaningful contribution! I put together a couple of scripts and some other stuff to make it really easy for me to create a flashable NBH from the latest kaiser kernel sources.
Many thanks to dzo, JeckyllHavok, quitlahok, rzk333, -Arturo-, kallt_kaffe, the folks at www.codesourcery.com, poliva at the htc-flasher project on googlecode, and all the people who contribute to developing, testing, etc Android on HTC devices.
Note that none of the files these scripts download are mine. They were not created by me. They all belong to other people who have contributed much to the community.
The only things that I've made are:
- crnbh (which uses commands from scripts in the htc-flasher project)
- update-workspace
- everything under the patches and signatures directories
(just the patches, not the things they patch)
This requires an active internet connection to use. I don't plan on maintaining this but I thought I'd put it out there in the hopes that it could be put to good use or something.
Download the attached file
Extract to your home folder (important)
Read the README
If you want to change it, make it better, please do! Just mention me in the credits. Also please PM me so that I know it was helpful. Thanks!
Good luck!
May I ask what this does differently than my NBHCreator?
First off, sorry for stepping on your toes I didn't notice yours until I was halfway through making it, and I only posted it because I figured it might be something to look at for ideas or something... I don't know how to describe what's different so I'll just post what it does...
update-workspace:
Gets the latest kernel source code
Gets the latest tinboot source code
Patches tinboot.S so that it uses the zImage and initrd.gz that are built later
Gets the latest bootenv source code
Patches buildInitrd so that it is a little bit safer (maybe)
Gets Yang from the htc-flasher project on googlecode
Patches the htc-flasher makefiles so that they only build Yang and HTCFlasher and then install them locally (to avoid cluttering the user's system)
Gets the arm toolchain from codesourcery.com and extracts it to the android-ezb directory
Builds and installs Yang (to the android-ezb directory)
then crnbh:
Builds the kernel source code
Builds initrd
Builds tinboot
Uses nbhmerge to create the output.nb file
Uses Yang to create the NBH file for the device
LoveMyPhone said:
First off, sorry for stepping on your toes I didn't notice yours until I was halfway through making it, and I only posted it because I figured it might be something to look at for ideas or something... I don't know how to describe what's different so I'll just post what it does...
update-workspace:
Gets the latest kernel source code
Gets the latest tinboot source code
Patches tinboot.S so that it uses the zImage and initrd.gz that are built later
Gets the latest bootenv source code
Patches buildInitrd so that it is a little bit safer (maybe)
Gets Yang from the htc-flasher project on googlecode
Patches the htc-flasher makefiles so that they only build Yang and HTCFlasher and then install them locally (to avoid cluttering the user's system)
Gets the arm toolchain from codesourcery.com and extracts it to the android-ezb directory
Builds and installs Yang (to the android-ezb directory)
then crnbh:
Builds the kernel source code
Builds initrd
Builds tinboot
Uses nbhmerge to create the output.nb file
Uses Yang to create the NBH file for the device
Click to expand...
Click to collapse
NO...NO...NO...
Don't be sorry...
I don't care if you make your own and post it...
I was only wondering because your OP was lacking in information as to what this did.
Actually the same thing happened to me just before I released my nbhcreator, loserskater released his nbh editor.
Your creator does some things mine doesn't (YET)
like actually pulling tinboot etc...
things like that I was putting off as an option for a later release.
other than that I am building the output very similar.
Now that I am in this deep I wish I would have gone without the GUI.
Seems to be creating cross-platform issues.
Well, please feel free to integrate any of it into yours. The two files are just shell-scripts written for bash... nothing more
The result of probably more than 100 hours of solo hackery: a working COM DLL for allowing any application to elevate itself to SYSTEM (root) permissions.
What you need:
An interop-unlocked HTC phone. Sorry second-gen and Arrive users.
A working HtcUtility driver. It's possible some HTC update at some point crippled this. It works for me; if it doesn't work for you let me know what updates you have.
What it does:
Allows changing the security token of any application to give that app unrestricted permissions. At this point, you can call any user-mode API, perform any operation, with full access.
It also allows you to read or write any value from memory, even kernel memory (this is how it modifes the security token).
What it can be used for:
Darn near anything. If it can be done while the phone is booted, you can do it.
What it can't be used for:
Modifying the ROM - the R and O stand for "read only" and they mean it.
Interop-unlocking a phone - it requires interop-unlock to get root in the first place.
How to use it:
In your app, include the HtcRoot.dll library.
Include the code from DriverAccessTest.cs in the test app (defines the COM API and enables using it).
Call the OpenHtcUtility function (will throw an exception if your device is incompatible).
Call the MakeMeRoot function (can also throw exceptions).
(OPTIONAL) Call the ReturnZeroIfRoot function to make sure your app is elevated (does not throw exceptions, will return an error code if you get one).
Do stuff with SYSTEM permissions (probably using another COM DLL, such as for registry or filesystem access).
Call the RestoreToken function (failure to do this *might* cause a kernel memory leak).
Call the CloseHtcUtility function (OS will probably handle this if program just exits).
What you can do right now:
Try the test app. It should pop up a series of messge boxes. Hopefully none of them say anything like "FAILURE".
Report any bugs or failures you discover.
Build things with this library, and publish them!
Breakdown of the download:
There are two folders in the ZIP, one for the Visual Studio 2010 C#/Silverlight XAP project, and one for the Visual Studio 2008 C++/COM DLL project.
The test XAP is in the HtcUtilityTest\bin\Debug folder.
The native (COM) DLL is also available in that folder, or under its own project.
If you want to mess with this, I'm going to assume you are already familiar with hybrid native/managed development for WP7. If not, Heathcliff74 has posted an excellent tutorial on this forum.
Special thanks to:
Heathcliff74 for the hybrid app tutorial and interop unlock info.
Paul_Hammons for the links and info about HtcUtility, the driver that makes this possible. Thread: http://forum.xda-developers.com/showthread.php?t=1434793
Supported devices / firmware versions / ROMs
All HTC devices (if interop-unlocked and with the right firmware numbers) should be compatible.
Some custom ROMs work, some do not. This will depend on the version of the firmware that the ROM's HtcUtility driver is taken from.
I believe I compiled the test app as Mango-only, but the native library doesn't care at all.
Compatible:
Stock ROMs with compatible firmware for HD7, Trophy, Mozart
HD2 (BttF [XBmod-Yuki] v2 SP1)
Not compatible:
Firmware version 2250.21.51004.401 or newer
Verizon Trophy firmware version 2305.13.20104.605 or newer
DFT ROM with build 8107, Firmware 5.10.401
Arrive (except on pre-Mango), Titan, Radar, Titan 2 (no interop-unlock)
Others are untested or results are incomplete.
Goals and future work:
Support more devices:
* Try and add support for newer firmware.
* Help ROM cookers ensure the library is supported.
* Look for similar openings in other OEM libraries.
Future-proofing:
* Allow installation of a mod to support this capability after known updates.
* Resilience against possible future updates.
* Allow users with incompatible devices to downgrade (possibly to NoDo), install the mod, and be able to use the phone after upgrading.
Improve the library:
* Fix some memory leaks.
* Clean up the code - remove dead code and improve comments.
* Allow reading/writing more than 4 bytes at a time from managed code.
* Add APIs to elevate other processes (by name or ID) to SYSTEM.
Develop homebrew around the library:
* Support accessing common APIs (filesystem, etc.).
* Resurrect the Advanced Explorer app, perhaps (registry and filesystem).
* Support native app launching on stock ROMs.
Also reserved
Reserved for OP #2
It does not work on HTC 7 Mozart (HTC Europe):
Error to Write the value 1337 to test address - System.Runtime.InteropServices.COMException (0x8007001F): A device attached to the system is not functioning
Click to expand...
Click to collapse
OS: 7.10.7740.16
Firmware: 2250.21.51101.401
Radio: 5.71.09.02a_22.51.50.21U
Boot: 5.11.2250.1(133487)
Please include the full error message or a description of what went wrong.
Failure on fully updated devices is unfortunately possible - my phone is (intentionally) a few updates behind. I'm looking into ways to make it work anyhow (either sending an older CAB update to roll back, or using the root acess to create an unlocker/root-enabler that survives subsequent updates). I'm going to look into how the full-unlock ROMs differ from standard ROMs, and see if I can do the same thing in running software.
Does it works with custom roms?
If the custom ROM has a working HtcUtility driver, then yes. My goal is to unlock the kind of capabilities normally restricted to custom ROMs on stock firmware, though.
@bleh815: Thanks for the report. That's frustrating; it looks like it is capable of doing read but not write. Write might just be restricted in what addresses is allowed, or it might be disabled entirely (the driver gives the same error code for every problem that I've encountered so far). Time to figure out
A) what update causes the problem (I'm on 2250.21.30102.531, HD7, stock ROM)
B) what restrictions that update introduces
C) how to work around those resrtictions (possibly by downgrading and then using root access to add something that will still work after upgrade).
GoodDayToDie said:
A) what update causes the problem (I'm on 2250.21.30102.531, HD7, stock ROM)
Click to expand...
Click to collapse
I've just downgraded a mozart of mine back to stock NoDo (TMOB-DE) to find out which OEM update breaks (actually fixes) it.
Cool, thanks! It's one of the post-Mango HTC updates; a Microsoft update wouldn't have modified an HTC driver, and my phone has all the pre-Mango HTC updates but it still works.
.
..........
Hi, at first it says "SUCCESS!", then it says "Trying to open a file gives error 1260" and then it says "Now opening a file gives error 0" and finally "Finally, opening a file gives error 1260".
System informations:
OS=7.10.7720.68
Firmwareversion=2250.21.12200.162
Radio=5.68.09.05a_22.50.50.21U
Bootloader=4.6.2250.0(129185)
HTC 7 Trophy.
That is *exactly* the sequence of messages it is supposed to give!!
In particular, the messages I need to see are the "SUCCESS" (the rest is potentially interesting info, but not very important) and then the "Now opening a file gives error 0".
The "SUCCESS" means that a sequence of read/write tests succeeded.
The "Now... error 0" means that the process has been elevated to full permissions.
The "Finally... error 1260" means that the security token was successfully restored at the end, so it was unable to open the file again. This is the expected and correct behavior.
I don't recognize your Firmware Version number; I'm guessing it's specific to your phone. What method did you use to upgrade to Mango?
how do i install it?
Tried on interop-unlocked HTC Surround, not working Tested any call in VS debug mode - no luck at all.
I can confirm that it works with any OS version, from 7004 to 8107.79
On a HTC 7 Mozart (TMOB-DE) it works with firmware 2250.21.13201.111 (Stock NoDo ROM) but the hole gets fixed with 2250.21.51101.111 (1st Post-Mango HTC Update).
You guys are gods taking programming to a hole new level!
I wish to see ms take you all more serious and not let wp7 fail like minmo6.5 did!
I wish I could get on your level!
I realy need some help lerning basic silverlight my self!
But I have read how hybrid working ant this is just fantastic!
conradulations on all your developments so far you guys are truly amazing!
Oh, that code, beautiful reading that!
Thanks for sharing this learnfull code!
I'd like to try it on my Verizon HTC Trophy, I would love to get file access back....
I downloaded the package and I even have VS 2010 installed but beyond that I have no idea as I am not a programmer.
Can someone post a compiled XAP for us to try to see if our phone works with it or not ?
Or some step by step VS 201 directions to try would also be helpful.
@Ttblondey: *FACEPALM* The path to the test XAP is given in the opening post. You install the XAP on your phone using any XAP deployment tool. It requires that your phone be interop-unlocked; Heathcliff74 has a nice long thread about that. The app is called called HtcUtilityTest. Run it, and report the results. If you want to actually *use* the DLL, the instructions for doing that are given too but you need to write some code.
@sensboston: PLEASE give a more complete report! Success and error messages, at the least. Also, your phone version info. Thanks!
@bleh815: THANK YOU! I mean, it's a little annoying to know how far back this was fixed ("First post-Mango HTC update" means the one that was included *with* Mango for most people, or the one after that?) but good to know. Now, to look at exactly what they changed...
@jackrabbit72380: Thanks man! As for working with it yourself, like I mention below, I'm planning to provide a universal homebrew library that people can easily use to do whatever they want.
@fiinix: You're welcome! Honestly, I didn't expect anybody to call my mess of debug-commented and mildly hacky C++ "beautiful" but that hack itself *is* pretty awesome. My only concern with using it is the risk of a context switch causing the wrong app's token to get overwritten, and I should probably look into that, but I think it's OK for the moment. There are bigger fish to fry.
In the meantime, it should open up a huge list of capabilities for tools like your DllImport project. I'm currently considering reviving Advanced Explorer (like TouchXplorer + Registry Editor, but open source; was never ported to Mango though) using the root access instead of using ComFileRW and the provxml driver. Let me know what you want to do with it!
One other thing I'd like to add is the ability to easily elevate *another* process; it's not hard to do but I haven't written it yet. This could be handy for apps where we don't have the source code (for example, elevate Schaps registry editor, which uses low-privilege native code for browsing, so it can read *all* registry locations instead of just some of them).
@DavidinCT: Well, running the test app is easy, just install the XAP. It just runs a battery of tests though, it doesn't actually *do* anything useful. To get filesystem access, you'll need to write some native code (which means using Visual Studio 2008 and the CE/Smart Device plug-in, see Heathcliff74's toturial on the subject). Basically, you would first use this DLL (accessed via COM, you can look at my own C# code for how to do that) to opent he driver handle and elevate the process to root. You could then write your own COM DLL that uses the standard Win32 filesystem APIs (CreateFile, etc. - all are documented on MSDN) and exposes those APIs, or the results of them, to managed code via COM. Then, back in your phone app (the one that called into my HtcRoot DLL) you can call into your own DLL to access the file system.
If that's too big a leap, don't worry. I plan to release a general-purpose high-privilege homebrew DLL that exposes some of the most-used functionality (filesystem, registry, provxml, and other things by request), is easily extensible (possibly using something like the DllImport project, where you just specify the function you want to call and the DLL it's located in right from C#), and that will be a lot easier to hack with. You'll still need to know C# and basic Silverlight, but it'll be a lot easier (and hopefully useful without knowing any C++ or COM).
GoodDayToDie, you are amazing, always keeping me interested!
When starting the test xap, I get the below, it then goes into the "Page Name" and that's it.
Device Info here, running a FullUnlock DFT Rom by a Chinese dev from the DFT Forum.
Nonetheless, top work on getting this started and can't wait to keep reading about the progress!
XeKToReX
Over the past few days, I have been working on a new version of Seven-Eighter based off of the source code that Jaxbot kindly provided. I have made numerous improvements to the original version.
One of those improvements is instead of embedding the links to the update files as strings in the actual program, my version of Seven-Eighter downloads a config file from the internet which contains the links to the update files. In this manner, you, the user, do not have to download a new version of the program every time Microsoft releases a new update for Windows Phone 7.x. All I have to do on my end when a new update comes out is to just update the config file once I find links for the new update.
Some more improvements include improved error handling and some better instruction to help you with the update process. If you haven't yet, you should really check it out. I am curious as to what people think of my version compared to the original.
You can find the link to download my version of Seven-Eighter on my blog here: http://bit.ly/ZOzAz9
Now as such, I am always looking to improve. I welcome any and all suggestions. If you want to throw something my way to help with development you are welcome to do so, but not required (your satisfaction works just as well, check my signature for instructions).
Nice work!
Steven855 said:
Over the past few days, I have been working on a new version of Seven-Eighter based off of the source code that Jaxbot kindly provided. I have made numerous improvements to the original version.
One of those improvements is instead of embedding the links to the update files as strings in the actual program, my version of Seven-Eighter downloads a config file from the internet which contains the links to the update files. In this manner, you, the user, do not have to download a new version of the program every time Microsoft releases a new update for Windows Phone 7.x. All I have to do on my end when a new update comes out is to just update the config file once I find links for the new update.
Some more improvements include improved error handling and some better instruction to help you with the update process. If you haven't yet, you should really check it out. I am curious as to what people think of my version compared to the original.
You can find the link to download my version of Seven-Eighter on my blog here: http://bit.ly/ZOzAz9
Now as such, I am always looking to improve. I welcome any and all suggestions. If you want to throw something my way to help with development you are welcome to do so, but not required (your satisfaction works just as well, check my signature for instructions).
Click to expand...
Click to collapse
hi, for htc mozart with dynamic v2.0 rom doesn't work.
Do you know how I can update my phone?
Thanks
ruso said:
hi, for htc mozart with dynamic v2.0 rom doesn't work.
Do you know how I can update my phone?
Thanks
Click to expand...
Click to collapse
To be honest, I didn't test my version of Seven-Eighter with a custom rom image (only stock factory rom image). What build is it currently running?
I have the exact same question.
I pretty much bricked by bootlaoder on my AT&T HD7S using the initial version of SevenEighter from jaxbot and now can't even use the gold card method to downgrade since I need it unlocked.
My RGB bootloader screen only shows one line of text at the top in the red and nothing in the white space where it should say USB HOST/Loader Mode.
But at least I had a 7.5 Zune backup that I can restore to, the only thing being that it doesn't restore my bootloader.
So, question is, can I use your software to upgrade to a custom unlocked 7.8?
Thank you!
I was finally able to get my Focus S upgraded to 7.8. Got tired of waiting. I had a problem with the application and had to close it. when I relaunched, it continues where it left off. Nice! I left the update.log just in case.
Now I just need to unlock it for side loading. Anyone recommend ways that still work? Thanks.
Will
Steven855 said:
Over the past few days, I have been working on a new version of Seven-Eighter based off of the source code that Jaxbot kindly provided. I have made numerous improvements to the original version.
...
You can find the link to download my version of Seven-Eighter on my blog here: http://bit.ly/ZOzAz9
Now as such, I am always looking to improve. I welcome any and all suggestions. If you want to throw something my way to help with development you are welcome to do so, but not required (your satisfaction works just as well, check my signature for instructions).
Click to expand...
Click to collapse
Screenshot please ?
anybody updated at&t titan 2 to 7.8?
Yes. The seveneighter app worked perfectly. I just wish I could install the version of htc connection setup I had on my hd2 so I could change my apn settings for my carrier instead of being locked out of my mms.