My phone rarely reboots (maybe 2-3 days and sometimes longer) and it's livable to say the least. BUT, my phone also after 1-2 days would always slow down like something was getting bogged down and a reboot would clear the problem and it'd be super fast.
This happens like clockwork and so I figured I'd try something for giggles.
I have ROM Manager installed and I have the 'fake' ClockwordMod Recovery installed. I reboot into recovery and went to advanced and then Wipe Dalvik Cache. That's IT.
Reboot into phone.
And you know what? Phone is still super fast after 2 days and overall seems way more stable!! This could explain why those who do a factory reset after they get their phones have less issues - part of a the factory reset is a wipe of Dalvik.
So if you experience slowdowns or reboots or weirdness try this out.
1. Download ROM Manager from market
2. Flash recovery in ROM Manager for G2X (this doesn't actually flash a recovery so your phone can still get updates from LG and be returned,etc.)
3. Reboot into Recovery via ROM Manager
4. Once CWM starts up, go to Advanced
5. Go to Wipe Dalvik Cache
6. Reboot back to the phone.
Done.
Good luck. I love playing with this stuff
Or just just use root explorer, data/dalvike_,cache and delete it there without rebooting into clockwork..
That's been known to cause issues and might not delete properly since the fs is in use. Recovery is the best way to guarantee it works.
smashpunks said:
Or just just use root explorer, data/dalvike_,cache and delete it there without rebooting into clockwork..
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App
smashpunks said:
Or just just use root explorer, data/dalvike_,cache and delete it there without rebooting into clockwork..
Click to expand...
Click to collapse
i usually do it this way with no problem, a lot quicker as well
or if u have the nvflashed recovery scroll down to advanced then choose dalvik...
Yea. When I always get a new phone, I always "play" with it. Change all the settings, play with the new apps, etc.... then I wipe and forget about most of it.
I try to get a feel for stock before flashing a custom rom.
I've done this to all of them because I would load up that Racing game to check the backlight bleed... I would skip the initial setup to make it faster. Once it checked out, I would factory reset and set it back up properly.
Always a good thing to do.
Related
So i was restoring my phone on odin when my daughter pulled on the usb before odin restored my phone now i have a symbol when going on download mode. Its of a (phone---!---computer). Is there anyway to restore after that?
Thanks any help will be appricated
I think that happened to me after flashing some funky things that didn't work. Boot to Odin mode like you would normally:
Disconnect USB.
Pull battery.
Put battery back in (do not turn on!)
Hold down both volume keys and plug in the USB cable to phone & PC while holding them.
Phone should show the PC & Phone and it should look very angry like it has before.
Odin should detect your phone on COM## (where ## is some number). You should be able to repeat the Odin process just the same as normal.
Aou said:
I think that happened to me after flashing some funky things that didn't work. Boot to Odin mode like you would normally:
Disconnect USB.
Pull battery.
Put battery back in (do not turn on!)
Hold down both volume keys and plug in the USB cable to phone & PC while holding them.
Phone should show the PC & Phone and it should look very angry like it has before.
Odin should detect your phone on COM## (where ## is some number). You should be able to repeat the Odin process just the same as normal.
Click to expand...
Click to collapse
You are amazing bro thanks. Another question will i be able to reflash infused rom?
After you use the ultimate unbrick, you will need to:
-Root your device again (if applicable... some versions of the unbrick have root included)
-(You might get a bunch of FC's on apps when it starts): Wipe data from 3e recovery
-Install the modified 3e recovery
-Install CWM and Rom Manager
-Download/install the rom through Rom Manager.
-Alternatively, you can install the rom through CWM, but I find Rom Manager to be very nice and easy.
This set of instructions you'll find scattered around the forums.
EDIT: forgot to add: you you'll just need to wipe user data, and wipe any/all caches. NO need to wipe your internal sdcard!
Oh, and as a rule of thumb: never, ever use Titanium Backup to restore SYSTEM DATA. It will cause all sorts of hellish bugs.
bvspunjah said:
You are amazing bro thanks. Another question will i be able to reflash infused rom?
Click to expand...
Click to collapse
yes. you will. i had to ODIN my phone when something messed up when i tried to upgrade from 1.5.3 to V2 stable. did ODIN and accidentally did the same thing you did(accidentally pulled USB).
dddeemann2 said:
yes. you will. i had to ODIN my phone when something messed up when i tried to upgrade from 1.5.3 to V2 stable. did ODIN and accidentally did the same thing you did(accidentally pulled USB).
Click to expand...
Click to collapse
Yeah, something went wrong for me also. I did follow instructions normally (i.e. let the voodoo disable do its work converting back, etc.), but it still gave me a samsung boot-loop. The Odin/unbrick-and-retry method worked flawlessly after that.
Pretty much, as a rule of thumb with this device, if it powers on to ANY screen whatsoever, it's likely recoverable. If it doesn't turn on (black screen, no lights), you're hosed. Trust me, it's very, very difficult to get an Infuse to this state. I am one of a very small handful that has succeeded in this.
Aou said:
After you use the ultimate unbrick, you will need to:
-Root your device again (if applicable... some versions of the unbrick have root included)
-(You might get a bunch of FC's on apps when it starts): Wipe data from 3e recovery
-Install the modified 3e recovery
-Install CWM and Rom Manager
-Download/install the rom through Rom Manager.
-Alternatively, you can install the rom through CWM, but I find Rom Manager to be very nice and easy.
This set of instructions you'll find scattered around the forums.
EDIT: forgot to add: you you'll just need to wipe user data, and wipe any/all caches. NO need to wipe your internal sdcard!
Oh, and as a rule of thumb: never, ever use Titanium Backup to restore SYSTEM DATA. It will cause all sorts of hellish bugs.
Click to expand...
Click to collapse
im not to sure what FC means and i also dont now how to wipe user data and caches. sorry im the ultimate noob
FC = force close
wiping data and cache will show as an option when you flash V2.just follow GTG's instructions when installing V2 ROM and youll see him mentioning it.
And this should be in General, as it has nothing to do with development. (by the way, Q&A is coming.)
Ok be prepared, this post may be rather long winded however I will try my best to prevent that. I have a Tmobile G2x I purchased on launch date. Ive not attempted to Root, change roms, or anything of the sort. (as much as I always wanted to, I always felt that my skills were not good enough to attempt these ideas no matter how easy they may seem. I just did not want to be the cause of screwing up my phone that I paid dearly for)
So I have a friend who claims to be the master (of disaster so it turns out) of rooting androids and such. He stops by my house just to hang out and eventualy convinces me to let him root my phone and install CM7. Within a few minutes the phone was rooted (super1click) and was running CM7 release candidate. (I really dont know what all these things truly are but I drilled him for answers once he jacked up my phone and left me with a half-bricked phone) So he installed Rom manager and convinced me to upgrade to the premium version via marketplace so I did. He was then showing me how easy it was to flash new roms at the touch of a few buttons. He put on some other rom which looked like CM7 but claimed to have extra tweaks. It worked fine. A few minutes later he put on some Faux Rom which gave a boot up screen like my old Nexus One did. (Multicolored X) It seemed to work fine as well. Then he said lets check out the nightly CM7 Rom so he put it on. (however I dont think it ever actually put CM7 back on.-still on Faux?) Thats when things got crazy.
Now I get the com.google.process.gapps force close message all the time. He tried to fix it for 4 hours and finally gave up. Here is what I know he/we tried: After searching the internet for hours we tried everyone elses ideas. Clearing calenders cashes, un syncing, etc. We did about 40 factory resets. We have tried to install my backup (which was from BEFORE he even touched my phone) and upon holding both volume rockers and plugging in USB (no battery installed) and it still does nothing. Windows recognizes device but phone screen stays black. Tried Debug mode while doing this as well. If we hold the volume down button and power the little install bar comes on the screen and it does its thing (whatever that is) and goes right back to the way it was. I keep getting the gapps message all the time. After factory reset I cant even type in my gmail address to start the initial setup of the phone. The force close keeps cutting me off. If I type fast, I can sync the account but I cant use market whatsoever. Tried installing Rom manager to re-flash but just sticks at starting download and gapps pops up again.
My son is starting school tomorrow and he has a medical condition. I NEED this phone to communicate with the school nurse via emails and such. As of now I can only text, call, or surf web all while dodging force closes. If ANYONE out there can please help me get my phone back to normal Id greatly appreciate it. Im sure its something easy but as I said before, Im not good at this thing and thats why I never attempted it myself. Your welcome to submit answers here or PM me your phone # if you want to walk me through it on the phone. (I have a landline phone to talk to you on) Thanks in advance for everyones time and Im sorry this ended up being so long.
Download latest Gapps.zip from Cyanogen site to your phone's SD card, boot into recovery, wipe data and cache then flash the Gapps.zip file. Let me know if this helps.
I will try this now. Thank you
Im unable to get anywhere. It still has stock recovery and I cannot get to the screen where I can wipe. Im not great at this sort of thing but Im trying.
Omnichron said:
Download latest Gapps.zip from Cyanogen site to your phone's SD card, boot into recovery, wipe data and cache then flash the Gapps.zip file. Let me know if this helps.
Click to expand...
Click to collapse
i think you would be better off starting from scratch
1. remove your sd card from your phone and plug it in your computer
2. download the latest rom here
3. download gapps from the download links at the bottom of this page
4. transfer both files onto the sd card and put it back into your phone.
5. with your phone off, boot your phone into recovery by holding vol down+power
6. wipe data, cache, and dalvik cache
7. flash only the cm7 file
8. reboot normally
9. reboot into recovery
10. flash gapps
11. reboot normally
after you flash one file, it is highly recommended that you reboot before you flash another file (if your friend didnt do this, this may have been the problem)
HurtsBad said:
Im unable to get anywhere. It still has stock recovery and I cannot get to the screen where I can wipe. Im not great at this sort of thing but Im trying.
Click to expand...
Click to collapse
to flash custom recovery, use this (method two on the page)
EDIT: original post (http://forum.xda-developers.com/showthread.php?t=1056847)
Thank you guys for all your help. The instructions helped me out. Im very thankful. I can now rest better knowing that my sons school nurse can contact me if needed. Have a great night.
no more force closes? sounds good
feel free to post again if you have any more problems
sweetnsour said:
i think you would be better off starting from scratch
1. remove your sd card from your phone and plug it in your computer
2. download the latest rom here
3. download gapps from the download links at the bottom of this page
4. transfer both files onto the sd card and put it back into your phone.
5. with your phone off, boot your phone into recovery by holding vol down+power
6. wipe data, cache, and dalvik cache
7. flash only the cm7 file
8. reboot normally
9. reboot into recovery
10. flash gapps
11. reboot normally
after you flash one file, it is highly recommended that you reboot before you flash another file (if your friend didnt do this, this may have been the problem)
Click to expand...
Click to collapse
....touché
Hi there,
I need some help here. My wife's Sprint Nexus S is acting up - keep popping messages such as "Unfortunately XXX has stopped." So I decided to do a hard reset. I followed the instructions but weirdly the phone did not do it. It acted like doing the hard resetting but then rebooted with nothing changed. I tried both the software way - Settings, factory reset, and the hardware way - Vol up button + Power, then recovery, then Vol up + Power again at the Android with exclamation image, chose "Wipe all data and factory reset." However, the phone boots with nothing changed.
Can anyone help me with this? What else can I try?
Thanks much in advance.
<DELETED>
You could try fixing the permissions on the files through Rom Manager; it fixes a lot of Force Close generally.
kwudude said:
Have you tried installing a custom recovery and doing a hard reset through that route yet? E.G. ClockworkMod or TWRP
Click to expand...
Click to collapse
Thanks. I will give it a try. Can you point me to some instructions / files for downloading, etc.?
Cpu.gastronomy said:
You could try fixing the permissions on the files through Rom Manager; it fixes a lot of Force Close generally.
Click to expand...
Click to collapse
This one is actually the Sprint stock rom untouched. So... no Rom Manager on it. Thanks anyway. I guess a custom recovery is the only way to go now...
<DELETED>
I wouldn't install a custom recovery, and ultimately technically void your warranty, for the sole purpose of resetting it though...
Just use a one click root tool, it flashes superuser, cmw, but keeps the rest of the (stock) rom you're on!
---===:::Greetzz, jojoost:::===---
Sent from my iPad using Tapatalk HD
Thanks to you all for all the good suggestions. I have tried several things but did not succeed.
1. Flashed a clockworkmod recovery. That was successful. So I went ahead to use its factory reset function. The process completed without error but once rebooted, the phone remains the same as before.
2. Connected the phone to a PC, turned on USB storage, copied a ROM image zip file to a folder. Then tried to install it through Recovery. But the file I copied was nowhere to be found.
3. Put then phone into the bootloader mode, connected to PC, use fastboot to flash boot, system, recovery, userdata, radio image files. All went through with any issue. Rebooted, phone is the same.
In short, whatever I do, the phone remains the same. No changes can be made.
I also tried the one-click tool but could not proceed ahead. It required USB debugging turned on. I turned it on, the check mark was there, but it was really NOT turned on because on the PC, the message is that it is not on. On the phone, if I switch to a different application, or simply go back one step, and then go to developer option, the checkmark was not turned on.
It feels like the internal memory/storage becomes read-only. No changes can be made. I am not sure if the hardware is bad, or some permission issue.
Any ideas that I should try next?
From what I read and understand, I think I had a bad nand problem. Guess time to let the phone go RIP.
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
AndroidKills said:
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
Click to expand...
Click to collapse
I would recommend to flash the stock image to get the phone running again and not use toolkits anymore.
Look here for how to flash a factory image: http://forum.xda-developers.com/showthread.php?t=2513701.
gee2012 said:
I would recommend to flash the stock image to get the phone running again and not use toolkits anymore.
Look here to flash a factory image: http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
yeah i figured i should flash stock back, but the problem is trying to push the file or something. but ill look into that link asap!
thanks for the quick response
You'd probably do best to start from the top by reflashing the stock image... http://forum.xda-developers.com/showthread.php?t=2513701
This time don't use any toolkits or canned scripts, learn how to do each step by yourself, get familiar with all the commands, and do it yourself. You're less likely to screw anything up that way.
AndroidKills said:
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
Click to expand...
Click to collapse
I had the exactly same situation before. What I did was a factory reset by using the wiping function in TWRP, Then you get a freshly-new system. Hopefully you have backed up your data.
Guys stop flashing the cache it really isn't needed and causes issues... I haven't done it since Android 4.3 and not had one problem
Sent from my Nexus 5 using Tapatalk
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