Overclock on Desire Z - G2 and Desire Z Q&A, Help & Troubleshooting

Ive done everything possible but apparently my version is not the right one, Im on the Bell network and Im very excited about this. Any help whatsoever would be great. Thanks.
Sent from my HTC Vision using XDA Premium App

If you are not running a T-Mobile G2 with HTC kernel 2.6.32.17, you MUST also give the kernel some other configuration options too! Pull the file /proc/kallsyms and search for the address values of acpu_freq_tbl and perflock_notifier_call. When loading the module, specify these addresses along with any other parameters: insmod vision_oc.ko acpu_freq_tbl_addr=0xc055e1a0 perflock_notifier_call_addr=0xc006c974
This is what I need to do but what does it mean?
Sent from my HTC Vision using XDA Premium App

Hello,
My name is Mirek and I am new here, that is my first post on that forum so if I write something wrong please forgive me and suggest me the right answear.
BACKGROUND:
I would like to overclock my HTC Desire Z also and I have made temproot (confirmed with the help of "Root Checker"), because I do not want to have a perm root or make complicated and risky (can brick the phone) downgrades of Android version and I do not want to loose my guarantee from the seller.
PROBLEMS:
(1.) Later on I have uploaded special scripts to my sd card and with the help of Gscript I have tried to use those scripts (I know there is also possibility to upload scripts to "/data/local/" without of Gscript app) but when I do that some error occure which says: "insmod: init_module '/data/local/vision_oc.ko' failed (Exec format error)".
(2.) From my later investigation and read post from different forums I know that is because file which I have uploaded to sd card "vision_oc.ko" has not actual addresses related to my current kernel version.
I have downloaded addresses from my Desire Z and I am enclosing that to this post (“kallsyms.zip”). I can find there address of “perflock_notifier_call”, but I can not find there „acpu_freq_tbl” address…
QUESTIONS:
(1.) Is it possible that the „acpu_freq_tbl” address is hiding on some another designation?
(2.) Maybe someone has already properly modified "vision_oc.ko" file for version of kernel "2.6.35.10-g7b95729" and can send me that so I can try?
(3.) I am enclosing to that post “kallsyms.zip” file with addresses from my Desire Z, maybe someone experienced can prepare new "vision_oc.ko" with the right addresses from the file which I enclose “kallsyms.zip” or at least can suggest how can I modify that "vision_oc.ko" by myself?
Can someone help me with that?
My kernel version is:
2.6.35.10-g7b95729
[email protected] #1
Android version:
2.3.3
Compilation no.:
2.42.405.2
Link to vision_oc.ko made in past by Michael Huang (coolbho3k) but for Kernel 2.6.32.17:
ww w.github.com/coolbho3k/vision_oc

Related

T-Mobile UK 1.76.110.6 system folder and config.gz

The system folder and config.gz from the T-Mobile UK G2 Touch.
-/system folder:
http://rapidshare.com/files/261342855/system_folder_from_T-Mobile_1.76.110.6.rar.html
MD5: BA140B0EF3F4B8068A72F7CB3BFDB1B5
-config.gz (as attachment)
Once again has a 10 download limit, would appreciate it if somebody could re-upload.
Cheers,
Phil
uploading it now
EDIT: all done
http://rapidshare.com/files/261350092/system_folder_from_T-Mobile_1.76.110.6.rar
Even a newer firmware? Nice! Checking the diffs now!
Edit: Just 6 Days newer.. SHouldn't be much changed..
To be fair it's probably just the addition of T-Mobile bookmarks, etc but I thought I'd put it up just in case there's a hidden gem.
Hello Sir,
I tried PM but for some reason I could not send it.
I have HTC Hero with dev watermarked software
HBOOT-1.75.2000
Radio 6.35.04.04
I downloaded T-mobile ROM you posted and I am wondering if I can just try to push the system folder to my device directly or there is something else I need to do as well ? Can I get step-by-step instructions please ?
Also if I put this release is there a chance that my device will get locked to T-Mobile network ?
Many thanx in advance
Hi there,
I'm afraid I don't know the answer to your questions. I followed instructions I was given to pull the system folders from the phones. What I posted wasn't actually a ROM that you can flash but rather a dump of the folder that contains the HTC applications, etc. This can then be used by ROM cooks to add the Sense UI to their custom ROMS.
I can't imagine that you'd be able to push the system folder across as the system folder is read-only on non-rooted devices. If you did somehow manage to push it across I doubt it would solve your problem but it also wouldn't lock your phone to T-Mobile, that goes much deeper than the system folder (please correct me if I'm wrong).
Cheers,
Phil
g2
sorry for maybe silly Q but i got tmobile G2 with 2.73 ROM but would like to downgrade it so can later install Modaco ROM and root it but can't do it with this updated ROM, as far as my research goes last few hours... now i got your files, could you tell me how i can downgrade it again to 1.76?
many thanks, michael
mishocub said:
sorry for maybe silly Q but i got tmobile G2 with 2.73 ROM but would like to downgrade it so can later install Modaco ROM and root it but can't do it with this updated ROM, as far as my research goes last few hours... now i got your files, could you tell me how i can downgrade it again to 1.76?
many thanks, michael
Click to expand...
Click to collapse
Checkout this:
http://forum.xda-developers.com/showthread.php?t=572683
thanks, guys, just removed my tmobile and will try now update it to modaco rom...

