yashsingh1/xdaforums huggingface dataset:
[P3600 ROM Development] Kenzneth:
Thank you for spending time on me

I know it is rather annoying to explain a few things

Really Really Thank you for helping me

I hope that my post could be a guide for others

Update:

The rom is still unbootable after a day of trying.

Does the OEM section be edit before updating the build?

Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]

May be i started from the wrong step?

What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5

Thank you for spending much time on helping me

If it can be google, simply give me the keyword,

I will finish the entiry

And finally, thank you!!
[P3600 ROM Development] SuperSport:
I'm actually going to bed before 3am tonight, so I will not be long here, but I just had a thought. When you cook the ROM, are you checking "Real WM 6.5 AKU" in the Kitchen? Don't do that. You cannot actually use a Native 6.5 Kernel on the Trinity as one does not exist. Also, as mentioned by the.Decoy before, you MUST have 'wince.nls' in your Kitchen somewhere or it will not boot. Thirdly, try cooking a version without ANY Extended packages. Only the original XIP and SYS and see if that boots. When you get that going smoothly, start adding EXT packages. Good Luck!

I'll check back in a couple days to see if you've made any progress. If you'd like to send your kitchen to me also, I'd be happy to look it over and see if I can find anything wrong in there. ;)
[P3600 ROM Development] Kenzneth:
Again and Again

I keep remind myself that Native 6.5 Kernel should be checked

OMG The Bug is here

And Thanks Decoy

Thank You

Thank You!!!!!!!!!!!!

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

Update:

I saw a folder called 0_ROM_Version in EXT Shared

What is it and what function does it have?

Thx
[P3600 ROM Development] the.decoy:
Ummm are you trying to use a freshly extracted OEM from an official ROM? :eek:

If so then yes, there is a massive amount of conversion that must be done to it before you an cook it into a rom. Even before you break it up in to components and edit all the reg and dat files ... you first need re-sign everything with an SDK cert because you won't have the official cert that HTC built them with.

Seriously. If you are just starting out then use an existing chef's OEM (use mine or anyone else who has posted a kitchen).

Even I have not yet ever had the time to complete build an OEM from scratch (not that I don't want to one day). I was always just adapting the OEM that Chanvi had provided us in his kitchen, primarily because he had already done all the work to make it mesh with WM6.5

I am bit confused by what you said there :confused:

As Supersport explained, we do not have a Native 6.5 kernel for Trinity.

So that option should not be checked.

Again, this is why I said to try "Load ROM" and see what happened :D

Those are just simply EXT packages which contain 1 single provxml. Each one sets the registry value for "ROM Version" (the info that comes up in "About Device" in Settings). There is one for every type of "Saved ROM" you can build from that kitchen.

I created them so that people could build each of the several types of rom from my kitchen but never need to edit the provxml files to change what the version info was.

If you are going to try cooking your own roms, the best advice I can give you is find a text editor you like and just start opening up ALL of the REG DAT RGU and PROVXML files you can find and see what they are doing.

You can even do it from within EVK. Select the type of file on the left panel called "Editors" (or just select "All") then click "Show Editor". You can open the files it finds by double clicking them in the panel on the right.

Anything custom that ever happens in the setup of a rom is controlled by these files.

If you want to see how something works (or what it does), just open up the files and read them ;)
[P3600 ROM Development] Kenzneth:
Sorry, wt i mean is that my rom become bootable after unchecking it

~~ :D That is so amazing ~~

Now i am Reading the horrible, endless.....etc tutorial, [I can finally have my own rom :D]

1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.

I googled around and found several solutions.

1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]

2 is that i should mod the size of the xip.bin

Therefore it is big enough to store it.

3 Adding in some registry with my selected country code

Thanks for helping me :)~~
[P3600 ROM Development] the.decoy:
Sorry can't help you there. :(

I have never ventured beyond WWE lang for my kitchens.
[P3600 ROM Development] Kenzneth:
nvm

I am now porting a new phone canvas to the rom

Yet i found hard but still find no ways to edit the registry

I even tried the rgu edit in EVK

Yet none of the rgu file shows what i want

I think those are stored in boot.hv, isn't it?

However, I can't even convert it with the hv to rgu

Or there are other ways to edit it?

Thx for helping

========================update

Got Silly Mistake = =

The Rgu inside the folder is what i want to edit
[P3600 ROM Development] Kenzneth:
Hi Decoy or other guy who can help me

After i Built up my rom, i found Camera doesn't work

