I did an OTA update from Cyanogen mod 10.1 to 10.2, and it broke a bunch of my google services (play store, calendar and contact sync, etc). I assume I need to update to a newer version of the gapps since I'm now on a newer version of android. I got the gapps for this version of CM/Android, but I can't seem to install it. I try to boot into clockworkmod to install the gapps by holding volume down and power when I turn the phone one, but instead of clockworkmod I get a screen with the android logo that says "a custom os can cause critical problems in phone and installed applications" and gives me the option to cancel or continue (Could be Odin? I saw that somewhere). Cancel reboots the phone, continue goes into some other screen that says it is loading custom OS and not to power off the device. It stayed on this screen for about half an hour at which point I gave up and removed the battery. This didn't seem to have any negative effect on the phone.
How do I get back to clockworkmod so I can update my gapps? Is there a better way to update my gapps?
Volume UP and power. Down puts you in download (Odin) mode.
Or you could just reboot to recovery from the expanded power menu in CM.
Sent from my SPH-L720 using Tapatalk
Related
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
If you have recovery, you should be fine. Just flash your favorite image and wipe your userdata.
DOD1 said:
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
Click to expand...
Click to collapse
Holding Home + Power is supposed to take you into the recovery image.
At the bottom of your recovery image does it say Amon Ra 1.5.2 or 1.6.2 or something like that?
If your phones rooted then just wipe and reinstall you rom.
Like lets say your doing the new cyanmod
you apply zip
DR83
With out rebooting apply zip
Cyanmod-rom 1.4xxxx
If it boots back into Android System recovery Utility just hold home and back again.
Give it time to write its radio and its first time rebooting it says on the boot screen for a awhile some longer then others.
This site has always helped me its better to see the instructions rather then read them.
http://www.google.com/search?q=the+...s=org.mozilla:en-US:official&client=firefox-a
ThinkPad Tablet A400
Android v. 4.0.3
Have an app that needs to run on Android 4.1 and quickly found out this 2 year old device was pretty much left unsupported since about 3 months after I bought it in May of 2012. So, I located the links to xda-developers and dove into the install process.
Got the device to Root following install directions etc.
Cannot get the device to reboot into recovery mode from ROM Manager nor via ROM Installer.
Tried installing the CyanogenMod v0.9 anyway from inside either aforementioned utility (from the .zip file), just reboots back to the normal state.
I'd pay to download & install Android 4.1 on this device, seriously...just lost 6 hours of time attempting to do this ROM upgrade.
any suggestions?
First thing that comes to mind is that you should use the volume up button multi-press on device power-up to get to Recovery Mode.
pwstein said:
First thing that comes to mind is that you should use the volume up button multi-press on device power-up to get to Recovery Mode.
Click to expand...
Click to collapse
I've tried various combinations of that Vol button....still stubbornly refuses to go to CWM.
Now, I am running Android 4.0.3..perhaps that is the issue, ie. perhaps the CWM image file was intended to be used on TPTs running Android 3.x.
It'd be nice to go to a site and buy a $50 OS load....
Well....wonders never cease. I happened across a post talking about the TECHNIQUE to reboot the TPT into CWM...so, sure enough...I got the puppy into CWM.
HERE 'tis for the rest of us nuves out there:
Entering/Booting CWM Recovery on the Thinkpad Tablet
Shut down your Thinkpad Tablet
Press the power button until the Tablet vibrates
Keep pressing and releasing the volume up button until you see Booting Recovery Kernel Image in the upper left corner. It's all about timing of when the volume up button is pressed. That's why it's a good idea to just keep on pressing and releasing the button until the message appears.
Well i continued on with the Jelly Bean load from the xda-developers...and after reboot to ver 0.92 the tpt seemed to freeze on the os boot screen.
So, i fell back to the 4.0.3 os and will read-up on what can freeze the reboot into 4.1 android.
CWM is a cool program..gotta say it.
Can't get it to install CWM
Tried numerous times but now I have lost my original recovery and it just loops,
Changed permissions but won't go and when I am in the recovery boot after pushing the volume button it just reboots as there is nothing there suggestions?
Honestly, the best thing you could do is get something newer/better supported. I hate saying that, because I bought the 64gb version right around the same time you did. The tablet had so much potential with the pen, USB, sd slot, and even pci-e, but it suffered from non-existant Lenovo support, and very little dev support. Koshu's work on it was amazing, but without trim I feel like I have to constantly wipe and start fresh to do anything with it. Clearing dalvik from time to time helps, but not as much.
I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
If someone here can help you, they will. But you might have better luck asking over at http://forum.xda-developers.com/galaxy-s4-att as this is the International S4 section.
Sorry, I didn't catch that. Thank you.
Just for the record, I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.
Just a quick suggestion...
You just need to hold down both VOLUME buttons + POWER button + HOME key to REBOOT. No need to CANCEL, etc. This is how to reboot at any stage.
So, I installed this new rom: Commotio Android 6.0.1 and with it the latest open gapps for Android 6.0.
I rebooted the device and everything was fine and I got to the setup wizard, chose the language, chose the wifi, but after chosing "No thanks" when asked if I got another device, it just says that "Google play services has stopped working".
The thing is, that I can't get to recovery, or I would've flashed another gapps package. I mean I can fix it all by going to download mode and flash stock rom then go back to my custom rom. But that just takes longer and I don't have the time right now.
Edit: By experience I know this problem is caused by the Gapps package. Because I've solved it many times before by flashing other Gapps packages
Is there a way I can just bypass the setup wizard??
OK, I figured this by (accidently) rebooting into safe mode. I did this by turning the phone off, holding power, volume up and down buttons and releaasing only the power button when logo shows up. Then I continued normally with the setup wizard but it didn't ask me a couple of things, witch actually made it work!
Remove sim card and reboot without connect to WiFi and when to choose mouthed of internet connection do not choose ethir WiFi or mobile data that work on miui ROM and all lp stock ROM (normally I do not install gapps with aosp because I love to try fast experience of android)
Not sure I am posting in the right spot, but pretty sure the people that can answer are in this section.
After putting it off for months, I upgraded my 6T T Mobile converted to international to OOS 10.3.3 with the ElemetalX kernel, and xxxNoLimits 10.2. Did this several days ago, no problems. Great battery, smooth performance. Even getting 2 days with my VPN on and mock location set to "always".
I went into app ops and noticed almost every app now has "access location from media" and started going through and denying that permission for almost, if not all, the apps. I remember a couple of system apps I did that to. Google play framework being one of them, and, I think, google play services. There may have been 1 or 2 more system apps I did this with also.
I do not have a google account on my phone. I don't want to make it any easier for my pocket tracking device to track me than I have to.
I added an open source mock location app a day or so ago, not problems.
About 5 or so minutes after finishing up in app opps, I went to get the kiddo some food and looked down and noticed my phone rebooting. Now, it is in an endless boot loop.
I can hold power + up volume and get it to power down, but can't get back into TWRP recovery. Figured a quick reflash puts me back to zero and I can start over.....more carefully....but the phone is not cooperating.
I should be able to use adb and flash TWRP that way and use adb to reboot to recovery ( going to have to brush up on the how to before I start though.).
Any thoughts as to WHAT I have done and WHY I am now stuck on endless boot( w XXX animation )??
Is there an easy fix I am overlooking?
Thanks in advance,
JC
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool
Can you get into fastboot? Then you might be able to boot TWRP again temporarily?
Thanks, that gets my into TWRP, unfortunately, my dumb ass deleted the last OTA update after I flashed it. Should be able to side load it onto the phone, then flash it via TWRP.
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
PattayaGlock said:
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
Click to expand...
Click to collapse
Flash twrp recovery via adb commands, you'll find tutorials on several XDA forums or YouTube