Database Users

ANOTHER PRI PROBLEM!!!!!!(but with going to other roms after new damage)

now im just guessing through trial and error but i believe that if you go to the new damage rom then you WILL NOT be able to go back to any roms that will change the PRI because i and others have been noticing that when getting the damage rom and we dont like it and want to wait for a faster stable version we try to go to the previous version and it freezes on boot screen, and in fact i just tried this with a few eris build that have been reported to change PRI and even the modded version of damage and that's what my phone has been doing any one else try and notice this or can confirm this?

rulyskull said:
now im just guessing through trial and error but i believe that if you go to the new damage rom then you WILL NOT be able to go back to any roms that will change the PRI because i and myself have been noticing that when getting the damage rom and we dont like it and want to wait for a faster stable version we try to go to the previous version and it freezes on boot screen, and in fact i just tried this with a few eris build that have been reported to change PRI and even the modded version of damage and that's what my phone has been doing any one else try and notice this or can confirm this?
Click to expand...
Click to collapse
I have been on the new v2r2 and gone back to 1.5 and damagev1 2.1. My pri is the same. It changed last night but was able to get it back to the right one using the MSL fix.

rulyskull said:
...because i and myself have been noticing that when getting the damage rom and we dont like it...[/B]
Click to expand...
Click to collapse
Multiple personality much?

Wasney said:
Multiple personality much?
Click to expand...
Click to collapse
my bad meant others lol thanks for pointing that out

Last night when all the PRI issues popping up, I was a flashing fool trying to simulate what was going on!
And I can tell you that the only thing that affected it was the ERIS builds!
I should say it was the Eris build and user error!
You gotta wipe after everything, if ya did it do it again!

Have you read the sticky threads on how to fix the issue???
if not, do it...thanks!

redram38 said:
I have been on the new v2r2 and gone back to 1.5 and damagev1 2.1. My pri is the same. It changed last night but was able to get it back to the right one using the MSL fix.
Click to expand...
Click to collapse
you have? so this is probably a different error but does your phone have the with google on the back? because mine doesn't and i know that the with google has a higher sense version (by like .55) and they fixed some problems with the ones without with google when changing sense so what im thinking now is that its not the pri its something different and going to be a pain to find out

Roman G said:
Last night when all the PRI issues popping up, I was a flashing fool trying to simulate what was going on!
And I can tell you that the only thing that affected it was the ERIS builds!
I should say it was the Eris build and user error!
You gotta wipe after everything, if ya did it do it again!
Click to expand...
Click to collapse
see i did this at least 8 times and still has this issue

The cause of the change of the PRI is not Damages latest ROM.
I was one of those that had to get their MSL to reset the phone, but I went
and re flashed Damages latest and the PRI stayed good.
So I'm pretty sure is not his.
There is people testing around trying to find which was the ROM that caused
it, but not sure if they have found out yet.

Okay this is what I did!
I am rooted and running a stock sprint ROM, this morning I flash this damage 2.0, bluethooth audio still does not work, but everything else was working great though. I nandroid back to 1.5!
Fast forward to this evening and all the problems everyone else has, and damage new version, I figure I will flash again to try it out! Then everyone starts talking about the PRI, so I jump in and start flashing other ROMS to try to get a different PRI#(Mine is 1.70_003).
So I go to the eris leak and flash PRI, it is still the same, but I have unknown operator and no sprint on my lock screen. Just for ****s and giggles I decide to flash back to the newest damage build without a wipe and what do ya know!
Now I have unknown OP and my PRI has changed to 2.11_002!
So now I am going to wipe and try to flash the newest damage build and see if it changes back!
I am wondering somewhere along the way some of you did not wipe first before flashing all these ROMS!
So it seems not doing a wipe causes this to change and stick for some unknown reason!
I am now back to rooted but stock and I still am stuck with the same bad PRI 2.11_002.
That was lastnight!
So this morning I did the PRI fix and got back to 1.70_003, and downloaded the legend leak ROM, did a wipe and flashed and verified my PRI was 1.70_003, then I nandroided like I did before without a wipe back to stock with root and my PRI is the same, so it is without a doubt related to the ERIS leak, and I also think that not wiping first has something to do with it as well!
I KNOW WITHOUT A SHADOW OF A DOUBT THE ERIS LEAK CAUSES THIS!
AND THAT IS REALLY THE ONLY ONE THAT WOULD AS THE PROBLEM DID NOT POP UP UNTIL THIS CAME OUT!

