Database Info

[Q] phone is dead , can only enter in cloxkworkmod recovery

Hi all expert,
my nexus s is unrooted. i installed ADB in my win7. I did wipe out all data/sd card without any back up. so my phone cant go anywhere ,except into clockworkmod recover. when I try to boot, error say it cant find any image. I cant instal image if i cant get in to the phone and set the usb connection. So my question is how to force install image into the phone without enablimg the usb connection? Please help. thank you

rongsokan said:
Hi all expert,
my nexus s is unrooted. i installed ADB in my win7. I did wipe out all data/sd card without any back up. so my phone cant go anywhere ,except into clockworkmod recover. when I try to boot, error say it cant find any image. I cant instal image if i cant get in to the phone and set the usb connection. So my question is how to force install image into the phone without enablimg the usb connection? Please help. thank you
Click to expand...
Click to collapse
you have clockwork recovery right? theres an usb storage option in the recovery itself. connect it to your computer, turn on the usb storage. download a rom(and gapps) to your computer, copy/paste into the device, turn off usb storage, then flash the files in clockwork recovery. then reboot.

After you do what he said, either do alot of research about rooting, and flashing roms and kernels or sell your phone.
Sent from my Nexus S 4G using xda premium

simms22 said:
you have clockwork recovery right? theres an usb storage option in the recovery itself. connect it to your computer, turn on the usb storage. download a rom(and gapps) to your computer, copy/paste into the device, turn off usb storage, then flash the files in clockwork recovery. then reboot.
Click to expand...
Click to collapse
So I did follow your instruction. I went storage->mount usb storage->unmount(I can only select this, I try reboot the phone still give me this only option). so I also tried mount sdcard, mount system, all that.
Finlally, I got removable disk on my computer, but it show 0 byte, when i click on it, it says plz insert a disk into removeable disk. so i went click
property->hardwares->highlight Android UMS composite usb device(type: disk drive) and property. then I select driver-> and there is driver details, update driver. So do I update this driver? If so which driver?
I try to format it, it gives errorlz insert a disk into removeable disk
I have clcokworkmod recovery v5.0.2.0 and it is unrooted. thank you for the help!

I also install PDAnet into my computer but it keep saying connecting to your phone..... I try using different usb port and no luck.

rongsokan said:
So I did follow your instruction. I went storage->mount usb storage->unmount(I can only select this, I try reboot the phone still give me this only option). so I also tried mount sdcard, mount system, all that.
Finlally, I got removable disk on my computer, but it show 0 byte, when i click on it, it says plz insert a disk into removeable disk. so i went click
property->hardwares->highlight Android UMS composite usb device(type: disk drive) and property. then I select driver-> and there is driver details, update driver. So do I update this driver? If so which driver?
I try to format it, it gives errorlz insert a disk into removeable disk
I have clcokworkmod recovery v5.0.2.0 and it is unrooted. thank you for the help!
Click to expand...
Click to collapse
By the way you just click on mount usb storage and LEAVE IT there for a few seconds. It takes a little time for the computer to recognize it usually. You only click unmount when your done...

ok i got it. now i could put files into the sd storage. Do you guys know what i need to put for stock, out-of box image?
I need to reset this to factory setting and root the phone.
I did some serach but the file needed to download is not working anymore. anyone know? thank you

rongsokan said:
ok i got it. now i could put files into the sd storage. Do you guys know what i need to put for stock, out-of box image?
I need to reset this to factory setting and root the phone.
I did some serach but the file needed to download is not working anymore. anyone know? thank you
Click to expand...
Click to collapse
Here is a thought... read some more before messing with your phone instead of asking questions which have been already answered many times.
Sent from my Nexus S 4G

I have been reading reading again... the whole day today. I just dont want to install the wrong drive or file. for nexus s tehre is so many version. the one i got for bootloader is i9020xxka3
for baseband version- i9020xxkf1
fastboot mode stil showing- NO BOOT OR RECOVERY IMG
I give up may be I am too idiot.