When ever i try to open it, it report that link is missing.

Even i click it from windows folder,

It cannot open as well

Sth like Unsigned ......

Any way to solve that?

And the most important,

Usb to PC can't Disable the Advance Network Fuction

It keeps reporting me "failed to disable rndis to use serial"

I hav not created any ports

Yet i found some fix with registry editing

Yet I found it hard to search through the RGU foler

Anyway to do that?

Thx!!
[P3600 ROM Development] SuperSport:
Hello OPzero,

I am sorry, but due to our language differences, it is a little hard for me to fully understand what you are asking, but I'll try. ;)

I think I may have one answer for you. If you are asking how to edit the RGU files, simply browse to the folder that contains the RGU you want to edit, then right mouse click on the RGU file and select 'Open with...', then select 'Notepad'. Make all your changes, then save the file. If the file is blocked from saving changes, right mouse click on it again, select 'Properties', and remove the check from 'Read-only', save the file, then replace the check back to the 'Read-only' attribute. I hope this is one of the questions you were asking.

Lately, I have been using the Kitchen for all my XML, RGU, REG, DAT, Provxml, etc, editing. All the files are easily found this way, and the 'Read-only' attribute is automatically removed for saving. Using this method, you have access to ALL the files. If there is a reg setting in the kitchen, it will show up here. It may be found in REG, RGU, DAT,Provxml, or Initflashfiles.dat. They all have the ability to make changes to the Registry.

About the dialer, somebody else will need to help on that subject as I am over my head on that one.

PS: While in any of the editors, hit 'Ctrl' + 'F' on your keyboard to bring up the 'Find' window. This will help you find that hidden REG key you are looking for.

PPS: You are sure gung-ho by starting your first kitchen the way you are, from scratch. I started by using a complete working kitchen, then making small changes to it one at a time. But, Good Luck! It will be nice to have another chef on the forum. :D A lot of us have had to let it go for a while so we can focus on our 'Other' lives. I have been slowly working on another release, but it may still be a while till it's ready. It's based on an older ROM of mine, but cleaning it up for daily use.
[P3600 ROM Development] the.decoy:
Yeah, Supersport pretty covered it.

"Unsigned" error means you have not included the SDK Cert(s)" so that you can run unsigned apps.

I have the SDK certs embedded in one of the Provider PROVXML files in my OEM. You can find thaty PROVXML file and include it in your OEM.

Sorry, Phone cavases are beyond me too. Even though I have tried :(
[P3600 ROM Development] Kenzneth:
Sorry For my Bad English

I forgot to check again before pressing the post:p

Thx for helping
[P3600 ROM Development] SuperSport:
Please don't be sorry about your english. You are doing fine. :D I only wish I knew other languages so I could understand more. If I cannot understand, I will ask for clarification. ;)
[P3600 ROM Development] Kenzneth:
Still having trouble with the advance netwok problem....

When ever i uncheck the option in USB to PC, it reports "Failed to disable RNDIS to use Serial"

Any fix for that? thanks!!:(
[Nexus One Q&A, Help & Troubleshooting] roberto188:
Periodically When i open my marketplace it only shows the apps installed to my phone. The other apps that are installed to my SD card are not shown. I have to then clear the data and cache from the market and it refreshes. Any ideas why this keeps happening?
[Nexus One Q&A, Help & Troubleshooting] jimbobalu:
I am having a similar issue but I only see 7 of my like 30 installed apps. It seems to just be my purchased apps and Google maps. I have cleared the cache and force stopped it but it is still not displaying all my downloaded apps. Stock N1 with 2.2

Thanks
[Nexus One Q&A, Help & Troubleshooting] mtw4991:
Happens to me too occasionally. I uninstall Tmo's MyAccount, then reinstall it...bam! apps are back.
[Touch 3G General] Patpwns:
hi, i havent had any windows mobile phone before, im completely new, however im not stupid and can learn quickly :)

ive ordered a clone, to get used to it, then ill buy a real jade once im familiar with it all ! :D

so ive ordered one of these :

www . dealextreme.com/details.dx/sku.12811

so does anyone know how i go about installing a WM6.5 rom on it ? ill need guiding alot as i dont know what software to use to flash or what to do etc...

all help is appreciated

thanks

Tom
[Touch 3G General] cPT.cAPSLOCK:
If you're not stupid, you should be smart enough to read the stickies and such ;)

if you read this you will see you have to run this to unlock your device, so that you can install custom ROM's on it.

Just follow the steps provided.

Next, you can download a rom. the rom will have two files: customRUU.exe and ruu_signed.nbh

Just hook up your device to your computer, run customRUU.exe and you're done!

Flashing takes about 10 minutes, and in my experience you can use your computer while it's busy.

After the ROM is flashed, hard-reset your device to make sure the ROM is loaded correctly by your device.
[Touch 3G General] mua30:
Bro,

keep in mind, that although the phone is clone to HTC jade or elphin, the hardware between the original & clone is deffer, so all the roms here will not work on ur incomming clone.

Add to this it will not be at that good quality like HTC or ACER or Lenovo or samsung....

at the end, its ur decision.
[Touch 3G General] Xenograph:
same opinion here:

wouldn't have ordered a clone, but the original. difference in price cannot be that huge any more.

sorry lad, you're on the wrong track.
[Touch 3G General] haree:
not development related moved to Jade general
[XPERIA X1 Q&A, Help & Troubleshooting] Paitor:
Hi,

first off I have to say that I have the Scandinavian keyboard with åäö.

I have tried allot of itjes roms and right now I am using 20905 of the standard Energy ROM from NRGZ28. The problem is that it is almost impossible to write without double space and problems with that åäö isn't written in the same order as a push the keys. (instead of "hej där" it will be "hej ädr") It can't be something wrong with my phone because it works with stock ROM. Is it that these ROMs doesn't work with Scandinavian keyboard?
[XPERIA X1 Q&A, Help & Troubleshooting] Draken Korin:
Mod. edit: not dev related,moved to general

sounds like auto correction issue...

set \HKCU\ControlPanel\Sip\SuggAutoCorr to 0 and soft reset to disable it, try again and drop feedback

best :)
[XPERIA X1 Q&A, Help & Troubleshooting] Paitor:
i to I isn't the big problem though.

