Connectivity Error On Custom ROM - 8125, K-JAM, P4300, MDA Vario ROM Development

Hi, I am Using 004's kitchen to make a Custom Core2n. I do all the steps correct, i add some Packages (some from the xda ftp, some that I've made). Also splash screen of my own.
I get no error from the building programs, but when I flash the ROM I get connectivity error on 99% (after a 5 min freeze) and then Only bootloader mode goes on. To bring back my wiza200 I flash the T-Mob 2.26
Anyway, the thing is that, I tried to build using the Farias Kitchen Pack also just to try if It would work, but It did the same thing.
Do you have any Idea about whats goin' on?

Related

Best stable ROM for my model

Two questions:
1. How do I tell what generation my Prophet is? I see a lot of references to G3 and G4 but no information on how to work this out.
2. I currently have the latest i-mate JAMin rom, which is AKU2.0. Is there is a stable AKU2.3 ROM people have been using or is this still "experimental" It's hard to work this out from the threads.
Thanks all.
spaceboy said:
Two questions:
1. How do I tell what generation my Prophet is? I see a lot of references to G3 and G4 but no information on how to work this out.
2. I currently have the latest i-mate JAMin rom, which is AKU2.0. Is there is a stable AKU2.3 ROM people have been using or is this still "experimental" It's hard to work this out from the threads.
Thanks all.
Click to expand...
Click to collapse
1: during bootup, 2nd screen find
SPL
2.xx.0001 = g4
2.xx.0000 = g3
2: aku 2.3 seems very stable. Everything works as expected. i've only installed one version, after reading this thread: http://forum.xda-developers.com/sho...ht=16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe
it's the 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe from this sites' ftp. It has been much more stable and responsive (due to the larger cache) then the preinstalled AKU2.0 on my qtek s200. Boot time is shortened by about 20s.
Before you install this you HAVE to unlock the CID:
http://wiki.xda-developers.com/index.php?pagename=Prophet_Upgrades
i didn't do this first time, and had to find a valid qtek rom that would install, since my device didn't bootup anymore..
Thanks for that. A question about unlocking the CID:
On the Prophet upgrade page you link to, it has the warning (3 times, in bold!): *WARNING!!!!! DO NOT PERFORM THIS IF YOUR PROPHET HAS THIS ROM "SPL 2.xx.0001" (New G4 Version)
Don't all G4's have that ROM? Mine does (2.13.0001). So where does that leave us for unlocking?
Thanks again.
Im also running a JAMin with the latest official rom and ive seen some good things about the 2.3 updates but im new to the whole cooked roms thing but ill figure it out.
What would I loose by upgrading from my JAMin rom and what would I gain?
Can I go back to my jamin rom if I dont like it?
I have installed the latest DOPOD ROM and I run it native without any soft installed and I reboot only about 1 a month!
To partially answer my own question: The CID unlock process looks like it IS for G3s only. To upgrade G4s you use pdocwrite.exe.
I've seen the details for using pdocwrite to install the pdamobiz ROM, but has anyone used it to install the 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe?
Cheers
dannyoneill said:
Im also running a JAMin with the latest official rom and ive seen some good things about the 2.3 updates but im new to the whole cooked roms thing but ill figure it out.
What would I loose by upgrading from my JAMin rom and what would I gain?
Can I go back to my jamin rom if I dont like it?
Click to expand...
Click to collapse
I'm guessing you'd loose some of the vendor customisations - which really are only some useless themes and the network provider settings - which for me just means setting up GPRS. Of course, you also risk loosing your JAMin entirely if you stuff it up
What you gain is a more up-to-date OS which is faster...
what about the extended rom? all the custom stuff is in there, i can access it no probs but would that remain with the rom mentioned above?
would I still be able to run them (if I back them up)
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
dannyoneill said:
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
Click to expand...
Click to collapse
To anyone reading this, here is my experience as of last night.
On my G4 I tried installing 16Mb_AKU2.3_GSM02.30.21_Extrom-4PDA.ru.exe after first hard-resetting my device. The installer went ahead fine, but it would not start-up: it would not get past the boot loader screen. So I reinstalled the latest i-mate ROM, booted up, then proceeded to try: ftp://xda:[email protected]/2006-10-05_Upgrade ROM_AKU2.3_lvsw.rar.
This uses the PDAmobiz method to upgrade a G4 which is essentially running a batch file while it unlocks and writes to the ExtRom and the ROM - then doing a hard reset, but it is not the PDAmobiz ROM.
This worked fine, and I now have AKU2.3. Even better, it is not customised, so there's no extra software installed, which I'm happy about. It's been running over night and seems very stable so far. I'm not sure what the paging size is on the ROM, maybe it's smaller = more stability.
So that's my experience!
My experience:
My JAMin running IPL/SPL 2.13.0001 using that rar file that worked for you...
hung on the copy of the OS to the device.
Trying now to recover it by downloading and trying to install latest JAMin update.
I cant get activesync / network connection using USB to phone... Don't know if that will be a problem trying to recover. Its sitting at the 3 colour screen atm.
Is there a way for me to update to IPL/SPL 2.15.0001 from 2.13.0001 before trying again? (assuming my phone is not already dead).
orian said:
My experience:
My JAMin running IPL/SPL 2.13.0001 using that rar file that worked for you...
hung on the copy of the OS to the device.
Trying now to recover it by downloading and trying to install latest JAMin update.
I cant get activesync / network connection using USB to phone... Don't know if that will be a problem trying to recover. Its sitting at the 3 colour screen atm.
Is there a way for me to update to IPL/SPL 2.15.0001 from 2.13.0001 before trying again? (assuming my phone is not already dead).
Click to expand...
Click to collapse
If your phone is G4, you should be able to install the vendor ROM no problem - which is magical really. You don't need ActiveSync running; well - it won't connect as the device is dead .
When you say it hung copying the file... it took a good 15-20 minutes to copy across for me, so I hope you weren't just being impatient.
yeah the JAMin rom worked so I'm back where I began.
I did wait 30 mins and it had crashed.... activesync wasnt doing anything, buttons / screen taps weren't working on pda.
Is it because I am running 2.13.0001 is my worry? The update specifies its for 2.15.0001. Is there any way I can update to 2.15.0001 from 2.13.0001 before trying again?
Cheers.
Tried the update again, and this time it worked.
Device is running AKU2.3 now, but still says 2.13.0001 for ipl and spl on boot.
Any ideas anyone on how I can update that to 2.15.0001? and what kind of change that makes anyway?
Thanks all.
dannyoneill said:
just been researching this rom, looks like it defaults overclocks your device and installs a ton and I mean a ton of apps that most people dont want.
Be warned, its heavily customized and may not be to everyones liking.
Anyone know if I do upgrade to this and unlock my CID if I can then re-apply the official JAMin rom?
Click to expand...
Click to collapse
you have been researching a different rom. this one does certainly NOT overclock the device by default. And it's a clean install, without any overhead, but WITH the stereo bluetooth headset support. perfect for my uses.
looks like i was looking at another rom, one loaded with junk.
I took the plunge and updated my jamin to the 16mb 4pda rom and im now back on the official jamin, it was way too unstable. Today I rebooted 5 times.
The volume is too low on headset and loud speaker
and some other annoyances.
I need stability
when i'm using AKU2.3,
in Settings / Regional Settings:
there is no "Turkey" option (also Russian).
how can i do that, is there a patch for apply these regions ?
thats why i'm using latest official jamin rom now (wwe) (from clubimate.com)
Ive found the source of instability with the 4PDA rom. Its the radio rom 02.30.21
I went back to my old ROM on my jamin and all was fine, a day without crash, Then loaded on radio rom 02.30.21, hardreset for good measure and setup again,. same as always.
Then, every hour or so im resetting.
Back to official jamin rom and all is fine again.
Radio ROM 02.30.21 is just totally unstable. Ideally I would like the AKU2.3 updated rom but without this awful radio rom they seem to be putting in them all.