rulyskull said:
you have? so this is probably a different error but does your phone have the with google on the back? because mine doesn't and i know that the with google has a higher sense version (by like .55) and they fixed some problems with the ones without with google when changing sense so what im thinking now is that its not the pri its something different and going to be a pain to find out
Click to expand...
Click to collapse
yes, it has with google, but I still changed to the bad PRI last night for some reason. I got back the right one using the fix and it has stayed there even though I have had 3 diff Roms on my phone today, one being the new Damage v2r2. I am on v1 right now due to needing apps2sd. The only thing I did diff last night was forgot to wipe when flashing from one rom to the next once. I somehow think that is part of the issue.

You also have to remember that alot of builds that came out after the Eris leak were for the most part based on or contained part of the Eris leak!
So even if it did not say Eris leak it prolly had aspects of it in!

Roman G, I dont know if you are aware of this yet, but only way to get your old PRI 1.70_003 is to get the MSL and do a phone reset.
Flashing a RUU or any other Rom won't do the job.

MjPayne said:
Roman G, I dont know if you are aware of this yet, but only way to get your old PRI 1.70_003 is to get the MSL and do a phone reset.
Flashing a RUU or any other Rom won't do the job.
Click to expand...
Click to collapse
I not sure if your aware of this yet, because obviously you have not read anything I have posted, but I have done this 4 times already!
Thanks for the advice though!

I went back to my nandroid backup after installing damage's rom and I still don't have protected apps in the market. At least one other person has reported this so I know it's not just me.
I tried running the RUU back to a stock 1.5, still no protected apps.
I tried the pri fix that everyone is talking about. Called Sprint to get my number and followed the steps. Everything seemed to work ok but still no protected apps.
Anybody got any ideas?

I am wondering if there will be any issues returning my phone to sprint with the flipz01 PRI and this thread seems the best place to ask.
trying to clean sand from under my screen I blew out the microphone and can not use voice. I used Flipz tool to flash back to a stock ROM, however I noticed today that for PRI it says Flipz01. Sprint has already ordered me a replacement phone, but when I do give this phone back is there any way Flipz PRI can come back and penalize me?
Thanks in advance!

[Q] Is there a Stand-alone Radio Image Update to 2.22.27.08?

I'd like to use the new radio with my oem Donut. Is it as simple as taking the file from one of the update guides and flashing it in the traditional manner? I'm kind of noobish so I'm reluctant to try to take one piece of a Froyo update guide and flash the radio. I'm not really in the market for a sleek black paperweight.

I wouln't do it!
This has BAD IDEA written all over it please don't try this. That being said why not upgrade to the official FROYO? I know it's hard to fathom after seeing ECLAIR in action but it truly is a totally different and better experience.
QUESTION: What does DONUT have that you like so much?

Edubyah said:
This has BAD IDEA written all over it please don't try this. That being said why not upgrade to the official FROYO? I know it's hard to fathom after seeing ECLAIR in action but it truly is a totally different and better experience.
Click to expand...
Click to collapse
lol, I agree, that's why I posted first.
QUESTION: What does DONUT have that you like so much?
Click to expand...
Click to collapse
SPEED. I tried the TMUS rom posted up here a few days ago and it was ok, much better than other Froyo ROMs I've tried, but still laggy compared to my oem androoted Donut.

it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.

aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
I'm scared to try this. Is this the radio that came with the T-MOUS Fro-Yo OTA? I wonder why there isn't a thread for it yet.

Moving to General

aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
The hboot? Which hboot are you talking about? The first half of the ota update succeeded but the second half failed so I have the new SPL but not the new radio or OS.

The new radio does work with cm6, well cm6.1 rc1. I flashed it on my wife mt3g 3.5mm awhile ago, everything booted up just fine.

d3vilskid said:
The new radio does work with cm6, well cm6.1 rc1. I flashed it on my wife mt3g 3.5mm awhile ago, everything booted up just fine.
Click to expand...
Click to collapse
Cool, did you or she notice any improvements?

Yea i got to messed with it a little bit more, signal is pretty strong and stays constant, but that might vary from phone to phone, not much to say about the market since it was down a couple days back. Overall she is satisfied with it. Cant wait till it is ported to the 32b phones so we can take advantaged of the extra 10-15mb it frees up.

aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
So I just flash this through recovery as I would any other zip file? Any idea if this is compatible with older roms? If I nandroid back to my oem 1.6 without rolling back to 23.02 will my phone explode? How about Eclair?
If I flash this is it just as easy to flash back to 23.02 if I need to for some reason?
Sorry for all the obsessive questions; I've never flashed a radio before so I don't know what it is that I don't know.

aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
im flashing that radio now onto cm6.1, ill post my results
EDIT: Your .zip file doesnt work. It did nothing, after i flashed and rebooted then shutdown and went into fastboot my radio was still 2.22.23.02.

Foo_Blyat said:
im flashing that radio now onto cm6.1, ill post my results
EDIT: Your .zip file doesnt work. It did nothing, after i flashed and rebooted then shutdown and went into fastboot my radio was still 2.22.23.02.
Click to expand...
Click to collapse
It worked for me, except it caused a bootloop because it's not compatible with the CM6 kernel, or at least ezterry's CM6 kernel. I had to flash back to 2.22.23.02.
If you're not using the oem t-mobile/android kernel, don't flash this radio.
I really want to know if this radio is compatible with oem Donut.

Going Back to My Stock Eclair

Dear All
before i restore my last eclair stock rom by red cwm, what should i do??
right now i using 2.4 voodoo with enable lagfix.
Do i have to :
1. go to cwm, disable lagfix
2. wipe all
3. restore eclair backup
4. reboot, flash by odin di01modem.tar
5. that's it
is it work to get me back my eclair stock rom??
or i just follow this Link
Odin Restore files to get you to stock
or
[ODIN] Full DI01 ODIN Package
Thx

Odin for full di01 will do the trick, no need for anything else.
Sent from my SCH-I500 using XDA App

To add to this post, disable voodoo and restart phone to let it disable add
Gurm said:
Odin for full di01 will do the trick, no need for anything else.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Rocking dj05 and jt's voodoo 5

It is my understanding that if you run the complete odin package it will overwrite even voodoo.
Sent from my SCH-I500 using XDA App

i have killed my phone 3 times not disabling voodoo correctly when flashing roms. and each and every time adrynalyne's full di01 restore package has overwritten the whole thing for the win.
so if you are going back to bone stock, unrooted, full bloated eclair, (ie because you need to bring the phone back to verizon for warranty work) then that is your best bet. it will indeed wipe any and all voodoo whatnot from your phone.

Isn't it fine just to bring it back to stock DL09 Eclair, since that's the latest official OTA release? I don't see why you need to go back all the way to DI01 if you're planning on returning it. But I guess in the end of the day it won't really matter either way.

It doesn't really matter, all of the all in one vzw fascinate odins will work.
You technically don't _need_ to odin anything but the modem though.
For me, there was no lagfix and I had a working cwr/rom manager, so I did it in three quick steps.
1. Nandroid restore my DL09 setup.
2. Odin DL09 modem over EB01.
3. install a DL09 kernel from clockwork recovery and wipe the cache.
I was exactly where I was before with no headache.
Nandroid doesn't flash modem nor kernel.
However the all in ones may be faster if you are building from scratch (and absolutely the fastest route to stock). You should pick an all in one with the modem and kernel you want or you will have to do steps 2 & 3 either way.
Swyped w/ XDA App. A clean tie attracts the soup of the day.

trully guys, do you happy with leak froyo right now??
for me battery issue thats why I have to go back to eclair.
fascinate with eclair has the speed,powerfull n stable, its the same like I feel when use leak froyo.
there were no freeze or stuck either on both OS.
Sent from my SCH-I500 using XDA App

capunkjd said:
trully guys, do you happy with leak froyo right now??
Click to expand...
Click to collapse
I am happy, its Freakin' FROYO
for me battery issue thats why I have to go back to eclair.
Click to expand...
Click to collapse
For me, Froyo has been MUCH better with my battery. Have you wiped your Battery Stats?
fascinate with eclair has the speed,powerfull n stable, its the same like I feel when use leak froyo there were no freeze or stuck either on both OS.
Click to expand...
Click to collapse
I agree, but Froyo does make is a little more faster but with leaked ROMs they aren't fully tested, so that's why they are a little buggy, and thats why we have great devs here that fix em as soon as we find em
Sent from my SCH-I500 using XDA App[/QUOTE]

capunkjd said:
trully guys, do you happy with leak froyo right now??
Click to expand...
Click to collapse
I found that turning of gps when not in use(I never use it) stopped the battery drain.

I also want to go back to eclair and cant find it anywhere. I have my phone on metro and I cant get my web and mms to work, also my phone shows only 1.47 g internal memory. I bought this phone used so who knows what was dont to it. Anyone have an idea where to get eclair???
Edit- Installed this via odin as instructed. worked great took me back to 2.1 update 1 which is what i had when i got the phone. Will continue to work on the mms and web issue. Oh and still have the memory issue