Edit: I removed that question so we can focus on the real issue here.
[XPERIA X1 Q&A, Help & Troubleshooting] mal13:
If you mean using hardware keyboard with äöå... then you need to edit registry.

open total commander and go there plugins -> registry -> HKLM -> HARDWARE -> DEVICEMAP -> KEYBD -> CurLang: Hex: 40B.

Or if you want use different keyboard for touchscreen...FingerKeyboard 2.1 and there's swedish layout.

Hope that helps and take XT9 off. There's also language settings for xt9 but i find it very annoying so i won't use it.
[XPERIA X1 Q&A, Help & Troubleshooting] Paitor:
Yes I mean that I have the problem with double or triple space and letters in the wrong order with the hardware keyboard. Changing language for the keyboard is already done otherwise I wouldn't get the åäö letters at all.
[Nexus One Q&A, Help & Troubleshooting] roberto188:
Anyone know how to get the battery percentage to show in the battery icon in Froyo? Thanks.
[Nexus One Q&A, Help & Troubleshooting] blaboy51:
cant happen until froyo source is out.
[Nexus One Q&A, Help & Troubleshooting] allofusjw:
You can, but not perfect

I too wanted the percentage in the battery. In the development thread you'll see that the phoenrom has it included in the rom. I ended up making my own custom rom with the kitchen made by dsixda just to get that damn percentage in the battery icon! Its also not a very accurate measurer of percentage as it only works in percentages of 10(40,50,60etc). I still like it though.
[Nexus One Q&A, Help & Troubleshooting] leonnib4:
Now that the source is out,

I tried to apply the bat. %, but failed.

I edited the xml to link to the pngs from 0 to 100.

I edited the PNGs.

Compilation warns me about bad pngs and when I reboot, the framework is totally messed up or even worst, as I unlock my phone, it just reboots...

Any help on how to do this?
[Nexus One Q&A, Help & Troubleshooting] RashaMatt:
I use Battery Widget (free). Takes up one icon space on your home screen (shows battery percentage in 1% increments), also allows quick toggling of Wifi/GPS/Bluetooth, and access to Screen settings.
[Nexus One Q&A, Help & Troubleshooting] leonnib4:
You know it has been released, no?

Check to forum: a simple jar to push
[Droid Incredible General] dreamersipaq:
P.S.

If you've passed around 15 seconds (maybe truthfully 12 or so), you need to start back at 0. After 12 - 15 seconds I'm pretty sure you've already missed the window.
[Droid Incredible General] deficitism:
I'm not going to lie. I initially planned on bashing this post, until I read through it all. You are 100% (maybe 90%) correct as far as timing being the key. The snatch people are having is the randomness in their attempts. Putting in no effort find 'the sweet spot'.

