Q&A for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][V500][5.0.x][CM12] Official CyanogenMod 12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
axelander1 said:
is there any way of getting MULTICAST enabled in the CM12 stock kernel?
Click to expand...
Click to collapse
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Deltadroid said:
Yes, the first step is to submit a patch to gerrit. Is there a patch available?
Click to expand...
Click to collapse
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
axelander1 said:
I could probably create one.
Do you know which kernel config is used? is it one in https://github.com/CyanogenMod/android_kernel_lge_v500/tree/cm-12.0/arch/arm/configs ?
Is this even the kernel repo which is used for the cm12 nightlies?
Click to expand...
Click to collapse
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Deltadroid said:
This is the script that generates the config and moves it to arch/arm/configs/
https://github.com/CyanogenMod/android_kernel_lge_v500/blob/cm-12.0/make_defconfig.sh
Click to expand...
Click to collapse
this file takes a parameter, I suppose awifi070u-perf_defconfig is used (see the other make script make_awifi070u_defconfig.sh).
However this has CONFIG_IP_MULTICAST=y.
I somehow doubt that this is the config which is actually used for the official builds. If I understand http://wiki.cyanogenmod.org/w/Build_for_v500 correctly, the command "breakfast v500" would pull the kernel repo and triggers make for the kernel's .config file?
Yes. You can also create a local manifest to pull a specific repo without having to pull everything.
Example:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="cmhub" fetch="git://github.com/CyanogenMod/" review="review.cyanogenmod.com" />
<project path="device/lge/v500" name="android_device_lge_v500" remote="cmhub" />
</manifest>
Example Procedure:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
repo sync device/lge/v500
repo start my_fixed_branch device/lge/v500
cd device/lge/v500
<edit files>
git commit -a
repo upload device/lge/v500
---------- Post added at 12:23 AM ---------- Previous post was at 12:11 AM ----------
Just substitute "device" for "kernel" in the project path and name.
How do I know if I'm using hardware or software decoding for Netflix? No idea if I need your patch.
Also, I installed cm-12-20150226-NIGHTLY-v500.zip yesterday. Updated to cm-12-20150227-NIGHTLY-v500.zip with CyanDelta today, works like a charm. Thank you!
If you make a backup of /system/etc/media_codecs_google_video.xml then you can revert the patch. It only removes one line in that xml file so that adaptive playback is not an option for h264 decoding. The only difference is that hardware decoding should save on the battery. This patch was taken from slimRom and I need it for other devices, so I thought it would be worth testing for this device also.
Hi everyone, I am on 28\02 nightly and Google Now doesn t work, showing "Network error. Check your network connections".
Does anyone knows how to solve it?
It's working here. Either the Google services is temporarily down in your area or you need to install the correct version of gapps. The "Delta" gapps that I have posted in the development section are up to date and working.
cm12 crashes after flashing
Everytime I flash cm12 it fails. I get into the setup process, login to wifi' cyanogenmod, and google. I never get passed this. During setup I get messages that say "unfortunately there is a problem with music", then the same for camera. Then the screen stars flashing and eventually goes dark. The back key shows at the bottom, but the other two do not show. The back key is nonresponsive. I have to power down and get back to recovery and restore my cm11 backup.
When I got the gpad, it came with 20D, andI had to use the lgflashtool to get back to 4.2.2. (20A0. Then I rooted with stump and installed twrp using flashify. Then I was able to flash cm11 (m10, 11 and 12). Cm11 ran like a champ.
A couple of weeks ago I decided to flash a cm12 nightly and had the problem described above.
I have tried multiple combinations of steps to solve this problem: going back to 4.2.2, rooting and flashing cm12 from 4.2.2, I have tried 4.4.2. I have tried multiple versions of twrp and philz. I have wiped with and without wiping system. I have tried different versions of gapps-lp. I have tried different versions of the nightlies.
Every time I get the same result (which I think is the definition of insanity).
What is most frustrating is that I have another gpad that went from cm11 to cm12 with no problems. Worked the first time using the 0217 nightly,
So what am I doing wrong? Why am I having problems with cm12 after I flash it?
Thanks in advance. Xda has been a life saver since I got my first tablet, a viewsonic, a few years ago.
John
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Still can't set up CM12
Deltadroid said:
It sounds like you know the procedure of installing CM because one of your devices works fine. There seems to be a difference between your two devices. Have you looked at the thread for "back cam fix" in the development section to find out how to check which camera module your device has? Maybe one of your devices has a different camera module than the other (which requires other camera drivers). Although, the device should still function with cm12 even if your camera module is unsupported.
Also, make sure you format the cache, Dalvik cache, and system partitions in addition to a factory reset before flashing from your internal sdcard.
Click to expand...
Click to collapse
Thanks for the suggestions. I first checked the camera.
While in CM11 I turned on the camera and took a picture. I also opened a terminal window and grepped both the OV and the S5K cameras. Nothing came back for OV. I did get stuff from S5k. So I assume the camera is the right one.
Then I did went into recovery, carefully wiped and formatted, and flashed CM12 and Gapps.
I am still getting the camera and music errors. Then the screen flashes to black and the it locks.
The bad news is that I cannot get back to recovery. It looks like I'm back to the lgflashtool.
I will try again from stock. But right now I think it is miller time.
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Are you sure you did wipe SYSTEM before flashing?
Still can't set up CM12
Deltadroid said:
Yeah, if it was working on cm11 then your camera is supported.
Maybe going back to latest stock Rom with lg tool would help fix any unknowns. Instead of flashing the 10a firmware, stay on 20d stock and just replace aboot so you can install a custom recovery. Next, install cm12 with red kernel or mani kernel to support your stock 20d 4.4.2 firmware.
Click to expand...
Click to collapse
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
johnseidel said:
No cigars yet! Same error with camera and music then screen locking.
I found an XDA tool called Original LG Firmware.exe. It allowed me to download V50020d_00.kdz.
I used LGFlashTool2014 to install.
I used Stump to get Root.
I downloaded SuperSU and Flashify to set up recovery.
Recovery failed. It didn't think I was rooted.
I used another tool, LGGPabRecoveryTWRP 2.8(BypassBootloader).apk to resolve this problem
I installed CM11-M12.
Then I went to recovery to install CM12, gapps, and red kernal.
The first attempt used the 0305 nightly. It hung on the flash.
I forced a power down and manual reboot into recovery.
Did all the wiping and tried the 0217 nightly. The flash was successful but as it initialized, CM12 crashed and burned again.
I'm beginning to believe I have a poltergeist in this gpad.
Click to expand...
Click to collapse
The reason your recovery failed is because your 20D firmware has an aboot.img that is not loki exploitable. After rooting, you will need to replace your aboot.img with the aboot.img from 10A firmware. This means you are keeping the 20D bootloader but only downgrading the 10A aboot.img so that you can use the loki tool to install a custom recovery. Flashify also needs a loki exploitable aboot.img (10A) to be installed before it can work and install a lokified recovery. The trick is to keep your new bootloader from 20D but only downgrade the aboot.img. There is a batch file in the development section that does this with a script using the dd command.
Okay.
20D is flashed and rooted.
V50020_aboot_twrp_v2 has been executed.
Flashify flashed TWRP 8.0.0.0 and rebooted.
I am assuming the next step is to flash CM12, but wanted to make sure. I've shot myself in the foot so many times I'm running out of toes.
Next, factory reset, and format /system. You could also format your internal sdcard, but it's not often necessary.
Finally, install latest nightly build of cm12. You can install gapps later.
---------- Post added at 02:45 AM ---------- Previous post was at 02:36 AM ----------
Note, make sure you copy the files to your sdcard first if you plan on formatting the internal sdcard.
Related
For CM11 Nightlies:
Find nightlies here:
http://download.cyanogenmod.com/?device=n1
If you're already on CM 10.2, just wipe cache and dalvik. Flash over your current build.
If you're coming from anything else, wipe cache, dalvik, data, and system. Then flash normally.
If you want gapps, you'll have to flash gapps as well.
No need for any modified files on nightlies. I assume that official stable builds will still be defaulted to flash on stock recovery though.
————————————————————————————————
CM 10.2 Information. Please do not use the following to flash CM11!
This is the method that I used to install CyanogenMod on TWRP.
I have tested this, and it is working perfectly on CM builds:
cm-10.2-WPPH47N-n1
cm-10.2-WPPH50O-n1
I will continue to test and update as new CM builds come out until CM flashes normally on TWRP
————————————————
First - Have TWRP as your recovery (2.6.3.1). Don't ask me how to do that.
Second - Backup your ROM! Just in-case something breaks, it's not my fault, and I'm not responsible.
————————————————
Now, we begin:
Download the newest CM build for the Oppo N1 from http://www.cyanogenmod.org/hardware/oppo-n1/#images
————————————————
After downloading your CM build from the above link, you'll need to follow these instructions to get setup for flashing in TWRP.
To modify your downloaded CM file, you can use either of the two methods below:
1: You can modify it yourself. It's actually very simple, just one line change.
2: I have attached an already modified updater-script to my post. You can use that and drop it into place (the file inside the zip, not the whole zip).[/b]
YOU ONLY NEED TO USE ONE OF THESE METHODS!
Method 1: To modify the file yourself:
First, open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Open the updater-script
Remove the first line only! You will remove:
Code:
assert(getprop("ro.product.device") == "N1" || getprop("ro.build.product") == "N1");
Do not remove anything else unless you know exactly what you're doing!
If you modified the file within the .zip, just save the file and it should save to the CM zip.
If you extracted the .zip, save the file and then go back and rebuild the zip.
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
——————————
Method 2: To download my pre-modified updater-script
Download my attached file (updater-script.zip)
Extract the file inside the zip (there's only one file)
Open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Simply copy your extracted updater-script from where you extracted it and drop it into the CM zip (It should save after)
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
————————————————
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
:victory:
I hope this all makes sense...
Basically you download the CM rom
Modify or copy the updater-script into the zip
Then you move the ROM to you phone
Then you go through the above area with wiping and flashing
* Pictures are attached
* Please let me know if there are any problems with this.
* Both versions of CM released so far have identical updater-script files. The .zip that I have attached will work on both builds.
* I will keep updating as needed
• Last updated: January 1, 2014
We're working on fixing TWRP so the asserts work properly.
https://github.com/omnirom/android_bionic/commit/4482d8513920d614e3799a214c5bad07b72580d2#diff-1 broke a lot of things.
https://github.com/omnirom/android_bionic/commit/ad76c85b9ca587084089d086f954158bc0eae905 allows flashing newer firmwares on older recoveries - but not the other way around.
The short-term fix is a TWRP build made from a 4.3 tree - this is 90% done.
@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img
Entropy512 said:
We're working on fixing TWRP so the asserts work properly.
Click to expand...
Click to collapse
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:
rayfin said:
@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img
Click to expand...
Click to collapse
BTW, I'd prefer that my personal dropbox not be directly linked. The same file is now an attachment to my post in the TWRP thread.
Harfainx said:
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:
Click to expand...
Click to collapse
i have some question can u help me :3
1. this download link is the file you already fix it right ?
https://www.4shared.com/download/UPP...N-N1_FIXED.zip - No wait - Direct download link - Full flashable ROM
Click to expand...
Click to collapse
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?
kenjilolip0p said:
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?
Click to expand...
Click to collapse
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.
Harfainx said:
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.
Click to expand...
Click to collapse
Camera orientation is handled by the camera HAL blobs.
CM does have back touchpad support but it's wonky (which is why omni hasn't merged it yet, we're still discussing whether to completely rearchitect it or just fix it.)
good work
Sent from my M045 using XDA Premium 4 mobile app
Except root it works
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.
fesar said:
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.
Click to expand...
Click to collapse
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?
nowy57 said:
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?
Click to expand...
Click to collapse
Go into SuperSU and remove it in the settings (unroot). That will get rid of all of the current SuperSU stuff.
Then flash SuperSU in TWRP.
To flash the unmodified CM, you can try the TWRP in post #3 of this thread HERE.
Or you'll have to remove the same line in the updater-script. The same method posted in the OP. Don't use the uploaded updater-script that I have there though. You'll need to change your own. It's a really simple fix. You don't have to extract all the files out. You can just modify the one file (I use Notepad++).
Sometime tomorrow I'll update the whole OP to include the newest CM version. I'm about to head out to our New Year's event, so I won't be available for the evening.
Enjoy the evening everyone. I wish you all the best! :good: :victory:
i have installed TWRP from #3 - not succes install CM newest version after this
i have unthick superSU and then install again via TWRP superSU.zip after that thick superSU on system android and no succes - root acces didnt come
happy new year
-------
I am a little dissapointed couse I downloaded CM ROM from OFFICIAL SITE http://www.cyanogenmod.org/hardware/oppo-n1/#images and I cannot install it SIMPLE on my device
OP updated! The newest release of CM has been added. I'll keep on top of it from now on, sorry about the delay.
I'm not going to host the CM builds anymore, since the modification is so small from the original CM build. Everyone flashing this should be capable of making the small change that's outlined in the OP.
:highfive:
@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy
nowy57 said:
@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy
Click to expand...
Click to collapse
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
okay , I will try it and confirm
I v got mac osx
under mac I unzip ROM , deleted first line from script then zip it , it doesent work .
but under windows - working good
Harfainx said:
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
Click to expand...
Click to collapse
What's wrong with wiping system?
You don't even wipe system if you go from ColorOS to CyanogenMod?
- Frank
cm11 nightlies are out and downloadable from cyanogenmod
Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
Cm11 nightlies are out..
Do you think we can flash on twrp
If so what would you wipe...
I was thinking about using banks minimal.. 19 MB..
Please give the community tour thoughts and a step by step tutorial..
I would download the nightly from cyanogenmod and banks gapps.. Check md5 alla onmy phone
Reboot recovery and wipe all maybe even system except sdcard
Flash cyanogen then gapps then
Rewipe cache and dalvik
Reboot
I am on omni nightlies now.. Thanks in advance
where do you see nightlies for oppo n1 ?
edit:
ohhh I see
http://download.cyanogenmod.org/?device=n1
better later than never
I just lost hope for good support and sold my oppo n1
I didnt belive for good support having it from one month and non of help from CM team
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
riazrahman said:
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
Click to expand...
Click to collapse
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Higgs_Boson said:
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Click to expand...
Click to collapse
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
riazrahman said:
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
Click to expand...
Click to collapse
Sorry. After re-reading your post, I do see where you mentioned switching to PhilZ. However, please make sure that you have the latest version of PhilZ (which can be found at the link I previously provided).
After reading up on MerkMod, I have no reason to believe that ROM to be the cause of your issues. It is OMNI ROM-based and I have run OMNI ROM on my device without any issues. I, personally, use CM11 as my daily driver. But, as long as you are using the latest PhilZ recovery and flashing D2LTE ROMs to your device, there should be no issue. Also, make sure the GAPPs package you are using matches the Android version of the ROM you are flashing (e.g. 4.4.4 GAPPs --> 4.4.4 ROM)
If you download the .MD5 version of PhilZ, you can flash that via ODIN. Good luck to you.
Also, forgot to mention it in my previous post, but congratulations in advance on your engagement!
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
CNexus said:
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
Click to expand...
Click to collapse
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
riazrahman said:
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
Click to expand...
Click to collapse
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Higgs_Boson said:
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Click to expand...
Click to collapse
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
riazrahman said:
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
Click to expand...
Click to collapse
The only thing that repartitioning will do is restore the memory partitions in your phone in the event that one of the partitions became corrupted.
This is essentially what a PIT would be restoring:
Code:
sprint # cat parted.txt
cat parted.txt
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 30777344s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8192s 131071s 122880s modem
2 131072s 131327s 256s sbl1
3 131328s 131839s 512s sbl2
4 131840s 132863s 1024s sbl3
5 132864s 136959s 4096s aboot
6 136960s 137983s 1024s rpm
7 137984s 158463s 20480s boot
8 158464s 159487s 1024s tz
9 159488s 160511s 1024s pad
10 160512s 180991s 20480s param
11 180992s 208895s 27904s ext4 efs
12 208896s 215039s 6144s modemst1
13 215040s 221183s 6144s modemst2
14 221184s 3293183s 3072000s ext4 system
15 3293184s 28958719s 25665536s ext4 userdata
16 28958720s 28975103s 16384s ext4 persist
17 28975104s 30695423s 1720320s ext4 cache
18 30695424s 30715903s 20480s recovery
19 30715904s 30736383s 20480s fota
20 30736384s 30748671s 12288s backup
21 30748672s 30754815s 6144s fsg
22 30754816s 30754831s 16s ssd
23 30754832s 30765071s 10240s grow
Info credit: http://androidforums.com/virgin-mob...ameleon-some-efs-imei-info-brick-backups.html
Hence, I have no reason to believe this would help you.
Temporarily forget it. Link removed.
TWRP 2.8 v2 for e980.
Fixed auto-loki support.(But there will be a weird floating loki option, i will fix the position of it when i have time)
Should be no longer have secure boot issue after flashing kernel.
Reboot-into-recovery-loop bug still presents, always prepare madmack's twrp for e986 hack, in case boot-loop happens!
When recovery-loop happens, please flash madmack's hacked TWRP 2.6 for e986(please see post #23), then reboot into madmack recovery(you can install back my recovery in this step), reboot system, the recovery-loop will stop.
I am not able to solve this bug, as with Philz touch also has this bug and never solved.
**This recovery will only cause recovery-loop. All other bootloop will not be cause by this recovery!**
**I held no responsibility for any damage due to the use of this recovery.**
Features:
1)Full nandroid backup is much faster on TWRP than on CWM / PHILIPS TOUCH.
2)Ability to format any partition into F2FS/EXFAT/FAT/EXT2/EXT3/EXT4, and read/write all these format partitions.(don't use F2FS format until a compatible kernel and rom come out.)(I am using stock at this moment, still love stock, but failed to make stock rom fully compatible with F2FS, what a pity!)
Download it from attachment.
Backup anythings important.
Flash through recovery.
Enjoy!
Wing
P.S. I am **not** a developer, so I **may not be able to** fix any bugs if you encounter!
P.S. Again, i am using phone network at home, which have data usage limit, so the source will be uploaded when i can use wifi.
P.S.I am not programmer, I used very long time to understand what is what, if you think this recovery is useful, consider make a donation!
Wow, thanks! Working great!
Wow .thank you so much .already flashed waiting for new build to test .will report back .thanks again
---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------
Keep this thread alive
Actually, the thing i actually want/try to do is to add F2FS support to CM kernel and whole CM rom.
Since i am not a developer, i use a lot of time try to figure out what need to patch and failed.
I used too much time and can't understand what make the compile fail and give up.
Then I do the next thing I want to do: compile a fully working twrp to replace the easily boot-loop PhilZ Touch recovery.
This TWRP is actually a side product of my failure attempt.
(ha, i still don't have right to post external links, so i will put the TWRP e980 compile method and source up later)
Wing
Great job man .thanks
mukwing said:
Actually, the thing i actually want/try to do is to add F2FS support to CM kernel and whole CM rom.
Since i am not a developer, i use a lot of time try to figure out what need to patch and failed.
I used too much time and can't understand what make the compile fail and give up.
Then I do the next thing I want to do: compile a fully working twrp to replace the easily boot-loop PhilZ Touch recovery.
This TWRP is actually a side product of my failure attempt.
(ha, i still don't have right to post external links, so i will put the TWRP e980 compile method and source up later)
Wing
Click to expand...
Click to collapse
how did u build i could help i have linux on virtual mmachine on windows 8.1
bountyman334 said:
how did u build i could help i have linux on virtual mmachine on windows 8.1
Click to expand...
Click to collapse
Attached is the patch file for cm kernel to make it support F2FS.(I forget where to get)
Not all codes can be patched sucessfully, some I need to modify the kernel sources by hand.
It seems some codes will lead to compile error, but i am not programmer, I don't know how to adjust.
I am using up-to-date CM sources, without modification, i can compile unofficial cm build successfully for my own test.
Wing
Forget this patch. I think this patch might be outdated.
I am trying to investigate the commits about F2FS in Nexus 5 CM F2FS kernel sources.
Will try to merge these commits to see if it can compile.
If I sucessfully getting a F2FS supported CM kernel, will try to make a F2FS supported TWRP.
Making CM rom to support F2FS seems to be easy, there exists some tools ready to do it.
Wing
Thank you so much for you hard work
I finally learned how to correctly patch kernel commits!
Good news. A F2FS suppported kernel has been successfully compiled!
(need testing, but need to compile F2FS suppported TWRP and ROM before i can test.)
Next step, F2FS suppported TWRP.
Wing
I can't find resources of how to modify TWRP 2.8.0.0 to support F2FS for our device.
But the modified KT-TWRP from the following
http://forum.xda-developers.com/showthread.php?t=2778248
I can compile it successfully against e980 CM sources.
So, I get F2FS supported TW-TWRP working on my phone.
I still haven't try format partition to F2FS.
Will report if it works later.
I don't want to be another failure, used me sooooo much time to research.
Wing
version?
It says in the flash screen that it is madmack's 2.6.1.0 only.
I am confused..
Edit - but the recovery header says it is 2.8.0.0
XD
Edit 2 - It has messed up with the phone. Not able to get into the ROM. only boots into the recovery. Tried philz recovery and then tried to boot again but it isn't working anymore.
mukuluppal said:
It says in the flash screen that it is madmack's 2.6.1.0 only.
I am confused..
Edit - but the recovery header says it is 2.8.0.0
XD
Edit 2 - It has messed up with the phone. Not able to get into the ROM. only boots into the recovery. Tried philz recovery and then tried to boot again but it isn't working anymore.
Click to expand...
Click to collapse
It say madmack's 2.6.1.0 because i use madmack's old zip and replaced the recovery.
If in the boot-into-recovery loop, install philz recovery, then install TWRP again should fix it?
BTW, is it caused by wiping of /data?
Again, i am not programmer. I will try to find out reason to see if i can fix it.
Wing
mukwing said:
It say madmack's 2.6.1.0 because i use madmack's old zip and replaced the recovery.
If in the boot-into-recovery loop, install philz recovery, then install TWRP again should fix it?
BTW, is it caused by wiping of /data?
Wing
Click to expand...
Click to collapse
Yeah i tried that and it didn't work.
So i tried a bunch of my old recoveries and the twrp e986 hacked one worked.
Now i can see ext card too in twrp. But that's not your recovery. It's old one.
No it didn't happen coz of wipe data.. After flashing it,the recovery boot started.
Failed to find out why has this bug on this recovery. Sorry.
Btw, testing of F2FS gave me soft brick of my phone. When I returned to stock, I surely love the smoothness of original stock lg 4.1.2. So I may stay with stock for a while.
When I feel too boring with stock again, I will return to cm and try compiling something to have fun again.
recovery updated.
please test!
Wing
If anyone tests this out let me know if the Loki works because last time I tried it it made my phone soft brick. It was an easy fix to unbrick it but I'm hoping it doesn't do that anymore.
mukwing said:
recovery updated.
please test!
Wing
Click to expand...
Click to collapse
So..
If you go to install,there is a "Loki support" floating checkbox that won't go away...
If you try to Enable MTP and actually try to copy something to internal SD card, recovery reboots and copy fails (I noticed that you can still delete stuff).
It also got me a bootloop when flashing a rom, I had to recover through download mode and a KDZ...
Bunch of issues that are pretty noticeable, OP,are you even testing this on your phone before sending it out risking other phones?
The floating Loki doesn't affect the usage much.
And the boot loop have been mentioned using madmack 2.6 e986 to solved.
Sorry, will never share anything again.
Jeez....
2SHAYNEZ
Q&A for [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi guys I did try it on my p601 and its ecelent
thought its easy just exported my modem on old p601 and tried to import it but I didnt make the trick
some other developer did mods for p601 then p600 maybe they can give a hint what else need to be done on a p601
ACTUALLY I use xkat 2.0 that developer did first an p601 and downgraded then a p600 version
would have no issue to use my device as p600 but get only internet by 3g
To get 3g to work requires a new device tree you can't just import your modem there will be a lot of files that need to call specific hard ware files, etc to get the 3g to work. I wish it was as simple as that
Sent from my SM-N9005 using Tapatalk
Does this Rom Have any Spen Support? Can anyone confirm?
cm12 how do i remove the mouse cursor?
As the question really. I am an artist and need to remove the onscreen mouse cursor when spen is used. I don't use an external mouse so dont mind losing it entirely.
Any ideas how?
Many thanks
My P600 will come in the mail within a few days.
I've spent a few days (4) reading through the forums before posting my very first questions on xda......
1. Is this rom based on RaymanFX 12/18 build?
2. Would clean flashing version RaymanFX 12/5 then dirty flashing Temasek's UNOFFICIAL CM12 BUILD fix the camera force close?
WILDrBEAST said:
My P600 will come in the mail within a few days.
I've spent a few days (4) reading through the forums before posting my very first questions on xda......
1. Is this rom based on RaymanFX 12/18 build?
2. Would clean flashing version RaymanFX 12/5 then dirty flashing Temasek's UNOFFICIAL CM12 BUILD fix the camera force close?
Click to expand...
Click to collapse
I don't have the camera issue,i dirty flashed like you are intending to.
Dirty flashing will fix the camera issue as in dirty flashing guy rom over raymanfx build or the nexus experience ... Some reason from source code the camera is not working. I want to build regular cm to check what portion I am missing (if any) of correct sources. I know what the error is from the logs however I fix one part and another crops up so I think there is something missing
Sent from my SM-N9005 using Tapatalk
Thanks!
I also think that this rom ir best of best.
Can anyone confirm pressure sensitivity is working? I cant find an answer, I read that spen is only a pointer so that does not work for drawing apps that use pressure?
My P600 came FedEx today and I'm ready to root and flash.
Should I update the device from P600UEUCNI1 to P600UEUCNK2 to get the latest KK recovery before I start? (if the 2 newer updates even makes changes to recovery).
I am getting the update prompt though it doesn't say which build.
The recovery shouldn't matter it will get flashed over with a twrp build anyway...
I am not up to date on the root ability of the newest bootloader as my device was rooted when I got it stock and I don't recall updating bootloader at any stage
Sent from my SM-N9005 using Tapatalk
problem when flashing
Im tryingto flash youe rom, but during the file's verification in recovery mod, the device fails and after 2 tries is just force closes aand reboot on touchwiz. Dont know where I made my fault
patrykket said:
Im tryingto flash youe rom, but during the file's verification in recovery mod, the device fails and after 2 tries is just force closes aand reboot on touchwiz. Dont know where I made my fault
Click to expand...
Click to collapse
Sounds to me that you are having problem with twrp recovery I had this when flashing on any other recovery other than 6.3.3.3... What version twrp are you using
Sent from my Nexus 9 using Tapatalk
joshndroid said:
Sounds to me that you are having problem with twrp recovery I had this whdden flashing on any other recovery other than 6.3.3.3... What version twrp are you using
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
2.7.4.5 the newest one avalaible on googlemplay
---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------
patrykket said:
2.7.4.5 the newest one avalaible on googlemplay
Click to expand...
Click to collapse
Im actually trying the version you told me. But not to use it, but to install it. The zips doesnt want to be installed, .img too. Cant you send me the installation file (and eventually the whole file) on my mail?
[email protected]
patrykket said:
2.7.4.5 the newest one avalaible on googlemplay
---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------
Im actually trying the version you told me. But not to use it, but to install it. The zips doesnt want to be installed, .img too. Cant you send me the installation file (and eventually the whole file) on my mail?
[email protected]
Click to expand...
Click to collapse
your a bit hard to understand.
to flash it correctly you need to use odin and not the img flash tools, etc from the market. These tools can cause problems and can flash to the incorrect partition block for the device.
none of the TWRP zip files on their website ever seem to work for me, so i have also flashed these things manually because to many times i have been left with no recovery or back to stock recovery. Manual flash is always better.
you need an .img.tar file - here is the direct link from twrp website for lt03wifi (note 10.1 wifi only model) - https://goo.im/devs/OpenRecovery/lt03wifiue/openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar
this needs to be flashed with odin, i would suggest read here first - http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
within this there is a further guide on how to use odin, the link of odin iteself can be obtained here - http://www.andromint.com/download-odin-latest-version/
joshndroid said:
your a bit hard to understand.
to flash it correctly you need to use odin and not the img flash tools, etc from the market. These tools can cause problems and can flash to the incorrect partition block for the device.
none of the TWRP zip files on their website ever seem to work for me, so i have also flashed these things manually because to many times i have been left with no recovery or back to stock recovery. Manual flash is always better.
you need an .img.tar file - here is the direct link from twrp website for lt03wifi (note 10.1 wifi only model) - https://goo.im/devs/OpenRecovery/lt03wifiue/openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar
this needs to be flashed with odin, i would suggest read here first - http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
within this there is a further guide on how to use odin, the link of odin iteself can be obtained here - http://www.andromint.com/download-odin-latest-version/
Click to expand...
Click to collapse
I'll try to be clearer.
Actuallynit's the forst time I'm trying to work with roms etc. Actually I feel a little lost. I managed to install Odin on my computer (tried 3.09 version) managed to root my device. But the problems that I have occur from there. What do you meam by manually flash your rom, why do ypu ask to use tpwr if you tell me now it never works. And where do I need to download the cyanogenmod's rom file? On mu tablet, sd card or on my computer? I don't wan't to say this tutorial how to get the cm installed on ypur device is unclear, but as a newbie, I encountered some difficulties.
Thx for everything.
Ps. I took a looknon every link u sent me, but it didnt really help me.
patrykket said:
I'll try to be clearer.
Actuallynit's the forst time I'm trying to work with roms etc. Actually I feel a little lost. I managed to install Odin on my computer (tried 3.09 version) managed to root my device. But the problems that I have occur from there. What do you meam by manually flash your rom, why do ypu ask to use tpwr if you tell me now it never works. And where do I need to download the cyanogenmod's rom file? On mu tablet, sd card or on my computer? I don't wan't to say this tutorial how to get the cm installed on ypur device is unclear, but as a newbie, I encountered some difficulties.
Thx for everything.
Ps. I took a looknon every link u sent me, but it didnt really help me.
Click to expand...
Click to collapse
Please re-read my previous post.
I did not say manually flash rom, i was talking about the RECOVERY which is the TWRP recovery by using ODIN.
Please have a good read through guides, if the ones i linked don't help you try googling, there are plenty others. There are videos on youtube showing how to flash files/recovery using odin.
Please read as much as you can before starting, because when it goes bad no one is going to be able to fix it for you. As much as it is at your own risk i wouldn't like to see someone's hard earned money turn into a paperweight.
Tell me please, working s-pen?
The GPS is not working for me on this rom, heres what I did...
Step 1:
I flashed TWRP 2.6.3.3 with Odin 3.10,
Made a backup with TWRP,
Cleared Cache,
Cleared Dalvik,
Cleared Data,
Flashed cm-12-20141205,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test Works, so does Navigation.
Step 2:
Flashed cm-12-20141218,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test Works, so does Navigation.
Made a backup with TWRP,
Step 3:
Flashed cm-12-20150104 v4.2,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test does not work, neither does Navigation
Also tried "Step 3" with cm-12-20150103 v4.0 AND cm-12-20141231 v3.8 with the same result.
THIS ROM ROCKS! VERY SMOOTH AND FAST!!
Could this be a simple fix? did I take any incorrect steps?
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
ejaf said:
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
Click to expand...
Click to collapse
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Here is the link to the latest, grab the first tar flash it via odin & you should be good to boot into recovery to flash roms.
https://dl.twrp.me/d2spr/
Lonelyskatter12 said:
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Click to expand...
Click to collapse
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
ejaf said:
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
Click to expand...
Click to collapse
Yes, the official thread is CM13, you don't need Cwm, pretty much twrp supports marshmallow now.
And i believe you would need root.
If there's any way for you to be able to download the files, id be happy to give you step by step instructions :good:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
ejaf said:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
Click to expand...
Click to collapse
Yeah the Unofficial thread was being maintained by a Developer, who stopped as soon as the officials came out.
And yes
1.) Wipe Data, Cache, System, & Internal Storage (So backup anything on there)
2.) Flash Rom, Gapps, SuperSu 2.71 (If you want root)
& should be good to go
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
ejaf said:
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
Click to expand...
Click to collapse
That's the order, now about the apn im not sure, i just use mine for wifi and stuff.
That Cyanogenmod build "04282016" wasn't running so well for me, so I'm on AICP for now.
But i would suggest, OctOs , AICP, or Exodus Roms. Those are the most stable roms for this device.
Same steps just different ROMs.
But i did hear Exodus gives you data right off the bat, so that'd be good to try
Interesting...thanks for the tips. Hopefully I won't have to bother any of you all again, since I really don't have much in the way of knowledge to return
E
FYI...was able to boot up into CM 12.1 over the weekend. Jury's still out on whether to go to a 6.0.1 based ROM, but appreciate all the help.
Eric
I found the APN fix didn't work with the CM13 rom (I've used it previously with 12.1 fine). I also found that the build-in cm update failed on 20160505 nightly. Not sure if this was just that day or a known bug.