Database Info

[Q] In need of aid :(

Hi
Bourght a nexus s a few days ago. Today i tried to root the phone using a guide from youtube, if you search for "root nexus s" and look for the user named "Zedomax", thats the one i tried to follow.
First i unlocked it.
next thing was to:
fastboot flash boot recovery clockwork.img (shortend the name to help my self)
last thing:
fastboot flash boot rootboot.img
After this was done my phone is unable to reboot again, it just stops at a google logo with a lock under it. And at that point im unable to do anything. Only thing that works is removing the battery. Think i have killed it
Any ideas to what i could do? is it possible for me to save it yet?
best regards,
Fonain

try to use the pc software to repair it or to reinstall android.. there is no problem..

pc software? could you please tell me what software are you talking about, maybe a link to where i can download it? And do you by chance know how to reinstall android?
any help is highly appreciated
Best regards,
fonain
edit: at work atm, so might not be able to answer right away

Odin.
http://forum.xda-developers.com/showthread.php?t=94795
I have yet to use it on my NS but i used it regularly on my vibrant. You will need to get into download mode for it to work.

your link doesnt work

does anyone know where i can find the original files for nexus s so i can use em in fastboot and make my phone work again?

fonain said:
does anyone know where i can find the original files for nexus s so i can use em in fastboot and make my phone work again?
Click to expand...
Click to collapse
which phone model do you have?
i9020 or i9023 ?

Bootloader version is I9020XXKA3
Baseband version is I9020XXKB1
dunno if those version names have been changed while i have been tampering with my phone, if not its the I9020

that looks good
if it's really a 9020 then you can use the unlocking + rooting guide for the 9020 in the general section
once you get CWR installed, you can flash to any ROM you like

Thanks ill try look deeper into that, and see if that will solve my problem.
but it is already unlocked and partly rooted...i think.
have used a clockwork img and rootboot img, and after that my phone couldnt start up again.

fonain said:
Thanks ill try look deeper into that, and see if that will solve my problem.
but it is already unlocked and partly rooted...i think.
have used a clockwork img and rootboot img, and after that my phone couldnt start up again.
Click to expand...
Click to collapse
those files are wrong use the mirror recovery image on the i9020 rooting topic in general http://forum.xda-developers.com/showthread.php?t=895545

Think i should have used that guide instead of the one i have been using the first time... looks great step by step!
But....
i still have the problem where my phone just stops loading.
1: unlocked it
2: typed: fastboot flash recovery recovery.img
3: finished at 1.132 sec (no problems so far)
4: reboot my phone, then it stops.
and it stop when showing this screen.
http://i53.tinypic.com/m74byg.jpg with a lock at the bottom which is unlocked.
And it just stops there, waited for several minutes as i have seen that the startup could take up to 2 mins after tampering with the nexus s.
get to the point in the guide where it tells you to download superuser.
Hope you can see if i have done something wrong
best regards,
Fonain
EDIT: oh yes, forgot to mention that the 2 touch buttons to the left on my SNS lights up. First one glowes for a sec or two, then it turns off again. The second stays on all the time.

repeat the fastboot flash recovery recovery.img one more time
after that is done, boot into the CW Recovery
you know hold up and power
then select mount USB
then copy over a stock nandroid backup for 2.3.3 rooted
after that unmount the usb
and select the option to restore rom from backup
and choose the folder that you unzipped into your mounted SD

3 words...
you are awesome!
thanks alot!!
Best regards,
Fonain

[Q] In a Bit of a Predicament with Nexus S 4G; is it possible to fix?

So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.

Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|

polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.

Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.

polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.

Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.

[GUIDE Win/Linux/Mac] Debrick 4.3 with Odin or Verizon Utility + PIT [SOFT BRICK]

THIS WILL WORK ONLY IF YOU CAN GET INTO DOWNLOAD MODE (Odin mode) if you bricked your bootloader try HERE
Who can benefit from this?
Anyone who took the OTA to 4.3 then tried to downgrade resulting in a soft brick
Anyone who took the OTA to 4.3 and somehow lost there recovery or follow restoring stock recovery instructions HERE
Anyone who took the OTA to 4.3 but failed with access to download mode
Anyone who wants 4.3 but for some reason can not OTA
Anyone who took the NC1 update (new 4.3) and wants to revert to ML1 (old 4.3 with saferoot and safestrap support)
Linux and Mac users must follow the Odin method using the correct PIT file (found at the bottom of the op) and substitue Odin with Jodin3 found HERE and spam AdamOutler thanks button for making Jodin3
WARNING! UPDATING TO 4.3 WILL RESULT IN A LOCKED BOOTLOADER FOREVER!!
4.3 with Odin
How to enter Download Mode
Make sure your device is completely off
Hold Volume Down + Home
While holding both of them simultaneously press the Power button until you see the disclaimer on the screen
Then let go of all the buttons and press Volume Up
=====================================================================================
Download and extract Odin <--- New link 1/23/14
Download and extract ALL_I535VRUCML1_I535VZWCML1_2198062_REV09_user_low_ship.tar.md5.7z (official old 4.3 tar ball) or ALL_I535VRUCNC1_I535VZWCNC1_2198062_REV09_user_low_ship.tar.md5.7z (official new 4.3 tar ball)
Download kies and install as administrator. make sure the [Unified Driver Installer] check box is checked at the end of the install (Might take some time)
Windows Kies Here
Mac Kies Here
Enter Download Mode
Make sure Kies is closed then plug in your phone and wait for drivers to install
Open Odin As administrator
You should see your phone under ID:COM (you should also see it has been added in message)
Make sure only Auto Reboot and F. Reset Time is checked
Check PDA [ ]
Click on [PDA] And select the .tar file you just extracted (Only use PDA Never use the others)
Wait for it to verify the MD5 then click [Start]
From here on out its all automated Odin will Flash SCH-I535_I535VRUCML1 then restart (dont forget first boot takes time)
If you get stuck in a boot loop go into recovery and do a factory reset (probably should regardless)
4.3 With Verizon Utility [will always push the most recent firmware atm 4.4.2 and you will not be able to go back to 4.3] (Windows only for now)
How to enter Download Mode
Make sure your device is completely off
Hold Volume Down + Home
While holding both of them simultaneously press the Power button until you see the disclaimer on the screen
Then let go of all the buttons and press Volume Up
=====================================================================================
Download and unzip
Windows SUA_ar.zip <--- New Link
Mac SUA_ar.zip
Open SUA_ar folder
Install SUABnRSetup as administrator (might take some time and may not be nessesary)
Download kies and install as administrator. make sure the [Unified Driver Installer] check box is checked at the end of the install (Might take some time)
Windows Kies Here
Mac Kies Here
Make sure Kies is closed then go into download mode and plug into your pc (hold here until drivers install)
Run SUA.exe as administrator
Click on [Repair Assistant] (on the left)
Click on run [Repair Assistant] (on the bottom)
After repair assistant recognizes your phone click [Repair Galaxy S(R) III] (on the right side)
It will say "Due to the condition of your phone/tablet, all data will need to be erased during the repair."
Click [continue]
From here on out its all automated it will download and install SCH-I535_I535VRUCML1 then restart (dont forget first boot takes time)
If you get stuck at 84% try THIS
If you get stuck in a boot loop go into recovery and do a factory reset (probably should regardless)
If you keep failing it might be because you have bad partitions. Download the pit file that matches your phone (16gb S3 use the 16gb pit file or 32gb S3 use the 32gb pit file) Follow the Odin instructions with the addition of your pit file By clicking [PIT] in Odin. Or try this fix Here
SCH-I535_D2VZW_16gb.pit
====================
SCH-I535_D2VZW_32gb.pit
As long as things went smooth you should be back on 4.3 ready to take on the world!
Want root on 4.3? Use saferoot (ML1) HERE or towelroot (ML1/NC1) HERE Remember you are on a locked bootloader. You can not flash insecure bootloader, roms or custom recovery.

awesome. I had given up and was just waiting for the 4.3 tar
I'm really hoping this works since you had the exact same symptoms as me
Thanks in advance!

kangeon said:
awesome. I had given up and was just waiting for the 4.3 tar
I'm really hoping this works since you had the exact same symptoms as me
Thanks in advance!
Click to expand...
Click to collapse
I was waiting as well, But I was about to chuck my Droid x against a wall. Another funny thing is right before I tried this my phone got sudden death syndrome (power button stayed compressed so every time battery is put in it automatically tuns on then off ). Luckily slamming my phone against the table wasn't a internet troll and it got fixed.

ThePagel said:
I was waiting as well, But I was about to chuck my Droid x against a wall. Another funny thing is right before I tried this my phone got sudden death syndrome (power button stayed compressed so every time battery is put in it automatically tuns on then off ). Luckily slamming my phone against the table wasn't a internet troll and it got fixed.
Click to expand...
Click to collapse
Bro I hate my Droid X. I sent my phone out today to have it JTAG to 4.3 and hours later this came out LOL. Good job bro!!!!:good:

I got it working
Thanks so much!

You are a life saver. Thank you!

Good to see that some folks can resurrect their device now. A locked but working phone is certainly better than no phone at all.
Awesome work ThePagel!
Sent from my SCH-I535 using Tapatalk

I signed up just to say thank you. I decided to go for broke and take my phone into Verizon just to see what they said and they suggested I upgrade to a new phone. I'm sure they could have performed this for me, but I'm glad I did it myself. Once again, thank you.

Couple things, when you redo the OP could you make sure to detail what scenario would lead you to using this tool? Maybe make that a little clearer.
Also, we don't have a bootloader to boot directly into like say HTC devices. Samsung let's you boot into recovery or download mode. Download Mode may be an equivalent term to "bootloader" for other devices but it may be confusing to new S3 users down the road. Cheers!
Sent from my SCH-I535 using Tapatalk 4

@ThePagel I PMd you. I will go ahead and post a mirror for the SUA_ar.zip here. You can move this link to the OP. Once everyone wakes up they are gonna shut down your dropbox for excessive traffic.
http://www.androidfilehost.com/?fid=23269279319199403

Would this work on a phone that wasn't bricked but you wanted to just restore it to pristine stock 4.3? (a sort of "oh crap, I accidentally deleted a bunch of system APKs - how do I get those back?!" moment)

s'pht said:
Would this work on a phone that wasn't bricked but you wanted to just restore it to pristine stock 4.3? (a sort of "oh crap, I accidentally deleted a bunch of system APKs - how do I get those back?!" moment)
Click to expand...
Click to collapse
Kies should handle that. Not sure but as never used Kies but you should not need that other file. Just repair in Kies.

Will this repair a broken recovery also? After I took the OTA I rooted then tried to install a custom recovery. Now when I boot to recovery I get the error "SECURE FAIL: KERNAL" as well as the yellow triangle. The phone does work and I can get into download mode, I just want my recovery back so I can do a factor data reset if needed.

harrst1 said:
Will this repair a broken recovery also? After I took the OTA I rooted then tried to install a custom recovery. Now when I boot to recovery I get the error "SECURE FAIL: KERNAL" as well as the yellow triangle. The phone does work and I can get into download mode, I just want my recovery back so I can do a factor data reset if needed.
Click to expand...
Click to collapse
It seems this method will restore the phone to the factory state thus should repair your recovery also.

SlimSnoopOS said:
Couple things, when you redo the OP could you make sure to detail what scenario would lead you to using this tool? Maybe make that a little clearer.
Also, we don't have a bootloader to boot directly into like say HTC devices. Samsung let's you boot into recovery or download mode. Download Mode may be an equivalent term to "bootloader" for other devices but it may be confusing to new S3 users down the road. Cheers!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I think I can manage that
prdog1 said:
@ThePagel I PMd you. I will go ahead and post a mirror for the SUA_ar.zip here. You can move this link to the OP. Once everyone wakes up they are gonna shut down your dropbox for excessive traffic.
http://www.androidfilehost.com/?fid=23269279319199403
Click to expand...
Click to collapse
Thankyou!
s'pht said:
Would this work on a phone that wasn't bricked but you wanted to just restore it to pristine stock 4.3? (a sort of "oh crap, I accidentally deleted a bunch of system APKs - how do I get those back?!"
Click to expand...
Click to collapse
Yes
prdog1 said:
Kies should handle that. Not sure but as never used Kies but you should not need that other file. Just repair in Kies.
Click to expand...
Click to collapse
Because he is on 4.3 kies is no help. Its still giving us 4.1.2
harrst1 said:
Will this repair a broken recovery also? After I took the OTA I rooted then tried to install a custom recovery. Now when I boot to recovery I get the error "SECURE FAIL: KERNAL" as well as the yellow triangle. The phone does work and I can get into download mode, I just want my recovery back so I can do a factor data reset if needed.
Click to expand...
Click to collapse
Yes this will work just remember you run the risk of a hard brick if things go wrong

ThePagel said:
I think I can manage that
Thankyou!
Yes
Because he is on 4.3 kies is no help. Its still giving us 4.1.2
Yes this will work just remember you run the risk of a hard brick if things go wrong
Click to expand...
Click to collapse
Ok. I see now. You are just using the drivers from Kies.

Interesting...even after going through this procedure I still get the Samsung "Custom Lock" screen.
Thanks for this btw!!

eudoxia said:
Interesting...even after going through this procedure I still get the Samsung "Custom Lock" screen.
Thanks for this btw!!
Click to expand...
Click to collapse
A lot of original S3s came with that lock. Don't know if we ever figured out why.

eudoxia said:
Interesting...even after going through this procedure I still get the Samsung "Custom Lock" screen.
Thanks for this btw!!
Click to expand...
Click to collapse
prdog1 said:
A lot of original S3s came with that lock. Don't know if we ever figured out why.
Click to expand...
Click to collapse
That is weird. Mine did not ship with custom but after the brick it did have it, then after the unbrick it was gone. Is your warranty in download mode 0 or 1?

prdog1 said:
A lot of original S3s came with that lock. Don't know if we ever figured out why.
Click to expand...
Click to collapse
I stand corrected, after pulling the battery for a minute and rebooting the "Custom Lock" screen is gone..
Thanks ...You Rule :good:

[Q] Help with KitKat + CWM 6.0.4.6

Hi!
My P500 was originally Gingerbread 2.3.3, than I used CM 7.2 with AmonRa 3.0.6 recovery for a year.
So I tried to flash KitKat (http://forum.xda-developers.com/showthread.php?t=2589303), and got some issues.
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Whatever I choose, I got that black screen with
"fastboot mode started
udc_start()".
Thaaaan, I see this: http://forum.xda-developers.com/showthread.php?t=2439466
and tried to downgrade SU to v1.55. But the CWM got an error, and cannot install (even with AmonRa)...
After all, I can't get KitKat working, and got back to AmonRa recovery and CM 7.2.
To complete the "good vibe", my Android can't get AT ALL connect through USB, so I can't test any ADB command.
I don't know where I'm doing wrong... Any directions??
Thanks!!!!

SOS
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.

LonerPrime said:
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
Click to expand...
Click to collapse
The way back home without buggy LG Mobile anything: Remove and replace batter, press home, volume-down and power keys simultaneously. Can be a bit tricky but will get you back in recovery. I assume you did that backup before playing. Restore it to get the phone back up.
Two ways to get your Kitkat:
1. Using the Version-8 install, do a clean install and be sure to choose an item in the various menu panes. Should work with this and then you need to reinstall and setup everything.
2. Take the "nightly" and install normally doing the requesite steps in the backup.

Thank you, but– Nvm fixed it.
@Dovidhalevi
Thank you for your amazing advice. I was able to get into recovery and restore from my nandroid backup. *Thank god I did that*
But kittkat ROM is still being a pain. I decided to read the logs of version 8 of the ROM a bit more closely and found this:
Upgrading from CM-10.2 or older / Fresh (First time) Installation: Now DON'T WIPE ANYTHING (Data/Factory reset, Wipe Cache partition, Dalvik Cache, Format System) everything have built in Aroma Installer. Simply flash through sdcard or adb sideload, Follow the Aroma Menu. Finish and Reboot device. Avoid Facebook, Whatsapp, Viber, Hangout apps while selecting apps to be flash, it may gives you fastboot mode. Done!!!
I decided to try my luck once more and disabled all those apps during the installation. But just before rebooting my phone lost root access again and asked if I wanted to fix it or not and then it froze again on LG logo afterwards. Another force restart and it went straight into fastboot mode. Had to do another restore to get my phone working on the older backup.
Now I know it isn't the CWD cause I am running that with my older Cynogen 7.2 OS and its rebooting without a hitch unlike kittkat which mysteriously loses root access...
I really apologize if I am being a bit noobish. Even though hardware/networking/linux[Red Hat] is like playing in my backyard, android itself is a new concept to me, hence I really appreciate all the help I can get on this to work.
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime

I'll try
LonerPrime said:
@Dovidhalevi
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
Click to expand...
Click to collapse
Glad you fixed your phone!! I forgot to say what I did to "fix" it...
Read error... maybe???
I'll try as soon as I get home, with results!! Thanks!!!

I did that... =/
yes.. i was doing right. All the 6 times I tried...
And tried again now, just to be sure, and FASTBOOT again.
=/

jpesci said:
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Click to expand...
Click to collapse
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.

It's fixed, but no Kitkat...
shinobisoft said:
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
Click to expand...
Click to collapse
Oh, sorry. Maybe bad explanation. I did get it fixed. All the "x" times, heheh =)
I just got in recovery by pressing home+vol up+power, and flashed back my older ROM. Now I'm trying CM 10 by Jenkins.
The problem isn't the "fastboot" message itself... but don't get Kitkat working =/
But thanks for the reply anyway!

kitkat by mukulsoni... ui stops with multiple popupd
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..

amit2411 said:
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
Click to expand...
Click to collapse
Boot in to your recovery and try wiping your cache and dalvik cache.

still no working
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".

jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes. ​

shinobisoft said:
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes. ​
Click to expand...
Click to collapse
Thanks for explanation!! But... still nothing.
I did EVERY SINGLE STEP like you said. Except for baseband, cause my phone was originally 2.3.3. But all new downloads...
After flashing, try to reboot... DAMN! "root access possibly lost..." YES/NO, gives me same problem. I read another thread about this erros, people said about SU. Can it be? I tried to flash another SU version, but CWM return an error too =/

jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559363 try this.

voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
Click to expand...
Click to collapse
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)

