Woke up this morning, unplugged my touchpad, and turned it on. And it's stuck in a bootloop. I've been using it daily since release and updated to the latest alpha at its release.
It's stuck on the cm7 boot animation.
I've rebooted it multiple times. No luck.
Swifted from my Atrix.
Have the same problem right now again, last time I got this I had to reinstall the system and it was so frustrating....
I'm on the same situation today for no reason ..It was working fine for over a month. Any way to solve this without reinstall ... I know alpha 3 is out so just want to update... if I'm on webos how can I get to "sd card" folder to put alpha 3 file for upgrade ?
Never mind, fixed it... transfer alpha 3 file in to root of touchpad from webos and reboot to cwm , wiped cache and dalvik cache, install zip file from sd card ..choose the latest alpha 3 zip file .. then install and reboot.. that took care of cm7 endless bootloop and got alpha 3 installed as well....
Mentioning you have a bootloop and not giving the output of logcat helps no one.
Total wipe/reinstalled to fix it, right before alpha3 got released, kinda pissed at the timing.
Swifted from my Atrix.
Related
I had my HP Touchpad working with the last 3 versions of CM7 up until Alpha 3.5. Once that came out I rebooted into Recovery, wiped data, cache, and dalvik and when to install the cm7 alpha 3.5.zip. In the very beginning of the install the touchpad restarted. So I wiped and retried a couple times with alpha 2 and alpha 3 however it still did the same thing. Next I did a secure wipe in webos and used the hp webosdoctor 3.0.4 from the hp login website (not command line) and restored the unit. Then I went back to WebOS, created the cminstall all over again and tried to use acmeinstall again however I ran into the same thing with the touchpad restarting at the very beginning of the cm7 install.
My touchpad is working however I am unable to get cm7 back on it again.
Any suggestions would be great.
Having enjoyed CM7, I decided to try out CM9 with the latest version Alpha 0.04 on my NT 16GB. Install went smoothly and was able to boot into CM9 but as soon as I try to change the wallpaper it rebooted. Then I tried to install an app from the Play store and it rebooted again. It rebooted every time I did either of these things.
I tried the newboot.zip fix from succulent and the instructions mentioned here http://forum.xda-developers.com/showpost.php?p=26694005&postcount=609 but it didn't fix the problem.
Then I tried installing CM9 from rooted stock 1.4.2 and I'm encountering the same problems. I've also noticed that it seems to reboot approx. 10-15mins after boot no matter what i'm doing.
Any help with this problem would be appreciated.
I have a 16GB and I have not experienced this issue upon initial installation of .04 or after flashing the fix.
Have you been wiping data/cache prior to installing?
Yes, I have been wiping data/cache prior to installing.
This was my first attempt at CM9 and I didn't have this problem with rooted stock or CM7.
Fresh downloads of all the zips on another computer seems to have helped. Going on 3hrs without reboot.
Hello XDA,
Up until last week, I was happily using my Transformer Prime tablet with CM9 Release Candidate 2 and AOKP Milestone 6. Then my Galaxy Nexus came in the mail and I fell in love with JellyBean and I wanted it immediately. I downloaded the latest CM10 Nightly. I started downloading every time GooManager told me there was an available update.
So I kept updating until one day GooManager helped me download a version of the CM9 NIGHTLY instead of the CM10. My tablet was then stuck in the boot animation until the battery died. I wiped and then tried to re-flash the rom hoping I won't be stuck but I was stuck again. I don't know how to add any files to my tablet since the only time it functions is when I'm in TWRP and I can't get past the boot animation. I can't update my TWRP because I don't know how, so I don't have external SD card support either. I had ONE recovery image from when I made the switch from CM9 to AOKP but it seems like I deleted it so I have no idea what to do.
Is it bricked? Can I fix it? I'm not getting error messages.
After flashing the latest version( pa_i9300-5.1-20150528.zip) in recovery, 'Reboot System' reboots to recovery itself. Weird! So I flashed the earlier version(pa_i9300-5.1-20150520.zip) and it rebooted to system and it works. Now I get the OTA update in 'Paranoid OTA' app for the latest version that gave me problems. If I install,
1. Will there be any issues with reboot or any other related issues?
2. Should I reinstall installed apps after update?
Thanks
Not sure if related but I installed pa_i9300-5.1-20150520.zip some time ago on my i9300, everything has been working nicely. Then came the 28th update and another one earlier this month... but installing those updates just resulted in a crash after installing (as in the boot screen looping). Now my system just popped up with an 20150619 update so I thought to try again, but again it download and installs just to loop the boot screen. This time thought I afterwards decided to re-install superSU and my boeffla kernel, that seemingly did something as the phone booted and update. Now maybe this is something one have to do for each update for it to work? I'd love to know for the future as I'm no expert on this, though if you have something similar maybe that's what is required.
Organizer21 said:
Not sure if related but I installed pa_i9300-5.1-20150520.zip some time ago on my i9300, everything has been working nicely. Then came the 28th update and another one earlier this month... but installing those updates just resulted in a crash after installing (as in the boot screen looping). Now my system just popped up with an 20150619 update so I thought to try again, but again it download and installs just to loop the boot screen. This time thought I afterwards decided to re-install superSU and my boeffla kernel, that seemingly did something as the phone booted and update. Now maybe this is something one have to do for each update for it to work? I'd love to know for the future as I'm no expert on this, though if you have something similar maybe that's what is required.
Click to expand...
Click to collapse
I think flashing the Kernel as you did after the dirty flash will help. But the there is no stable Kernel available for CM12.1, even the Boeffla you are using is in the alpha stage, no support yet! So how is the battery life and stability with Boeffla Kernel?
Running No-Name ROM for 5+ months.
OTA downloaded 6 days ago.
Moved OTA file to Ext. SD
Disabled Update with debloater.
All was fine until yesterday... Woke up to dead phone battery.
Tonight, the LG shutdown sound woke me up!
When I looked, the phone had rebooted itself into TWRP!!!
Apparently, this will happen nightly now in [FONT="]perpetuity unless one of you geniuses can fix it.:laugh: [/FONT]
Try wiping Dalvik & Cache. Maybe fix permissions.
Also wouldnt hurt to update TWRP.
Or try a new Rom.
Did all that. Running latest TWRP already. Won't know if it's fixed for 24 hours.
Double0EK said:
Try wiping Dalvik & Cache. Maybe fix permissions.
Click to expand...
Click to collapse
Fixed! Thanks!:laugh: