Related
Hey I just got the touch for Verizon and have a few rookie questions.
I read a lot about changing the ROM but am a bit confused. What is flashing? Is this necessary? I see that it is really dangerous and irreversible for Verizon. I see general instructions, but are there Verizon specific ones around anywhere?
Also I downloaded this Valhalla gps cab to get GPS working. After I resetted, I downloaded google maps and tried the gps with no luck. Can anyone tell me what I'm doing wrong?
Also I'd like to get that Manilla 2d on my phone. What's the best route for this? Am I risking getting rid of the cube?
I know I am asking a lot of questions, if you can answer one I would greatly appreciate it.
Thanks in advance,
Zack
zfly9 said:
Hey I just got the touch for Verizon and have a few rookie questions.
I read a lot about changing the ROM but am a bit confused. What is flashing? Is this necessary? I see that it is really dangerous and irreversible for Verizon. I see general instructions, but are there Verizon specific ones around anywhere?
Also I downloaded this Valhalla gps cab to get GPS working. After I resetted, I downloaded google maps and tried the gps with no luck. Can anyone tell me what I'm doing wrong?
Also I'd like to get that Manilla 2d on my phone. What's the best route for this? Am I risking getting rid of the cube?
I know I am asking a lot of questions, if you can answer one I would greatly appreciate it.
Thanks in advance,
Zack
Click to expand...
Click to collapse
Great switch! I had to ditch my i760 too !
Flashing is the term used to basically say your upgading your ROM. It's not necassary, but once you do it, you'll be much happier with the overall performance.
Other vocab to know:
ROM: Read-Only Memory, all your system files, your OS.
Radio: This is for your phone, and GPS, you need a v3.XX for GPS functions.
RUU: ROM Update Utility, the application used on your PC to flash the new ROM.
Bootloader: When flashing, this will be the screen you need enter, you can enter it by pressing and holding the Power & Camera buttons, then soft reset. You only need to enter this when checking SPL versions, and for flashing.
Kitchen: The set of files used to cook a ROM.
Cooking: Another term for creating a ROM.
You need to read as much as you can before you decide to flash a new ROM. When you do, you'll see those terms thrown around quite a bit, so know you won't be as confused, I hope. Those are the ones I could think of off the top of my head.
For now, flashing the xv6900 is irreversible, so if you decide to do it, make sure you are fully aware of what you are doing, and be prepared in the event something goes wrong. But, if you can successfully update the ROM, you'll be happy with the end result. Trust me, it looks confusing, but when you're done you'll see it was really a piece of cake !
The reason your GPS does not work is because you have the stock Radio, it must be updated first, but as I said before, be sure to have a good knowledge on what you are doing.
If you want the Manilla 2D, just install the .cab file from its thread. It will not remove your cube, since they are two different "apps." But, my suggestion is to get rid of it, since it's quite useless, just search around, once you find the other great developments here, you'll want to ditch it ASAP.
For extras, see my Tips & Tricks thread, link in my sig.
What rom do you recommend? I am ready to flash it. I am looking for threaded text as well. I'd really like to use GPS as well. And I though there was a ROM with Manilla 2d, maybe I am confused. Anyways, please recommend a popular rom, and where I could find some instructions.
Thanks so much.
I e-mailed you, but I then figured I should make it public
zfly9 said:
What rom do you recommend? I am ready to flash it. I am looking for threaded text as well. I'd really like to use GPS as well. And I though there was a ROM with Manilla 2d, maybe I am confused. Anyways, please recommend a popular rom, and where I could find some instructions.
Thanks so much.
I e-mailed you, but I then figured I should make it public
Click to expand...
Click to collapse
There really isn't a "popular" ROM in the sense each one is different and better suited for different people. 99% of the ROMs available will have the updated Radio as a mandatory step, so GPS will be included, and threaded SMS is a default for WM6.1, also a standard in most ROMs. I think there are a few Manilla 2D ROMs available, but all it really means is, it's included with the ROM.
When you flash the new ROM, you update all the system files, so after a flash, if you were to do a hard reset, you will not go back to the original VZW ROM, but the new one you flashed. So, with that in mind, do some browsing around to find what's included in the ROMs available.
All the ROMs you find will be different, they will have different apps, tweaks, and graphics. Just think what you would prefer, a fast ROM, lots of included apps, or one with more storage memory?
After your first flash, the Radio will be updated, and the device will remain unlocked. So unless you need a new Radio version, which I highly doubt, you can flash any ROM of your choice, without having to unlock the device or update the Radio. You'll probably go through a few to see which one you like the best.
Also, make sure you have read everything possible, thinking about this logically, you've got a 50% chance to do this wrong, nothing personal. Just be sure your confident you have read enough, and know you can fix it if there is a problem. As you know, it's irreversible, before you flash, ask yourself if you have a spare $300-$400 just in case.
Happy Flashing !
just discovered this, which is what ive been looking for which should help you.. its in the wiki tab but heres the link
http://wiki.xda-developers.com/index.php?pagename=Flashing Guide
thanks champ
thanks champjt your post was informative
Wow 50 percent chance? I don't like those chances. Is there a clear step by step instructions link somewhere, so I can increase my chances?
Also it says to delete your partnership with activesync. I'd like to keep all my contacts and datebook. Is this necessary?
Also, is it possible to just update the radio? Just to get GPS? And if so, how risky is this?
imdarkside said:
thanks champjt your post was informative
Click to expand...
Click to collapse
No prob !
zfly9 said:
Wow 50 percent chance? I don't like those chances. Is there a clear step by step instructions link somewhere, so I can increase my chances?
Also it says to delete your partnership with activesync. I'd like to keep all my contacts and datebook. Is this necessary?
Click to expand...
Click to collapse
Not always 50%, but there are really two options, it works or it doesn't, which is why I say it like that. I've got a link to a really good guide in my Tips thread.
zfly9 said:
Also, is it possible to just update the radio? Just to get GPS? And if so, how risky is this?
Click to expand...
Click to collapse
Updating the Radio and flashing are pretty much the same, considering you need to flash the new Radio for a new ROM, for the GPS enabled ones at least, which is almost all of them. Once you have unlocked your device and updated the Radio, flashing the ROM will be done almost in the snap of your fingers, the ROM is the easiest and most painless part. The first two, the Radio and unlocking, are the ones you need to pay the most attention to, and you should only really need to do those steps once for any ROM flashes ever on this device.
I recomment OMJ's bell ROM's, you can find them on ppc geeks. What's nice if you decide to install the manilla 2d today plugin it seems to work near perfect with his roms.
TheChampJT said:
Great switch! I had to ditch my i760 too !
Flashing is the term used to basically say your upgading your ROM. It's not necassary, but once you do it, you'll be much happier with the overall performance.
Other vocab to know:
ROM: Read-Only Memory, all your system files, your OS.
Radio: This is for your phone, and GPS, you need a v3.XX for GPS functions.
RUU: ROM Update Utility, the application used on your PC to flash the new ROM.
Bootloader: When flashing, this will be the screen you need enter, you can enter it by pressing and holding the Power & Camera buttons, then soft reset. You only need to enter this when checking SPL versions, and for flashing.
Kitchen: The set of files used to cook a ROM.
Cooking: Another term for creating a ROM.
You need to read as much as you can before you decide to flash a new ROM. When you do, you'll see those terms thrown around quite a bit, so know you won't be as confused, I hope. Those are the ones I could think of off the top of my head.
For now, flashing the xv6900 is irreversible, so if you decide to do it, make sure you are fully aware of what you are doing, and be prepared in the event something goes wrong. But, if you can successfully update the ROM, you'll be happy with the end result. Trust me, it looks confusing, but when you're done you'll see it was really a piece of cake !
The reason your GPS does not work is because you have the stock Radio, it must be updated first, but as I said before, be sure to have a good knowledge on what you are doing.
If you want the Manilla 2D, just install the .cab file from its thread. It will not remove your cube, since they are two different "apps." But, my suggestion is to get rid of it, since it's quite useless, just search around, once you find the other great developments here, you'll want to ditch it ASAP.
For extras, see my Tips & Tricks thread, link in my sig.
Click to expand...
Click to collapse
Wow TheChampJT! I wish i have seen this inmy earlier days, when i started tweaking my vogue! Thanks, this is a great contribution... Maybe worth a sticky?
socrate007 said:
Wow TheChampJT! I wish i have seen this inmy earlier days, when i started tweaking my vogue! Thanks, this is a great contribution... Maybe worth a sticky?
Click to expand...
Click to collapse
LOL! Happy to help! Its not finished yet but i have a tips and tricks thread, link in my sig.
So has anyone on here gone into the VoicePlus Beta? A lot of people on there are curious if anyone has looked into rooting the img or extracting the Apk. http://forums.t-mobile.com/t5/Voice...ash-the-Voice-Plus-Beta-ROM-Image/ta-p/325923 Even one of the mods has said he uses Cyanogen and was wondering if anything was going on over here.
p.s. Cyanogen....you ROCK!
wm1 said:
So has anyone on here gone into the VoicePlus Beta? A lot of people on there are curious if anyone has looked into rooting the img or extracting the Apk. http://forums.t-mobile.com/t5/Voice...ash-the-Voice-Plus-Beta-ROM-Image/ta-p/325923 Even one of the mods has said he uses Cyanogen and was wondering if anything was going on over here.
p.s. Cyanogen....you ROCK!
Click to expand...
Click to collapse
why not just extract the apk yourself using an appmanager? the post to forums
complete
Honestly...because I've never done it. ;-) I know not a really good reason, but between school, work and the fam...I haven't been able to take the time to learn. I'm hoping that over my next deployment (I'm in the Army also) that I can learn to create an app and maybe cook a ROM.
Interesting
I like the CityID and the call divert and call defer seems neat - hopefully better visual voicemail than T-mobile's other app.
I'd like to see it integrated in Cyanogen, and SuperD roms
its a waste, dont flash u will LOOSE ROOT
i pulled the system image
ok, I've been picking this up as I'm going... I extracted the nbh file and now have .nb files, but I dont know where to go from here...
anyone can point me in a direction would be helpful. I have SDK installed and can make and start a virtual device.
Ok, I'm loving Gingerbread, but m-deejay has been including Cyanogenmod in his recent builds, which I don't want.
I'm REALLY keen to work on my own Gingerbread build...but need pointers on the steps I need to take.
I want to use a clean custom Nexus One Gingerbread build, such as http://forum.xda-developers.com/showthread.php?t=885784
Then I'll have to replace the Nexus drivers and stuff with the HD2 ones...this is where the problem starts...how do I know which files are needed for HD2 specifically?
And then I need to add/remove apps etc to customise it?
I don't want anyone to hold my hand, just to at least point me in the right direction, as finding this information seems to be very difficult, unlike Windows Mobile cooking, which has lots of good tutorials...even though I'd expect that to be the other way around
I taught myself WM cooking & dev, but this is a whole new ballgame to me....
Appreciate any help I can get...
I'll happily donate a few $ to anyone who can help me get a stock build going...
No one able to shed ANY light? Give me ANY pointers?
Like I said, I'm willing to donate $ if I get help to get a ROM built...
Good pointers!!!
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.
NemanjaLO said:
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.
Click to expand...
Click to collapse
Yea I saw that, thanks...only problem is that it's an old build, and it's miui.
Where do I find the latest drivers etc? And how is a NAND build different? How do I package up a NAND ROM?
I was thinking the very same thing but when I started looking into it I got put off by the complexity and the time it would take.
Have you thought about just modding MDj's ROM, stripping it back to bare ginger and replacing the bits we dont want, this might be easier that building one from scratch.
Yea, it's a possibility...but I won't learn as much doing it that way...and I'd rather try to create my own than use someone else's hard work as a base, if you know what I mean.
I have time, and am willing to learn as much as I need to...I just need some pointers...there are plenty Android HD2 chefs now, surely one of them is willing to help out
It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.
I'd love to see this too!
SamanthaMarquez said:
It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.
Click to expand...
Click to collapse
Hey,
yes I've VERY interested...I'm hoping to get a stock-ish one together with my own little touches...maybe release one if I learn enough about it.
Any help you can give would be much appreciated...
Even to start with, a list of the basics...ie get ROM dump, extract xyz, do this...anything at all...
I just got back from a swim at the beach to relax, intending to come back and try to figure it out on my own with what help I can get from that page linked above...but if you have managed to get one together, thats even better
This might be of some use for windows users (I've successfully tried extracting MDJ's Gingerbread system.img with it).
http://android.modaco.com/content/z...-boot-recovery-system-userdata-kitchen-ready/
yea extracting is easy...but I would prefer to use a clean build to start from, rather than m-deejays...trying it using the guide in the link above with the Nexus S dump...having to use some donor files from m-deejays build though...still trying to get my head around it all
Well I gave it a quick try using the above guide, and it gives "NAND Kernel Open Fail".
I used m-deejays kernel, and put all the relevant files into the correct directories before making the system.img, and i put initrd.gz and zimage into boot.img, so I dont know what I did wrong...?
You don't use system.img on nand. You need to create a yaffs.img. Which I've never done before. I've only made builds the sd way, not nand. Maybe all you have to do is rename the .img after you create it. You should jump on irc, room #htc-linux-chat. You would get your answer in like 5 secs;p
NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2
i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G
Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.
g.lewarne said:
i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G
Click to expand...
Click to collapse
Yea, something like that would be handy...but even to start with, I'd just love to know the basic processes needed to get a basic Android build running on the HD2, without having to rely on someone elses current build.
I tried the link above, and it did sort of help understand a little of whats going on...but this stupid kernel error is preventing me from knowing how my test build works/or doesnt work...
I mean I had too use m-deejays gingerbread dump to get some of the driver files etc from...but where does he get them from? Thats the stuff I dont know...
It's obviously not overly difficult as there are so many devs pumping out HD2 ROMs...would just love one of them to share the secrets
Cash - not sure ... depends on how much help I get, but I'm willing to donate along the lines of US$20 or so...
mattfmartin said:
Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.
Click to expand...
Click to collapse
hehe...
What server is that chat room on?
the_scotsman said:
NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2
Click to expand...
Click to collapse
Is it possible that the img files need to be created as ext4 rather than yaffs? I know gingerbread runs on the ext4 system (where froyo ran on yaffs2) but I'm not sure how this relates to building the rom.
Nah, don't think so...not accroding to: http://forum.xda-developers.com/showthread.php?t=897940
Ive tried a few more times but am still getting the kernel error...so I cant even test if my build works or not as it wont even boot...so very frustrating...
Lets break it down........
1st
Here's a brief intro I did a few days ago read it..
http://forum.xda-developers.com/showthread.php?t=897940&page=2
The above goes for any .img used with DAF, they are yaffs2 images.
2nd
The sensible option for a clean build would be an existing stock gingerbread rom on a sister device. AdamG just happens to make the cleanest Desire roms around. I've had my eyes on this build for a minute, check it out and see if this what your looking for. Oxygen v2.0-RC6
3rd
I've been able to unyaffs disect, reassemble and get some 'customized' roms running. They flash, boot, & work great.....but I lose root permissions. lol
I was acutally doing this with the 1.6 NAND rom of MDJ that came as a single.img
That particular file was just system.img & boot.img yaffs2'd together. After I disected it I was able to unyaffs the 2 images and edit/modify change kernels, etc. etc. The only problem I have run into is the root issue.
Conclusion:
----------------------------------------------------------------------------
I'd be glad to help out any way I can in porting a ROM worthy of our devce
Any serious inquries can be directed to my inbox for private discussion on gtalk .
I'm no dev and am in no way claiming to be. I do have some findings and that's why I'm offering my help. Cheers
Hello everybody, It´s been like a week since I last posted, a lot of things went wrong in my house and I somehow lost all my computers
anyway, back in business again, Last night I had to install the stock Sprint GB sbf, to my surprise it worked Really, Really good.
I´ve had a Defy+ and a Milestone 2, And I remembered having lots of issues with modding aka. no signal, wifi issues (like the cm7 and 9 ones) data issues, system lags, poor battery life, kernel errors on development, Overclocking settings not being saved, recovery mess-ups, and a lot of depicable stuff, most of all kernel-related.
Anyway, last night I flashed the stock rom over cm7 and noticed a real speed, functionality and battery boost, so I thought of just theming, de-bloating and optimizing the stock Sprint ROM.
Please follow me here:
We will never be able to flash custom kernels (not w/o the help of a reaaaaal good DEV)
CM9 &10, though they are eye-candy, are based actually on Gingerbread kernel, so no new features can be added besides the ones you can get withg new apps.
CM7, though stable, lacks the performance and functionality of the stock rom.
Finally, the stock rom as I said, (and I´ve tested TONS of ROMS in different motorola devices) is the one with the best responsivenness, snappiness and battery life, plus It's almost clean (eg. bloatware is easily removed.)
How will it be done?, you may ask.
Well Our first step, will be deodexing the stock GB SBF.
After deodexing we will be optimizing the build.prop on our phone, to trick apps into installing on our phones, and to make some quick optimizations.
Once we have deodexed our rom, we will be able to run,autorun and theme /system/apps.
Apps like Gnow, the statusbar and other tweaks can be easily (RELLY EASY) ported to deodexed ROMS
So this is the challenge guys, Let´s build our own stockcustom ROM.
So far I´m re-flashing stock sprint GB to continue testing only the essential apps, so we can build from there.
And just for a tease; here is my latest build.prop, with some tweaks and tricks taken from other roms and my personal experience, just make sure you have root access, fire up a file explorer and replace your build.prop
Please Refer to next post for links on how to maybe help me with deodexing the full rom.
And please, developers, dont take this as a shady move towards your development, I just think that the best way to make something is to start from scratch..... there are too many source files, modded files and crap files on cm7,9&10 specially when not officially supported (Because everybody messes with the files and re-distributes them, so a lot of clutter and unneeded files, references and code are injected on some releases....)
So my friends, we have a common goal, By now I have succesfully overclocked/undervolted the phone to 1350/233 mhz (not on recovery!!)
I´ve deodexed system/framework/
and Im stuck trying to deodex system/apps/
Xprt Owners of the world, please come on over here, we can do this...
I´m an architect/artist so I really want this to have a sleek look, but not copying a specific stock look, if you know what I mean....
From now on refer to the "wished features post" for features you´d like
And now my final statement:
Though it IS possible to compile JB or ICS from source to our phones, my experience with this somehow outdated android motorolas, is that you will not get significant performance boosts or super cool functions with new software. The only way to get this functionality is by upgrading the kernel which I again declare IS NOT POSSIBLE on our phone. CM9 and 10 my look like JB and ICS, but run straight off a GB kernel.
Yes you will get a lot of new stuff like menus and graphics, but the functionality will be the same, plus all the eye candy will trade off your new features with lags and possible errors.
Software is built in time with devices, and it doesn´t matter how much you say "but the hardware is capable of more!!", incremental software updates "ignore" some HW features, so they have to be forced or modified to run, which adds more procesess/tasks to the kernel and this will suck your speed and battery.
Let´s build something pretty...............:laugh:
Hello everybody, and welcome to the world of modding.
From today, we will be coordinating an army of people to work towards a common goal: Having the best ROM for our phones, and surviving the day.
The tools you absolutely need:
Brain
Hands
Eyes
Text-comprehension.
Be a self-troubleshooter
Advanced Google skills
Patience
Some Weed
First of all I will just oversee the topic: ODEXED vs DEODEXED
In simple words, Odexed systems have XX.apk and XX.odex, which store certain app properties (like icons, colors, fonts, menus) so that they wont be messed up with, thus making the system more stable, Deodexed systems, have only APK´s with their icons, colors and behaviors packed on, thus making theming, modding and using alternative system apps easier.
If you would LOVE to read about the subject, please refer to this: http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
Well, now that you are totally aware of the odex-deodex situation, you might ask yourself..
-how the phuck do I deodex my system??????
Well, deodexing implies merging the .odex properties onto the apk.
Hey!!!! but how???
you need brains, patience, Java SDK7, Android sdk, and music.
http://forum.xda-developers.com/showthread.php?t=1852322 this instructions are for deodexing.. good luck....
To save your time, you need Android SDK and JSDK properly installed, you need xUltimate (Try and find the version that works on you), and you need the patience and willingness of Sidharta.
Ive tried already 5 versions of xUltimate to find out errors on different files!!!!!!
http://forum.xda-developers.com/showthread.php?t=2065270This will tell you some other basics on the xultimate deal.
There are other ways to deodex, help me google that.
We will be based on the stock 1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-110-KNS-46-49-test-keys-signed-Sprint-US SBF....
I would love to develop something good to both sprint and boost, but I have a Sprint handset, so I cannot assure our development will work on boost handsets, so please just sprint handset owners only for now.
For xultimate errors and troubleshooting, please refer to Google.com!
Ive been up all last night deodexing my system apps, and found out that most google related apps cannot be deodexed...
maybe that's why you need to install gapps in cm7 or other custom roms...
anyway people, let's get fully deodexed.
Make sure you have both Android SDK and Java SDK 7 PROPERLY installed oin your pc before trying this.
Cheers, luck and please reply
One last thing, I dont know if it is related somehow, but try to flash your stock rom without a SIM card inserted
Quick update: I Think I´ve got it figured out....
You need full Android SDK, and Java development kit, Android sdk tools alone wont do it, and java alone wont do it, you need developer runtimes and libraries for some programs like xultimate to run right.....
And you need not to activate, use or anything your phone before trying to deodex, I guess just starting up and entering simple things as the time, or having a sim card installed, or your google account can write data on the phone and mess up with the deodexing process.....
xultimate has already deodexed full framework and has passed from the yesterday´s troublesome google quick search box...(first thing to fail last night) so let´s hope it goes well.. it is indeed a loong process...
and just another error, but now I think I have it figured out, you need smali-baksmali assembler/disassembler for some specific .jar packed files... I´ve just installed it, and hopefully will post a fully deodexed stock rom today or tomorrow, for you to test and for us to start theming.
remember if you want to try... you need jdk not just java, you need full android sdk bundle, and you need smali/baksmali on your jdk installation for it to work properly...
%#%"!!!
This completely sucks, I´ve been trying to troubleshoot the errors xultimate is throwing at me on specific files, that lead me to download A LOT of java JRE and JDK versions, and both in x64 and x32 flavors, which apparently caused a major mixup on my PC´s guts....
Now I´m freaking trying to clean up my dev enviroment, trying to re-set the appropiate paths and classes, but hell with it...
Anyone succeeded??? please let me know if you´ve tried and if you get into any error can you please upload a screenshot???
thanx
Sounds like hell. I haven't tried, because I just don't have enough time in the day to do something like this. Plus, the xprt is my only phone, so I can't afford to experiment on it much.
Sent from my XT720 using xda premium
tzuba12 said:
Sounds like hell. I haven't tried, because I just don't have enough time in the day to do something like this. Plus, the xprt is my only phone, so I can't afford to experiment on it much.
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
Same.
Sent from my MB612 using xda app-developers app
are you trying to deodex the stock rom?
rongsang said:
are you trying to deodex the stock rom?
Click to expand...
Click to collapse
yes sir, but in the mean time I managed to patch it with the battery mod, power menu and ICS style notifications
If I can deodex it I think I can improve it a little bit more in terms of performance and looks and functionality , but my powerful pc is a zombie right now, this is no task an old notebook can handle
I have deodexed it a long time back but sadly I can't upload it now. You can run kitchen from cygwin and it will deodexed your rom completely.
Sent from my MB612 using xda app-developers app
Ive used the kitchen and xUltimate with no good results mate!...
I always get smali errors or heap size errors despite I was using even a 4gb heap size, and tried using different versions of smali baksmali....
I am beggining to think I´ve been cursed by the digital gods.
BTW, if you´re able to upload it, I´ll be very thankful dude! I think Im going nowhere right now
GIve me tools to make my own rom pls
nuribg said:
GIve me tools to make my own rom pls
Click to expand...
Click to collapse
I don't want to sound mean but the fact that you're asking for it here instead of looking for it yourself makes me think you aren't up for it.(as if you don't know what you're looking for). And when you'l encounter the hundreds of issues instead of googling you'll ask for them here too?
However if you insist there are many good guides here available. Just a few taps away.
ok i didnt explained very whell, im using superR free kitchen but when i compile and install the rom gives me fail
Its not that simple bro. You need a Linux distro with Java 8 or 9 installed. The android SDK. A strong knowledge of Linux. You need a github account. You need to sync a repo for the ROM. And build your device tree. Some coding knowledge Is preferable. I can help you via pm when you get stuck but it took me a long time to be able to turn out a working ROM..