So I purchased my new LG Optimus 2x from Wind two days ago and I managed to root it today. After rooting it, I downloaded ROM Manager from the android market and did I backup using the built-in clockworkmod recovery app. After doing that, I installed the latest Cyanogenmod stable release and installed it. Everything worked fine, until it rebooted. Now, my device won't get past the lg splash screen. Any help would be greatly appreciated!
thefantasticdron said:
So I purchased my new LG Optimus 2x from Wind two days ago and I managed to root it today. After rooting it, I downloaded ROM Manager from the android market and did I backup using the built-in clockworkmod recovery app. After doing that, I installed the latest Cyanogenmod stable release and installed it. Everything worked fine, until it rebooted. Now, my device won't get past the lg splash screen. Any help would be greatly appreciated!
Click to expand...
Click to collapse
That isn't bricked.
NVFlash Clockworkmod (EXTREMELY IMPORTANT)
Then get the latest nightly, the stable CM7 is too old to be relevant or usable compared to the nightlies and wipe data, cache, dalvik cache, and system before flashing, and then flash gapps and you will be good.
Know that this will wipe everything though.
After flashing clockworkmod with nvflash, would it be possible to go back to my old, wind-provided stock android rom?
Phew, I managed to fix it by installing the T-Mobile rom onto my phone. Thanks for the help! Mods, you can close this thread as you please.
download another version and flash again.u will be fine.
First off, like many others here, I would like to thank all the CM devs, the xda devs, and everyone else who has made it possible to run CM on the Skyrocket. I came from stock GB and the upgrade made it a new phone. You guys rock!
My question may be simple and I apologize in advance, but I am somewhat of a newb and I have made it this far without having to post a question. I have been able to search and find all my answers about installing a custom recovery, radio install, CM upgrade, and everything else associated with flashing a new ROM so I don't feel too big a newb.
Now that I have a clean install of 10.1 up and running along with the associated Gapps package, CM is telling me that 10.1.3 is available for download. My question is this...Is it safe to upgrade within CM? I am assuming it verifies the md5 hash to prevent a corrupt file from being installed? And when CM reports that 10.2 is available, how would I go about updating Gapps, since that requires a different Gapps package? Would you have to flash the new Gapps from recovery? Would it install over the older Gapps package? What about 10.2-would it have to be flashed in recovery, or would it be safe to upgrade within CM (once it becomes available)?
Thanks in advance for your replies, and thanks again to everyone who has made it possible to extend the life of the Skyrocket.
I would change CM Updater to show "Stable Only" updates for now until you become more familiar with everything. In a nutshell, yes you can use CM Updater to upgrade to CM 10.1.3.
For CM 10.2, it's currently in Nightly status and the upgrade process is more involved than just allowing CMUpdater to do the work. Go read the thread for more info. Short answer: CMupdater is perfect for nightly/stable updates of the same version (ie CM10.1.x to CM10.1.x). Don't use it for upgrading to release versions (ie CM10.1.x to CM10.2).
Okay so I've been having an SGS3 with me lying around, but always love using it. It has TWRP on it and uses the app HIapn global so I could use T-Mobile on it. But I've been wondering, if I Install CM 12 on it will it erase the apns and not be unlocked? Because I can't stand touchwiz in anyway. Its on 4.1.2 with TWRP on it, Sch- I535. Will the phone also be bricked in any sort of way, because I've heard the new boot loader on the s3 makes it impossible to install a custom ROM. If anyone could help asap, it will be appreciated . :good: I just don't want my T-Mobile service gone Edit: service is now working fine, except every rom i install, I get no incoming calls? Any ideas? Roms I installed Mastamoon Cm11, Mastamoon Cm 12, LS Lollipop, Bliss 4.4, and Cm 11 by Invisiblek . Could it have anything to do with the baseband/modem version?
Hi. After I posted this message, the problem seems to be that my ROM is hopelessly old. But after following the recommendations, I still couldn't update.
I tried to install "cm-11-20141112-SNAPSHOT-M12-moto_msm8960.zip" from ClockworkMod recovery. Got this error message:
Code:
This package is for device: moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish; this device is xt925.
(Status 7)
Installation aborted.
But I was told (and the message on the CM wiki confirms it) that builds have been unified.
What should I do?
Looking for installs for xt925 specifically, the last stable is the one I have, and the few nightlies are very old as well and I doubt would solve the problem.
There is the CM12 nightly for xt925 released today, but since I'm highly dependent on my phone functioning while traveling next week and can't afford things going wrong, I'd rather avoid nightlies and experimental versions unless I have absolutely no alternative to have my phone encrypted.
Advice?
Thanks a lot.
By the way, I prefer to not make a factory reset unless it's necessary.
Is it necessary? Do I have to wipe cache? Wipe dalvik? Some sites say yes, some sites say not needed.
Is the answer different depending on whether I would be upgrading to a more recent version of CM 11 or to CM 12 nightly?
Thanks!
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
That's right, I overlooked that, thank you. Was able to upgrade now.
I thought that because my Android stock was KitKat before I flashed CM11, that the bootloader would also be KK. It was a jbbl, because now it worked.
Everything seems to be working just fine, was no need to clear caches or data or anything. My compass is also now fixed.
I just started encryption and it wasn't locked in the robot anymore, it booted and now shows a progress bar with 4% complete.
Thanks, kabaldan!
Just one more question, will there be CM12 for moto_msm8960_jbbl later, or if I want to upgrade to CM12 I will have to do this kkbl workaround you mentioned?
kabaldan said:
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
Click to expand...
Click to collapse
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445