obsanity said:
Here is a thought... read some more before messing with your phone instead of asking questions which have been already answered many times.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Coming from someone that also finds conditions & situations similar but not precisely like my own in the multitude of answered threads..... Some of us can get to a certain point but get stuck, and since these are devices we need to work we want to be sure we don't do something to turn an expensive device into a pretty paperweight.
You learned by fiddling and asking questions did you not? If you are sick of the same old question don't answer the thread.
Sorry, I have no great advice for the OP, you aren't an idiot you are uninformed [just yet] of the proper fix for your problem. I'm still trying to fix something myself so the couple of snipes hit a nerve this morning.

I read read read and read again, its been almost a week. Good god I cant get the solution or may be i dont undderstand it. I try go to cmd prompt and "type fast boot lock" to get it rooted. No luck
my phone situation:
No back up or recovery ( I wipe all sd/back up/system)
fasboot mode-no boot or recovery img
Lock state- unlocked
can only go into clockwork mod
my Goal: lock the phone and flash it to factory stock setting.
I just own nexus s for 7 days and did a ton of research coz stuck at google X animation keep loading and install MIUI and unroot the phone. Soooo stupid of me now that I broke the warranty. Softkeys is no even working!!!!!! when i suscessfully get into the phone.
is there a proper step by step to do this? is there any expert here that can point to the right direction? I am checking this post every 5 minutes

Clearly this is too much phone for you.
Sent from my Nexus S 4G using xda premium