pinkmini said:
I also want to go back to eclair and cant find it anywhere. I have my phone on metro and I cant get my web and mms to work, also my phone shows only 1.47 g internal memory. I bought this phone used so who knows what was dont to it. Anyone have an idea where to get eclair???
Click to expand...
Click to collapse
http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/53549-how-flash-full-package-dl09-stock-di01-via-odin.html

Cant restore eclair
Guys i have a bit strange problem. I'm trying to restore stock Eclair on my x8 but for some unknown reason i cant do it. Tried flashing it, tried with SEUS and no result plus it wont go into recovery wso i cant access root menu im running out of ideas help pls. Btw im running GingerDX v 0.26.
I got it to work. Sorry for disturbing guys. Thanks.

Revert Back to Telus 1.84 ROM

Hello
I'm trying to revert my phone back to the stock ROM from telus. I've downgraded to 1.32 and gave up when i found out that sound on the desire HD doesnt work on CM7.
How do I revert back?
ive searched the forum and tht's all ive found
" just flash a stock RUU? That uses your PC to flash your phone, not bootloader."
any help would be appreciated. Where do i get the RUU file and how do i go about doing this.
A $10 paypal donation will given to anyone who helps. i really need to get the phone back, its my girlfriend's. (
btw i have turned S-air off and done a perm-root with visionary already.. how do i get the cherry back in place?lol

You can flash either Raidroid in clockworkmod, or use Telus RUU. Android Revolution HD is also a good (the best) option if you want performance and good battery life.
Raidroid is a stock ROM that will keep your root and S-OFF, so it is easy to flash a custom ROM in the future. RUU will revert your phone to stock, Radio S-OFF will remain if you used it. Android Revolution HD is the best custom ROM out there. Every option gives you working sound.

jkoljo said:
You can flash either Raidroid in clockworkmod, or use Telus RUU. Android Revolution HD is also a good (the best) option if you want performance and good battery life.
Raidroid is a stock ROM that will keep your root and S-OFF, so it is easy to flash a custom ROM in the future. RUU will revert your phone to stock, Radio S-OFF will remain if you used it. Android Revolution HD is the best custom ROM out there. Every option gives you working sound.
Click to expand...
Click to collapse
are there any issues with android revolution?like sound problems with the CM7?

Nope, Telus users are reporting that it works great. Some users have had small microphone echo while using it, but that can be fixed by flashing a simple zip in clockworkmod just like you would flash a ROM.
http://www.wbakkercomputers.nl/mic_fix.zip

jkoljo said:
Nope, Telus users are reporting that it works great. Some users have had small microphone echo while using it, but that can be fixed by flashing a simple zip in clockworkmod just like you would flash a ROM.
ok, i'll try android revolution hd. Earlier today when i checked the terminal was showing the # instead of $. now when i checked, its back to $. I went on visionary app again, did a temp root and perm root, and checked the terminal again but its still showing the $ sign.
i don't know what the build number is for, but its now on 1.32. I wanna go back to the 1.84. I've noticed that the revolution HD has the 'official HTC RUU 1.84.61.2', so in the process of flashing the ROM, 1.84 should be back, right??
I'm a little bit confused about baseband versions and md5 checksums. mine is 12.28b.60.140eU_26.03.02.26_M. which radio version should i flash with?
I'm totally new to this and I hope to get working by tomorrow night. I really appreciate your help, donation will definitely be made once i get this thing working. i couldnt pick up any calls today..lol
Thanks a lot
Click to expand...
Click to collapse

ziyaad89 said:
Hello
I'm trying to revert my phone back to the stock ROM from telus. I've downgraded to 1.32 and gave up when i found out that sound on the desire HD doesnt work on CM7.
How do I revert back?
ive searched the forum and tht's all ive found
" just flash a stock RUU? That uses your PC to flash your phone, not bootloader."
any help would be appreciated. Where do i get the RUU file and how do i go about doing this.
A $10 paypal donation will given to anyone who helps. i really need to get the phone back, its my girlfriend's. (
b
btw i have turned S-air off and done a perm-root with visionary already.. how do i get the cherry back in place?lol
Click to expand...
Click to collapse
Android Revolution works perfect, and has lots of customization options.
In case you still want Cyanogen, CM7 nightly build 12 worked just fine on my Telus... It has the sound fix built in to it.

