Samsung Galaxy Note 3

  • Thread starter Thread starter kingrob
  • Start date Start date
Piesang said:
What is the PIT backup? User and app data or critical backup in case your phone doesn't want to work anymore?
Click to expand...
I'm not too clear on the function of PIT files. But from my searching it seems to be used for correctly formatting your device.

But from my experience it's most important to have a nandroid back up above all else. This includes: system, data, EFS, modem, cache.
 
The guide on XDA doesn't say that the phone must be put in download mode. Is it supposed to be in download mode?

Never mind. Figured it out. Lollipop is running.
 
Last edited:
I am so happy and impressed that you finally took the training wheels off.

Well done!!
 
I decided to install CyanogenMod yesterday. Officially rooted! I thought I'd share my problems with everyone and maybe help understand the process.

TLDR; Heimdall Suite failed, TWRP incompatible with CyanogenMod, create my own .tar from a CWM image, sideloaded CyanogenMod, sideloaded Google Apps.

Firstly, I tried to use the installer from the site, but my phone is not compatible (SM-N9005 with KitKat). I tried following the instructions for using Heimdall Suite and discovered that it's incompatible with Android 4.4.4 (some PIT error when flashing). I also downloaded the latest CyanogenMod stable build here (for use later - it's about 220 megs).

After searching, I worked out I could use Odin. You must reboot your phone into download mode (Volume Down+Home+Power) to upload the recovery image to your phone. I downloaded a CWM image here as mentioned on CyanogenMod;s site, but when you click the AP button in Odin to load the image, it only wants TAR files. I tar'd the image myself, but that failed. I then downloaded a TWRP image in a tar file from another tutorial for Lollipop and uploaded it onto the phone through Odin.

You must then reboot your phone into recovery mode (Volume Up+Home+Power) to use the image. Use the volume buttons to navigate, power/home to select menu items. It worked and I wiped the phone data (required first step!).

I DON'T have an SD Card and could not figure out how to get the image onto the phone to install, so I used ADB to sideload it. There is a menu item in recovery mode for sideload and it waits for you to do it on the PC. Open a command prompt, navigate to the directory where the install zip (mentioned above) is located and run the command as follows:
adb sideload cm-11-20141112-SNAPSHOT-M12-hlte.zip
Click to expand...

This failed! I'd just wiped my phone for nothing! NOO! :cry:

After researching the error, it turns out you MUST use a CWM image to install CyanomodGen. TWRP is incompatible with it. But now I only had .img files and the .tar file I made didn't work. So I opened up the TWRP tar file and saw that the file inside is named recovery.img. I renamed the CWM img file inside the tar file to recovery.img and it worked in Odin! Booted back into recovery mode and sideloaded successfully!

I booted into my new ROM and played around. I discovered that the Google apps were missing. The is part of the legal issue with Google and I had to sideload them myself. You need to download the Google Apps separately (called GApps) and install in recovery mode in the same way I ran the adb sideload command quoted above.
 
KamikazeHamster said:
I decided to install CyanogenMod yesterday. Officially rooted! I thought I'd share my problems with everyone and maybe help understand the process.

TLDR; Heimdall Suite failed, TWRP incompatible with CyanogenMod, create my own .tar from a CWM image, sideloaded CyanogenMod, sideloaded Google Apps.

Firstly, I tried to use the installer from the site, but my phone is not compatible (SM-N9005 with KitKat). I tried following the instructions for using Heimdall Suite and discovered that it's incompatible with Android 4.4.4 (some PIT error when flashing). I also downloaded the latest CyanogenMod stable build here (for use later - it's about 220 megs).

After searching, I worked out I could use Odin. You must reboot your phone into download mode (Volume Down+Home+Power) to upload the recovery image to your phone. I downloaded a CWM image here as mentioned on CyanogenMod;s site, but when you click the AP button in Odin to load the image, it only wants TAR files. I tar'd the image myself, but that failed. I then downloaded a TWRP image in a tar file from another tutorial for Lollipop and uploaded it onto the phone through Odin.

You must then reboot your phone into recovery mode (Volume Up+Home+Power) to use the image. Use the volume buttons to navigate, power/home to select menu items. It worked and I wiped the phone data (required first step!).

I DON'T have an SD Card and could not figure out how to get the image onto the phone to install, so I used ADB to sideload it. There is a menu item in recovery mode for sideload and it waits for you to do it on the PC. Open a command prompt, navigate to the directory where the install zip (mentioned above) is located and run the command as follows:


This failed! I'd just wiped my phone for nothing! NOO! :cry:

After researching the error, it turns out you MUST use a CWM image to install CyanomodGen. TWRP is incompatible with it. But now I only had .img files and the .tar file I made didn't work. So I opened up the TWRP tar file and saw that the file inside is named recovery.img. I renamed the CWM img file inside the tar file to recovery.img and it worked in Odin! Booted back into recovery mode and sideloaded successfully!

I booted into my new ROM and played around. I discovered that the Google apps were missing. The is part of the legal issue with Google and I had to sideload them myself. You need to download the Google Apps separately (called GApps) and install in recovery mode in the same way I ran the adb sideload command quoted above.
Click to expand...

