I have a stock non-rooted s6, I've done the OTA update already, and everything seems to be working just fine. However after the update I went to wipe the cache partition and after holding the power, volume up, and home button a little android pops up with a rotating star in it's chest, and it says installing system update for several seconds before it takes me to the screen where I can do the cache wipe. I've never rooted a device, so I'm not familiar with a lot of this, but in everything I read about doing this it never mentioned the "installing system update" part. I figured it might have been part of the OTA update that wasn't completed, but I tried doing it again and had the same message pop up. Can anyone confirm if this is a normal occurence?
Thanks in advance.
I noticed this today as well. I went to wipe cache as well and had the same android guy with the "installing update". I thought something did install correctly from the update as well since in recovery there is an option to install update from ADB, external storage or cache. I would say it is nothing to be concerned over.
Well I'm glad to know it's not just me, but I wish I knew why it does that. There's a quick pop up after the Android that says something like "no command" and an icon I didn't catch. So every time you boot to recovery it goes through that little sequence before you get to the menu options. Puzzling. Thanks for the reply. Hopefully someone figures out what it means.
ac42 said:
Well I'm glad to know it's not just me, but I wish I knew why it does that. There's a quick pop up after the Android that says something like "no command" and an icon I didn't catch. So every time you boot to recovery it goes through that little sequence before you get to the menu options. Puzzling. Thanks for the reply. Hopefully someone figures out what it means.
Click to expand...
Click to collapse
just scroll down the menu to wipe cache partition
using your volume key down
then when u get to wipe cache hit power button
to select it
the it will take u up to reboot hit power button
again and your done
dont worry about the little android guy
you are NOT updating anything
Related
I've followed up to step 3 of part III on http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
When I select recovery, it shows me the n1 logo with the unlock symbol below it, then it goes to a green android with a warning triangle.
The video shows a recovery screen, and volume up + power doesn't give me the menu with the correct options.
I've tried it plugged in and not.
You didn't flash the recovery correctly, that is the stock recovery screen.
Thanks, that helped.
Well anyway, I downloaded cyanogen from here: http://theunlockr.com/downloads/android-downloads/android-roms/nexus-one-roms/
and when it booted up it kept giving me "x application failed, force close" for pretty much everything, and no matter how many times I hit force close, the messages kept coming.
So I'm trying to recover to stock for now, as I need my phone for tomorrow, and I forgot what my serial/key/build was. Is there anyway of finding that out so I know which ROM to flash?
XSafire said:
I've followed up to step 3 of part III on http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
When I select recovery, it shows me the n1 logo with the unlock symbol below it, then it goes to a green android with a warning triangle.
The video shows a recovery screen, and volume up + power doesn't give me the menu with the correct options.
I've tried it plugged in and not.
Click to expand...
Click to collapse
Did you remove the two scripts like you were told? /system/etc/install-recovery.sh and /system/recovery-from-boot.p
XSafire said:
Thanks, that helped.
Well anyway, I downloaded cyanogen from here: http://theunlockr.com/downloads/android-downloads/android-roms/nexus-one-roms/
and when it booted up it kept giving me "x application failed, force close" for pretty much everything, and no matter how many times I hit force close, the messages kept coming.
So I'm trying to recover to stock for now, as I need my phone for tomorrow, and I forgot what my serial/key/build was. Is there anyway of finding that out so I know which ROM to flash?
Click to expand...
Click to collapse
Wipe /data and /cache in recovery before reinstalling the custom rom should address the force close issues.
I have G1 sitting around that I never messed with until last night, so if it's bricked, it's not a big deal. The phone will turn on, and loop through the splash screen. The only way it will boot is in safe mode. When trying to do ANYTHING in safe mode (aside from power down), everything will FC. If i go into the recovery menu with the Home plus End key sequence, I get the "can't open cache recovery command". I've tried to install RC33 in that screen, and get "installation interrupted".
The phone was given to me, so I really don't know if it was rooted or what was on it before. I do remember it worked, and just one day stopped working. When it was working I never saw a superuser icon or any other apps you usually see with a root. Thanks in advance for any help.
No one? Is there just a full update I can throw on the SD card and get it running?
Try formatting the sd card fat32, putting dreaimg.nbh(search) on it. Then, put it in the phone and boot with camera+power. Follow the onscreen instructions, and hopefully it'll work.
If it doesn't, not my fault. Good luck!
Thanks Michael, but I did that already and it really didnt change anything. I noticed the recovery menu looks a bit different, and when I go to safemode, the "android" looks different, but thats it. Still cant boot, and still shows there is no recovery in the recovery menu.
Just prepping my o2x to return for a replacement (too many random reboots, charge unplug-of-death) and the tech support on the phone wanted to "confirm how I performed a factory reset".
I've done it several times with CWM, but she obviously wants to check the procedure with the stock recovery otherwise it's obvious I've flashed something.
I ran the stock nvflash to restore the phone and recovery to default as I'll need to do this before returning anyway. Now when I hold vol-down and power, I get the lg logo, then the lg logo and a progress bar, then a box with an arrow coming out and pointing to a green droid and a progress bar and then after about ten seconds, it reboots.
In adb I can then see that the reboot is now rebuilding the /data from fresh. Sounds all correct - it's done a factory reset nicely.
Can anyone confirm if that is the correct way the stock recovery "reset to default" works..? No menus, no confirm..?
hbls00190 said:
Just prepping my o2x to return for a replacement (too many random reboots, charge unplug-of-death) and the tech support on the phone wanted to "confirm how I performed a factory reset".
I've done it several times with CWM, but she obviously wants to check the procedure with the stock recovery otherwise it's obvious I've flashed something.
I ran the stock nvflash to restore the phone and recovery to default as I'll need to do this before returning anyway. Now when I hold vol-down and power, I get the lg logo, then the lg logo and a progress bar, then a box with an arrow coming out and pointing to a green droid and a progress bar and then after about ten seconds, it reboots.
In adb I can then see that the reboot is now rebuilding the /data from fresh. Sounds all correct - it's done a factory reset nicely.
Can anyone confirm if that is the correct way the stock recovery "reset to default" works..? No menus, no confirm..?
Click to expand...
Click to collapse
Yes that's is stock recovery works so
Excellent - thanks for the reply. I'll get on the phone tomorrow and get a replacement ordered. It's just so tempting to re-root it and start removing all the LG crap, but I must resist!
Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.
TPizzle said:
Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.
Click to expand...
Click to collapse
When you wiped the cache, did you get the dalvik, too?
Yes I wiped the dalvik as well, but all that does is make the initial boot longer (when I manage to get it to successfully boot that is).
Did you try to reinstall/re flash CM7? You don't lose anything by doing that, and you could do it right from Clockwork recovery. Maybe something got messed up in the installation and reinstalling it would fix it.
Will give it a shot and let you guys know. Thanks for the input. Also one more question, do you guys go through the same thing at all? Or are all your initial boots successful straight to the home screen like any other Android device. Thanks again.
TPizzle said:
Hi all, I'm having some serious booting issues on my touchpad running CM7. I always seem to get this error when I start it up:
Selected: 'boot CyanogenMod'
Loading '/boot/uImage.CyanogenMod'...OK
Checking uImage...Invalid Data CRC
BOOT FAILED!
Press SELECT to continue
, or on anything else I want to boot.
Then I have to do a power + home button restart a whole bunch of times before it successfully boots into webOS/CM7. This is a procedure I have to go through every time I turn on this device, so you can imagine it takes me anywhere from 5-10 minutes to finally get into the home screen.
I do however can see this coming, on that initial moboot screen, there is a dashed green line that randomly appears at times; this is an indication that the boot will fail. Also sometimes it goes through to booting android, but then boot loops back to moboot then displays that message again that I mentioned above.
To fix this I've been trying to avoid a full re-installation of CM7 but I've wiped the cache many times and did a full wipe back when this problem started.
Any suggestions for a fix? Thanks.
Click to expand...
Click to collapse
Sounds like you either have corruption on /boot filesystem or faulty
hardware.
I would try running webOS doctor and then re-installing moboot/CM/etc.
with ACMEInstaller. This should not require a reinstall of apps, etc.
If you still have the same after that, then you probably have some bad
hardware.
Ok so I did the suggestion of jcsullins. Did webOS doctor with latest version (3.0.5) and re-installed moboot. A funny thing happened though, after the installation of moboot, the cyanogen and clockwork settings did not show up on the moboot menu, only the webos, recovery for it, shutdown and reboot. This was fixed with another re-installation of moboot. Long story short, everything seems to be fixed, my data and settings are in tact, and I just turned it off and on (not reboot) 6 times now with each initial boot being successful. Just posting this to thank you guys and for anyone else in the future that may have this problem. Thanks again!
same problem with moboot disappearing after the update. ive reinstalled moboot three times and still cant get the menu to display the cyanogen or clockwork options.
Is there something I am doing wrong?
edit: ended up adding moboot, the original CWM, and the latest XRON build and running ACME Installer and all is well. Just cant install preware to the touchpad since i used webdoctor to install the latest update.
justininhifi said:
same problem with moboot disappearing after the update. ive reinstalled moboot three times and still cant get the menu to display the cyanogen or clockwork options.
Is there something I am doing wrong?
edit: ended up adding moboot, the original CWM, and the latest XRON build and running ACME Installer and all is well. Just cant install preware to the touchpad since i used webdoctor to install the latest update.
Click to expand...
Click to collapse
Just reroot webOS and re-install preware.
I installed the beats audio installer and things seemed to be working ok, except that my phone volume was either lower than expected or overly loud where the external speaker had distortion. So I opened the app and clicked uninstall from within it. Afterwards I rebooted my phone as it said and now it's stuck in a bootloop. My brother rooted my phone for me when I went home for a visit for me. I'm not root or phone savvy. I live in South Florida and I can't make the 12 hour drive back there anytime soon. How do I fix this? I had performed a nandroid backup but I noticed my external storage was 100% full after I did that a few times. So I went into storage in settings and deleted the clockwork mod stuff sitting at 6.86 gigs. That must have been the backup in there I know. Now with no backup I did a factory reset, still a bootloop. Phone is rooted still. I'm thinking maybe the audio drivers were damaged. Please help how do I fix this? Thanks!
darinthereal said:
I installed the beats audio installer and things seemed to be working ok, except that my phone volume was either lower than expected or overly loud where the external speaker had distortion. So I opened the app and clicked uninstall from within it. Afterwards I rebooted my phone as it said and now it's stuck in a bootloop. My brother rooted my phone for me when I went home for a visit for me. I'm not root or phone savvy. I live in South Florida and I can't make the 12 hour drive back there anytime soon. How do I fix this? I had performed a nandroid backup but I noticed my external storage was 100% full after I did that a few times. So I went into storage in settings and deleted the clockwork mod stuff sitting at 6.86 gigs. That must have been the backup in there I know. Now with no backup I did a factory reset, still a bootloop. Phone is rooted still. I'm thinking maybe the audio drivers were damaged. Please help how do I fix this? Thanks!
Click to expand...
Click to collapse
I don't think the audio drivers were damaged. A factory reset wipes the /data partition, which is where all the personal data is stored, but it does not touch the /system partition, which is probably where the Beats Audio installs/modifies files, since it probably needs root (I'm just assuming, don't know which app that is nor what it does).
Since you have Clockwork Mod (CWM), I'm assuming your recovery is still working, right? When you start up your phone, the LED should turn on (either blue or purple), and then you should press volume up/down to enter recovery. Do you have an external SD card?
yes I have an external sd card
Antiga Prime said:
I don't think the audio drivers were damaged. A factory reset wipes the /data partition, which is where all the personal data is stored, but it does not touch the /system partition, which is probably where the Beats Audio installs/modifies files, since it probably needs root (I'm just assuming, don't know which app that is nor what it does).
Since you have Clockwork Mod (CWM), I'm assuming your recovery is still working, right? When you start up your phone, the LED should turn on (either blue or purple), and then you should press volume up/down to enter recovery. Do you have an external SD card?
Click to expand...
Click to collapse
Thanks for replying, I'm crushed. When I boot the phone the led goes red then purple. If I hold down volume down and power the purple becomes yellow then it goes into recovery but I have absolutely nothing to backup from. If I reboot it bootloops.
also...
darinthereal said:
Thanks for replying, I'm crushed. When I boot the phone the led goes red then purple. If I hold down volume down and power the purple becomes yellow then it goes into recovery but I have absolutely nothing to backup from. If I reboot it bootloops.
Click to expand...
Click to collapse
The phone says there is no OS now and when I power up it's stuck on the Sony logo. At this point am I able to install a custom rom say a stable version of Kit Kat? If so, where do I find one and how do I install it? I don't know how to get into download mode I'm afraid to because I don't want to hard brick my phone. Thanks!
darinthereal said:
The phone says there is no OS now and when I power up it's stuck on the Sony logo. At this point am I able to install a custom rom say a stable version of Kit Kat? If so, where do I find one and how do I install it? I don't know how to get into download mode I'm afraid to because I don't want to hard brick my phone. Thanks!
Click to expand...
Click to collapse
Ok, since you're talking about custom ROMs, I'm assuming you have an unlocked bootloader. You won't hardbrick your phone unless you mess up real bad, although I am wondering how on earth you ended up with "no OS". That would only happen if you wiped the /system partition. Here's what you're going to do:
1.- Download the links number 1,3 and 4 from this post.
2.- Connect your SDcard to your computer with a USB adapter or an SD adapter, and copy all those downloaded files to your external SD card.
3.- Once that is done, put the SDcard back in your phone, and turn it on and enter recovery.
4.- Navigate recovery with volume buttons up/down and Power button for enter, and select the "Wipe Data" option, which is the same as a Factory Reset (just for good measure, since you already did this); it will ask you to confirm the operation, select "Yes".
5.- Do the same with "Wipe Cache".
6.- Go to "Install ZIP from SDcard1", and, with vol +/- navigate to the file you downloaded in number 1 from the link above (filename should be "LT29i_Rockers_X_ROM_v1.2_03292014-signed.zip"), and press the Power button to confirm that you want to flash that file, then confirm with "Yes".
7.- Once that completes, do the same for the file from number 3 (filename should be "LT29i_9.2.A.1.199_kernel.zip").
8.- Finally, do the same with the file from number 4 (filename should be "UPDATE-SuperSU-v1.94.zip").
9.- Reboot your phone.
It should power up now, and if you have any doubts regarding the procedure, post back and/or read through the original thread here.
I just posted how to do method 2, described in the original link.
EDIT: In my opinion, there is no "stable" version of Kitkat. FXP has a CM11 ROM, but it has kernel issues regarding battery life; if you can live with a battery not lasting more than 7 - 9 hours, maybe you'd want to try that, but I wouldn't recommend it.
http://fxpblog.co/qualcomm-krait-200-family-1st-gen/sony-xperia-tx/
Antiga Prime said:
Ok, since you're talking about custom ROMs, I'm assuming you have an unlocked bootloader. You won't hardbrick your phone unless you mess up real bad, although I am wondering how on earth you ended up with "no OS". That would only happen if you wiped the /system partition. Here's what you're going to do:
1.- Download the links number 1,3 and 4 from this post.
2.- Connect your SDcard to your computer with a USB adapter or an SD adapter, and copy all those downloaded files to your external SD card.
3.- Once that is done, put the SDcard back in your phone, and turn it on and enter recovery.
4.- Navigate recovery with volume buttons up/down and Power button for enter, and select the "Wipe Data" option, which is the same as a Factory Reset (just for good measure, since you already did this); it will ask you to confirm the operation, select "Yes".
5.- Do the same with "Wipe Cache".
6.- Go to "Install ZIP from SDcard1", and, with vol +/- navigate to the file you downloaded in number 1 from the link above (filename should be "LT29i_Rockers_X_ROM_v1.2_03292014-signed.zip"), and press the Power button to confirm that you want to flash that file, then confirm with "Yes".
7.- Once that completes, do the same for the file from number 3 (filename should be "LT29i_9.2.A.1.199_kernel.zip").
8.- Finally, do the same with the file from number 4 (filename should be "UPDATE-SuperSU-v1.94.zip").
9.- Reboot your phone.
It should power up now, and if you have any doubts regarding the procedure, post back and/or read through the original thread here.
I just posted how to do method 2, described in the original link.
EDIT: In my opinion, there is no "stable" version of Kitkat. FXP has a CM11 ROM, but it has kernel issues regarding battery life; if you can live with a battery not lasting more than 7 - 9 hours, maybe you'd want to try that, but I wouldn't recommend it.
http://fxpblog.co/qualcomm-krait-200-family-1st-gen/sony-xperia-tx/
Click to expand...
Click to collapse
YES the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. THANKS! I'm going to try this. I erased the OS last night. Before all of this I installed One Click Scroll from GooglePlay. It worked perfectly but it install TeamWin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok I'll let you know how it goes thank you even if this doesn't work!
darinthereal said:
YES the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. THANKS! I'm going to try this. I erased the OS last night. Before all of this I installed One Click Scroll from GooglePlay. It worked perfectly but it install TeamWin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok I'll let you know how it goes thank you even if this doesn't work!
Click to expand...
Click to collapse
Well, directions still apply to TWRP; wipe /data and /cache, flash files in the order posted previously, then reboot. Good luck.
I love you!
darinthereal said:
yes the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. Thanks! I'm going to try this. I erased the os last night. Before all of this i installed one click scroll from googleplay. It worked perfectly but it install teamwin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok i'll let you know how it goes thank you even if this doesn't work!
Click to expand...
Click to collapse
i love you thank you how do i thank matt?!!!!!!!!!
darinthereal said:
i love you thank you how do i thank matt?!!!!!!!!!
Click to expand...
Click to collapse
Glad to be of help. If you must, just clicking on the "Thanks" button on a post is good, that's what it's for. And you'll have to probably find one of matt's posts too (don't know who you're talking about) and do the same, I guess.
THANKS!
Where is the thanks button? Lol
darinthereal said:
Where is the thanks button? Lol
Click to expand...
Click to collapse
Under each post, left side of the screen.
THANKS!
darinthereal said:
i love you thank you how do i thank matt?!!!!!!!!!
Click to expand...
Click to collapse
JUST CLICKED EVERY THANKS BUTTON THAT I COULD FIND THANK GOD FOR YOU! I had to come to my laptop the thanks button don't show in my mobile boat browser weird. Again thank you dearly Antiga Prime, cool name btw!