Hi, I've had my Z2 tablet for a while now. Soon after opening the box, I had the device rooted and cyanogenmod installed, however, this came with a problem that i have now had for ages, whenever i install or update my CM version, it automatically wipes the recovery i have installed, and installs the crappy CM recovery. I have since tried to flash other recoveries, they say they have worked in Command Prompt, but when i boot into recovery, i am greeted by the Cyanogenmod recovery. Help please!
SGP512 Wifi only, 32GB, CM12 Nightly, latest as of 24th Feb 2015
Related
Hello,
I was running cm 10.2 and decided to upgrade to cm 11 nightly cm-11-20140707-NIGHTLY-i9300.zip.
Problem is the upgrade failed and i have been trying to recover my phone since.
Current status:
I can boot into recovery mode.
I can boot into download mode.
i can boot my device with an installed ROM but it wont load past the first boot.
I have tried:
Roms:
CM 11
CM 10
SlimBean
SlimKat
Installers:
ADB sideload
ADB push to sdcard and then install
Cyanogenmod installer.
Clockworkmod:
Newest Version
6.0.4.6
Older version that i had installed
All with the same result a rom that can't complete its first boot.
Im out of idea's at the moment and wondering if you guy's could provide me with a new course of action.
solution of samdroid did the trick of getting a rom installed.
links to files used:
cm: http://download.cyanogenmod.org/?device=i9300
gapps: http://wiki.cyanogenmod.org/w/Google_Apps
recovery: http://forum.xda-developers.com/gala...touch-t2002953
now i have to problem of no sim card, but that might be unrelated
Sporedd66 said:
Hello,
I was running cm 10.2 and decided to upgrade to cm 11 nightly cm-11-20140707-NIGHTLY-i9300.zip.
Problem is the upgrade failed and i have been trying to recover my phone since.
Current status:
I can boot into recovery mode.
I can boot into download mode.
i can boot my device with an installed ROM but it wont load past the first boot.
I have tried:
Roms:
CM 11
CM 10
SlimBean
SlimKat
Installers:
ADB sideload
ADB push to sdcard and then install
Cyanogenmod installer.
Clockworkmod:
Newest Version
6.0.4.6
Older version that i had installed
All with the same result a rom that can't complete its first boot.
Im out of idea's at the moment and wondering if you guy's could provide me with a new course of action.
Click to expand...
Click to collapse
Im not the most experienced guy out there but:
Visit the offical CM11 Thread
Then download the custom recovery thats shown there (this will only work for cm11
flash that custom recovery
then do a full wipe
reboot back to recovery
install a new cm11 rom
That /should/ if your issue, (try it without the full wipe first)
[from personal experience while upgrading from cm9 to 10]
I'm on nightly 3/21, which I installed clean yesterday. I want to update to 3/22, but the update will not work automatically in TWRP. (TWRP cannot mount e:, which is a problem I encountered several times while trying to install CM, and ended in me having to reflash to stock several times before it would work again.... Anyways, that's a separate issue.) I selected the option in Dev options to automatically update CM recovery, but this option does not seem to be working. After having selected that option, then downloading the update and selecting update, the tablet still reboots into TWRP and does nothing.
Which brings me to my question. Can I get the CM recovery img from somewhere and flash it myself in order to get the updates to work? I haven't been able to find it, and TWRP has just been a pain in the neck anyways.
Thanks!
I know this has been mentioned elsewhere for other Xperia Models, typically newer than the Z U, but I am running in to an issue where my two z ultras are trying to use the same mac address.
I wondered if there was a device specific work around for the z ultra and / if this is being addressed.
Running the latest nightly CM12 builds.
Cheers in advance.
http://d-h.st/agR
Download this zip and flash, it is a fix for when the mac address changes after flashing a custom rom.
Regards
Hi,
Thanks for the post, but unfortunately I am getting a package verification error and a footer error when I attempt to flash the package in recovery.
You are using cyanogenmod recovery, right? If so, you have to use TWRP or CWM to flash it, cm recovery have signature check and you can't turn it off, all custom recoveries have it disabled by default.
Regards
Thanks for the heads up teddy. I was using CM recovery. Installed TWRP and flashed the zip/update. However, CM12 goes tits up with TWRP every time I update CM12 and only seems to play nice with CM recovery. Gapps seems to be the issue with none stop force stops. Seems in order for this to work I have to flash TWRP, flash the mac address zip and then flash CM recovery back every time I want to update via nightly.
You can flash TWRP to the FOTAKernel partition if you don't want to flash it everytime you update rom and if you flash it, it should work like CM recovery and it will be booting instead of CM recovery. Just download an app called Rashr and install TWRP from the app I assume the fix is working for you, isn't it?
Regards
I did use rashr to install TWRP and that's when the issues arose.
Unfortunately the nightly update came through after installing TWRP so I did the update for 30th and the phone was in an unusable state via gapps force closes as mentioned. So I flashed back to CMr via the update and haven't installed the update yet.
Until I have a workable solution to the recovery issue I won't be proceeding. It will be too much hassle each time the updates arrive.
I don't think that gapps are force closing because of the recovery installed, that would be weird. Have you tried flashing another gapps? Because I have also used CM12 with TWRP and gapps and I haven't got that sort of problems, even now I am using CyanideL (CM12-based) with TWRP and on my configuration it is OK. I will try using CM12 nightlies with TWRP tomorrow and I will write you back if I found a solution
Regards
Yes, I was using the signed gapps dated late last year, but when I came across the issue I reflashed the whole of CM12 with the more recent ones dated April I think. I still had the same problem, which is when I read up and saw it was attributed to using a non-CM recovery and reset everything back to CM12 nightly + CMr, I did however keep the most recent gapps. Let me know how you get on.
Hi, does Xposed Framework not work for Xperia Z2 Tablet?
I've tried severel times but it won't work. It used to when I ran Android 4.4 on it, but ever since I've installed 5.0 and later 5.1 it will not. When I try to install it through recovery, everything seems to work fine. But then when I reboot, it just starts the bootup process, but nothing ever happens. Only thing I can do, is to turn it off, start up in recovery and reset the device.
I'm running latest official CyanogenMod (12.1-20160410-NIGHTLY-castor) with standard kernel and recovery is TWRP 2.8.7.0
My device is Castor (LTE+WiFi)
It works fine with the stock firmware, so it's probably related to Cyanogenmod.
Hi guys,
i have an old ASUS MeMOPad FHD10 LTE, which i am trying to use LineageOS with.
TLDR: suddenly no Touch input in TWRP Recovery AND LineageOS 15.1/16 after it worked at first, OTG cable with mouse/keyboard input as workaround, in stock ROM the touch input IS working without problems
I unlocked the bootloader, did a backup of stock recovery img, flashed TWRP v3.2.3-0 for [Asus_ME302KL][DUMA] (from here). I rebooted to TWRP and made a NANDROID backup and flashed LineageOS ROM 15.1 (from here)
Everything worked perfectly fine until here, i booted up LineageOS 15.1 successfully, then i tried to flash mindthegapps (from here), i noticed too late this was the 64bit Version and ofc it bugged out to hell.
I then wiped data/cache and flashed 15.1 ROM and this time i used opengapps full package for 8.1 and flashed it directly after, but on reboot LineageOS 15.1 got stuck (just rebooted after 20min loading screen).
Then after a few more steps and tinkering, including trying out Lineage 16 for ME302KL, at one point the touch input in TWRP stopped responding on entering recovery. Multiple restarts didn't help. I didn't do anything other then flashing ROMs and wiping data/cache (at some point /system too).
I plugged in an USB Mouse with OTG and was able to navigate and flash back the stock ROM from nandroid backup, the touch input worked just fine!
Then i rebooted into TWRP, still no touch. I flashed LineageOS 15.1 ROM, and to my shocking, also no touch input after booting up. Flashing back stock ROM did get it back to working again. I even flashed back the stock recovery IMG and re-flashed TWRP again, still no luck.
What else is there, that i can try?
I was thinking of fastboot erase/format in bootloader, which partitions do i have to delete for a FULL reset, since flashing back stock recovery/rom didn't help?
Got touch input working with twrp-3.1.1-0-duma (older version), proceeded to flash Lineage 14.1 for MeMOPAD10 FHD... still no touch input there.. im so confused, any help?
Got touch working now with AOSP Extended ROM: https://forum.xda-developers.com/android/general/rom-aosp-extended-v4-4-t3637692
For now i'll stick to that.. but why does it break on LineageOS?
Hi, May i know how you unlocked the boot loader? for me the .apk downloaded from ASUS is not working. it always says "An unkown error occurs, which may be a network connection issue. please wait and try again later".
is there any other way to unlock the bootloader? appreciate your response.
Hello, may I ask how you unlocked the boot loader?