So I recently installed CM and I forgot to also install GApps. I tried downloading those and flashing them onto my phone via Clockwork recovery and suddenly I got a message saying that the Android Keyboard has stopped working. Now I want to go back to the stock rom, and possibly try CM again some other time I read that you can do this with several steps involving Odin, except I use a Mac (Odin is only Windows), and I'm sort of a noob at these things, so any help or suggestions would be appreciated.
I rooted my SCH 1535 and installed CM Version 11-20140215-UNOFFICIAL-d2vzw. Android 4.4.2 (Baseband: l535VRBLMD3) (Kernel:3.4.80-cm
It was working OK except in order to see my WiFi I had to reboot every time WiFi was turned off.
Plus I was having trouble updating ROMs with ROM Manager.
I had both TWRP & CM installed, although the phone defaulted to TWRP in recovery.
I downloaded seveeral CM ROMs via the CM updater in Settings > About Phone & wasn't able to flash.
So, I (stupidly) WIPED with TWRP
Now, I still have the CM KitKat ROM on my phone but when I try Play Store it starts & immediately closes.
Android Keyboard stops as soon as I boot up, so i can't log even into my Google account.
I'm pretty sure I'm no longer rooted & there's no recovery - in fact the Return, Menu & Volume buttons don't seem to work.
Most of my apps are gone except for Google & Samsung, but I can't log in.
I did do a nandroid backup & have Internal & Card backups on my PC as well as Odin.
So, my question is Should I try to restore to stock and start over? (What's the best way to do that from my build?)
or do I go for a KItKat ROM? (any suggestions?)
I want to make sure I have the proper recovery, bootloader (SuperSU_Bootloader_FIXED.zip ?)
I am wide open to suggestions on the best way to proceed. I'm really hesitant to try the Factory Data Reset - since I've heard that can brick a phone completely.
Thanks!
Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
AusomBabs said:
Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
Click to expand...
Click to collapse
Good Job if You Could Explain For Latest Problem Solved. I Think this is the problem from cwm or maybe the latest rom of cwm snapshot, need to investigate for problem occured. before this update we never have this problem. "When Reset Factory Default within Setting than it will always bootlop". My a701 have this problem too. looks like @Flupkes Problem too, the different is i Reset it From Snapshot M7 this my old thread and could make the adb working because the usb slot problem.
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.
I was running KatKiss 4.4.4 on TWRP v2.6.3.0.
Lately it was getting extremely slow. Yesterday I removed some apps I didn't use anyway. I think I removed too much perhaps because today suddenly gapps and many other things started crashing.
I thought I'd just reinstall it, and discovered there's now a KatKiss 6.0.029:
https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496
so I downloaded it, and all the other files, rebooted into TWRP and wiped, and tried the install - it just left me with a boot loop. Ugh.
Got back into TWRP and happened to format everything. Then I installed Universal Naked Driver 0.72 in Win10.
Current behaviour:
Regular reset: boot loop.
Power+up: APX mode.
Power+down: tiny menu, then boot loop after cold boot.
Power+down+up: TWRP.
EasyFlasher asks me to go into APX, then I select one of TWRP 2.2.1 and RogueXM and Roach CWM and even the WW_epaduser9_2_1_24UpdateLauncher.zip file, but in all cases it's just the same. There's some text output, then suddenly a 0.001ms black popup disappearing before I can read it, then the regular window says OK. BUT... there is no change at all.
Any idea what I can try? I searched a lot before deciding to ask here.
The KatKiss link above assumes that the files are already inside the TF101.
How do I put the files into the TF101? What is the next step?
After mannnnnnny hours, I actually managed to install and run the Asus ROM.
I went on to TWRP 2.8.1.1, KatKiss 6.0.029 and the belonging files. Now it's booting up Android, but... not very far.
It keeps complaining with many popups "Google Play services stopped". Is that normal for a fresh ROM?
I add Wifi - then it gets stuck on Checking Connection "it can take a while". It's now more than half an hour. How long is a "while" normally?
I gave up on KitKat 6 and went back to 4.4.4 which then starts.
Still the weird frequent popups "Google Play services stopped".
Reinstalled three times now (KitKat and gapps) and still the same problem.
Could this be a hardware problem?
Well, for all you who read all the above (no one? lol), it is not a hardware problem. It's google messing up: https://forum.xda-developers.com/ee...google-play-services-update-breaking-t3555444