[ROM] Official G2/DZ shipped ROMs

Now,I have collected most original/official RUU.exe files for Desire Z and
Vision/G2 TMOUS zip files for the Users,Devs or Mods.
Uploaded all to "shipped-roms.com":
LINK http://shipped-roms.com/index.php?category=android&model=Vision
So we have all files collectively and don`t need to look for it.
Files which are available:
RUU_Vision_HTC_WWE_1.82.405.1_R_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168383_signed.exe
RUU_Vision_Orange_FR-B2B_1.85.73.2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_170528_signed.exe
RUU_Vision_HTC_ARA_1.83.415.2_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_168396_signed.exe
RUU_Vision_Hutch_AUS_1.85.861.3_Radio_12.28h.60.140f_26.06.02.27_M_release_172438_signed.exe
RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28b.60.140e_26.03.02.18_M2_release_154437_signed.exe
RUU_Vision_HTC_WWE_1.72.405.2_R_Radio_12.28e.60.140f_26.04.02.17_M2_SF_release_163285_signed.exe
RUU_Vision_HTC_WWE_1.72.405.2_Radio_12.28e.60.140f_26.04.02.17_M2_release_160660_signed.exe
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
Vision_TMOUS_1.12.531.0_Radio_12.18.60.05P_26.01.00.17_M2_144460.zip
RUU_Vision_hTC_Asia_WWE_1.34.707.3_Radio_12.28b.60 .140e_26.03.02.18_M3_release_154628_signed.exe
RUU_Vision_HTC_Egypt_1.72.466.4_Radio_12.28e.60.140f_26.04.02.17_M2_release_160882_signed.exe
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
RUU_Vision_HTC_WWE_1.22.405.1_Radio_12.26.60.1301_26.02.00.24_M2_release_151197_signed.exe
RUU_Vision_HTC_WWE_1.31.405.1_Radio_12.28a.60.140e_26.03.02.08_M_release_153504_signed.exe
RUU_Vision_HTC_WWE_1.34.405.4_Radio_12.28b.60.140e_26.03.02.24_M_release_155297_signed.exe
RUU_Vision_hTC_Asia_HK_CHT_1.34.708.3_Radio_12.28b .60.140e_26.03.02.18_M2_release_154602_signed.exe
RUU_Vision_hTC_Asia_India_1.34.720.3_Radio_12.28b. 60.140e_26.03.02.18_M2_release_154620_signed.exe
RUU_Vision_hTC_Asia_TW_1.34.709.3_Radio_12.28b.60. 140e_26.03.02.18_M2_release_154597_signed.exe
RUU_Vision_HTC_WWE_1.34.405.3_Radio_12.28b.60.140e_26.03.02.18_M2_release_154596_signed.exe
Click to expand...
Click to collapse
Theres no place like 127.0.0.1
Jobehonda said:
Theres no place like 127.0.0.1
Click to expand...
Click to collapse
everybody has 127.0.0.1
I guess he wants to use it as placeholder for the real IP...
I know garbage i was making a reference to theres no place like "home" or in this sense, 127.0.0.1 i didnt have the heart to tell him any other way. lol
http://www.thinkgeek.com/tshirts-apparel/unisex/generic/5d6a/
Hm,using this programm:
http://downstairs.dnsalias.net/homeftpserver.html
How you can get access,have done something wrong
How'd you host the files on my own computer
Also you need to give us an IP address we can access outside of your LAN, dont give us a number starting with 127, 10, or 192, those are all local. I recommend DynDNS or No-IP for dynamic IP updaters. if you need help PM me
I PM'd you
Test again:
Server: gani.dyndns-home.com
Port: 21 (if needed)
UPDATE:
All files now available at "shipped-roms.com".
Missed
RUU_Vision_HTC_WWE_1.34.405.3_Radio_12.28b.60.140e_26.03.02.18_M2_release_154596_signed.exe
Now added too
Deserves a bump.
Thanks, I've been using this thread quite often (I stupidly delete ROM's after I extracted stuff I need so I need to re-download them once the extraction business is on again... ). Having to look for it on page 3 or 4 is horrible so here we go, I get it back on the front page.
Link no longer works.
Link from first post? (shipped-roms.com)
I have no problems!
Can someone please explain to me and I'm sure others would appreciate, what is all the wwe ruu tmous stuff mean. I look at that list and barely have a clue what I should be flashing if I want the latest, what belongs to what provider etc. Also if your s off aren't there quite a few of these that if you flash you will semi brick?
I have tried finding a breakdown of all this info and had no such luck. If someone does not feel like explaining all that can u just tell me the latest tmobile released rom and if its safe to flash with s off and eng bootloader? Thank u.
Sent from my HTC Vision using XDA Premium App
does anyone here have the original belgian rom RUU?
Either 1.72.1100.x or 1.83.1100.x
I just got a replacement G2 and noticed i have a version number not listed in this thread
I have:
1.22.531.5 CL277427
Wondering before i root, if I can make an image or copy the rom into a zip file for anyone???
xsteven77x said:
Can someone please explain to me and I'm sure others would appreciate, what is all the wwe ruu tmous stuff mean.
Click to expand...
Click to collapse
WWE = World Wide English (?), means about as much as "global release". A version of a ROM which is released to one could say "unbranded" devices coming from HTC directly, intended for worldwide use. No G2, no Vodafone, just pure HTC.
RUU = Rom Update Utility, a Windows OS executable file which flashes a ROM onto your device, partially or fully. A so called "official RUU" is usually a ROM updater coming from HTC, still in it's untouched state, unmodified, means no root pre-included, no locks removed, no traps defused, just pure HTC.
TMOUS = T-Mobile USA. Questions?
I look at that list and barely have a clue what I should be flashing if I want the latest
Click to expand...
Click to collapse
Technically quite incorret but it will do as an explanation: we all have the same devices, they are just distinguishable by the software put on them. Since the hardware is the same, all devices worldwide will run every "Vision" ROM there is. So basically, as normal in IT, take the one with the highest number and youre good to go 1.34 is older than 1.72 is older than 1.84 is older than (...). The stuff after 1.34.xxx is for the "release/sales region" a ROM is intended for. 405 for example is more or less western europe, so ROMs released for the german/austrian/swiss/whatever market are 1.xx.405.z ROMs.
what belongs to what provider etc.
Click to expand...
Click to collapse
Doesn't matter, a Vision is a Vision. A "provider ROM" just means it will have some provider specific junk loaded as opposed to a "clean" HTC ROM. Exception: G2 vs DesireZ. G2 is "pure" Android (with T-Mo junk) where as DesireZ get Sense from HTC.
Also if your s off aren't there quite a few of these that if you flash you will semi brick?
Click to expand...
Click to collapse
Semi brick? If you got a semi brick unbrick it by flasing something which works. Beauty of flashing HTC devices. Ever heard of locked Motorola bootloaders? A pain in the hole, and very much at that...
...and if its safe to flash with s off and eng bootloader?
Click to expand...
Click to collapse
S-OFF and ENG Bootloader means your device is basically (very stupid things to do excluded) bomb proof. In this combination there is almost always a way to get it back to a working state. One thing I would consider: I'd take a modified, pre-rooted ROM, an "official" ROM might close a loophole used to root and crack and hack the device.
Mikey1022 said:
Wondering before i root, if I can make an image or copy the rom into a zip file for anyone???
Click to expand...
Click to collapse
You'd need a custom recovery for that. And without ROOT you can't load a custom recovery. Hmm... you could temp-root, put recovery on, factory reset (wipe temp root stuff off device), pull a backup, and then perm-root. This way you'd get a quite clean backup. Anyone disagree?
I'm not able to download a single file, either download never starts or it just stops randomly at any point during the download have not been able to download more than 50mb
This may be obvious but which country is AUS as in RUU_Vision_Hutch_AUS_1.85.861.3_Radio_12.28h.60.14 0f_26.06.02.27_M_release_172438_signed.exe ?
Australia....
Desire Z - with XDA Premium
Thank you, ok so what is XDA premium?

Telus HTC Desire HD 2.3.3 Root and Flash

Hello XDA forum!
I've been researching my topic for some time now and I noticed alot of vague information and the only usefull info seemed to be specific to each model... So, I have a Desire HD and my carrier is telus.
1. Is my phone branded or not? (There's not a bunch of telus apps or wallpapers, there is just one telus scene. Also it says HTC on the back where you would expect it to say telus)
2. Can you downgrade the Telus HTC Desire HD running 2.3.3 Gingerbread at this time? If so what tools would you use?
The reason I am doing this is because everything seems to be very vague information that, like stated above, seems to be specific to each post. However all the posts that I've read don't describe the methods used to identify key information or how to troubleshoot what to do if a step doesn't work (ex. Getting $ instead of #)
If someone could post back on this it would aid me greatly. I aim to downgrade, root, and flash Android Revolution HD and possibly a new radio to improve battery life and signal strength (which is non-existent in my basement)
My phone info is...
Android version:
2.3.3
HTC Sense version:
2.1
Baseband version:
12.56.60.25U_26.10.04.03_M
Kernel version:
2.6.35.10-gdc4b908
[email protected] #1
Fri May 20 22:02:48 CST 2011
Build Number:
2.43.661.1 CL70542 release-keys
Software number:
2.43.661.1
Browser version:
Webkit/533.1
Please if you have an answer or anything to say regarding my post please use full explanations so that this thread can be useful to other members/guests.
Thanks in advance!
PS. Any additional information you require from me don't hesitate to ask!
Now running Android Revolution HD!!
Ok so I found some key factors in this that I'd like to point out to anyone looking into rooting and flashing a custom rom.
First Downgrade
Settings > About Phone > Software Information > "Build number"
That is what you're looking at when searching for a downgrade. 1.32.405.6 is what you want to be at.
The downgrade guide I used is here.
Remember if your build number is above 2 you'll need to use section 2b and skip 2a
Make sure you download the attached folder at the bottom of the first post and the stock 1.32 ROM (link in section 1)
After this point I had a stock phone with 2.2 Froyo build number 1.32.405.6. My speakers did not work (no sound at all) and I could not connect to the mobile network which alarmed me at first thinking that Telus wouldn't like me hacking my phone or something x3
Second Root
Telus Desire HD - Rooting and Flashing
This was the first guide I tried to follow and it would have worked if it had simply added in that extra file and the commands:
Code:
adb push misc_version /data/local/tmp
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
./data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
Anyways I downloaded the files for this one (the light version since I had previously downloaded the PD98IMG.zip) and skipped to step B.b
I did the temproot successfully but the easy radio tool wouldn't work for me so I just used Visionary+ to permroot and Then I got the superuser request on my phone and the radio finished rapidly.
Went very smoothly after that.
Third Flashing!
Finally the time came when I was ready to flash my shiny new ROM. I read through step C of the above mentioned guide but decided to go through with the proccess mentioned in [ROM] Android Revolution HD™ 6.1.3 since it was more of a do it yourself thing and I like starting clean (it wants you to run superwipe from cwm before flashing the new rom)
I would recommend using a card reader rather than mounting as a disk drive cause it's more reliable.
Hope this helps someone!
Not sure if this has been said or not but:
http://www.xda-developers.com/android/how-to-root-the-htc-desire-hd/
It's as easy as "download, run" and it works brilliantly!
I suggest you just boot a Ubuntu Live CD (it's not as bad as it sounds, I actually liked it the first time I tried it and now I have it installed by my Windows) and just run the command:
wget http://droid.neolobster.com/roms/aahk-25102011.zip && unzip aahk-25102011.zip && sudo ./hack-ace.sh
Click to expand...
Click to collapse
in terminal, press "1" and be afk for 5 mins.
Doesn't erase your data, doesn't format your phone, doesn't downgrade your Android OS. It...it just works!
Good luck with it
does the method dragancla posted work for the Telus Desire HD?
milestoned said:
does the method dragancla posted work for the Telus Desire HD?
Click to expand...
Click to collapse
I was just about to ask the same question, and if you can return to stock, but then I checked the Advanced ACE Hack Kit (AAHK) thread:
http://forum.xda-developers.com/showthread.php?t=1259821
Where it says:
Easy return to stock for AT&T, Telus and WWE CID HTC__001
Click to expand...
Click to collapse
Might be worth a shot
I worked for me. thx
which method worked? the one mentioned by dragancla or Nekura7?
root
I wanna root my desire hd can anyone help me , its my first time to root my phone. Can somebody messge me the full steps for first timer , my current version 2.3.3 sense 2.1 i was thinking to root it to sensation xl rom??? 2.3.4 sense 3.5 and beats enable? And usb host capable? Please try to help me thnks , [email protected] heres my email,
milestoned said:
does the method dragancla posted work for the Telus Desire HD?
Click to expand...
Click to collapse
Yeep! It sure does work I tried it and flashed the android revolution hd rom. Brilliant thanks a lot! Only thing is the sound seems a little different. It is much louder but also has this tinny effect at times. I will patch the cm7 audiofix and see how it goes.
Go to htcdev dot com, you'll find the official way to do it by HTC
luismontreal said:
Go to htcdev dot com, you'll find the official way to do it by HTC
Click to expand...
Click to collapse
I tried that, but the HBOOT update failed every time
I can confirm that the Advanced Ace Hack Kit works
how to root desire hd
I want to root my Htc desire hd . Please guide me in right way
My phone info is...
Android version:
2.3.3
HTC Sense version:
2.1
Baseband version:
12.54.60.25U_26.09.04.11_M2
Kernel version:
2.6.35.10-gd2564fb
[email protected] #1
Thu Jun 9 14:20:29 CST 2011
Build Number:
2.50.61.3 CL123205 release-keys
Software number:
2.50.61.3
Browser version:
Webkit/533.1
Please if you have an answer or anything to say regarding my post please use full explanations so that this thread can be useful to other members/guests.

[Q] question about ROM Kitchen and Wildfire S

i am wanting to experiment with making a ROM for my WFS. i have ROM kitchen, but it doesnt natively support these phones. i have seen a thread or 2 from people that have made a ROM with the kitchen, so i was wondering if the ones that have done it can point me in the right direction to making the mount file needed to make it work right. any help is greatly appreciated, and i plan on sharing my creation here if i get one stable and working.
*note-i tried to ask this question in one of the mentioned threads, but it wouldnt let me post in the dev forums. not a problem, but wanted to explain why i asked here.
easy nuff
I've used it. What carrier you with? And what software number you got fron that carrier [Found in menu settings about phone software info]? What version of kitchen did you install on what kind of platform? Ok I asked three questions, shoot me the answers back and feel free to ask three of your own.
Rob
I have virgin mobile USA. I'm running 2.3.4, and i have kitchen installed on Ubuntu. Not sure what version of kitchen, it was the latest one from the original posting of it.
Sent from my Wildfire S
i was away from my computer when i read your response. my kitchen version is 0.182, the newest one on the official thread.
noted
Ok. What questions do you have about the kitchen?
Rob
just mainly wondering how to get the mount points i need to make the ROM work properly. aside from that unless you have any tips for a new guy, then i think thats all. i appreciate any info you provide, and i also appreciate you responding.
Rom Kitchen
Since you've made it through the setup (I assume). For your stock Rom, (in recovery) run a nandroid, now clear all your data (factory reset) and run another nandroid (just something I like to do to ensure no data will be pulled... Probably not necessary but it gives you your revert to (with data) and your (clean) build nandroid. Now take your build nandroid and open it up with a file manager (ie es explorer). You will want to grab two files from this nandroid... boot.img & system.img (may have called it system.yaffs2.img but just grab it and rename it to system.img). Ok now you have your ingredients for your first build. Connect the phone to your computer (USB storage) pull the two files across to the folder in your home directory that says put Rom here. You are ready to start cooking. Start the kitchen and use those 2 files to build your working folder. You can also try out the various features dsixda has built in. For example lets say you make your Rom rooted, you add apps2sd support, and just for giggles you deodex too. Now any additional changes you want to make can be done in the working folder. So, for our figurative example lets say you wanted to delete flashlite and add a full flash player, download the apk (think there are links to flash player or new market in the app & theme forum), delete flaslite.apk from the system folder in your working directory and paste your full flash player.apk in... Ok you've done all the editing to your working folder that you want to do (lots that you can change, but you want to have a working build and you don't have to make any changes to working folder if you just want to go through the options and read what the kitchen can cook in automatically; as you gain knowledge, you will edit your working folder more and more by hand, but that time will come). Ok start back up your kitchen and make sure all the options you wish have been completed (option 10 I think). Then if it all looks good, cook it (option 99); Also make sure you convert the update script back to updater. Go to the output folder and there you will have your flashable Rom. And thus concludes the lesson for today ;-)
Rob
InsaneDDay69 said:
just mainly wondering how to get the mount points i need to make the ROM work properly. aside from that unless you have any tips for a new guy, then i think thats all. i appreciate any info you provide, and i also appreciate you responding.
Click to expand...
Click to collapse
thanks insink71 for your help. but I think what he mean is kitchen template in 'edify_defs' dir.
there is no template for marvel (I'm stuck too )
example:
Code:
edify_defs # cat vivo
# HTC Incredible S
change_mnt=yes
param1=ext3
param2=MMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p25
cache_mnt=\/dev\/block\/mmcblk0p27
boot_mnt=\/dev\/block\/mmcblk0p22
data_mnt=\/dev\/block\/mmcblk0p26
sdcard_mnt=\/dev\/block\/mmcblk1p1
edify_defs #
zero13th said:
thanks insink71 for your help. but I think what he mean is kitchen template in 'edify_defs' dir.
there is no template for marvel (I'm stuck too )
example:
Code:
edify_defs # cat vivo
# HTC Incredible S
change_mnt=yes
param1=ext3
param2=MMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p25
cache_mnt=\/dev\/block\/mmcblk0p27
boot_mnt=\/dev\/block\/mmcblk0p22
data_mnt=\/dev\/block\/mmcblk0p26
sdcard_mnt=\/dev\/block\/mmcblk1p1
edify_defs #
Click to expand...
Click to collapse
You are correct, but the tips are invaluable to me as a beginner. I have read somewhere that there isn't a new template to make for the marvel, but I don't know if its true. That was the reason for my asking lol. I appreciate the responses.
Sent from my Wildfire S
edify defs
I didn't make one [and cooked a couple stock roms], but thanks for bringing it to my attention. I'll look into it.
Rob
It may not require one, but according to dsixda it should. Either way you have been very helpful in getting me started with developing.
Sent from my Wildfire S
It doesn't matter if gsm or cdma, what rom version you have or what os you are running to use the kitchen. Then the mount points won't matter either, as the kitchen defaults to mtd which is nand devices. In which the wilfire is one, the only time you need to worry about the mount points is on a emmc device.
Which below is why those files matter for the emmc devices:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p26");
or
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/system");
Those are from my hero s rom's updater. Where the nand devices always use something like below:
Code:
format("MTD", "system");
or
Code:
mount("MTD", "system", "/system");
Where the above is from my leansense rom for the uscc wildfire s.
Edit: Here is the marvelc's virgin mobile and uscc mount points. The first is from my device config for cm.
Code:
#dev: size erasesize name
#mtd0: 00100000 00040000 "misc"
#mtd1: 00500000 00040000 "recovery"
#mtd2: 00340000 00040000 "boot"
#mtd3: 106c0000 00040000 "system"
#mtd4: 02300000 00040000 "cache"
#mtd5: 09600000 00040000 "userdata"
#mtd6: 00500000 00040000 "devlog"
Also off topic but just so you guys know the process you used to s-off corrupted the misc partition. Which makes fun for weird and stupid issues. Then also like on the desire and others a corrupted misc partition bricks usb and such. I have the stuff for uscc and virgin mobile, I just have to get it up in a post how to fix it.
Thanks
I figured we had cleared the memory block instead of altering it. That will be a very useful tool. Thanks so much.
Rob
Sent from my marvelc A510c using Tapatalk
2fast4u88 said:
It doesn't matter if gsm or cdma, what rom version you have or what os you are running to use the kitchen. Then the mount points won't matter either, as the kitchen defaults to mtd which is nand devices. In which the wilfire is one, the only time you need to worry about the mount points is on a emmc device.
Click to expand...
Click to collapse
So here's another marvelc wannabe chef that made it to this thread with the same questions. I thought my problem was not having a marvelc file in my edify_defs... thought the _template indicated I needed one.
2fast4u88 said:
Also off topic but just so you guys know the process you used to s-off corrupted the misc partition. Which makes fun for weird and stupid issues. Then also like on the desire and others a corrupted misc partition bricks usb and such. I have the stuff for uscc and virgin mobile, I just have to get it up in a post how to fix it.
Click to expand...
Click to collapse
Corrupted misc... wow... how is that fixable? Or how can I verify whether I have a corrupt misc?
Here is my problem, perhaps someone has ideas how to proceed. I am fairly new to this, as you may guess since I am here and am asking questions I downloaded some ROMs that simonsimons34 cooked up. When I flashed them, the phone would get stuck on boot, on the mfg logo screen. adb logcat would not capture anything when I tried. (I have captured it for a working ROM boot, so I think I know how to do it). I also inspected the recovery.log and found nothing weird there. Then I downloaded 2 versions from insink71 and they both booded, but the newer one had issues running, which for now is beside the point. Point is they BOOTED! So now I tried to cook my own. Trying to start simple I made no modifications, just sent a known working nandroid through the kitchen and recompiled and it get stuck trying to boot. Again no output to logcat, recovery.log looks good. So I came across the edify_defs in the kitchen tools and figure that's where my problem is. build.prop has ro.product.name=marvelc and _template tells me I need a marvelc file. Of course I don't know the mount points. So now I read you don't need it? And insink71 says his ROM did not use a marvelc?
Any pointers from thos that have gone down this road would be greatly appreciated! My environment:
phone HTC Wildfire S Virgin Moblie, A510c
windows 7
oracle VM VirtualBox
linux 11.10 with java6
DsiXDA kitchen 0.183
Regards,
Rich
help
rkleinhenz said:
So here's another marvelc wannabe chef that made it to this thread with the same questions. I thought my problem was not having a marvelc file in my edify_defs... thought the _template indicated I needed one.
Corrupted misc... wow... how is that fixable? Or how can I verify whether I have a corrupt misc?
Here is my problem, perhaps someone has ideas how to proceed. I am fairly new to this, as you may guess since I am here and am asking questions I downloaded some ROMs that simonsimons34 cooked up. When I flashed them, the phone would get stuck on boot, on the mfg logo screen. adb logcat would not capture anything when I tried. (I have captured it for a working ROM boot, so I think I know how to do it). I also inspected the recovery.log and found nothing weird there. Then I downloaded 2 versions from insink71 and they both booded, but the newer one had issues running, which for now is beside the point. Point is they BOOTED! So now I tried to cook my own...
And insink71 says his ROM did not use a marvelc?
Any pointers from thos that have gone down this road would be greatly appreciated! My environment:
phone HTC Wildfire S Virgin Moblie, A510c
windows 7
oracle VM VirtualBox
linux 11.10 with java6
DsiXDA kitchen 0.183
Regards,
Rich
Click to expand...
Click to collapse
Ummm all my roms have been for marvelc and all have booted and run decently [by most accounts]; you had a unactivated phone. I would guess that my first build [from shortly after root] was activated. Team marvelUSc will always release working boots; which, should work activated or not because they're using base roms from official RUUs to build with. Until yesterday, I was just working from copies; but today I have RUUs thanks to the wizardry of Football [see first stickied thread in development, contact him, donate to his work- he will probably share openly after he receives enough donations to cover his expenses gathering them] Other roms have been written for marvelc [some of which, may have failed to boot]; not my concern. Whether or not one has a marvelc device to test with [which is what I relayed to you]; potential concern for development; but not mine since I do have a marvelc and I do test my roms. Having a non-booting rom; that would be a grave concern [if it happened to me or the new team; also formed yesterday]...
The kitchen is a tool that people can try, or even [contrary to opinion] developers can use it too [and teach people how to get started; which being helpful and relaying knowledge; which, is the sect of XDA I'm from]. There are other tools as well.
Yesterday, when I got official RUUs, I tried to do the smart thing; [team build]. Simonsimon34 thought it a decent idea, I handed him the vm RUU. I went to who I believed to be a US Cellular developer [see the informative post above... though I won't mention names]; he was busy writing a post launching personal attacks at me [which have already been deleted], I withheld the USCC RUU meant for him. It was my intention to look at MetroPCS, and I did that briefly and made a rom [that boots and works] from it with dsixda's kitchen. If yesterday I sent you a message when my blood pressure was through the roof; I apologize. I will continue to help you privately via email on the version numbers etc for kichen if you wish. Just wanted to tell my perspective.
Rob
insink71 said:
Just wanted to tell my perspective.Rob
Click to expand...
Click to collapse
Thanks, Rob, I took no offense to posts or email from you, all info I got from you has been helpful. There's one more bit of info I have I forgot in the summary above: I had a PM from someone who ALSO had an unactivated phone, and he had no problem flashing and booting simonsimons34's ROM which failed to boot for me! So it's probably not the fact that mine is not activated... I really thought I was doing something fundamentally wrong until I downloaded your ROM and it booted fine. Now I am planning to look through the kitchen scripts to learn more about the process of making a ROM. I'm fairly tenacious and will get this to work some day I'll email you with something you may be able to help me with.
Regards,
Rich
so... in summary,
can someone create a template or upload a 'working' kitchen to cook custom ROM for marvel/c?
zero13th said:
so... in summary,
can someone create a template or upload a 'working' kitchen to cook custom ROM for marvel/c?
Click to expand...
Click to collapse
it works just fine for the wildfire s, as long as the base ROM was for the same phone. I'm not sure about porting yet though, it may need a template.
Sent from my ICDroid X

[Tools] Best HTC & Android Tools

I realized that we all need a thread like AllInOne thread. And started to make a post like this. I hope you like it.
SuperOneClick
Universal root and unroot kit for all Anroid Devices.
Link : http://turbobit.net/26dewv4ncij3.html
Apk Batch Installer Tool
You can install Apk files via your PC to your phone.
ps: You need root access for this and don't forget to enable ' Android USB debugging'
Link : http://turbobit.net/yn2t43g4moj6.html
Universal HTC USB Driver
Universal HTC Driver for Windows OS
Link : http://turbobit.net/uqkmxha4btoa.html
HTC QuickRoot Tool
Universal root & unroot tool for ONLY HTC Devices
Link : http://turbobit.net/42t4v5eb3e6x.html
Apk Editing
You can edit any apk file via this tool,you can install new language for your mobile software and make adjustments on apk files.
Link : http://turbobit.net/b533rjhjrou9.html
Android Language Project , Language Editor , IMEI Restore
You can install new Languages to your custom rom on your device and edit the old language. (NEED ROOT)
And you can restore imei on Samsung,HTC and LG devices.
Link : http://turbobit.net/0nb4vqm16xf5.html
Supercharger v6
It allows you to speedup your device,and it's Universal, you can apply this script to any Android Device.
Link : http://turbobit.net/qsz342o0ir68.html
Ps: Thanks you for all of these software's producers. And these are not my own software I just wanted to SHARE.
Not a bad idea to have this thread but it belongs in the general section
Also I wouldn't even mention click to root apps/programs here, maybe instead link the xda wiki
Probably should add some scripts/mods specific to the vision here like kebezies aroma installer for nik3r's data swap
Or some of the keyboard changes
Sent from my HTC Vision using xda premium
I'm not sure those rooting apps will work with the desire z... have u tested them? I rooted a long while ago, so i might not be up to date with rooting stuff, but afaik to root our device it had be done manually, or ud have a big risk of bricking... As for the other tools, i think having a link to the htc drivers is the most usefull... but anyways, thanks for caring and putting this stuff up, might come in handy some day
Coldsun15
coldsun15 said:
I'm not sure those rooting apps will work with the desire z... have u tested them? I rooted a long while ago, so i might not be up to date with rooting stuff, but afaik to root our device it had be done manually, or ud have a big risk of bricking... As for the other tools, i think having a link to the htc drivers is the most usefull... but anyways, thanks for caring and putting this stuff up, might come in handy some day
Coldsun15
Click to expand...
Click to collapse
I tested the superoneclick and it worked for me on 20+ devices including Desire Z.
and this post is just a test for me,I mean If i get positive opinions i'll improve this post more and more. just triying Thanks for your attention
Wrong section, but nevertheless good programs, except for they won't let me download, the download site says unavailable in my country.
can't donwload,is it possible to add mirror please?
Hi Guys - look them http://androidcommander.com/
Respected sir
how can i get full version of this software
android language project ..?
can u provide me the direct link to download this software with crack file
thanks and regards ..

Categories

Resources