ziyaad89 said:
jkoljo said:
ok, i'll try android revolution hd. Earlier today when i checked the terminal was showing the # instead of $. now when i checked, its back to $. I went on visionary app again, did a temp root and perm root, and checked the terminal again but its still showing the $ sign.
i don't know what the build number is for, but its now on 1.32. I wanna go back to the 1.84. I've noticed that the revolution HD has the 'official HTC RUU 1.84.61.2', so in the process of flashing the ROM, 1.84 should be back, right??
I'm a little bit confused about baseband versions and md5 checksums. mine is 12.28b.60.140eU_26.03.02.26_M. which radio version should i flash with?
I'm totally new to this and I hope to get working by tomorrow night. I really appreciate your help, donation will definitely be made once i get this thing working. i couldnt pick up any calls today..lol
Thanks a lot
Click to expand...
Click to collapse
After you flash a ROM with 1.84, you'll be back on 1.84
I wouldn't mess around with radio just yet, it works fine using stock Telus radio. If you notice battery drain or reception issue then flash the recommended radio.
Click to expand...
Click to collapse

cue_32 said:
ziyaad89 said:
After you flash a ROM with 1.84, you'll be back on 1.84
I wouldn't mess around with radio just yet, it works fine using stock Telus radio. If you notice battery drain or reception issue then flash the recommended radio.
Click to expand...
Click to collapse
ok so i'm running revolution HD right now, and the in-call sound quality is really bothering. I've installed that zip file mentioned above that is "supposed" to fix it but still the same
Are you running CM7 on yours?hows the incall sound quality? i might revert back to the stock ROM. Its weird how a slightly modified stock ROM is giving such an issue.
Click to expand...
Click to collapse

[Q] Image version reported by RUU prior to unrooting

Hey guys.. My Shift 4G has been rooted for quite some time, and I had been running CM 7.1 RC1 most recently.. After the past several weeks, I have experimented with various ROMs and Radios.. At one point I did upgrade the radio firmware to 1.08.00.0506 and the WiMax Radio to 27240.
I had also experimented with the rooted 2.76.651.4 Sense ROM posted by x99percent.. I wasn't thrilled with Sense, and ended up going back to CM7.1 RC1.. I also downgraded the radio 1.07.00.1129 and WiMax back to 27167.
Since I was playing around with the various ROMs and Radios, my Shift will never charge above 85%.. I am familiar with clearing batterystats.bin - and had tried various measures to get the battery to charge above 85%.. I used Battery Monitor, and it showed that basically around 85%, the Shift was turning off the internal charging circuit (Current would show usually less than 100mA..)
Thinking that perhaps something was sticking around from my various experimentations, I decided to use the original RUU (RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.1129_NV_SPCS_1.52_1103_release_160079_signed) to revert back to stock and start over.
One of the things that came up when I ran the RUU was it showed the current image version as 2.76.651.4.. This was even though my radio was 1.07.00.1129. Does anyone know why that would be reported that way?
I'm currently on the original sense RUU, and now it appears to be charging correctly. Once it does, I'll re-root and go back to CM7.1 RC1.
Thanks,
Rick

RickNY1971 said:
I had also experimented with the rooted 2.76.651.4 Sense ROM posted by x99percent.
...
One of the things that came up when I ran the RUU was it showed the current image version as 2.76.651.4.. This was even though my radio was 1.07.00.1129. Does anyone know why that would be reported that way?
Click to expand...
Click to collapse
Makes sense to me.
...and wrong forum.

Once your on the RUU how are you going to root again with a s-on bootloader?
Sent from my HTC Speedy Ball'o Fire using xda premium app not tapatalk

x99percent said:
Makes sense to me.
...and wrong forum.
Click to expand...
Click to collapse
Sorry about posting to the wrong forum.. I PM'd the mod to have it moved to Evo Shift 4G General.
The thing that did not make sense to me was the fact that I had restored my Nandroid backup from CM7.1 RC1, and restored the radio with the bootloader to 1.07.00.1129. I ran the RUU against CM7.1 RC1 and radio version 1.07.00.1129.
sparksco said:
Once your on the RUU how are you going to root again with a s-on bootloader?
Click to expand...
Click to collapse
I used the orignal RUU for Froyo -- not the Gingerbread RUU.

Oh my bad haha. I was about to say...you should be good to re-root then no? I flashed the new radio's manually just fine over cm7. Still on the same radio's and cm7 to this day
Sent from my HTC Speedy Ball'o Fire using xda premium app not tapatalk