HELP. Brick after Crossbow Most Beautiful Edition

Hello all,
i have installed Windows Mobile Crossbow Most Beautiful Edition and every thing wenk ok during the installation but now after i finished flashing the ROM i am stuck on the splash screen and my wizard keeps reseting and fails to pass the splash screen.
i have tried to reflash another ROM but i can't even start the bootloader (3 colors screen)
pleaes, what shall i do?
you already tried holding down the camera button and pressing the power button?
ammar said:
Hello all,
i have installed Windows Mobile Crossbow Most Beautiful Edition and every thing wenk ok during the installation but now after i finished flashing the ROM i am stuck on the splash screen and my wizard keeps reseting and fails to pass the splash screen.
i have tried to reflash another ROM but i can't even start the bootloader (3 colors screen)
pleaes, what shall i do?
Click to expand...
Click to collapse
downgrade to this ROM :
http://rapidshare.com/files/18711114/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe
this is the way to solve the problem and then after downgrading to this ROM u can the unlock and then install any other ROM but u must first downgrade to this ROM downlaod it from the link above
Perhaps the best way to restore your device its using the Love Rom.
Flash, and flash again the WM6 ROM, follow the Shell Tool method closely and you will have your device working in no time.
It worth the pain, believe me
Hi,
Thanks you all for your help
i have used the camera button and the stylus to get it into the boot loader and then i reflashed my original k-Jam rom with IPL/SPL 2.16 then i flashed again crossbow ROM and it worked.
it seems that after CID unloking i had IPL/SPL 1.01 and i should have reflash a ROM with higher IPL/SPL before WM6. so the idea is to get a stable ROM with SPL 2.26 like everybody here is doing but i tried my 2.16 and it is ok now.
Regards.
golfernutnflorida said:
What rom is that you are referring to? Is that the Button rom or the Wizard Love Rom?
Click to expand...
Click to collapse
that is the orignal first ROM for Wizard that came out first from the factory with this ROM THIS is the first ROM for wizard i mean the oldest one !!
QUICK FIX for WM6 Won't Boot/Resetting Problem
I've had the problem mentioned in this thread every time I've loaded a WM6 rom. Last summer, I fell in the lake with my wizard so I've always attributed weird problems to the water exposure.
Anyway, when your rom won't boot. Here's a trick that works for me. Do a soft reset, then as soon as you get into the green screen with the spiral, open your keyboard and hold down the space bar. My rom has ALWAYS booted when I do this.
I got the idea from and old PC repair trick. Good luck.
Always upgrade to a 2.xx original ROM before upgrade further. I always use the T-Mobile 2.26 ROM.

