Related
Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!
Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk
If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk
So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?
Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.
I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.
What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.
At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App
To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!
Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App
I have come to the conclusion that something is wrong with my phone. I have tried to install ICS....a lot. I am not exagerating when I say that I have tried every Odin install, and every ICS ROM that has more than a few positive results. Nothing will work. I am not new to flashing, I have had a Captivate, Inspire, Tab and have had no issues with those, even created a few themes and build.prop tweaks. I know what I am doing and I follow the OP instructions perfectly. The damn thing just wont take. I get the white Samsung screen, a black screen, a vibration, and a reboot. So at this point I think I am just going to stick with GB for right now and hope that either the offcial ICS update works (when available) or maybe 5.0 later this year.
Two weeks of try to make this work has run me ragged. Outside of the ICS issues though this is by far the best device I have had in terms of performance and reliablility.
Rant over.
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
icenight89 said:
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
Click to expand...
Click to collapse
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
mahausrath said:
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
Click to expand...
Click to collapse
I will give it a shot. I would really like to get back to ICS, I got so used to it on my other phones.
I have been using superuser, haven't had a problem yet from that.
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
^^^ this makes sense. Also I was asking about the note radio to advise u against it, or u may end up screwing up ur phone even worse, and have to make a visit to my corrupt efs fix thread lol.
hcyplr29 said:
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
Click to expand...
Click to collapse
I will try to get a different download, but I do not think that is it. The only reason I say that is because my phone had the exact same response for EVERY ROM I have download. They can't all be bad files. I have tried on two different PCs with three different USB cables. Good thought though, I have had bad downloads before. I am going to keep trying as the ROMs are updated and hope that I figure out what is going on, and hope that I can get the official update at some point. Then I will just root it and get rid of the bloat myself if I have to
I am going to stay away from the L5 radio, not worth the hassle.
On a side note, if installing a rom from the site, remember, most will work with the "base"
But need to reset/full boot before "updating".. dont just flash rom and flash update then reboot
I had a hard time with ICS as well with different problems, all I can say is it disproves the definition of insanity. Trying the same things over and over again will eventually make it work!
Hang in there, it's worth it. Whenever you do get the ODIN one click to work I highly recommend flashing Raider03's SMOOTHIE ROM. Awesome battery life and extremely "SMOOTH"! But be prepared for a few FCs and bugs with all of the ICS ROMS for now!
Well, it won't let me post in the official thread so I'm forced to put it here.
I recently installed the Team EOS Jelly Bean nightly (Stingray MZ602) their gapps, and reflashed the ICS radio as recommended using Rogue Recovery. Things have been working well except the WiFi. It tends to cut out randomly. It will be connected yet not transmit or receive. I have to turn it off and on frequently in order for it to work. No, it's not the router or my network. I am hoping for a solution other than going back to ICS.
First thing I would do is to full wipe and format /system
And flash twrp recovery that is advised as stable flasher.
Then redownload the ROM and gapps and make sure check sum is OK,
Then flash and reboot.
This way, you would id the source of your issue, ROM bug or recovery flasher? Cuz I know other guys face no issues like yours with twrp. Worth to try. Good luck.
The twrp page hasn't been updated since April and the project itself hasn't been updated since October of 2011. How can you be sure that it'll work with the radio zip better than Rogue? Or even the Team EOS JB build?
Twrp is advised by team eos. They asked to use it. And you need twrp for Xoom,
http://forum.xda-developers.com/showthread.php?p=28988754
Installation method 4 thru goo manager.
I remember one of the stingray users had an issue with the radio flashing and it went great with twrp.
Good luck.
Didn't work. I still have to reset the WiFi every 5 minutes or so. Also, the twrp recovery takes a LOT longer to load than Rogue's. Almost thought it wasn't going to work for a bit until the 'curtain' finally rose.
Over 24-hour bump...
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Wifi Issue
First Aid Computing said:
Just put on EOS 138 and reflashed the radios after going back to Rogue. Still radio issues with WiFi. Found some other threads detailing that Jelly Bean in general seems to have WiFi issues. As much as I hate it, I'm starting to think that I will have to 1) revert to ICS, 2) wait for an updated radio file, or 3) deal with it.
Click to expand...
Click to collapse
I always have that problem with their roms. Flash a kernel, thats always helped my situation.
Also I have zero issues with wifi on JB with my GNexus, N7, Infuse and Atrix. Its not JB, at least not as far as I have seen. Granted none are stock.
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
issues
First Aid Computing said:
Which kernel would you recommend?
Also, until JB I have not had this issue with EOS builds.
Click to expand...
Click to collapse
I flashed Eos 138 last night (was on CNA), without doing the radios, nor a kernel, and didn’t have any problems.
The Eos forum states that it has the kernel baked into the rom, so flashing the kernel is likely redundant.
However, for ****s and giggles I tried flashing the Eos 3.0.15 kernel and it would not flash, but I was able to flash the Eos 3.0.5 kernel instead and it took. I haven’t seen any issues, either before or after the kernel flash, so perhaps you should try re-flashing the entire rom sans radios and see what happens.
One of the nice things about the Xoom is its pretty easy to fix anything you could do to it via ADB and fastboot, so try some different combos, or start all the way over (from stock). If that doesn’t help, try a different JB rom and see if you get the same problem.
Also make sure you are flashing the right rom, there are several variants for the Xoom - 3G, 4G, Euro, and of course wifi only.
Just flashed CM10 and the non-EOS gapps without flashing radios. Running on WiFi for about 20 minutes so far without issue. Will try more testing later today.
EOS 4 & Kindle
Thanks EOS for 4.2.1! Feels like most things are working...except Kindle locks up on start-up. Just sayin'....
Okay.
So, I have tried to UTSE on this and found a thread that directed me to flash a new radio (http://forum.xda-developers.com/showthread.php?t=1116884) which I have done but the fastboot is still not letting my phone respond.
So...
My phone is a GT 19023.
I'd updated to jelly bean awhile ago but was having some serious performance problems and wanted to flash back down to ICS or GB. Of course, the recovery wasn't working so I went to Nexus Hacks and downloaded his recovery files, stupidly I didnt notice it was 4G specific (crespo4g), just that it was for ICS and JB. The recovery seemed to work ok, had the new touchscreen version, but then I tried to install a stock GB ROM from my SD card. At the end it seemed stuck on writing radio. Wasnt doing anything so assumed it was ok to reboot. When it rebooted every process was failing so I tried to do the fastboot flash recovery again and the phone just wouldnt respond.
Tht's where I am at now.
Saw another thread and got directed to the link above to flash the radio.
Did that, used the UCKF1 radio, no problems installed fine but the phone still won't respond to fastboot flash recovery using recovery-clockwork-3.0.2.4-crespo.
Can anyone point me in the right direction PRETTY PLEASE! I'm not a techie guy and its my only phone :crying:
You did a lot wrong here. NEVER DO SOMETHING UNTIL YOU HAVE COMPLETE KNOWLEDGE OF IT
Also you flashed the wrong radio. I would suggest you to stop as where you are right now.
You need to go complete stock first, by flashing the factory image.
I got a p500h from my friend since my razr droid died and I needed something to hold me over until I can save up for the note3. It had 2.2 on it so I flashed CM 10.1 for 4.2.2. When I put my sim card in I had no service.
I checked the baseband and it was unknown so I flashed it for v.20 and it appeared but I still get no service.
I don't have gapps installed because I don't really need it.
And that's pretty much it. I can't think of anything else to try, can someone help? I'm using a non-smart phone in the meantime and it is quite terrible.
Try the old Baseband fix, that did it for me some years ago, not sure if you need the v10 baseband coming from 2.2 but the fix should work. You can find it here on the Forum.
If nothing works, use kdz to flash the Stock Rom and start over.
Bartlebyxxx said:
Try the old Baseband fix, that did it for me some years ago, not sure if you need the v10 baseband coming from 2.2 but the fix should work. You can find it here on the Forum.
If nothing works, use kdz to flash the Stock Rom and start over.
Click to expand...
Click to collapse
Thanks, I wanted to try that but when I go to download the milk_os fix at the bottom of this page
http://forum.xda-developers.com/showpost.php?p=14743798&postcount=2
I get redirected to some bull****(lp.downloadsetup.net)
And I just don't trust this thing, is this really what I'm suppose to download?
Is definitely the fault of baseband. Some rom is incompatible with any type of baseband. Try to download from play store an application with baseband-ril match...
Toxic_Ninja said:
I got a p500h from my friend since my razr droid died and I needed something to hold me over until I can save up for the note3. It had 2.2 on it so I flashed CM 10.1 for 4.2.2. When I put my sim card in I had no service.
I checked the baseband and it was unknown so I flashed it for v.20 and it appeared but I still get no service.
I don't have gapps installed because I don't really need it.
And that's pretty much it. I can't think of anything else to try, can someone help? I'm using a non-smart phone in the meantime and it is quite terrible.
Click to expand...
Click to collapse
Sounds like you have an old baseband phone, but you flashed a new baseband ROM on it. In that case, simply flash the zip indicated below (I suggest you mount /system in recovery before flashing, even though the script auto-mounts /system, just to be sure). I'm attaching two zips for the sake of completeness; the one you want is the Use_New_BB_ROMS.zip.
Use_New_BB_ROMS.zip -- Flash this zip if you're trying to use a new baseband ROM on a phone that uses the old baseband. If you have no network on 2.3 and above ROMS, your phone probably uses the old baseband, so this is the zip you need.
Use_Old_BB_ROMS.zip -- Flash this zip if you're trying to use an old baseband ROM on a phone that uses the new baseband. If you have no network on 2.2 and below ROMS, your phone probably uses the new baseband, so this is the zip you need.
Syd_M said:
Sounds like you have an old baseband phone, but you flashed a new baseband ROM on it. In that case, simply flash the zip indicated below (I suggest you mount /system in recovery before flashing, even though the script auto-mounts /system, just to be sure). I'm attaching two zips for the sake of completeness; the one you want is the Use_New_BB_ROMS.zip.
Use_New_BB_ROMS.zip -- Flash this zip if you're trying to use a new baseband ROM on a phone that uses the old baseband. If you have no network on 2.3 and above ROMS, your phone probably uses the old baseband, so this is the zip you need.
Use_Old_BB_ROMS.zip -- Flash this zip if you're trying to use an old baseband ROM on a phone that uses the new baseband. If you have no network on 2.2 and below ROMS, your phone probably uses the new baseband, so this is the zip you need.
Click to expand...
Click to collapse
I tried to flash it but I get an error: can't copy META-INF/com/google/android/updated-binary
Should I be wiping cache for this? Dalvik cache?
I used LGMDP-v1.5 to get bb v.20 on my phone in the first place, I tried to do the same with v.10 after v.20 didn't work but it just went back to baseband unknown. when I tried to download the milk_os fix it just linked me to some phishing page.
What recovery are you using? I've tried with AmonRa & CWM 5.0.2.0 and both work. Other CWM versions will probably work, too. Haven't tried with TWRP.
If this flashed successfully but you still don't have service, then you might have borked something when changing baseband in KDZ. If that's the case, then hopefully others will be able to help you as I've never touched KDZ myself.
____________________
Sent from the moon.
Toxic_Ninja said:
I got a p500h from my friend since my razr droid died and I needed something to hold me over until I can save up for the note3. It had 2.2 on it so I flashed CM 10.1 for 4.2.2. When I put my sim card in I had no service.
I checked the baseband and it was unknown so I flashed it for v.20 and it appeared but I still get no service.
I don't have gapps installed because I don't really need it.
And that's pretty much it. I can't think of anything else to try, can someone help? I'm using a non-smart phone in the meantime and it is quite terrible.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2616412 <-- go here..i prefer you to use twrp.. hit thanks if i helped.
Syd_M said:
What recovery are you using? I've tried with AmonRa & CWM 5.0.2.0 and both work. Other CWM versions will probably work, too. Haven't tried with TWRP.
If this flashed successfully but you still don't have service, then you might have borked something when changing baseband in KDZ. If that's the case, then hopefully others will be able to help you as I've never touched KDZ myself.
Click to expand...
Click to collapse
I was using CWM 5.0.2.0, and I've never touched KDZ.
voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2616412 <-- go here..i prefer you to use twrp.. hit thanks if i helped.
Click to expand...
Click to collapse
I tried it, here's what happened.
First I just flashed it, I checked the baseband, it was unknown. Previously it was v.20 so I tried flashing in v.10 since this was a fix for v.10 AFAIK
Still unknown.
Tried flashing the fix again just to overwrite whatever it needed to overwrite and still unknown.
I'm back to square 1 on this one.
Toxic_Ninja said:
I was using CWM 5.0.2.0, and I've never touched KDZ.
I tried it, here's what happened.
First I just flashed it, I checked the baseband, it was unknown. Previously it was v.20 so I tried flashing in v.10 since this was a fix for v.10 AFAIK
Still unknown.
Tried flashing the fix again just to overwrite whatever it needed to overwrite and still unknown.
I'm back to square 1 on this one.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2559363 dude i think you did something which is not good.. i require you to restore ur stock rom with the link i gave.. or if ur affraid of kdz use odin.
if ur back with the stock rom never upgrade your baseband again..when u flash a custom rom with new baseband needed just simply flash the baseband fix i gave you..
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
Toxic_Ninja said:
I was using CWM 5.0.2.0, and I've never touched KDZ.
I tried it, here's what happened.
First I just flashed it, I checked the baseband, it was unknown. Previously it was v.20 so I tried flashing in v.10 since this was a fix for v.10 AFAIK
Still unknown.
Tried flashing the fix again just to overwrite whatever it needed to overwrite and still unknown.
I'm back to square 1 on this one.
Click to expand...
Click to collapse
dude i think you did something which is not good.. i require you to restore ur stock rom with the link i gave.. or if ur affraid of kdz use odin.
if ur back with the stock rom never upgrade your baseband again..when u flash a custom rom with new baseband needed just simply flash the baseband fix i gave you..
forum.xda-developers.com/showthread.php?t=2559363