Hope this helps a lot of people.
[Droid Incredible General] seanmcd72:
Great post but this part is incorrect - several other guides are completed without even downloading the SDK Google drivers

But I agree on the timing. I kept not looking at the clock but counting before inserting the card and once I got in, I had done it so many times I forgot what I had done when it was all said and done. I have yet to be able to recreate it!
[Droid Incredible General] rynosaur:
And you don't need a linux driver modified specially for the Incredible. i don't believe there's anything HTC device-specific about starting an ADB session. In other words, anything the reports itself as an Android device is gonna get the same treatment from ADB and host OS w/r/t mode 0c94, or whatever it is that renders ADB Composite.

Good notes on the timing, as has been said. I had figured it @ 7-8s, no wonder I've been so hitting adb shell so spottily. :o
[Droid Incredible General] Bxsteez:
Didn't work for me... Went all the way up to 12secs.
[Droid Incredible General] dreamersipaq:
try, try again

If it didn't work for you,

Restart at 0. The timing must be spot on since the window of opportunity is about < 1/2 a second. It's probably between 4.5 - 8.5 seconds depending on your card. But I was OCD so I started at 0 and went to 15. You probably missed it. My method took me 2 - 3 tries to get right. Patience is key!
[Droid Incredible General] Bxsteez:
I tried a few dozen times :P I'm 100% sure this method will work on my device cause i've already rooted by doing something similar. I'm just trying to get back to the recovery mode so i can remove some of this crap on the device..

The timing must have be down to the millisecond shoot maybe even the ns
[Droid Incredible General] rynosaur:
Getting no love out of this method, and I wiped my DI to try it :( In my past attempts, I always counted from vibrate and inserted the card ~ 7s, although the first time I didn't pull the card at all, I just put the 4gig/class4 in and it worked with a loop & simple drivers in Win7.
[Droid Incredible General] kmarriner:
I discovered this same method last night and found the timing to be around 7.5-7.8 seconds.

The only difference is that I can't listen for the hardware sounds as I am running osx.
[Droid Incredible General] bearmacerick:
Ah! It worked!! Mine worked at 2 seconds. First try. Thank you so much!
[Droid Incredible General] dreamersipaq:
Forgot to mention.

I had my wifi, bt OFF, though the phone was NOT in Airplane mode. SYNC and GPS were left ON.
[Droid Incredible General] dreamersipaq:
GLAD it worked.

If it got root for just one person besides me.... writing this up was worth it. CONGRATS!!!
[Droid Incredible General] rynosaur:
That's what I thought about my method, until me & another guy couldn't repeat my initial result due to it being a different day than the day when I first make it work ;) Hope yours is much more reproducable. *cry*
[Droid Incredible General] Kulaa:
Good job. I will be trying this when I get home .

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

Werdadge
[Droid Incredible General] 4x4r8d:
Same here. Thanks for write up. Now to find time when I get home :(
[Droid Incredible General] dreamersipaq:
Rooting steps...

This is what I followed after getting the error. I recommend reading the whole thing though, even if you follow my method to break into recovery:

http://sodpit.com/inc/#4b
[Droid Incredible General] bearmacerick:
just as a side note, i was able to repro this two more times about 30 minutes later. this time it was around 2.5 seconds.
[Droid Incredible General] Mudavo:
Great find and explanation. I NOW HAVE ROOT!!! Thanks!
[Droid Incredible General] dreamersipaq:
Awesome

Awesome :)
[Droid Incredible General] junjlo:
Nice mine was 2g patriot worked at 4 sec
[Droid Incredible General] cdd543:
I hit mine at 2 seconds..awesome and great tip!
[Droid Incredible General] dreamersipaq:
Great!

Nice to see all these guys getting in with this method. Awesome fellas !
[Droid Incredible General] gripper4hire:
Question: Do you get an ADB Android Device (or My HTC Device) in Device Manager when you enter recovery mode (with the triangle)?

I don't even get this, only the Mass Storage devices, which can't be read.

Also, what date do you have on your bootloader (the white screen)? My bootloader is dated May 15th.

-gripper
[Droid Incredible General] dreamersipaq:
okay

1) you should see andronid device or HTC interface or adb interface or something like that when on the white screen. Once it changes to black, it will change to 2 mass storage devices you can't access. That's normal. you should not see any yellow triangles indicating that the drivers aren't properly loaded