No ROM usable ??, hang on Opera9 customization process

I would need some help to understand the following :
whatever ROM i try to install, after successfull flash and the following reboot when you get the "customization will start in 3 sec", it always hang on the "Installing WM6_PPC_HTC_Opera9_WWE.CAB" (last time i wait 5h to see if it move)
i tried RomeOS1.01 as well as 1.02 (just a few minutes ago), same also happen with DCS-TouchProv13 or even when i try to revert to RUU_raphaelWWE1.66...
i have a successfull HardSPL1.90.1.3 Olinex properly showing up on the 3 color screen.
Soft reset allow me to use the phone with a somehow successfull install ? (i get some of the appz but not sure it is 100% successfull / how can i check??)
Only concern is that the phone get warm around the camera/speaker after a few hours of usage and battery doesnt sound very powerfull (full load stay on about 5 to 6h with no bluetooth but wifi on)
original is an XDA diamond pro from o2 germany (model RAPH120)
as of right now i have
ROM: ROMeOSv1.02 WWE
Radio: 1.02.25.11
Protocol 52.33.25.17u
Any idea why the custom... always hang on the Opera install ? i dont care to not use opera or dl and install it myself afterward ??
thks
Stephane
(frenchy leaving in Germany and working for a US company.... cannot afford to use a DE phone only )
How about flash ur stock ROM back, then revert the stock SPL. There may be semething wrong with ur device
GERMAN ROM
http://forum.xda-developers.com/showthread.php?t=426400
German ROM work fine
Guess what .... after flashing back to a german ROM (thks for the link to an htc oiginal ) the "customization" with Opera9_DE went well and finish up normally.
i am going to work/play a bit with the German version to make sure it does not come from the device
any other idea in how/why my German o2 xda does not love all the great simple ROM cooked here ??
is any o2 Germany user here havig successfully flashed their xda with an English (or French ) ROM ??
Thanks guys for the great work you do here !
Steph.
I am seeing this exact same issue.
I have had no end of grief flashing my Raph, I maintain an XP VM (I am on OS X) entirely for flashing. I have flashed many different devices with dozens of ROMs and never had a problem until I got the Raphael. I have seen BSOD's and numerous connection issues while flashing using both Raphael_CustomRUU_v1.2 and RaphaelWrapper.
Also, every ROM I have flashed (on a XP SP3 box I put together from old pieces just to flash this bastard) has hung whilst installing opera.
I am using the o2 uk variant (as yet unreleased XDA Serra).
It is a RAPH120, is this unique to o2 devices?
Would appriciate any help getting this sorted, it could become a more widespread problem with the o2 uk variant is released, as there may be an influx people wondering why their device wont flash properly.
nb. I have an unreleased o2 built ROM (RUU_Raphael_O2_UK_1.60.206.1_radio_sign_52.29.25.12_1.01.25.16_Test.exe) that flashes and installs fine even from inside my VM.
Thanks in advance for any help anyone could provide!
[UPDATE] I tried installing Opera build 1957 from a cab and it worked fine.
maybe a dumb suggestion... but try to get your device unlocked and see what happen
I checked with Oli about whether unlocking would help:
Olipro said:
I see, then that's a weird issue, however, not related or fixable by the unlocker.
your best bet is to do a soft reset as soon as the customization dialog appears and see what happens.
I was initially suspecting it could be region protection, but in those cases, the ROM doesn't boot at all, so your case is a strange one.
Click to expand...
Click to collapse
So no leads there, as an interim solution I will repack ROMeOS² v1.03 without Opera and see how that works out.
i have the same device and the same problem. I will try to repack it with the german version of opera..
Oh dear, so it would appear that current roms do not work on O2 variant devices...
Has anyone successfully flashed an O2 device (with a cooked rom)?
I have hit some problems repacking ROMeOS² as hung has included measures to stop people making their own roms based on his. I pm'd him last night asking if he could help us out, but as of yet I have not recieved a reply.
I will probably start making my own rom from scratch tonight, but its a fair bit of work just to take opera out of the customization sequence. Hopefully its just some odd bug in the opera install, rather than something more serious. I guess worst case scenario is that after opera is removed it just crashes at another point during the costomization process.
[UPDATE]
hang.tuah said:
@dabs
I'll try to make it [ROMeOS² without Opera] for v1.04 mate, thanks for ur support..
Click to expand...
Click to collapse
Excellent, so at least we have a workaround in the pipeline. Still, it would be best to find the cause of the problem, as not all cooks have the time and dedication to make special versions of their roms for a small sub-set of users.
Actually Opera is included but with no device specific & v1.04 is done
smaier said:
I would need some help to understand the following :
whatever ROM i try to install, after successfull flash and the following reboot when you get the "customization will start in 3 sec", it always hang on the "Installing WM6_PPC_HTC_Opera9_WWE.CAB" (last time i wait 5h to see if it move)
i tried RomeOS1.01 as well as 1.02 (just a few minutes ago), same also happen with DCS-TouchProv13 or even when i try to revert to RUU_raphaelWWE1.66...
i have a successfull HardSPL1.90.1.3 Olinex properly showing up on the 3 color screen.
Soft reset allow me to use the phone with a somehow successfull install ? (i get some of the appz but not sure it is 100% successfull / how can i check??)
Only concern is that the phone get warm around the camera/speaker after a few hours of usage and battery doesnt sound very powerfull (full load stay on about 5 to 6h with no bluetooth but wifi on)
original is an XDA diamond pro from o2 germany (model RAPH120)
as of right now i have
ROM: ROMeOSv1.02 WWE
Radio: 1.02.25.11
Protocol 52.33.25.17u
Any idea why the custom... always hang on the Opera install ? i dont care to not use opera or dl and install it myself afterward ??
thks
Stephane
(frenchy leaving in Germany and working for a US company.... cannot afford to use a DE phone only )
Click to expand...
Click to collapse
Hi Stephane and others having similar trouble,
I had the same situation but my original ROM was Japanese, after trying a lot of possible official WWE versions for flashing and cooked ROMs, only one version worked.. Check the official WWE version Singtel.. it worked up to customization without problem.. the only difference the default internet page is Singtel but it is not a problem cause I can still go to the other sites..