Ok I'll try to help you.
According to what I gather from your posts, you've been successful in unlocking the bootloader and managed to flash CWM recovery, that's a good first step.
Your goal is still unclear. Ok, you want to re-lock the phone and 'restore to factory stock settings'? Does that mean you want a stock firmware on your phone or would you settle for a custom firmware, like Cyanogenmod or MIUI? Either way, visit the Nexus S Development forum, there's a full list of firmwares , just pick whichever you want and download that.
Here's a fantastic topic with a list of all firmwares and also plenty of links to guides:
http://forum.xda-developers.com/showthread.php?t=1067813
Enter CWM recovery mode (VolumeUP + Power button and select Recovery in the Bootloader options).
Go to mounts and storage. We want to mount or SDcard so we can transfer files from the PC to the SDcard as a USB mass storage device. Make sure the phone is connected through USB.
So, select the option: - mount USB Storage. Wait for a few seconds, it takes a while to get initialized by the PC.
Once it's recognized by your PC, copy the downloaded firmware to the SDcard. It should have a .zip extension and be approximately 100mb (of course depending on which flavour you picked, but that's somewhat the standard).
Once it's copied, go back in the CWM main menu and select "Install zip from sdcard". If you want, you can first wipe your cache and Dalvik cache, but since you clearly wiped everything already this shouldn't be necessary, so anyway; install zip from sdcard and select your firmware.zip file. Select it and press the power button to execute the install.
It will install the firmware plus the kernel that it's packed with, all this should be enough to get your phone booted. So reboot your phone and it should work.
Once you've successfully booted into your device, you can do whatever you like. If you want to lock the bootloader again though, you'll need to reverse the steps you took to unlock it. This is through ADB and Fastboot. But this topic explains it step by step and in detail, all credits to the OP: (http://forum.xda-developers.com/showthread.php?t=875630).
If the bootloader is locked again, you shouldn't have any issues with the warranty. It's a Nexus...
Some of your posts were a bit contradictory so I can only assume what your current status is with your phone.
Maybe you should also understand what everything means and does instead of blindy formatting disks and running random commands. Learn what ADB is, learn what Fastboot does. See how the bootloader works and where the recovery comes in, read up on the different firmwares and what kernels do. It might seem like a big investment of your time, but it will help you understand the boot process of the Nexus.
Good luck,
Greetz

More B63M users here?

Hi all, I just ordered a Chinese B63M phone at cect-shop.
Nice phone with great specs.
I alreadu know how to root it, but are there already custom Roms available?
Could'nt find a lot of info, just a Russion version.

B63M... thats my phone
Henkdrenth said:
Hi all, I just ordered a Chinese B63M phone at cect-shop.
Nice phone with great specs.
I alreadu know how to root it, but are there already custom Roms available?
Could'nt find a lot of info, just a Russion version.
Click to expand...
Click to collapse
Now that makes us 2 people who owns a B63M and got it from cect-shop.
What I find out about their phones is that it may not easily allow you to perform some insider operations, for instance, maybe its me but I could not find any custom recovery installed and this led to my first issue after I rooted, and installed the ROM manager, I saw the 'fix permission' and clicked it hoping to resolve my force close issues and it asked me to reboot after performing the process but it never got out of the boot, the loop continued, trying to boot into recovery become impossible but somehow a combination got me into a mode where I was able to clear flash and this took me back to a pre factory flash good thing I backed up titanium so I cld restore my apps and upgrade.
Right now I have tried to flash and the screen has gone blank yet the phone is responding to touch as I can hear sounds when the screen is clicked, indicating that its not bricked I just cant see anything going on (this is my current situation and seriously looking for help).
Lastly, I am trying to find out the htc equivalent to this b63m, it looks htc but I cant be sure which of the htc has been more or less cloned... this is going to help with a lot of things if known.
Cheers

Hi there,
If you are looking for a custom recovery, try this forum, altough you have to translate it because it is in German.
Lots of people there with our phone end they know how to get a custom recovery on it.

Cect is German
Henkdrenth said:
Hi there,
If you are looking for a custom recovery, try this forum, altough you have to translate it because it is in German.
Lots of people there with our phone end they know how to get a custom recovery on it.
Click to expand...
Click to collapse
Yeah thanks, I have also stumbled on the site forum before but I cld not get something out of it, maybe I have not taken time enough to search, I am back on it now and hope I get a solution to the blacked out screen problems I have after flashing.
You know cect-shop is German, they are a German company in China... I am talking to them on skype and hoping they can help me out but they seem pretty busy or cant be bothered because their response is so much delayed or even not at all.

Well technoforum has a special B63M section with all tools required.
They also have nice custom roms like a Cyanogen fork.
I also don't speak Italian, but with the help of Google translate I'm getting pretty far.
But I do let Google translate from Italian to English, that gives me the best result.
Good luck!!
Do you also get no working screen after a reboot with both volume + and power button?
That should get you to the recovery screen without any ROM drivers.

Very correct, no screen even in recovery
When I do the button combination, I believe that it may have responded to my combination for recovery mode but I just cant see anything on the screen, it just remains the same way it was... maybe it graphics issue, as in is the graphics is messed up for some reason or resolution issue, you wont see anything being displayed.
I am just guessing here but all I did was to simply flash an update.zip from sd card.

That is very strange, since flashing a rom does not affect the screen of the recovery boot.
The rom video driver gets only active during the boot process of the rom.
In the past I had some boot problems with my Wildfire start-up that I solved by removing the SIM card and SD card, removed the battery for some minutes and them booted completely resetted.
You could try that, if that does not solve the problem, the only way to wipe the phone back to factory-reset is doing it blind.
After I get my phone I could make a step-by-step guide so you could get to the reset menu...
Another possibility is to re-flash a fresh recovery img to the phone. Since I don't know what was in your update.zip, you could messed up the recovery menue, or even the bootloader.
Re-flashing those could also help and you don. t need the display from the phone, since you use the PC for that.

Here it is
Here is the update.zip I flashed. http://chinamobiles.org/downloads.php?do=file&id=618&langid=4
I am a bit surprised myself that the screen is blanked out but the phone seem to be working still.
I have removed both SIMS and SD card plus battery several times etc. nothing changed.
You said ''After I get my phone I could make a step-by-step guide so you could get to the reset menu...'', I hope you get your phone soon tho, and i can see the step-by-step guide you made.
I have actually flashed recovery into it using flash tool, ODIN dont seem to see the phone (at least the yellow box saying COm4 or 5 is not showing), I can see the phone using adb but when I say adb reboot download or recovery, something happens but I cant see what it is.

I too have a B63M...!!! Spice Mi-350n...........
If you need a moded recovery, i can port it for you........but you need to follow some instructions...i'll give them tomorrow!!

Waiting on you... I hope my blank screen gets sorted.
balamu96m said:
I too have a B63M...!!! Spice Mi-350n...........
If you need a moded recovery, i can port it for you........but you need to follow some instructions...i'll give them tomorrow!!
Click to expand...
Click to collapse
Ahh thanks man... Ii will wait to hear from you tomorrow, I aim in UK and depending on what time zones you are in but I hope to find you online to connect again.
I hope you have understood my particular issue here tho, the screen if blank even tho the fone seem to be alive and it follows the boot sequence, I can even find it using 'adb devices' command, it just the screen gone blank.
Someone suggested it may be the boot.img but I dont know about that.
Cheers

I'm from India - Local time here is GMT+5:30......!!
So, here you go !!
B63M= MTK6573 + 650mhz + Android 2.3
So, one modded recovery.img can't be used for every B63M.......this is because a different B63M phone will have a different recovery.img..........(hope u understand)
Backing up everything:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'BackUpTools.rar' from HERE and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
Here i need two files.One is recovery.img and the other is firmware.info.
If you give both, i can port one for your phone !! Also mention your phone's model name/number because, without that it is not possible.

xdadeem said:
Here is the update.zip I flashed. http://chinamobiles.org/downloads.php?do=file&id=618&langid=4
HTML:
I am a bit surprised myself that the screen is blanked out but the phone seem to be working still.
I have removed both SIMS and SD card plus battery several times etc. nothing changed.
You said ''After I get my phone I could make a step-by-step guide so you could get to the reset menu...'', I hope you get your phone soon tho, and i can see the step-by-step guide you made.
I have actually flashed recovery into it using flash tool, ODIN dont seem to see the phone (at least the yellow box saying COm4 or 5 is not showing), I can see the phone using adb but when I say adb reboot download or recovery, something happens but I cant see what it is.
Click to expand...
Click to collapse
That was the problem, you flashed only the update, not a complete Rom.
I suggest you make a complete re-flash vorm scratch, so refash a fresh recovery.img and re-flash als a new Rom.
You can vind one at technoforum' as earlier mentioned

I thot you shd read my latest.
Ok guys I appreciate this a lot.
Here at this point I think you shd hear my developments before taking any further actions or suggestions.
aha thanks, I did just that and it worked although it is still blank at the beginning of boot but later something shows up on screen and completes boots.
Remember I mentioned that someone suggested it might be a boot.img problem... well, I used flashtool to flash a boot image and I can say it worked, I now have the visuals, even tho the screen is still blank at boot start but soon after it picks up and its working, now I have the phone again.
so @balamu96m, my issue was basically the screen, without seeing anything I cannot follow the back up suggestion you gave me here, but now I can see it again.
A couple of additional issues tho...
1- I checked the kernel and it has changed from 2.3.5 into 2.3.4 and >In the current ROM flash I have lost a couple of capabilities like Flashlight, camera etc
2- I followed this link http://www.technoforum.it/forum/viewtopic.php?f=73&t=3351 to flash recovery and it says Successful with the green Circle -OK-... but I still cant get boot into recovery either when I use the keys combi or when I try to boot into recovery in mobileuncle tools, it just goes blank and stays like so until I have to remove the battery and restart boot normally.
3- From the same link above they have the Golight ROM in part 2 after recovery in part 1, I am assuming this a good ROM to flash and the things I lost will get back, but I still cant boot into recovery.
Coming back to the response from balamu96m... Should I still go ahead with what yu suggested and provide you the files details you want? both recovery.img and firmware.info... I am asking because I no longer have the original ROM that came with the phone and like I said I cant even get into Recovery after I tried flashing a new recovery.img, this one from the same link above (see the recovery.img inside the 'Recovery Moddata' file from the 'UPDATEB63MRecovery2012' download file.)

Great to hear that you have visual again!
You still have root yes?
The golight rom from technoforum is a good one.
I expect mine any moment now so I can customize mine too.
Good luck!

xdadeem said:
Ok guys I appreciate this a lot.
Here at this point I think you shd hear my developments before taking any further actions or suggestions.
aha thanks, I did just that and it worked although it is still blank at the beginning of boot but later something shows up on screen and completes boots.
Remember I mentioned that someone suggested it might be a boot.img problem... well, I used flashtool to flash a boot image and I can say it worked, I now have the visuals, even tho the screen is still blank at boot start but soon after it picks up and its working, now I have the phone again.
so @balamu96m, my issue was basically the screen, without seeing anything I cannot follow the back up suggestion you gave me here, but now I can see it again.
A couple of additional issues tho...
1- I checked the kernel and it has changed from 2.3.5 into 2.3.4 and >In the current ROM flash I have lost a couple of capabilities like Flashlight, camera etc
2- I followed this link http://www.technoforum.it/forum/viewtopic.php?f=73&t=3351 to flash recovery and it says Successful with the green Circle -OK-... but I still cant get boot into recovery either when I use the keys combi or when I try to boot into recovery in mobileuncle tools, it just goes blank and stays like so until I have to remove the battery and restart boot normally.
3- From the same link above they have the Golight ROM in part 2 after recovery in part 1, I am assuming this a good ROM to flash and the things I lost will get back, but I still cant boot into recovery.
Coming back to the response from balamu96m... Should I still go ahead with what yu suggested and provide you the files details you want? both recovery.img and firmware.info... I am asking because I no longer have the original ROM that came with the phone and like I said I cant even get into Recovery after I tried flashing a new recovery.img, this one from the same link above (see the recovery.img inside the 'Recovery Moddata' file from the 'UPDATEB63MRecovery2012' download file.)
Click to expand...
Click to collapse
You flashed a recovery, but that is not working ah?? Oh God!!
Why did you do that bro??
Do you have any backup of the stock one??
If you dont have, then i have 2 ideas....one idea is to flash something else such that your fone won't boot....now you can send your phone back to the manufacturer and ask them to reflash everything!!!
The other idea, i'll tell you after sometime!!

It was always so
balamu96m said:
You flashed a recovery, but that is not working ah?? Oh God!!
Why did you do that bro??
Do you have any backup of the stock one??
If you dont have, then i have 2 ideas....one idea is to flash something else such that your fone won't boot....now you can send your phone back to the manufacturer and ask them to reflash everything!!!
The other idea, i'll tell you after sometime!!
Click to expand...
Click to collapse
The reason i flashed recovery initially was that my phone went into a boot loop and I was unable to get into recovery, after a while somehow i figure it out and cleared flash and then restored my phone apps and co and got on fine.
But if I could not get into recovery it means that there was not stock recovery on my phone or it got missing somehow. This I have to ask Henkdrenth since he is getting the same phone from the same shop too, but there was no recovery in my B63m, I already heard there is a recovery problem with the phone anyway, and thats why I flashed recovery and it worked but then I flashed ROM and the screen went blank, which is what got me to this forum.
I did not just go and flash recovery, it because there was none on the phone in my opinion.

xdadeem said:
The reason i flashed recovery initially was that my phone went into a boot loop and I was unable to get into recovery, after a while somehow i figure it out and cleared flash and then restored my phone apps and co and got on fine.
But if I could not get into recovery it means that there was not stock recovery on my phone or it got missing somehow. This I have to ask Henkdrenth since he is getting the same phone from the same shop too, but there was no recovery in my B63m, I already heard there is a recovery problem with the phone anyway, and thats why I flashed recovery and it worked but then I flashed ROM and the screen went blank, which is what got me to this forum.
I did not just go and flash recovery, it because there was none on the phone in my opinion.
Click to expand...
Click to collapse
Now, is the recovery working??
Does the phone boot properly??

Wrong section. Moving to general.

YES and NO
balamu96m said:
Now, is the recovery working??
Does the phone boot properly??
Click to expand...
Click to collapse
After many troubles, I found a mod for w690 which is the build version of my phone, I could not boot to recovery so used flashtool and when I load the scatter text of the one I found, it automatically load in every item on the list including recovery and boot img , etc, so I flashed these to my phone... and for the first time I was back in how the phone came to me,
Gingerbread has now returned to 2.3.5.
One thing I have noticed is that the phone freezes on me and then reboots?
I still cannot boot into recovery, I tried this again using mobileuncle tools...
It seem that I have flashed my phone which is good, but I was unable to wipe cache because I could not boot into recovery to do this which may be the source of the current freeze and reboot.
Can I solve this using the mobileuncle or what can I do to wipe cache, if that is the problem

Well, received mine, rooted it an flashed a new recovery from technoforum using myuncletools.
All went well, so I suggest you do also a fres re-flash with a proper recovery.
Hope that should solve your problem.
Edit: moved from my tablet to my PC to look for the link of a correct recoveryfile for you.
First, load this recovery.
Unpack it and put the content to the root of your SD card.
Use myuncletools to flash this recovery.
Now you should have a usable custom recovery that allows you to factory-reset and wipe your phone
Install a fresh rom
How to? Look here

[Q] Atrix 2 won't boot past "M" Motorola logo

Hey guys,
Forgive me for being frantic and (probably) not taking the steps needed to research this issue, or not taking the time to do so, but I'm sure you can all presumably imagine -if you've not been in this situation before- that it SUCKS not having a phone in this day in age...
My problem: Atrix 2 (Rooted + CWM Recovery) now won't boot passed the "M" Motorola logo upon start up. It won't even allow me to access the factory Android Recovery by holding down Volume Up, Volume Down, and Power. I think I inadvertently bricked the phone? (Hope not!)
Further, the "M" Motorola logo is skewed in appearance, like its not even loading correctly. I'm not sure what to do. This is my first time rooting and getting experienced with custom ROMS.
Anyone able to help this helpless sap?
Thanks is advance to your replies...

Step 1 is where you tell what you did to get into the state you are in. You wouldn't believe how far it goes toward fixing something if you know how it got broken.
Sent from my MB865 using XDA

If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.

KEB64 said:
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
Click to expand...
Click to collapse
Agreed pull the battery. If you run out of juice you'll be in some serious trouble.
Did you try to flash the fkz? Unless you have CWM on Boot it's the only way you can get your phone working.

Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.

pull the battery, put it back in, and hold vol up and down while turning on. choose ap fastboot at the menu. go to the thread in my signature and under the mirrors there is also a download of the return to stock script. run it while in fastboot and plugged in with usb. DO NOT pull the chord until it is done. when it is you should be good.

Apex_Strider said:
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
Click to expand...
Click to collapse
Yeah wiping the system partition is a no no unless you flash another rom afterwards. Do like ikrasner says and you should be back to normal.
Sent from my MB865 using XDA

Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!

can you read chinese?
Maybe I can solve your question,but poor of my english.
and what is your phone type?
at&t hktw or china ?
Sent from my ME865 using xda premium

Apex_Strider said:
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
Click to expand...
Click to collapse
It should ask you to install 2.3.6. Just go into setting>about phone>check for updates. Or you could go and install one of the roms that are based on 2.3.6 such as Lithium Sonya or SCv5.

Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.

Apex_Strider said:
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Click to expand...
Click to collapse
do not flash this. unzip it on your computer, choose to boot into fast boot in the same place you chose recovery, then run the .bat file that was in the zip.
Sent from my MB865 using XDA

What that file does is reflash your system.img, basically restoring your phone to factory default. And just as a sidenote you cannot flash things with the standard Android Recovery. You need CWM.

did you try apboot mode and ise fastboot to flash system.img ?
Sent from my ME865 using xda premium

Still not working... not sure how to flash from fastboot. I don't have any options to run a file from there, or at least not sure ow to go about that.

Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium

dickluo said:
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!

Apex_Strider said:
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Click to expand...
Click to collapse
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.

jfrank1485 said:
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
Click to expand...
Click to collapse
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!

Apex_Strider said:
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Click to expand...
Click to collapse
I'm glad it work , keep it at hand before doing anything to your phone, it really helps

[Q] Cannot get out of recovery menu

I've gone through all the old posts, tried various suggestions using Odin and the SDK but without success.
My son got his Samsung GT-i5800 locked because he forgot the swipe code. I tried suggestions on forums but no good. So I put the phone into the recovery mode and selected "wipe data factory reset" then selected "system reboot now". The phone then rebooted and arrived back into the recovery menu. Everything I've done has brought me back to "Samsung Recovery Utils for BML"
I've downloaded the SDK manager and tried typing "abd" into the command line but it is not recognised. I've pointed the command line at the tools folder, then the platform-tools folder found the abd application but cannot run any commands. Not that it would do much good anyway as the phone doesn't connect to the PC via USB when in the recovery menu.
I know this problem has been mentioned before but all the suggestions from those posts have not worked. I have now run out of ideas.
I've spent too many hours on this, so before I go buy another phone, does anyone have any other suggestions, please?
thanks.

itsar1 said:
I've gone through all the old posts, tried various suggestions using Odin and the SDK but without success.
My son got his Samsung GT-i5800 locked because he forgot the swipe code. I tried suggestions on forums but no good. So I put the phone into the recovery mode and selected "wipe data factory reset" then selected "system reboot now". The phone then rebooted and arrived back into the recovery menu. Everything I've done has brought me back to "Samsung Recovery Utils for BML"
I've downloaded the SDK manager and tried typing "abd" into the command line but it is not recognised. I've pointed the command line at the tools folder, then the platform-tools folder found the abd application but cannot run any commands. Not that it would do much good anyway as the phone doesn't connect to the PC via USB when in the recovery menu.
I know this problem has been mentioned before but all the suggestions from those posts have not worked. I have now run out of ideas.
I've spent too many hours on this, so before I go buy another phone, does anyone have any other suggestions, please?
thanks.
Click to expand...
Click to collapse
^First of all, there's no such command called as "abd". Also, I'm pretty sure that you probably haven't installed adb properly. Just follow the steps given in the following tut to make it work:
[How To] Setup ADB for Windows/ Mac
And secondy, there's no need to go through all that hassle. Simply pull out your battery. Insert it back and then press the following key combo:
"Vol Down + Home + Power Key". This would take you to the Download mode, now simply flash any stock or custom ROM via Odin. Here's a list of Stock ROMs available for our device:
Galaxy GT-15801 ROM/KERNEL List

h4r5h said:
First of all, there's no such command called as "abd". Also, I'm pretty sure that you probably haven't installed adb properly. Just follow the steps given in the following tut to make it work:
[How To] Setup ADB for Windows/ Mac
Click to expand...
Click to collapse
Thanks for your suggestion. I will give it a go when I get some more time. I was following quite carefully what others had written in posts. I can only assume they missed out a detail that they thought was obvious.
h4r5h said:
And secondy, there's no need to go through all that hassle. Simply pull out your battery. Insert it back and then press the following key combo:
"Vol Down + Home + Power Key". This would take you to the Download mode, now simply flash any stock or custom ROM via Odin. Here's a list of Stock ROMs available for our device:
Galaxy GT-15801 ROM/KERNEL List
Click to expand...
Click to collapse
Sadly I've gone through all that. You are not the first to suggest this. I flashed the rom to the phone, Odin says "PASS" but the phone just reboots back in recovery mode.
It feels like that the phone's equivalent to the bios is telling it to go into recovery mode and not boot up the operating system. So regardless of what ROM is flashed onto the phone, I get the recovery menu. :crying:

Delete boot partition
And reflash...
Hope it will ... or else try purumod ..
Sent from my GT-I5800 using xda premium

If u were on stock rom initially then u can always get help from Samsung service center
Secondly if u have cwm recovery u can install rom or update.zip through cwm itself
Also
Its surprising that after data wipe such problem appeared did u miss out something
Sent from my GT-I5800 using xda app-developers app

[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