2) .77 bootloader, not sure of date.
[Droid Incredible General] htc_woe_is_me:
It's nice to know that there are actually people out there getting this because otherwise I would've given up hours or even days ago. I've spent 3+ hours each day for the last 3 days. I'm now trying this timing method with no luck so far.

Do you think there should be a value before 0?? like -5 seconds or something?

I'll keep at it until someone else finds a better way. Thanks for pointing us in a direction
[Droid Incredible General] dreamersipaq:
NO. 0 is when you pop the sd card in at the same time as you hit power to start recovery. 1) what bootloader version are you. 2) can you access adb when your phone is booted normally?
[Droid Incredible General] gripper4hire:
I think I am on to something that might explain why some of us can't get root.

My device:

HBOOT-0.79.0000

MICROP-0417

TOUCH PANEL-ATMEL224_16ab

RADIO-1.00.03.04.06

May 14 2010,14:15:44

And I don't have the ADB Device on the white screen. I do have a ADB Bootloader device (as opposed to either the My HTC/Android ADB Device) at the white screen which goes away the moment you choose recovery mode and bootloader loads the recovery console.

Maybe HTC fixed this issue in newer firmware?
[Droid Incredible General] dreamersipaq:
.79

Not sure, never had .79 to begin with, but I do know that you can downgrade.
[Droid Incredible General] htc_woe_is_me:
I'm not sure? How do you access adb normally? When I plugged my phone into the PC earlier I saw a balloon pop up that said ADB device found...

on the bootloader screen mine says:

incredible xc ship s-on

hboot-0.79.0000

microp/0417

touch panel-atmel224_16ab

radio-1.00.03.04.06

may 14 2010,14:15:44
[Droid Incredible General] htc_woe_is_me:
No such file or directory!!!!!!!!!!!!!!!!!!!!!!

WOOOOOOOOOOOOOOOO!!!
[Droid Incredible General] rynosaur:
Hey fellas. I got my DI about 10 days ago, and it came with 079 HBOOT, date 5/14/10. I tried a bit to get the race condition with the newer firmware, then did a downgrade and immediately tried again with a 4gb/class4 Transcend, and I got it. Seems formatting FAT32 w/1024 block allocation size encourages a long delay window. Interesting enough, I was letting Android/Sense format my card, and it formats to 16xxxk block allocation size. Interesting! Later, I came to regret downgrading to 077 HBOOT, and flashed back up (downgrade/upgrading wipes completely, btw) to HBOOT 079. That's about when iPaq posted his timing method. I spent 8 hours straight today working with different cards, formats, and timings. Finally, I got it, tho unfortunately I did it in Linux with a script that didn't automatically include Busybox, which is a major faux pas, since so many rooted apps rely on busybox.

Anyhow, don't get discouraged. It's not your Firmware, it's your timing, format, and SDcard type: a combination of all three or just one or two--any of the above will bork your attempts. Don't give give, and don't get obsessed with drivers, either. There are some on XDA who are fervent about promoting specific drivers that the original creators of this method never used to develop it, and that's why drivers aren't specifically mentioned :rolleyes::rolleyes::rolleyes:

Basically, if you get two storage volumes mounted 15 seconds after vibrate and your adb shell loop/attempts don't change error messages, then you missed the window--due to bad timing or an sdcard card incompatibility. Good luck!
[Droid Incredible General] Ruben1123:
This man is a genius. Everything worked. You just have to get the timing. That is the hardest part. His instructions will work on any SD card including the sandisk that came with the phone (my experience). I got it at 7.1 seconds. Great guy. Thanks!!!
[Droid Incredible General] dreamersipaq:
Not sure, maybe the .79 is messing you guys up? I did it by going to hboot directly: Vol - + PWR. From there you can highlight recovery
[Droid Incredible General] htc_woe_is_me:
I got into recovery 3 times tonight using that same SanDisk 2GB. I was right around 7 seconds each time with mine.

If you have that card, try at 7 seconds... it seems to be working! Don't get discouraged, it will happen.
[Droid Incredible General] dreamersipaq:
Awesome!

Glad to hear. So far this method seems to be working pretty well.... as long as you're consistent and patient... and actually time it using a watch instead of guess-counting in your head. :D
[Droid Incredible General] jasoraso:
7.8 seconds!!!! Thanks for the encouragement to try a methodical approach. Helped prevent frustration.