reflash and or today replacement question

I want to reflash to my oem rom using the idiots guide on the Kaiser wiki. Does this also change the radio back to the original radio as well? The reason being is that when I install Manilla or WAD (basically any major Today screen replacement my radio does not work (no signal.) But when I quit these programs and go back to the today screen I get a signal again. Or is there some other way to get these programs to work without reflashing the ROM. THX

[fixed] stuck in spl after flashing cooked ppckitchen 21042 rom

In case other people have the problem: Update to the latest version of ppckitchen!
Hello,
I was not satisfied with the current available rom's and decided to cook my own, I used the ppcgeeks kitchen to cook a 21042 wm6.1 rom and included quite some OEM packages. After building and flashing the ROM my device started, and got in the SPL (where you can see the radio/rom version). But it would not get past there. I tried flashing again (without sim and or memory card), hard resetting after flashing, and upgrading the hardspl to 3.59. All to no avail.
I thought it might be an issue with one of the OEM packages, so I started a new project in the kitchen and left everything to default and directly build the bare ROM. The problem still persists. I noticed the only carrier available as a choice in the kitchen was AT&T, I live in europe so this might cause a problem? (absolutely not sure about this, just poking around).
Some more details:
R: 1.70.19.09
G: 25.83.40.02H
D: 3.14.00.00
Luckily I can get in the bootloader and flash whatever I want and just go back to the stock ROM, but I rather want my own, so I was wondering, can anyone help me with this issue?
Thanks in advance, peterrus
Does the backlight dim or does it stay on constantly? If it dims, then you have an issue with your SYS or OEM. If It doesn't dim, then you have an issue with your XIP. Was the kitchen already ported to run on a Kaiser? Which kitchen did you use from ppcgeeks? A little more information will help figure out your issue.
It does dim indeed, so it seems I have an issue with my SYS or OEM, tell me more.
I used the latest version but I am not aware of any versionnumbers, this is the announcement post: http://www.ppckitchen.org/forums/showthread.php?t=650
I could get the versionnumber from the kitchen, but I just uninstalled to try an older version, and updating it takes about 2 hours.
The kitchen is said to be kaiser compatible
I see however that there are others experiencing the same issues. I am gonna try an older version of the kitchen and see what happens.
Test the older kitchen like you are already doing. I suggest creating a base build without any packages included, so you can verify that the base ROM is OK. This will help with the process of elimination. Now, you should also read any documentation with that kitchen to verify that the OEM folder is exclusively for the kaiser. The OEM folder contains device specific settings and drivers. So using an Elfin or Polaris OEM with you kaiser will cause lots of issues (mainly the one you're experiencing now, stuck at splash screen). Again, give the older kitchen a try and post how that goes and we'll go from there.
Using the old kitchen () I can not succesfully produce a working 21042 ROM.
Using the old kitchen I can produce a working 20931 ROM.
I have not tested the new kitchen yet. But when I find time for that I will post results.
So, using the new kitchen I also can not produce a working 21042 ROM, a 20931 ROM works fine though, so I think i'll just leave it like this.
Unzip and add
This to your sys and see if it helps.
The ppckitchen authors have pushed an update which seems to fix the issue, so josh: I haven't tried your fix yet because I prefer the official update over other solutions, but thanks anyway it seems I can now succesfully boot the rom.

Categories

Resources