jpesci said:
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
Click to expand...
Click to collapse
I am considering the jenkins build from here: http://download.androidarmv6.org/_builds/
can anyone help with finding the smallest gapps that will fit?
Edit:No need

I've made a few extremely rash decisions, and I'm not sure if I can fix this.

Okay, this all happened because I tried to install CyanogenMod without taking into consideration the fact that I'm using the SV version, of which there does not seem to be any easy way to install CyanogenMod on.
My provider is Boost Mobile if that's important.
The first step I took was to unlock the bootloader, which was successful (I did use the HTCDev website, submit my identifier token, and it definitely worked).
The real trouble was when I tried flashing my recovery and boot .img's using the files in this link (for the HTC One S): ((I can't post links as a new user, but I tried acquiring my .img's from the CyanogenMod wiki, in the guide for the HTC One S, which was probably the root of this problem)
Terrible mistake, I know. I think my phone is bricked, but I'm not 100% sure because this is the first time I've tampered with any phone on this level. The only comparable mistake was when I accidentally formatted my hard drive when I tried installing Arch on my desktop, two years ago.
Right now, my phone won't start properly. When I do a normal bootup, by simply holding down the power button, I get treated to the HTC logo followed by a blank blackish-grey screen. I have to remove the battery to exit it. I can access fastboot, but when I attempt to access recovery I get taken to a perpetual load screen with an HTC logo and "Entering recovery mode..." on top of it. I have to remove my battery at this point because it never goes beyond that screen.
The other trouble is that while I seem to be able to access my phone through a USB cable, and apparently detect it using the "fastboot devices" command, the device itself doesn't seem to show up on Windows (as C525c, like it did before). I'm not sure if this has to do with me screwing up my boot and recovery .img's or my USB drivers.

Ok, this was not a good idea, to flash a boot.img from different device!
If there is any chance for your device, then try to flash the recovery from here (boost version).

old.splatterhand said:
Ok, this was not a good idea, to flash a boot.img from different device!
If there is any chance for your device, then try to flash the recovery from here (boost version).
Click to expand...
Click to collapse
Okay, I just did. I am finally able to boot into recovery! Thanks!
I'm not sure what I should do next though, because I don't want to screw it up again. Which options should I choose?
They are: Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot.

I'll guess you don't have a backup to restore?
Then you can try to restore some from here.
Or somebody gives you an backup from 4.2.2 boost version.

old.splatterhand said:
I'll guess you don't have a backup to restore?
Then you can try to restore some from here.
Or somebody gives you an backup from 4.2.2 boost version.
Click to expand...
Click to collapse
I'm unable to use any of the mega.co.nz links. I get taken to a loading screen, but it never actually starts downloading.

Try another browser.