Just flash the leaked Lollipop. It's great.
 
KamikazeHamster said:
I decided to install CyanogenMod yesterday. Officially rooted! I thought I'd share my problems with everyone and maybe help understand the process.

TLDR; Heimdall Suite failed, TWRP incompatible with CyanogenMod, create my own .tar from a CWM image, sideloaded CyanogenMod, sideloaded Google Apps.

Firstly, I tried to use the installer from the site, but my phone is not compatible (SM-N9005 with KitKat). I tried following the instructions for using Heimdall Suite and discovered that it's incompatible with Android 4.4.4 (some PIT error when flashing). I also downloaded the latest CyanogenMod stable build here (for use later - it's about 220 megs).

After searching, I worked out I could use Odin. You must reboot your phone into download mode (Volume Down+Home+Power) to upload the recovery image to your phone. I downloaded a CWM image here as mentioned on CyanogenMod;s site, but when you click the AP button in Odin to load the image, it only wants TAR files. I tar'd the image myself, but that failed. I then downloaded a TWRP image in a tar file from another tutorial for Lollipop and uploaded it onto the phone through Odin.

You must then reboot your phone into recovery mode (Volume Up+Home+Power) to use the image. Use the volume buttons to navigate, power/home to select menu items. It worked and I wiped the phone data (required first step!).

I DON'T have an SD Card and could not figure out how to get the image onto the phone to install, so I used ADB to sideload it. There is a menu item in recovery mode for sideload and it waits for you to do it on the PC. Open a command prompt, navigate to the directory where the install zip (mentioned above) is located and run the command as follows:


This failed! I'd just wiped my phone for nothing! NOO! :cry:

After researching the error, it turns out you MUST use a CWM image to install CyanomodGen. TWRP is incompatible with it. But now I only had .img files and the .tar file I made didn't work. So I opened up the TWRP tar file and saw that the file inside is named recovery.img. I renamed the CWM img file inside the tar file to recovery.img and it worked in Odin! Booted back into recovery mode and sideloaded successfully!

I booted into my new ROM and played around. I discovered that the Google apps were missing. The is part of the legal issue with Google and I had to sideload them myself. You need to download the Google Apps separately (called GApps) and install in recovery mode in the same way I ran the adb sideload command quoted above.
Click to expand...
From my experience all you needed to do was flash CF-Autoroot, and CWM via Odin3.09 then flash CM12 and GAPPS via CWM.

That's what I did back in May if memory serves.
 
shiverz said:
From my experience all you needed to do was flash CF-Autoroot, and CWM via Odin3.09 then flash CM12 and GAPPS via CWM.

That's what I did back in May if memory serves.
Click to expand...

Yeah...what he said....took me 5 minutes to actually root the device and then another 10 minutes to do the CM 12 installation.

Anway, im also running the unofficial lollipop. Im not sure how i feel about it tbh. Battery life isn't that great, but apparently i just need to wait for the OS to settle and let it cycle.

There is a noticeable delay between pressing the home menu when you want to try switch between apps, but other than this i haven't felt any lag. I compared the OS to that of my friends S4 4.4 and its definitely an improvement. Im just more used to no bloatware pure CM so not used to any lag.
 
Lostears said:
Yeah...what he said....took me 5 minutes to actually root the device and then another 10 minutes to do the CM 12 installation.

Anway, im also running the unofficial lollipop. Im not sure how i feel about it tbh. Battery life isn't that great, but apparently i just need to wait for the OS to settle and let it cycle.

There is a noticeable delay between pressing the home menu when you want to try switch between apps, but other than this i haven't felt any lag. I compared the OS to that of my friends S4 4.4 and its definitely an improvement. Im just more used to no bloatware pure CM so not used to any lag.
Click to expand...
Are you using Temasek's CM12. It's near perfect. I'm getting 6hrs SO battery.
 
shiverz said:
Are you using Temasek's CM12. It's near perfect. I'm getting 6hrs SO battery.
Click to expand...

How are you getting this much SO time?

Am on build 3.5 and not getting half of this. Had to get CPU tuner to turn down CPU freq when sleeping to stop the loss of at least 10% overnight
 
powermzii said:
How are you getting this much SO time?

Am on build 3.5 and not getting half of this. Had to get CPU tuner to turn down CPU freq when sleeping to stop the loss of at least 10% overnight
Click to expand...
I'm using FauxClock kernel settings as posted in XDA by ScoobyJenkins (I think). Lux Auto brightness. And the usual settings: Greenify, Lean Droid, GPS, NFC, WI-FI (when unavailable) and autosync Off. Using 2G when 3G and LTE unavailable. Etc.
 
Last edited:
shiverz said:
I'm using FauxClock kernel settings as posted in XDA by ScoobyJenkins (I think). Lux Auto brightness. And the usual settings: Greenify, Lean Droid, GPS, NFC, WI-FI (when unavailable) and autosync Off. Using 2G when 3G and LTE unavailable. Etc.
Click to expand...

Thanks m8. Will look into it and see the change
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X