Related
I'm new to the whole Android scene so let me know if I left out information and what not.
I'm currently running RCMix HD v5.9.3 and decided to flash my radio. I was using Radio_12.39.60.19_26.06.04.06_M - Cingular US 1.80.502.3 and every time I made a call, my phone beeps and then hangs up. I'll eventually make a call but its very annoying. I went ahead and flashed the suggested rom from this topic (Radio_12.28e.60.140f_26.04.02.17_M2_SF - HTC WWE 1.72.405.3 R2) and I thought that fixed the problem but it is starting to happen again and when I look down I will have almost full signal if not full.
Did I do something wrong while flashing it? Should I go back to stock?
All help is appreciated! Thanks
Did you do a backup (nandroid or otherwise) before loading the current ROM?
If so, you could start from there, restoring your backup and seeing if everything is fine. If you used either of the hack kits here, then the ROM you revert back to should be rooted and close to stock, meaning you have all of your basic functionality and can verify that the hardware is working.
Think back to when you installed your current ROM of choice - did you clear the cache and data when you did it? If not, then that could be a big part of your issue right there. Try reloading the ROM again after wiping cache and data.
You could also try a ROM closer to the stock ROM like ClearDroid - very nice one that I'm using at the moment, and the guys supporting it are active here and helpful with issues (though I myself haven't had any).
This would be my personal method of resolution - to pinpoint the issues and verify the source, be it hardware or software. Feel free to get a second (or more) opinion on this - I'm not "old hat" on the Android platform yet, but I have been tinkering with this and it doesn't seem like a phone that is terribly easy to brick.
Good luck with it, and post back with your resolution - maybe you can help someone else who's seeing the same issue.
The cell coverage in your area could be over loaded. Can you make calls at night or off peak without issues?
nightborne said:
Did you do a backup (nandroid or otherwise) before loading the current ROM?
If so, you could start from there, restoring your backup and seeing if everything is fine. If you used either of the hack kits here, then the ROM you revert back to should be rooted and close to stock, meaning you have all of your basic functionality and can verify that the hardware is working.
Think back to when you installed your current ROM of choice - did you clear the cache and data when you did it? If not, then that could be a big part of your issue right there. Try reloading the ROM again after wiping cache and data.
You could also try a ROM closer to the stock ROM like ClearDroid - very nice one that I'm using at the moment, and the guys supporting it are active here and helpful with issues (though I myself haven't had any).
This would be my personal method of resolution - to pinpoint the issues and verify the source, be it hardware or software. Feel free to get a second (or more) opinion on this - I'm not "old hat" on the Android platform yet, but I have been tinkering with this and it doesn't seem like a phone that is terribly easy to brick.
Good luck with it, and post back with your resolution - maybe you can help someone else who's seeing the same issue.
Click to expand...
Click to collapse
Thanks for the info. I'll do a backup and try going back to the rooted ROM I had with the hack kit later tonight. Thanks again for the ideas. I'm hoping something works *crosses fingers*
I was having the same issue as you when running cm7 or any gingerbread Tom using the stock radio. I ended up flashing a gingerbread radio and that solved the problem but now my upload speeds suck again :-(. Give it a shot
Sent from my rooted Inspire 4G using XDA App
I went ahead and wiped everything and basically went through the hack kit again to get root stock and everything seems to be working normally. I love the RCMix rom and will give start fresh from there and see if the same thing happens.
@nino313
I'll look at the gingerbread radio if things start messing up again.
yes i flashed a rom quite a few days ago- did a wipe on everything -rom loaded everything runs find ... twisted sense 1.5 with kernel that comes with sorry for my spelling trying to figure out whats going on anyway back to the problem at hand
im having issues were i could be doing anything on my tb all of a sudden it resets to the htc loading screen im like ok just a minor thing but it is now getting on my nerves i feel like i might of done something wrong yet im very cautious on how i flash rom using rom manager and its up to date of course. so i was thinking should i change it back to stock to see if that might cure my reset woes ? or just unroot and take it back ? any suggestions are helpful
This seems to be a known issue and is related to the new radio. Did you flash that?
*** UPDATE ***
I reverted back to...
-baseband verison
1.02.00.0103_2r
-kernel ver.
2.6.32.21-gb05544a [email protected] #1
tue mar. 1
-build number
1.12.605.6 CL338893 release-keys
-still rooted with S-on instead of S-off
Still doing the reset here and there...
yes i did flash the radio
Try reverting your radio back to stock (there is a thread in the Dev section) and see if it helps. I have been having this issue too, but it isn't bothering me enough right now to change it. Also I'm not sure if you can use the new framework with the old radio -- you may have to use an older ROM.
thats what im going to try
I have the new radio and I have never experienced resetting with any of the roms, etc. I might just be one of the lucky ones!
- thanks for rubbing it in -lol
Thats good...
i might be considering taking my tb back to get another if this doesnt work
lol my TB is stock and restarted 4 times by itself yesterday
crazed_z06 said:
lol my TB is stock and restarted 4 times by itself yesterday
Click to expand...
Click to collapse
do you have the new radio ? or out of box stock?
cjmcmillion said:
*** UPDATE ***
I reverted back to...
-baseband verison
1.02.00.0103_2r
-kernel ver.
2.6.32.21-gb05544a [email protected] #1
tue mar. 1
-build number
1.12.605.6 CL338893 release-keys
-still rooted with S-on instead of S-off
Still doing the reset here and there...
Click to expand...
Click to collapse
ok-
baseband changed to - 1.16.00.0223r
kernel changed to 2.6.32.21-gb05544a [email protected] #1
sat feb 19th
s-on and no longer rooted
hopefully no more resets if so im returning for another tb...
not giving up on a great device
cjmcmillion said:
ok-
baseband changed to - 1.16.00.0223r
kernel changed to 2.6.32.21-gb05544a [email protected] #1
sat feb 19th
s-on and no longer rooted
hopefully no more resets if so im returning for another tb...
not giving up on a great device
Click to expand...
Click to collapse
Damn that was harsh! lol really the first thing should have been to try a different kernel. It has become known with the tb they are not all created equal. Kernels or I should say switching them can make a big difference.
LeoD said:
Damn that was harsh! lol really the first thing should have been to try a different kernel. It has become known with the tb they are not all created equal. Kernels or I should say switching them can make a big difference.
Click to expand...
Click to collapse
yes i tried those before hand...but decided hey lets do a fresh start
which i reverted back to stock since i do enjoy the rooting process
in which i followed the ....
[ROOT] PermRoot + Unlock Bootloader - Safer/Easier 4/21/2011
http://forum.xda-developers.com/showthread.php?t=996616
followed by installing the radio on this thread the top...
Flashed -> CDMA Radio version: 1.16.00.0402w_1
LTE radio version that came with 1.13.605.7...
Thanks To Adrynalyne -
[RADIO] The Obligatory Thunderbolt Radio Thread
http://forum.xda-developers.com/showthread.php?t=1045081
Then i Installed the Rom Twisted Sense 1.5 running
kernel 2.6.32.21_bamf_4.42 which everything is running
smooth like silk now....Thanks Hedney3!!! Pick the Rom up here >>>>
http://forum.xda-developers.com/showthread.php?t=1040413
i suggest picking up the battery calibrator and ZDbox in the
market -
Well my problem with resetting still exisits i returned to stock now
i seem to still be having this problem...
so hopped over to verizon to speak with someone about this and they
told me this was a functionality of the phone that they could send
me a replacement out but would cost me shipping and handling and also
stated if they didnt find anything wrong with it that i would have to
pay full retail !!! i was like BS *&^&&%^%^ *^%^%$&^$% well you get
the point.
i still have the same tbolt just trying to figure out what to do now was thinking of returning for another tbolt but fear
that this so called " functionality " of the phone ... any suggestions?
my phone was fine until I decided to flash the new radio. I reverted back to stock radio and I'm still getting reboots
yes same here i told verizon about my tbolt self resets like once every hour if im on it they told me it was a part of the functionality of the tbolt
My old one did that.
My old TBolt did that, kind of like resetting the Sense interface (which takes forever). I called them and talked with a really nice guy, and he explained a hard reboot should fix it (which didn't and I lost my call, and got connected with a capital B the next time around _-_)
I also was having issues with the memory card getting "wiped" (data still there, just not viewable in phone) and (the kicker) my phone would reach temperatures of 69degC while charging, while off.
That last one had them change it out right quick.
No automatic resets at all here, and I've had it on and using it most of the time throughout the LTE outage and after. No resets when on EvDO/HRPD; no resets when on LTE/eHRPD; no resets when on EvDO/eHRPD. It only resets when I tell it to!
As for the connection, well... I do get the occasional dropout on LTE. More problems tonight than most nights with that. But EvDO seems to be pretty stable as always.
i didnt have any problems during the outage since im not in a 4g lte area
cjmcmillion said:
yes i tried those before hand...but decided hey lets do a fresh start
which i reverted back to stock since i do enjoy the rooting process
in which i followed the ....
[ROOT] PermRoot + Unlock Bootloader - Safer/Easier 4/21/2011
http://forum.xda-developers.com/showthread.php?t=996616
followed by installing the radio on this thread the top...
Flashed -> CDMA Radio version: 1.16.00.0402w_1
LTE radio version that came with 1.13.605.7...
Thanks To Adrynalyne -
[RADIO] The Obligatory Thunderbolt Radio Thread
http://forum.xda-developers.com/showthread.php?t=1045081
Then i Installed the Rom Twisted Sense 1.5 running
kernel 2.6.32.21_bamf_4.42 which everything is running
smooth like silk now....Thanks Hedney3!!! Pick the Rom up here >>>>
http://forum.xda-developers.com/showthread.php?t=1040413
i suggest picking up the battery calibrator and ZDbox in the
market -
Click to expand...
Click to collapse
Just a FYI for you, I do not have problems with reboots nor do I have most problems most say they are having, however my tb just did not like twisted sense 1.5. For me anyway I couldn't stay on it very long.
I have an idea if you want to give it a try. it will take some time and effort but on the other hand it just might save you the trouble of having to return your tb.
First, do a full wipe of data/cache, do it twice to be sure. flash BAMF, (either one don't matter). once you boot up go to settings/SD & phone storage and do a factory reset. let it reset and come back up. it will take a while to boot and you might even get errors which is ok.
Now hit the power button and reboot into recovery again wipe data/cache 3x, wipe cache 3x.
now try to install your rom. just for the heck of it at least for now stay away from twisted sense. I would use BAMF at least till you see if this solves your problem.
once you have your rom installed flash imoseyon's (SAFE) kernel.
If you do try this let me know how you make out. This has solved many issues for me in the past many times.
actually I stand corrected it was NOT twisted sense that gave me a problem it was tesla coil that I had problems with. so your choice there.
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
Please bare with me since this is the first time having to post for an issue since I usually find an answer on your forums
So here's the situation.
I bought the photon q 4g lte from ebay and it came with the unlocked bootloader.
Needless to say it was with the stock ics and i tried to find a jellybean update because it wasn't taking the ota and ended up going with cyanogen since i had no problems before. However those phones i had before were with sim cards not cdma.
I found out i couldn't update prl or profile manually without having to do something on the pc.
So after searching left and right i found i could use rsl lite (I used 6.1.5) and eventually found the "stock" file from this post
http://forum.xda-developers.com/showthread.php?t=2095536&highlight=rsd+lite
I did the stock jellybean, got it to go through the process and it booted up with no errors.
However, when it boots into the os it pops up a force close on omadmclient_sprint_dataservice and eventually also on the process com.android.phone.
I tried putting it in airplane mode to see if the service error would go away but it didn't work for the process part crashing.
I tried re-flashing, deleting cache in recovery, doing a data/factory reset in recovery and the one time i was able to do a data factory reset within the settings menu.
I could not find anyone that said they had a rom that worked with sprint and updating prl within the rom, if anyone knows of one let me know and i will flash it through rsd.
Otherwise does anyone have an idea of what could be happening because googling the omadmclient part did not pull up anything specific and pulling up the process issue for other phones has not helped me either.
Was this a hacked GSM phone, or are you using it as CDMA?
I've never heard of people having FC issues after flashing a FXZ from RSD. Which one did you flash? Android 4.1.2 - Sprint US - 9.8.2Q-122_XT897_FFW-5 (No simlock) ?
If you are on stock, you should be able to update the PRL within the ROM.
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
crispy6 said:
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
Click to expand...
Click to collapse
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
arrrghhh said:
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
Click to expand...
Click to collapse
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
crispy6 said:
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
Click to expand...
Click to collapse
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
arrrghhh said:
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
Click to expand...
Click to collapse
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
crispy6 said:
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
Click to expand...
Click to collapse
To downgrade to ICS, you need to remove some additional lines. See this post for more information on that.
However, you should be able to update the PRL on either stock ROM.
I think I said this before, but I will say it again. You need to do PRL updates, activate the phone, and get EVERYTHING working on stock BEFORE you flash ANY custom ROM. This is just standard practice - you don't want to put the cart before the horse! Get the phone working, then play with custom ROM's.