So I had quite the experience upgrading to lollipop.
Started with:
CM11 4.4.4 Nightly
600mb system
Philz Touch
1) I flashed Flintman TWRP within Philz Touch 6.0.4.9.
2) Downloaded Milaq's CM12 and PA Gapps 5.0.2. Pico.
3) Booted into TWRP, and created a backup.
4) Ran a factory reset in TWRP, and attempted to flash CM12. I had no idea where the /Downloads/ folder was, and I ended up finding it by going to /Internal Storage/data/media/0/Downloads
5) Encountered an error in mounting system, nothing was flashing.
6) Booted the touchpad into Web OS Recovery, and ran TPToolbox. An error was detected in the system partition, and 'Repair Partition' failed.
7) I then booted into WebOS and ran Preware 'Tailor'. Tailor also failed on 'Check Filesystem'. I then proceeded to delete the Android system partition. I never figured out why my system became corrupted.
8) I removed 400 mb from Android Data, and created Android System with 1000mb.
9) I booted back into TWRP, and successfully flashed CM12, and gapps.
10) After booting, I then proceeded to download Xposed for lollipop. I activated root in developer settings,.
11) I booted in to TWRP, and flashed Xposed, and rebooted the tablet.
12) All subsequent apps resulted in a -504 error when installing. It was discovered that Xposed was the culprit.
13) I then reflashed cm12, without xposed.
14) I downloaded Trickster MOD and set my CPU to 1782 Mhz and performance governor.
15) I experienced odd slowdowns and crashes when any audio played (include keyboard taps). I then proceeded to flash Viper4Android. I installed the driver, rebooted, and now my Touchpad audio sounds great! Make sure to select the best audio quality, and play with the Viper settings!
I now have a blazingly fast lollipop tablet. I tried 5.1.1, but I find it too unstable for daily use. The next step is to figure out how to get Xposed working.
Thanks to the devs for the hard work in development!
fwiw, all 4.4.4 and 5.x roms that I have tried excepting the Evervolv 5.0.2 last nightly have problems with the sound locking up the system, unless you turn off "OK Google" detection completely.
EricBlade said:
fwiw, all 4.4.4 and 5.x roms that I have tried excepting the Evervolv 5.0.2 last nightly have problems with the sound locking up the system, unless you turn off "OK Google" detection completely.
Click to expand...
Click to collapse
I had similar issues with the exception of Evervolv. Their 5.1.1 is even pretty solid now at this point; they're setting their sights on Marshmallow next!
rfoster2009 said:
I had similar issues with the exception of Evervolv. Their 5.1.1 is even pretty solid now at this point; they're setting their sights on Marshmallow next!
Click to expand...
Click to collapse
I still gget that lockup in 511.. hoping 6 kills the weird bugs
Sent from my Touchpad using Tapatalk
Interesting yet annoying
BuffMcBigHuge said:
So I had quite the experience upgrading to lollipop.
Started with:
CM11 4.4.4 Nightly
600mb system
Philz Touch
1) I flashed Flintman TWRP within Philz Touch 6.0.4.9.
2) Downloaded Milaq's CM12 and PA Gapps 5.0.2. Pico.
3) Booted into TWRP, and created a backup.
4) Ran a factory reset in TWRP, and attempted to flash CM12. I had no idea where the /Downloads/ folder was, and I ended up finding it by going to /Internal Storage/data/media/0/Downloads
5) Encountered an error in mounting system, nothing was flashing.
6) Booted the touchpad into Web OS Recovery, and ran TPToolbox. An error was detected in the system partition, and 'Repair Partition' failed.
7) I then booted into WebOS and ran Preware 'Tailor'. Tailor also failed on 'Check Filesystem'. I then proceeded to delete the Android system partition. I never figured out why my system became corrupted.
8) I removed 400 mb from Android Data, and created Android System with 1000mb.
9) I booted back into TWRP, and successfully flashed CM12, and gapps.
10) After booting, I then proceeded to download Xposed for lollipop. I activated root in developer settings,.
11) I booted in to TWRP, and flashed Xposed, and rebooted the tablet.
12) All subsequent apps resulted in a -504 error when installing. It was discovered that Xposed was the culprit.
13) I then reflashed cm12, without xposed.
14) I downloaded Trickster MOD and set my CPU to 1782 Mhz and performance governor.
15) I experienced odd slowdowns and crashes when any audio played (include keyboard taps). I then proceeded to flash Viper4Android. I installed the driver, rebooted, and now my Touchpad audio sounds great! Make sure to select the best audio quality, and play with the Viper settings!
I now have a blazingly fast lollipop tablet. I tried 5.1.1, but I find it too unstable for daily use. The next step is to figure out how to get Xposed working.
Thanks to the devs for the hard work in development!
Click to expand...
Click to collapse
I have been hving fun running Milaq 4.4 and i seen this post but Milaq's link and the link to the gapps and Exposed all are well i have no Idea how to download from those sites. IE can't find a link, only more info into what they are. can you check this out? repost if needed , thanks for sharing.. I hope i can get these files downloaded...
Related
Hello, I'm having a bit of an issue here I can't install a ROM after trying CM10.1.
I was using CM10, up until awhile, when I deiced to give CM 10.1 a try (Alpha build I'm aware of the risks).
I have installed CM10.1 using Rom Manager Premium. The installation progress went smooth without any errors, before installing I've made a backup of my current ROM.
Once CM10.1 finished optimizing application it started giving errors, that it can't load up Setup Wizard stopped from working, I have rebooted into CMW, wiped Dalvik cache and user data, I have booted up again, and was still was getting the same error, so I decided to restore my previous ROM.
But when I have booted up into CWM, I have discovered that the backup I made isn't there, not on the Internal memory and not on the SD card.
The issue I'm having is that I can't instal CM10 back, when ever I try to install CM10 ROM ZIP using CMW from external SD I get an error (Status 7)
Is there any ODIN CM10 installation route?
Thank you!
Update 1:
I have manged to flash The Official Rom, But it can't boot up, it seems like it's stock on the animation screen, the animation moves, but doesn't boot up. What might be the issue?
Update 2:
Solved the problem by wiping use data, and resting it to factory settings.
Update 3:
Got it fixed, everything is running like it used to be. Shame that I lost all my personal DATA, specially the DICM folder :/
Hello guys,
I have problems running latest official PA for GT-I9300 (Int'l).
After wiping dalvik, cache, system and data I installed rom zip and gapps zip and rebooted. Phone automatically rebooted me to recovery (TWRP 2.8.5.0).
Again I wiped everything installed rom zip and now I tried installing boeffla kernel 3.1 CM12 NG and gapps zip. After rebooting I see installing apps and when it completed all my applications forceclosed and phone rebooted. Now I keep getting optimizing apps and when it completes phone just reboots.
I tried doing same thing but with leanKernel AOSP v5.1 but I get same thing as installing no kernel.
I appreciate any kind of help. If you need more information just ask.
Thank you.
Official Paranoid is the only LP-ROM for S3, which doesn't boot with build-in kernel. So don't expect anything from that and take Gokulbalram's Inofficial.
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
TechKno said:
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
Click to expand...
Click to collapse
I haven't flashed either of those ROMs but perhaps you need different vendor images or something.
What build # are you on?
The latest is: mra58n
I personally am on Pure Nexus, and I didn't have to flash anything besides the ROM.
I just got the tablet on the 40% off deal a few weeks ago, it came with an early LP build, I first flashed the mra58n factory image, then I unlocked bootloader installed TWRP and rooted and made a backup.
Then I flashed Pure Nexus and all has been running smooth.
I would suggest giving that ROM a flash - it's been updated to Android 6.0 and runs great and battery is amazing.
andybones said:
I haven't flashed either of those ROMs but perhaps you need different vendor images or something.
What build # are you on?
The latest is: mra58n
I personally am on Pure Nexus, and I didn't have to flash anything besides the ROM.
I just got the tablet on the 40% off deal a few weeks ago, it came with an early LP build, I first flashed the mra58n factory image, then I unlocked bootloader installed TWRP and rooted and made a backup.
Then I flashed Pure Nexus and all has been running smooth.
I would suggest giving that ROM a flash - it's been updated to Android 6.0 and runs great and battery is amazing.
Click to expand...
Click to collapse
Thanks for the response, just tried flashing Pure Nexus to it but with the same thing happening. I know it's only been 5 mins so far but it surely should have atleast moved onto the OS's splash?
This was the version I used: pure_nexus_flounder-5.1.1-20150817.zip
I shouldn't need a working OS installed as the base due to the fact that installing a new OS would just overwrite it?
TechKno said:
Thanks for the response, just tried flashing Pure Nexus to it but with the same thing happening. I know it's only been 5 mins so far but it surely should have atleast moved onto the OS's splash?
This was the version I used: pure_nexus_flounder-5.1.1-20150817.zip
I shouldn't need a working OS installed as the base due to the fact that installing a new OS would just overwrite it?
Click to expand...
Click to collapse
that is Android 5.1.1 Lollipop
We want Android 6.0 Marshmallow
pure_nexus_flounder-6.0-20151113.zip
If this doesn't work I would personally flash the mra58n and start over.
Make sure to wipe in recovery before flashing.
andybones said:
that is Android 5.1.1 Lollipop
We want Android 6.0 Marshmallow
If this doesn't work I would personally flash the mra58n and start over.
Click to expand...
Click to collapse
Yeah, I think he's right. Sounds like you have a mishmash of android 5.1.1 and 6.0
Start clean by flashing the latest factory image (bootloader, boot, system, data, vendor). Once that's running, then you can flash TWRP (I suggest using the custom TWRP found under the FireIce kernel thread) and install an android 6.0 custom ROM.
Whichever ROM you choose, make sure to read thru its thread carefully. There are a number of things that can cause bootloops, so be sure to follow the installation instructions for that ROM.
TechKno said:
Hey Guys,
I have an unusual issue when it comes to trying to flash custom ROM's onto my Nexus 9.
I have already unlocked the bootloaded, installed the latest version of TWRP which worked fine.
I then went to do the usual wiping everything off my tablet before going any further (Dalvik Cache, System, Data, Internal Storage and Cache)
Then I use MTP to move the ZIP's that I want to install onto the internal storage (I've tested CyanogenMod 12 and the latest version of LiquidSmooth (At seperate times) )
The install process goes okay and doesn't show up any errors.
Then when I go to reboot the Nexus 9, I get the static "Google" logo (the splash screen before the operating system's splash) and it just sits there for 12 hours until the battery slowly drains (litterally 12 Hours)
Any idea's how to fix this? I can boot back into fastboot and access the recovery. I can also restore using the softbrick option in the Nexus Tool Kit to boot back into a fully functioning Android 6.0 but obviously that's not the aim.
Thanks for taking the time to read this
Click to expand...
Click to collapse
You should erase your internal storage. It happen to me I did the same steps that you did and I had to re flash the system files all over again. Once finish I only wipe dalvik cache,cache and data and it work perfectly
Hi,
I rooted my phone back in August. I made a backup of the rooted device. I have reset it numerous times. This time it will not work. I started without gapps the first time. I re-did the backup and did gapps but my phone is stuck on android is upgrading after it optimizes apps. I have Philz touch Clock work. I also have liquid smooth but it doesn't appear when I reboot. I have the liquid smooth file on my sd so i can install ls zip and then gapps and the phone will boot up so my phone is on on. The setup wizard fails and I cant access anything. I've tried different gapps 5.1 4.4.2(orignal one), 4.4.3 not compatible. I'm assuming i didn't brick it because it does start and go to myregular phone display.I don't know if something was updated with samsung which made my backup or gapps not work correctly. Any help would be greatly appreciated. I have wiped rom, davlik, cache, installed backup...same process install liquid smooth first. Ive done my backup without gapps and it starts but all apps fail because no gapps.
I got Resurrection Remix 7.1 (official 3/15) installed and working and I have never run a custom ROM before on any phone, but I must say WOW. This work(ed) so beautifully. Very responsive and clean interface and the battery life was looking phenomenal. It was basically everything I could have wanted and then some.
Now the bad news. I was trying to run a file manager that seemed to lack root access and I clicked on SuperSu which said it needed to update, I chose "update normally" instead of via TWRP. It ran and said it succeeded but needed a reboot. Now I am in the "Get Resurrected" bootloop and I don't know if there is any way to recover at this point. I can obviously get back into TWRP and I tried wiping and re-flashing 35B bootstack and RR ROM zips. No luck.
Before this ROM I was thinking seriously of upgrading from G3 to something newer but after seeing how well this runs on the G3 hardware I don't see any reason to upgrade given how well this run, though I only had it up to test for 4-5 hours.
Any help would be appreciated. I did find another post on CM13 in bootloop from SuperSu install/update and flashing a 'make permissive selinux' fix which worked for this situation. I am wondering if it may work for RR bootloop as well? Again any help would be appreciated.
Big thanks to Rohlm who suggest system format before re-installing!
I went into the Wipe options in TWRP and selected the format data and then went through the install steps again. Data, cache, Dahlvik wipe, 35B bootstack flash, RR 7.1 flash, gapps 7.1 arm flash and I'm now "Re-Resurrected!" And I checked still have root access!
Cheers,
-Scott