Related
Hi all.
with the 6800-
I flash nexvisions rom and the new radio. After reading ppcgeeks tutorial, I thought I needed to run IOTA.cab to get my data settings even though I'm on Verizon. Well, after doing a *228 and calling verizion to get my calls to go though, my data is now screwing up.
The problem is- when I run internet explorer (with google mobile as my homepage) it chokes after about 50 K downloaded and wont finish. The data connection is lousy. If I try to close out my data connection using the connection manager it comes up with a warning about IOTA data errors.
Now I know that vzw users do not need IOTA. Is there a way to reset what IOTA does to your data connection settings without doing a hard reset? I can't find a 'unintstall' IOTA.cab anywhere.
Anyone have any ideas?
Cook ROM as Verizon, not Sprint?
Maybe just run the ROM again
I can not think of a good way to get it all out but maybe someone has an idea. I am on VZW and it worked perfectly.
You should reflash.
Perhaps you shouldn't use Nexvision's ROM since it obviously has Sprint "parts" in it that seem to be interfering.
Here is what worked and is still working very well for me. I have no data or voice issues at all right now:
Geckotek said:
In fact, all is well.
I flashed back to the stock VZW ROM (third time I think), I made sure all of my provisioning issues with Verizon were worked out (finally had the tech "kick the switch").
1) Then I proceeded to load the 2.4 bootloader,
2) then the 3.16 Unauthorized Sprint ROM w/ radio,
3) then finally installed a cooked DCD 2.3.2 ROM.
Things to note:
1) I never let the Sprint ROM boot up (this is VERY important!!)
2) I had no signal so ran *22802 then hit End as soon as it connected
3) Still no signal after reboot
4) No A key, MSID, or MDN issues, but I did re-enter the MSID and MDN as discussed in other threads
5) After re-entering MSID and MDN then after reboot I had signal (even though they are there and correct, type re-enter the information anyway)
6) never had to run *228 to OTA program (in the past programming with *228 has reversed the effect of re-entering the MSID and MDN)
In general, I feel that the OTA from VZW sends down some programming that conflicts with the 3.27 radio...but I have nothing to prove that.
GPS is running great (I just loaded the AstroGPSLauncher)
Not sure about Rev A. It does seem snappy. What's a good site to test from the phone?
I'm happy and not re-flashing until a solid radio for Verizon arrives.
Click to expand...
Click to collapse
Thanks everyone for your feedback.
First- I'll try a hard reset first and see if that clears it up.
Then if that doesn't work, I'll try reflashing nexvisions rom and see if that clears it up.
If that doesn't work, I'll reflash trying the dcd rom.
spreeway said:
Thanks everyone for your feedback.
First- I'll try a hard reset first and see if that clears it up.
Then if that doesn't work, I'll try reflashing nexvisions rom and see if that clears it up.
If that doesn't work, I'll reflash trying the dcd rom.
Click to expand...
Click to collapse
If that doesn't work, you should do like I did and start with a clean slate. All the reflashing of ROMs and radios did me no good. Whatever issues I had were not going away with just another flash from one ROM to another.
Hard resetting fix everything.
I'm just curious, but after flashing the newest sprint rom and radio, I noticed that everytime I do a soft reset, I automatically get the roam triangle. This stays on for about 10 minutes till it goes to EVDO, or 10X. I am currently using the newest DCD 3.2.0 Rom, for Sprint, and there is no difference. Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Hopefully this hasn't been answered, and I missed it. If it has, I appologize. Thanks in advance.
Chem
Chemdawg said:
I'm just curious, but after flashing the newest sprint rom and radio, I noticed that everytime I do a soft reset, I automatically get the roam triangle. This stays on for about 10 minutes till it goes to EVDO, or 10X. I am currently using the newest DCD 3.2.0 Rom, for Sprint, and there is no difference. Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Hopefully this hasn't been answered, and I missed it. If it has, I appologize. Thanks in advance.
Chem
Click to expand...
Click to collapse
Do you know what version of the PRL you're using? It shows up as "PRL version" under Start->Settings->System->Device Information. Someone along the line you might have ended up with an outdated one. 60613 is the latest for Sprint EVDO-capable phones.
Chemdawg said:
Does anyone know how to prevent this from going into Roam mode when you do a soft reset?
Click to expand...
Click to collapse
I can confirm that with 3.2.0 (yes...I've finally moved on from my own kitchen based from Sprint's 3.35.xxx.... ) a soft-reset consistently reverts back to Standard for the Phonerefered Serving System. Over a soft-reset it should retain the choice of Home Only.
In the registry under HKLM\Software\OEM\InitProv\PhoneSetting what can I set to retain Home Only but retain the option to switch back to Standard when travelling?
This is an issue for me since I live by the water and the US is just across a straight leaving my phone often switching between my local and a US carrier.
Keystone said:
I can confirm that with 3.2.0 (yes...I've finally moved on from my own kitchen based from Sprint's 3.35.xxx.... ) a soft-reset consistently reverts back to Standard for the Phonerefered Serving System. Over a soft-reset it should retain the choice of Home Only.
In the registry under HKLM\Software\OEM\InitProv\PhoneSetting what can I set to retain Home Only but retain the option to switch back to Standard when travelling?
This is an issue for me since I live by the water and the US is just across a straight leaving my phone often switching between my local and a US carrier.
Click to expand...
Click to collapse
we probably need the previous version initprov.dll. i will look tonight. thanks for finding this
You're welcome, DCD.. Thank you!
This afternoon I may also have a chance to build a new ROM with a familiar initprov.dll and see if that resolves it.
With 3.2.0 on my Titan I just replaced the initprov.dll (v1.25.0.0) with the v1.21.0.0 (from the March Sprint release and what I was first using in my kitchen), rebooted, but still faced the problem of the phone defaulting back to Standard rather than retain Home Only.
That was without rebuilding a ROM with the older initprov version in.
...to note, the April Alltel ROM was also using this latest v1.25.0.0.
With 3.2.0 on my Titan I just replaced the initprov.dll (v1.25.0.0) with the v1.21.0.0 (from the March Sprint release), rebooted, but still faced the problem of the phone defaulting back to Standard rather than retain Home Only.
Click to expand...
Click to collapse
Certain dll's are self registering and some aren't. It's probably going to take a little more than just a copy/paste.
gc14 said:
Certain dll's are self registering and some aren't. It's probably going to take a little more than just a copy/paste.
Click to expand...
Click to collapse
Worth a shot.. Can't rebuild until I get home......
I realize now that it is related to the radio rom. Originally I installed the NEW factory firmware/rom upgrade. Well that was when it started. So thinking it was a factory rom issue, I installed DCD 3.2.0. Still doing it. So I decided to downgrade back to 3.1.6 which was what I WAS using before the upgrade.. Still doing it. So.. .It has to be the newest radio rom. I am going to downgrade the radio back to what I had and see if that fixes it.
I realize now that it is related to the radio rom. Originally I installed the NEW factory firmware/rom upgrade. Well that was when it started. So thinking it was a factory rom issue, I installed DCD 3.2.0. Still doing it. So I decided to downgrade back to 3.1.6 which was what I WAS using before the upgrade.. Still doing it. So.. .It has to be the newest radio rom. I am going to downgrade the radio back to what I had and see if that fixes it.
Click to expand...
Click to collapse
That's not necessarily true. It could have been something that was installed during the 3.56 factory customizations. Try flashing Sprint 3.35 stock rom/radio, let the customizations run. Then flash 3.2.0 and 3.42.02 or 3.42.30. If you're going to use the 3.56 stock rom/radio to flash 3.42.02, that's ok, just DON'T let the customizations run this time.
that was the issue with mine I ran the sighned sprint cab from the extended rom from the 3.56 "official" rom that was part of no2chems pre 2.2 after i did that my phone was stuck in roaming... Thinking it was the radio i downgraded 1 step @ a time from the 3.42.03 back to 3.39 still roaming went back to the stock radio that came with the 3.35 release still roaming when phone was booted. Figured it might be rom related @ that point so i reflashed to good ole 5069k left battery out after flash for 2 min... first boot it was roaming and would not lock onto a tower in sprint only mode... my muerom boot agent always runs the sprint carrier settings 4 me and on my second boot still no sprint signal only digital roam.. In a last ditch effort I reflashed via activesync the whole 3.35 stock rom/radio ... and wala all was fixed booted right up and even b4 the sprint custimization was started i had the evdo icon and no roaming triangle. Leaving the 3.35 stock rom on there i went forward 1 step @ a time radio wise and even with 3.39 and 3.42.02 i still got sprint coverage and evdo icon and connection. so i re-flashed to the nue 2.2 preview let it do tis sprint thing on first boot. then i did not go in and eun anything from the extended rom. No more roaming triangle. Something in the 3.56 exended rom i ran (sprint sighned whatever) Changed something in epst that dod not get reset even with flashes and hard resets till i relfashed back to stock 3.35 relaease full with radio from activesync.
So my suggestion would be that u can run the newer radio and roms just be sure to let your carrier settings run but don't touch files in the extended rom esp the file mentioned bc it stuck me in roaming and it would not get a sprint signal (home) for anything even after just letting it sit. and when setting roaming option to sprint only I would not get any bars @ all just the animated dots nest to the signal icon.
So it can't be anything in the new rom or settings in the new rom that is doing it nor the radio bc when downgrading back to stock radio from march update it did the same thing.
To fix your going to need to do a fill rom/radio flash then just pick your fav flavors after its flashed and has booted up the second time.
Boy, am I glad y'all started a thread on this. I've been trying to figure out what was wrong since this came out. My first flash of the new rom caused mine to be stuck in roaming, and sometimes it won't even come out.
I'll try what you guys suggested.
Customizations = Extended Rom
That's exactly what I said.
Ok, things a little different now. I reflashed back to the stock 3.35 Rom and let customizations run.
Then flashed just the new radio 3.42.30 from SD card
Last I flashed just the dcd 3.2.0 ROM and the carrier cab, and now no more roaming after the soft reset.
So, maybe the problem is in that radio included with the new 3.56 ROM
As long as I got it working, I'm happy
Ok, things a little different now. I reflashed back to the stock 3.35 Rom and let customizations run.
Then flashed just the new radio 3.42.30 from SD card
Last I flashed just the dcd 3.2.0 ROM and the carrier cab, and now no more roaming after the soft reset.
So, maybe the problem is in that radio included with the new 3.56 ROM
As long as I got it working, I'm happy
Click to expand...
Click to collapse
Again, it's not the radio. It's in the customizations from 3.56.
gc14 said:
Again, it's not the radio. It's in the customizations from 3.56.
Click to expand...
Click to collapse
If all we had to do was not let the customizations run, why didn't someone just say that? I've been asking about this for like 3 days now.
When I tried flashing the 3.56 rom without the Customizations it still would roam, so go figure
If all we had to do was not let the customizations run, why didn't someone just say that? I've been asking about this for like 3 days now.
When I tried flashing the 3.56 rom without the Customizations it still would roam, so go figure
Click to expand...
Click to collapse
That's because you've already let them run. They don't go away after a reflash, the same way Verizon users who let them run can't just reflash their rom to make it go away. You need to flash sprint 3.35, let THOSE customizations run. Then reflash 3.2.0.
Before you do anything though, you DO have Sprint right?
After accidentally running the sprint PRI update on my xv6800, I was stuck with the phone thinking it belonged on Sprint and was roaming. I'm not completely foolish and I did not purposely disregard the instructions; I downloaded it elsewhere and it was labeled as "GPS fix" or some such. Anyway, I relocked, flashed to stock Verizon, called 611 and had them do a DMU reset. No problems, everything worked fine after calling 611. Reflashed to olipro 2.40, radio 3.42.30, and dcd 3.2.0. After flashing everything was fine, I ran the carrier cab, did *228,1 and everything seemed to work correctly. I then ran Sashimi to reinstall my software, rebooted. Well, the roaming indicator was back after reboot. I thought that perhaps the Sprint PRI update cab had made its way into my autoinstall folder, but that was not so. Do you guys have any ideas that might explain how this happened? I am flashing back to 3.2.0 and don't want to repeat this experience
playoff beard said:
After accidentally running the sprint PRI update on my xv6800, I was stuck with the phone thinking it belonged on Sprint and was roaming. I'm not completely foolish and I did not purposely disregard the instructions; I downloaded it elsewhere and it was labeled as "GPS fix" or some such. Anyway, I relocked, flashed to stock Verizon, called 611 and had do a DMU reset. No problems, everything worked fine after calling 611. Reflashed to olipro 2.40, radio 3.42.30, and dcd 3.2.0. After flashing everything was fine, I ran the carrier cab, did *228,1 and everything seemed to work fine. I then ran Sashimi to reinstall my software, rebooted. Well, the roaming indicator was back after reboot. I thought that perhaps the Sprint PRI update cab had made its way into my autoinstall folder, but that was not so. Do you guys have any ideas that might explain how this happened? I am flashing back to 3.2.0 and don't want to repeat this experience
Click to expand...
Click to collapse
When you update the PRI, it does not install into your ROM, it actually updates something inside the phone (similar to flashing your radio/etc). You need to find a verizon PRI ripped from the verizon stock rom (if it is even there) and install and run PPST.exe again. My original post he reposted had said not to install on another carrier in big red letters
Read this here, should do the trick.
After doing yet another relock, stock rom, and *228, I installed the latest PPC Kitchen 5060 rom (set to Verizon) and new radio (3.42.30). As soon as the phone boots, it thinks it is roaming and *228,1,2 does not help at all. I've done all the steps on the thread that serfboreds recommended. It still thinks it is roaming. Any advice?
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
playoff beard said:
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
Click to expand...
Click to collapse
Reload stock and take to store. This is a common outcome after letting Sprint customizations run. It really hoses your phone and can cause irreparable damage.
Any other suggestions?
serfboreds said:
Reload stock and take to store. This is a common outcome after letting Sprint customizations run. It really hoses your phone and can cause irreparable damage.
Any other suggestions?
Click to expand...
Click to collapse
The only problem is that the phone seems to look and work fine when the stock rom is loaded, as long as the DMU reset is done for data. Problems don't appear until I load a custom rom. I can't figure out why the phone shows verizon network (1.35_002 PRI) when the stock rom is installed, but then shows sprint (2.03_003) when I load a non-carrier specific DCD roms and even carrier specific roms (i.e. ppckitchen 5060 for vzw).
I don't know how I can convince a verizon tech to swap when the phone appears normal with the stock rom.
playoff beard said:
I just don't understand this. The phone is fine until I install DCD 3.2.0 or nue 5060, after which it thinks it is roaming again. Getting desperate here...
Click to expand...
Click to collapse
When you do update to DCD 3.2.0, Are you installing the Verizon Carrier Cab?? Also, How are you getting the radio onto the device??
Hmm, works normal with stock rom and radio but funky when you upgrade?
Sounds like you are not loading the radio or verizon carrier as azclown suggests. after going back to vanilla rom, upgrade using gc's newest radio via sd, then load dcd 3.2.0, let his customizations run, then load verizon carrier and you should be fine. Dont load the newest sprint rom/radio.
serfboreds said:
Hmm, works normal with stock rom and radio but funky when you upgrade?
Sounds like you are not loading the radio or verizon carrier as azclown suggests. after going back to vanilla rom, upgrade using gc's newest radio via sd, then load dcd 3.2.0, let his customizations run, then load verizon carrier and you should be fine. Dont load the newest sprint rom/radio.
Click to expand...
Click to collapse
I've been unlocking with olipro 2.40, flashing the new 3.42.30 radio from a microSD card, and then installing the custom rom while still in the bootloader. After installing DCD 3.2.0, I ran the carrier cab and then used *228. Plus, I wouldn't think the carrier cab would be the issue, because I had the same problem when installing PPCkitchens 5060 verizon rom.
-Update: I've tried using radiorefurbish.exe /refurbish to reset my phone to Verizon, but when I run the radiorefurbish.exe using resco explorer, nothing seems to happen. Any more suggestions?
Problem Solved:
I finally resolved this by installing and running this version of radiorefurbish. I ran it using resco explorer with the argument '/refurbish'.
Thanks to you guys and drellisdee at PPCGeeks. You guys rock. I was horrified that I was going to be stuck with the tock VZW rom.
Take the following screenshots (making sure to block out any personal information) and post them:
Device Information
EPST->Security
EPST->M.IP Default Profile
Then, flash back to stock, re-take the screenshots, and post them.
Finally, flash back to 3.42.30 and 3.2.0, install nothing except the carrier cab, re-take the screenshots one last time, and post them.
playoff beard said:
Problem Solved:
I finally resolved this by installing and running this version of radiorefurbish. I ran it using resco explorer with the argument '/refurbish'.
Click to expand...
Click to collapse
I've got the same problem and I reflashed to stock Rom and reflashed to custom. Still stuck in roaming. Could you give details on exactly how you ran resco with an argument?
Thanks
I wonder how he got that working. i've used that file and still have the issue. Yes... I used resco explorer and tried the argument... but got nowhere
nitro66215 said:
I wonder how he got that working. i've used that file and still have the issue. Yes... I used resco explorer and tried the argument... but got nowhere
Click to expand...
Click to collapse
i distinctly remember that one of the customizations after flashing back to stock was radiorefurbish. youve gone back to stock right and loaded the vz PRL?
aguas said:
i distinctly remember that one of the customizations after flashing back to stock was radiorefurbish. youve gone back to stock right and loaded the vz PRL?
Click to expand...
Click to collapse
Yup. and yes... it did run when the Verizon stock ran it's customizations. The PRI stays as sprints PRI 2.00_003. This is the main issue. Also, the ERI is 0. I've tried updating the ERI via ##eri... to the correct 4.eri... but it just gives me a write error. Under ##PROGRAM... the ERI fails to read. Hence my dilemna with the stupid Roaming indicator. I've been back and forth flashing different roms, and am pretty fed up with it actually. This is a Sprint Mogal "Cloaned" as my original VZW XV6800. I left the 6800 in the box.
check this
this wont help for the cloned moguls. But it will help the xv6800 users if they install sprint customizations.
http://forum.ppcgeeks.com/showthread.php?p=401137#post401137
believe it or not, a few months ago i let the sprint customizations run and used it like that just for the better signal...only downfall was no data services....i just switched back to verizon radio stuff yesterday and got my data reactivated
I don't really feel like its that fast so i was going to just scrap the whole thing but then i was like well i'll let everyone else decide
First I just want to give a big thanks to Sogarth for this rom, without him this would not be possible so please thank him before you thank me I have made a vanilla of this rom with cab files for everything that was in the rom. **MOST CAB FILES FOUND HERE WILL NOT WORK WITH OTHER ROMS**
There is also a folder named extra that has some misc. stuff like ringtones…
What did I add?
Well I added .netcf 3.5, mortscript w/auto rotate toggle, disabled signed cert, and has about a 39 sec boot up time (not first boot)
For setting up on first boot: email accounts / connections settings / contacts with ringtones please see this link - http://forum.xda-developers.com/showthread.php?t=403458
Starting with:
Storage - 141.19MB
Ram – 77.77MB
Well that’s it, so have fun
SPL 1.2 - http://www.megaupload.com/?d=QSBNK2IC
http://rapidshare.com/files/131377692/vanilla_SPL1.2.rar.html
UPDATE: I think i fixed the loop problem please try and leave feedback thanks
SPL 3.5 - http://www.megaupload.com/?d=JQN3WITN
http://rapidshare.com/files/131503583/vanilla_SPL3.5.rar.html
-----------Reserved-----------------
irus, you are so fast and efficeint.
I'm going to test now!!!!!!
Thanks Irus and Sogarth for your works!
my next rom starts in 36 second from first splash screen...
it will be: ce os 5.2.20270 (build 5.2.20270.1.3.1)
irus said:
I don't really feel like its that fast so i was going to just scrap the whole thing but then i was like well i'll let everyone else decide
Click to expand...
Click to collapse
Well, no, it wasn't that fast. And then I added a 32 MB pagepool, set my glyph cache to 128 KB (0x0020000), set my font cache, took out a few things I wasn't using, and it's amazing how much faster it works.
Yeah, the 32 MB pagepool is probably overkill; I ought to see if a 16 MB pagepool works just as well... but... it's 32 MB!
On the other hand, maybe I ought to see if a ramdisk for caching works better instead...
michyprima said:
my next rom starts in 36 second from first splash screen...
it will be: ce os 5.2.20270 (build 5.2.20270.1.3.1)
Click to expand...
Click to collapse
lol, I hope so
Sorry, it goes to indefinite loop of customization.
panvita said:
Sorry, it goes to indefinite loop of customization.
Click to expand...
Click to collapse
Man... we totally haven't root-caused that.
Sogarth said:
Well, no, it wasn't that fast. And then I added a 32 MB pagepool, set my glyph cache to 128 KB (0x0020000), set my font cache, took out a few things I wasn't using, and it's amazing how much faster it works.
Yeah, the 32 MB pagepool is probably overkill; I ought to see if a 16 MB pagepool works just as well... but... it's 32 MB!
On the other hand, maybe I ought to see if a ramdisk for caching works better instead...
Click to expand...
Click to collapse
the ramdisk is a good idea, i tried to use it but would not work for me... maybe im stupid
panvita said:
Sorry, it goes to indefinite loop of customization.
Click to expand...
Click to collapse
what spl do you have
irus said:
the ramdisk is a good idea, i tried to use it but would not work for me... maybe im stupid
Click to expand...
Click to collapse
I think it might depend on what ramdisk you're using. The one I was thinking about is the temporary ramdisk that you need to reload on every boot - it would be nicer to have a permanent one, but a temporary one can be useful for some of the temp file caching, Internet Explorer or Opera browsing caching, etc.
Sogarth said:
I think it might depend on what ramdisk you're using. The one I was thinking about is the temporary ramdisk that you need to reload on every boot - it would be nicer to have a permanent one, but a temporary one can be useful for some of the temp file caching, Internet Explorer or Opera browsing caching, etc.
Click to expand...
Click to collapse
not a bad idea
Yes! This is what I like about you, Irus. Clean and empty for each installed what they like.
This ROM is got me stuck at an endless customization loop.
I'm using spl 3.5.
What should I do, flash back to my previous ROM?
irus said:
what spl do you have
Click to expand...
Click to collapse
I'm using spl 3.5 too.
Irus and Sogarth,
Thank both of you for this wonderful ROM. I've installed it while travelling on the road today, using my SD card, and it installed without any customization loop. Of couse, I'm on spl1.2.
Has anyone with spl1.2 got any customization loop so far? If yes, were you ever on spl3.5 ?
I downloaded the ROM directly into my device as usual without using a PC. I have 141.05 MB of storage memory and 81.43 MB of Program memory available after installation, which is slightly different from Irus' posted number. Wonder if it is because Irus has been on spl3.5 before, hence he has 3.49 MB less memory left than I have.
So far, I've only installed TomTOM7, which loaded very fast. In fact, seems faster than any other ROM. GPS fixed was also exceptionally fast.
Will continue to test and provide feedback. I can say that so far I like every bit of the concepts that goes into the making of this ROM.
Each time when I thought I already have the best ROM, Sogarth and Irus comes around and prove me wrong with even better ROM. Irus' idea of making everything a cab that we can install on our own is brilliant, and will make this ROM the most user customizable ROM ever. I'm thrilled to see things like subDisplay taken away, as I never use it ever. This should free up resources and speed up the device to the maximum extend possible. Of course, Sogarth is going to introduce RAM cache files to even better that soon, and wow, so many good stuffs are coming up from you two. Thank you both once again for this sensational master piece.
eaglesteve said:
Irus and Sogarth,
Thank both of you for this wonderful ROM. I've installed it while travelling on the road today, using my SD card, and it installed without any customization loop. Of couse, I'm on spl1.2.
Has anyone with spl1.2 got any customization loop so far? If yes, were you ever on spl3.5 ?
I downloaded the ROM directly into my device as usual without using a PC. I have 141.05 MB of storage memory and 81.43 MB of Program memory available after installation, which is slightly different from Irus' posted number. Wonder if it is because Irus has been on spl3.5 before, hence he has 3.49 MB less memory left than I have.
So far, I've only installed TomTOM7, which loaded very fast. In fact, seems faster than any other ROM. GPS fixed was also exceptionally fast.
Will continue to test and provide feedback. I can say that so far I like every bit of the concepts that goes into the making of this ROM.
Each time when I thought I already have the best ROM, Sogarth and Irus comes around and prove me wrong with even better ROM. Irus' idea of making everything a cab that we can install on our own is brilliant, and will make this ROM the most user customizable ROM ever. I'm thrilled to see things like subDisplay taken away, as I never use it ever. This should free up resources and speed up the device to the maximum extend possible. Of course, Sogarth is going to introduce RAM cache files to even better that soon, and wow, so many good stuffs are coming up from you two. Thank you both once again for this sensational master piece.
Click to expand...
Click to collapse
I flashed this rom under spl 3.5, and got endless roop of customization. But I was able to flash back to irus ultra lite under spl 3.5. After reading eaglesteve's finding that he succeeded in installation under spl 1.2, I used Cmonex downgrader to directly downgrade to spl 1.2 without going from AP4. After downgraded to spl 1.2, irus ultra lite rom kept loop of customization. I forcibly entered into the tri-color screen by pushing camera bottom and soft reset hole at the same time, and tried to install this Sogarth Base Vanilla Rom under spl 1.2. Now I ended up with the following statement:
Error [244]: Invalid Model ID
This Update Utility cannot be used for your PDA Phone. Please check your Update Utility
[? -SvrhvHOK-AUJH566
Now, I can go no where, no matter I tried flash back to irus ultra lite in spl 1.2, MiChY WWE full version in spl, AP Dual 3.0 in spl 1.2, or AP4, or any rom in spl 3.5, I got the same above statement. My device is bricked. Please help.
panvita said:
I flashed this rom under spl 3.5, and got endless roop of customization. But I was able to flash back to irus ultra lite under spl 3.5. After reading eaglesteve's finding that he succeeded in installation under spl 1.2, I used Cmonex downgrader to directly downgrade to spl 1.2 without going from AP4. After downgraded to spl 1.2, irus ultra lite rom kept loop of customization. I forcibly entered into the tri-color screen by pushing camera bottom and soft reset hole at the same time, and tried to install this Sogarth Base Vanilla Rom under spl 1.2. Now I ended up with the following statement:
Error [244]: Invalid Model ID
This Update Utility cannot be used for your PDA Phone. Please check your Update Utility
[? -SvrhvHOK-AUJH566
Now, I can go no where, no matter I tried flash back to irus ultra lite in spl 1.2, MiChY WWE full version in spl, AP Dual 3.0 in spl 1.2, or AP4, or any rom in spl 3.5, I got the same above statement. My device is bricked. Please help.
Click to expand...
Click to collapse
this is not good but your device is not bricked. you need to use cmonex's model ID fix app, click on the link and start reading at post 33 read the rest of that thread to see what problems may have come up and then go back to post 33 and try to fix the model id if you need help ask here or send cmonex a pm she is really nice and will help you if you need it http://forum.xda-developers.com/showthread.php?t=387454&page=4
Just for additional information. I am using spl 1.2 and I don't have the customization issues. I use to have spl 3.5 and downgraded a while back when cmonex provided the downgrader.
I have currently installed RUU_Le2_UK_1.72.206.3_Radio_15.32.50.07U_2.07.51.22_2_Signed_LEO_Ship
everything works fine.
i have tried Dutty CDLC version 14 which worked fine but due to the messaging client being not compatible with smartwatchM i had to go back to stockrom
i previously HSPL so i could install custom radio (to make android work)
after going back to the stock rom i have since tried various other roms and i have the same problem each time
it installs and boots fine, after a restart it just seems to hang at first screen (does not display radio rom etc in bottom corner like normal just screen)
only way to get anything to work again is to once again install the stock rom via bootloader screen.
is the HSPL damaged? or have i missed something
thank you for you help
you are flashing 576 ram enabled roms, but your radio is still a 51 version so they won't boot.
enter bootloader, flash something like 2.08.50.x radio and your phone will boot. don't forget every time you flash back to that o2 rom it will reset the radio to a 51 version.
that makes so much sense, im just an idiot.
i shall attempt this now. thanks alot
easy to overlook.
it worked ... altho i have to go back due to me not being able to find a new rom that works with my mbw150 lol , 2 days just to revert back
anyways im very happy for the quick reply and help and not mocking me for being dumb. thanx again