Very strange issue.
I cannot upgrade my ROM above 2.3.3 and I can't upgrade the Recovery Image to anything new as well.
Does not matter if Official ROM or Not.
I am grabbing the Official ROMs from here:
http://forum.xda-developers.com/showthread.php?t=1445570
I am currently with Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader
and If I try to install, 2.3.4, 2.3.6, or 4.03 the phone wont get past the "Google Logo" right from the beginning of boot. The screen will go Blank and the 4 soft keys will light up.
Before installing each ROM I am formatting/wiping cache, data, system & dalvik.
And Each ROM installation will claim that it installed successfully.
Recovery: So I am able to install ClockWork Recovery 3.0.2.4 and have it work.
I install the latest Clockwork ver. 5.0.2.0 it will install successfully, but not work.
And stop right after the Google Logo, as with ROM.
I have been at this for 2 days now. Any help would be AMAZING!!!
One last note: The phone was dropped, so maybe some how related, but I don't see how. The phone just came back from store that replaced the LCD. They claimed it was in a Recovery Loop. So I asked them to put CynogenMod. However they strangely put CynogenMod v 2.3.1 and not rooted.
are you flashing the right cwm recovery 5.x.x.x for your phone(amoled vs lcd)? try twrp recovery. do you wipe data(factory reset)before flashing? you should.
to Start, Thank you for the reply. Its very much appreciated.
So Yes, I am performing a full factory reset before flashing. And all of my most recent trials I used the native factory recovery that comes with each of the ROM's.
And I tried all of the below listed ROMs with the issue as described abouve.
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 4.0.3/IML74K/XXKI1 Radio/KL1 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
And regards to the Custom Recovery(cwm) issue, I used what on the CynogenMod Wiki:
wiki(dot)cyanogenmod(dot)com/wiki/Nexus_S:_Full_Update_Guide
They don't have any differenciation between the OMOLED or Super LCD Versions:
(OMOLED I9020T, I9020A)
(Super LCD I9023)
Is there in fact different Recovery's for each of the abouve listed models????
Where would I find those recoverys?
And thank you again for your time.
Help - anyone? - Please :-(
vringo said:
Help - anyone? - Please :-(
Click to expand...
Click to collapse
try using twrp recovery, i find it more useful than clockwork recovery http://teamw.in/project/twrp2
---------- Post added at 04:26 PM ---------- Previous post was at 04:18 PM ----------
if you want to flash the official 4.0.3, then you need to flash the official 2.3.6 first. if youre flashing a custom 4.0.3, like cm9, then you dont need 2.3.6.
Thank you for the TWRP recovery suggestion.
But still stuck without being able to flash anything above 2.3.3
Should I be able to flash official 2.3.6 on top of 2.3.3(after factory reset)?
vringo said:
Thank you for the TWRP recovery suggestion.
But still stuck without being able to flash anything above 2.3.3
Should I be able to flash official 2.3.6 on top of 2.3.3(after factory reset)?
Click to expand...
Click to collapse
you should be able to. try a custom rom instead of an official. lots of aosp builds in the development section. they are pretty much pure android with a few mods. theres a pure aosp build in the development section too, its pure android 4.0.3 without mods. your bootloader is unlocked, right?
Yes, bootloader is unlocked.
will give some of the aosp builds a try now
vringo said:
Yes, bootloader is unlocked.
will give some of the aosp builds a try now
Click to expand...
Click to collapse
good luck
This phone is messed up. while I was in 2.3.3, the whites began to turn purple, flickering. Ugh :-(
TWRP recover, no go
I just tried codename_aosp+_crespo-ota-eng.V3.0.2, also no go
I'm beginning to suspect its a hardware issue, or maybe something else it just messed up?
perhaps flashed a wrong component somewhere???
Is it possible to reformat all internal flash drives and reparation and truly start from scratch? with all aspects of this device?
(like on a pc, low level format the hard disk and start all over....)
vringo said:
This phone is messed up. while I was in 2.3.3, the whites began to turn purple, flickering. Ugh :-(
TWRP recover, no go
I just tried codename_aosp+_crespo-ota-eng.V3.0.2, also no go
I'm beginning to suspect its a hardware issue, or maybe something else it just messed up?
perhaps flashed a wrong component somewhere???
Is it possible to reformat all internal flash drives and reparation and truly start from scratch? with all aspects of this device?
(like on a pc, low level format the hard disk and start all over....)
Click to expand...
Click to collapse
One more thing, anyway to know if the store that fixed my phone installed the wrong screen? LCD vs OMOLED?
clarification of the "issue" if ROM not working.
- Working phone (with 2.3.3) boot description:
You see Google Logo, and then the Logo will flicker momentarily, and Google Logo some more, and then the flying colored NEXUS logo animation, etc...
- Non functioning ROM boot description: You see the Google Logo, and then at about the time you would see the Google Logo flicker, that is when the screen goes black, and all 4 soft-keys light up. if you push the power button, sometimes the soft-keys will go black, and if you push again, light up again. At this point I have to pull the battery....
Same issue if I try to load the stock recovery from a non-functioning ROM. so Fastboot Mode will work, and then select Recovery, Google logo and then Black, with 4 lit softkeys, where the logo would normally flicker.
Why can't I install the stock firmware above 2.3.3????
I just tried the update ROM from 2.3.3 to 2.3.4 or 2.3.3 to 2.3.6 (all GRI40)
What could cause this issue????
could it be a partioning issue? what would cause such a weird issue?
Related
Hello all,
Today I attempted to install android 4.0.3 ICS unofficially on my beloved AT&T Nexus S i9020A. I did this by unlocking my bootloader, then flashing clockwordkmod 3.0.0.0. crespo img, then flashing the stock i9020t (t-mobile) ics rom, planning to later flash the AT&T radios and get the update that way. This all failed however, because upon rebooting, my phone was stuck at the boot screen that says "google", and shows the unlocked lock, symbolizing the unlocked bootloader. I waited 15 minutes, and it would not go past this screen. I took out the battery and tried again, and still no luck. I then went back to the boot loader and into clockworkmod recovery (which still boots), and tried to install the stock i9020a 2.3.6. The install fails every time. It says there is no "cache" partition on my phone. I installed cyanogenmod 7 and it says the installation succeeded, but i still cannot boot past the google screen. I can only access the unlocked bootloader screen and clockwordmod. I have included screenshots of what happens in clockworkmod when I boot it up, or try to install a rom. Any help would really be very much appreciated. I am very sad to lose my beloved $529 phone, which has served me very well.
This is the guide I used to flash ICS:
http://dottech.org/mobile/android/25324/how-to-update-nexus-s-to-ice-cream-sandwich-android-4-x/
This is the guide I used to unlock my boot loader and flash clockwordmod:
http://forum.xda-developers.com/showthread.php?t=878446
you need a newer version of clockwork recovery, that one is old and wont work with ics. or you can try twrp recovery, i prefer it personally. i believe clockwork recovery is up to 5.0.2.X
Thank you so much! How would I flash a new version if I can't boot into any OS?
..
Ok. I've installed clockworkmod recovery touch (I believe it is the latest one) and was able to revert to cyanogenmod 7. THANK YOU SO MUCH!!! I really cannot thank you enough! You have saved my nexus!!!
monoloco1 said:
Ok. I've installed clockworkmod recovery touch (I believe it is the latest one) and was able to revert to cyanogenmod 7. THANK YOU SO MUCH!!! I really cannot thank you enough! You have saved my nexus!!!
Click to expand...
Click to collapse
no thanks needed, your excitement is enough
I brought a transformer tf300 a few days ago that was already rooted and unlocked. I can't get adobe flash to work. I tried side loading a few version of adobe but still no success. Google market says my device is not compatible with adobe. I don't think the rooted device really serves me any purpose so I would like to take it back to factory condition. I need some help doing it since I have never rooted a device before.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
Thanks for all your help if you can. I will need step by step instructions, and thanks again for the help
jflynn0 said:
I brought a transformer tf300 a few days ago that was already rooted and unlocked. I can't get adobe flash to work. I tried side loading a few version of adobe but still no success. Google market says my device is not compatible with adobe. I don't think the rooted device really serves me any purpose so I would like to take it back to factory condition. I need some help doing it since I have never rooted a device before.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
Thanks for all your help if you can. I will need step by step instructions, and thanks again for the help
Click to expand...
Click to collapse
download the latest firmware from the asus site first. http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Then install the current software version. You can use the instructions from here to reflash stock rom in post 2
http://forum.xda-developers.com/showthread.php?t=1668173
dxwilliams40 said:
download the latest firmware from the asus site first. http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Then install the current software version. You can use the instructions from here to reflash stock rom in post 2
http://forum.xda-developers.com/showthread.php?t=1668173
Click to expand...
Click to collapse
don't know what im doing wrong when i try to flash the stock rom i get stuck as the ASUS splash screen with spinning wheel. Any suggestions?!?
cjohnsonthe2nd said:
don't know what im doing wrong when i try to flash the stock rom i get stuck as the ASUS splash screen with spinning wheel. Any suggestions?!?
Click to expand...
Click to collapse
Did you unzip the firmware and flash the zip named "US_epad-user-9.4.3.29"?
dxwilliams40 said:
Did you unzip the firmware and flash the zip named "US_epad-user-9.4.3.29"?
Click to expand...
Click to collapse
yes and CWM says install from sd card complete, no errors. I get the intial boot screen with the blue progress bar then I get stuck at the spash screen with the spinning wheel.
Luckily I had a nandroid of my AOKP setup and can go back to that. Ive tried a few times today to return to stock with the same results.
cjohnsonthe2nd said:
yes and CWM says install from sd card complete, no errors. I get the intial boot screen with the blue progress bar then I get stuck at the spash screen with the spinning wheel.
Luckily I had a nandroid of my AOKP setup and can go back to that. Ive tried a few times today to return to stock with the same results.
Click to expand...
Click to collapse
Remember to full wipe before installation including /system and after clear dalvik and cache then fix permissions.
By not wiping /system can cause some data to be left and corrupt stock installation had this happen on my g2x and have seen it on some other threads.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
I wiped the cache before I started the install and now when I boot into the usb fastboot my comp flashed a bootloader notification but then nothing else happens. I tried it a second time and I dont even get the notification. Also if I let it boot regular the Asus screen shows when i first boot but then nothing ever comes up just black screen
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
Hi guys,
I had the Darkroom V3 ROM installed (TWRP Bootloader) and since I want to sell my phone I clicked on "reset phone" in the Android settings. After the process it restarded but never booted into the system anymore, instead, everytime TWRP boots (strangely, in this mode the menu and the back button (or home and search, forgot) glow).
I already did a clean reinstall of Darkroom's ROM, but it changed nothing.
Is this the infamous "boot loop"? I have no idea what's going wrong, please help!
giga111 said:
Hi guys,
I had the Darkroom V3 ROM installed (TWRP Bootloader) and since I want to sell my phone I clicked on "reset phone" in the Android settings. After the process it restarded but never booted into the system anymore, instead, everytime TWRP boots (strangely, in this mode the menu and the back button (or home and search, forgot) glow).
I already did a clean reinstall of Darkroom's ROM, but it changed nothing.
Is this the infamous "boot loop"? I have no idea what I can do, pleas help!
Click to expand...
Click to collapse
This setting is set by default : booting into recovery. You will notice that too in the cyanogenmod builds.
You can reset the phone by flashing a stock firmware.
I hope "stock" means, I could flash the official Android 4 Version or would I have to flash the "truly original" Gingerbread? oO
giga111 said:
I hope "stock" means, I could flash the official Android 4 Version or would I have to flash the "truly original" Gingerbread? oO
Click to expand...
Click to collapse
There are both official gingerbread and ics firmwares.
Okay thank you, I'll try the official ICS ROM then.
Reflashing the normal Android 4 worked, then flashed Darkroom's ROM, now got "Security Error". I read this comes from flashing a custom kernel on the stock bootloader. But TWRP is my bootload, isn't it?! So much trouble before selling the phone...
/EDIT:
I reflashed u-boot and all and now it works again, for whatever reason the loader was replaces...
But no worries, I have another problem: Since I messed up with my phone the menu-button doesn't glow anymore. Does there come anything to your mind about that?
giga111 said:
Reflashing the normal Android 4 worked, then flashed Darkroom's ROM, now got "Security Error". I read this comes from flashing a custom kernel on the stock bootloader. But TWRP is my bootload, isn't it?! So much trouble before selling the phone...
/EDIT:
I reflashed u-boot and all and now it works again, for whatever reason the loader was replaces...
But no worries, I have another problem: Since I messed up with my phone the menu-button doesn't glow anymore. Does there come anything to your mind about that?
Click to expand...
Click to collapse
Which model of Optimus 3D you have? Do you have 3 or 4 menu buttons?
p-vlad said:
Which model of Optimus 3D you have? Do you have 3 or 4 menu buttons?
Click to expand...
Click to collapse
I have 4 buttons.
giga111 said:
I have 4 buttons.
Click to expand...
Click to collapse
what about
system settings -> display -> front key light
This option doesnt affect this one malfunctioning button in lighting concerns. Also, when I had freshly flashed my phone again and the soft keys were flashing for a short time, the dark button was missing. I mean it remained dark.
giga111 said:
Reflashing the normal Android 4 worked, then flashed Darkroom's ROM, now got "Security Error". I read this comes from flashing a custom kernel on the stock bootloader. But TWRP is my bootload, isn't it?! So much trouble before selling the phone...
/EDIT:
I reflashed u-boot and all and now it works again, for whatever reason the loader was replaces...
But no worries, I have another problem: Since I messed up with my phone the menu-button doesn't glow anymore. Does there come anything to your mind about that?
Click to expand...
Click to collapse
Nobody explained to you that TWRP is custom recovery NOT BOOTLOADER.
Bootloader is something else and here, in your case, you had official locked bootloader so you got a warning massage after you flashed the custom rom.
If you want to flash custom roms and kernels, you MUST flash wkpark's v1.25 bootloaders(custom unlocked bootloaders).
Sent from my LG-P920 using xda app-developers app
Yeah I forgot about that u-loader and all, but I had flashed this before. For some reason it must have been replaced when I messed everything up by trying to reset the phone in the Adnroid settings.
Or does xball's official Android 4 include the stock bootloader? I can't remember I flashed the bootloader again when I switched to the official Android 4 (I had the SU760 before).