Develop Bugs

[Q] Nothing in my phone

Hi,
I have installed CWM_RecoveryTOUCH_v6.0.3.0_N7100 for international version of Note2.
I formated my phone from recovery, my mistake I've also deleted system files including internal storage. Now, there is no ROM in my Phone. No Super User access to my Phone.
Can anyone suggest a procedure to fix this.
Thanks.

You need to flash a ROM from Odin, if there is nothing on your phone... Go to http://www.sammobile.com/ and download the ROM you want to flash and flash it via Odin from your PC... Then flash SU binary to root (also from Odin).... there are numerous threads how to flash ROM and root.
cheers,
D.

prashanthsandela said:
Hi,
I have installed CWM_RecoveryTOUCH_v6.0.3.0_N7100 for international version of Note2.
I formated my phone from recovery, my mistake I've also deleted system files including internal storage. Now, there is no ROM in my Phone. No Super User access to my Phone.
Can anyone suggest a procedure to fix this.
Thanks.
Click to expand...
Click to collapse
1. Invent a time machine.
2. Go back and ***** slap yourself and say NO!!!
3. Profit!

SMT700 - Custom Rom /Installation/Backup

Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:

androidnoob222 said:
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
Click to expand...
Click to collapse
1. There is bootloops but hardbricks are rare. You can enter recovery and download mode(flash stock rom on broke os) in a bootloop. Just hold power, home or vol up for recovery and home +power +vol down for download mode.
2. Yes you can go back to any version of stock os unlike apple you have to be on the latest. The files are online for your device at sammobile. (google it) and also samsung updates.
3. All you need to perform a custom rom flash is a custom recovery called twrp and your device. Theres an app on google play for installation of it. (search on youtube on how to do so). But thats just flashing zip based roms(which most custom roms are). For stock rom installation, you will need a pc and a application called odin 309 to flash a stock md5 file rom in which you will need to be in download mode (like installing new update from itunes).
You will need to backup your whole rom with twrp before flashing a custom rom. You may need a micro sd if your short on space. You will also need to be rooted to install custom roms. Please go to the cfautoroot thread of your device to root your device in which you will viod warrenty.
4. Cm rom as of now still has bugs but is still useable for games and such. There should be a list of bugs on the thread and might have some missing features such as ir blaster and finger print scanner. Battery life may vary. So there are downsides.
5. I can go into more depth of custom stuff and flashing if you wish. Right now my fingers hurts xD. Hope this helps!

1) it is very, very unlikely even if you try intentionally to do so
2) yes, no problem. google for Samsung Firwares, it's all online
3) windows PC, Odin Software, and an USB cable, that's all. You can do it with Linux if you prefer. Some Roms are installed via zip file from the device itself, then you need to flash a new Recovery partition first, that is able to do so
4) ?

Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:

androidnoob222 said:
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
Click to expand...
Click to collapse
1. Sometimes odin and kies will fail for you. Twrp backups is to be really safe if you get bootlooped and odin fails for you. Its much easyer to restore a twrp backup and easy to make one. Its just if odin or kies fails which twrpnwould be your only hope. Just in case
2. Cfautoroot only flashes supersu and root. It keeps your apps and everything. So when you flash cfautoroot, it will say andriod is upgrading becuase its installing root and restoring back your apps.
3. After a full proper reset, it will not have root and revert back to stock. Thats where you flash cfautoroot to gain root again!
Hope this helps!

So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?

androidnoob222 said:
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
Click to expand...
Click to collapse
Most custom roms are to be flashed with twrp. Meanwhile stock roms/md5 is to be flashed with odin(firmware from website).

Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?

androidnoob222 said:
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
Click to expand...
Click to collapse
2.8 is the latest version of twrp. I dont think your device is klimwifixx. It should be klimwifi. What the wipe and and factory reset in twrp does is that it clears all your apps and wipe cache. It does not wipe any folders and it justs wipes your apps. So internal should not be affected unless you formatted it... You just need to swipe the factory reset on it when installing roms. For google play store you have to flash a file name gapps. There should be a link to it on the thread. To get into recovery, turn off your device, then hold power, home, vol up buttons at the same time to enter recovery. To exit recover just touch the reboot rectangle and hit reboot system. Hope this helps!

Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things

androidnoob222 said:
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
Click to expand...
Click to collapse
No no! Twrp replaces stock recovery. Download mode cannot be replaced. You enter it by holding power, vol down, home button when the device is off. Download mode is when you flash things. Recovery mode is when you clear cache or other stuffs. I have no idea with the linux stuff you explained but custom zip roms just adds some modifications and other stuff to the device. You would need to clear cache and factory reset so you wont have problems installing it. You can easyly go back to stock rooted by restoreing a backup you made in twrp. It has to do something with img and replacing those if thats what your talking about idk. No need to format as the rom add things to it. Just need to factory reset and cleae caches.

But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..

androidnoob222 said:
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
Click to expand...
Click to collapse
It shouldnt be as twrp only replaces recovery. Img did you try doing home, power, vol down?

Hi
I have a quick question I have the Galaxy tab S 10.5 wifi and was wondering can I install TWRP without the tablet being rooted?
Also there are some builds where it states that its rooted, debloated and de-knocked. Does this mean that they can be flashed without rooting the tablet and tripping knox.
Thanks for your replies, still trying to get my head around this.

One of my first ROM flashes, could you please double check?

Wow, what a ride I had with this phone.
Starting with the fact that the model of the phone was SGH-I747 with AT&T branding I then tried to flash a custom ROM for this model, of course everything went bad, we'll not everything, but I couldn't make any calls, see IMEI nubmer and so on.
Thanks to a very helping member of SGH-I747 board, audit13, I found out that my phone is in fact T-Mobile's SHG-T999. I was lucky enough and was able to restore stock ROM of this model.
Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
And I just wanted to make sure that I don't miss anything important.
Phone Data
Model: SGH-T999
Bootloader version: T999UVUENC2
Android Version: 4.3
I've rooted the phone using this guide - http://forum.xda-developers.com/showthread.php?t=1771687 and using March 2014 - 4.3 JellyBean.
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works

You could follow this thread to backup your efs folder: http://forum.xda-developers.com/showthread.php?t=1804117
I suggest flashing CWM directly from Odin in download mode. I would not install it using an App from the play store. This is just my personal preference.
All of the other steps look fine.

viltnieks said:
....Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
....
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Click to expand...
Click to collapse
StockMOD Custom has much (if not all) of the carrier branding removed. It has added some customization tweaks to the ROM; mainly XPosed App and Wanam XPosed Module. It also has a few other custom apps and features from newer Galaxy devices replacing the stock apps. It is themed to look like a Galaxy S5 instead of an S3.
The StockMOD ROM has very little removed; KNOX, Syscope, CarrierIQ, and maybe something else. Other than that it will look almost identical to what you now have, including all of the T-Mobile stuff. This one would match the filename in the thread title. It was created first and the StockMOD Custom was added to the thread afterwards, is my guess.
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
Click to expand...
Click to collapse
I would also suggest this post for backing up imei and other nvdata. Specifically the reboot nvbackup instructions.
Since you are on NC2 bootloader and modem(baseband) do not mess with changing your modem to MJC (step 12). You can confirm that it will work on NC2 in the second line of the changelog of StockMOD Custom thread (post #2)
Another thing: I see StockMOD Custom has an Aroma Installer. I have not used a ROM with this option. Aroma Installer will give you choices during the ROM installation, I can only guess what they are without installing the ROM. The choices probably entail choosing between the stock apps and the later Galaxy device apps; Note 3, S4, and S5.

Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.

viltnieks said:
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
Click to expand...
Click to collapse
You're most welcome. I personally have used several of these methods, redundancy causes no harm.

dawgdoc said:
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
Click to expand...
Click to collapse
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.

viltnieks said:
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
Click to expand...
Click to collapse
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.

dawgdoc said:
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
Click to expand...
Click to collapse
Coould it be related to the fact that I have data_1, data_2, data_3 folder in my root?
Also when I enter /storage/ I have a lot of folders like:
emulate
extSdCard
sdcard0
UsbDruveA
UsbDruveB
UsbDruveC
UsbDruveD
UsbDruveE
UsbDruveF

I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.

viltnieks said:
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
Click to expand...
Click to collapse
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.

dawgdoc said:
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
Click to expand...
Click to collapse
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.

viltnieks said:
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
Click to expand...
Click to collapse
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.

dawgdoc said:
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
Click to expand...
Click to collapse
Thank you very much!

Sprint Note 4 problems after rooting and installing ROM

hello everyone,
to make a long story short, I rooted my note 4. and ever since I've been having nothing but problems.
First I installed OJ6, and then I moved on to COK1 and things did not improve. I'm having serious lag issues, phone freezes while doing the most trivial things like using google maps, and randomly reboots itself.
I followed the steps for flashing each rom with a clean install; that is wiping all data, including internal memory.
at this point, I don't even care about being rooted, I just want my usable phone back.
Is there anything I can do to get my phone back , so that it wont freeze or reboot itself all the time? perhaps I should go back to an older band version???\
any suggestions will be greatly appreciated.
thanks.

likeminas said:
hello everyone,
to make a long story short, I rooted my note 4. and ever since I've been having nothing but problems.
First I installed OJ6, and then I moved on to COK1 and things did not improve. I'm having serious lag issues, phone freezes while doing the most trivial things like using google maps, and randomly reboots itself.
I followed the steps for flashing each rom with a clean install; that is wiping all data, including internal memory.
at this point, I don't even care about being rooted, I just want my usable phone back.
Is there anything I can do to get my phone back , so that it wont freeze or reboot itself all the time? perhaps I should go back to an older band version???\
any suggestions will be greatly appreciated.
thanks.
Click to expand...
Click to collapse
I've had this occasionally after flashing too much stuff. If I were you, I'd backup everything, wipe the whole phone a few times, then Odin stock OK1 tar. From there, you can Odin TWRP, then flash a rooted ROM if you'd like, or stay stock

beezar said:
I've had this occasionally after flashing too much stuff. If I were you, I'd backup everything, wipe the whole phone a few times, then Odin stock OK1 tar. From there, you can Odin TWRP, then flash a rooted ROM if you'd like, or stay stock
Click to expand...
Click to collapse
wipe the phone using TWRP right?
maybe I'm not doing this right but when I wipe everything (including internal memory) I get a message saying there's no OS.

likeminas said:
wipe the phone using TWRP right?
maybe I'm not doing this right but when I wipe everything (including internal memory) I get a message saying there's no OS.
Click to expand...
Click to collapse
Like beezar said, you need to start over fresh. Beginning from your current rom with TWRP recovery installed, do these steps.
1. Reboot to TWRP and do a factory reset then go into advanced wipe options and wipe everything exceptptsd-card and internal storage 3 times.
2. While still in TWRP go back and reboot to download mode and ignore any warnings about no os or root installed.
3. Download the stock OK1 rom tar from here. hhttp://forum.xda-developers.com/showpost.php?p=64337077&postcount=115
4. Extract the downloaded tar zip then open odin and use the "AP" button to point to the extracted rom tar file.
5. Once it finishes LET THE PHONE REBOOT AND ESTABLISH A DATA CONNECTION.
6. When you are ready to root, and flash a custom rom then simply use odin to flash TWRP and then flash the rom in TWRP.

tx_dbs_tx said:
Like beezar said, you need to start over fresh. Beginning from your current rom with TWRP recovery installed, do these steps.
1. Reboot to TWRP and do a factory reset then go into advanced wipe options and wipe everything exceptptsd-card and internal storage 3 times.
2. While still in TWRP go back and reboot to download mode and ignore any warnings about no os or root installed.
3. Download the stock OK1 rom tar from here. hhttp://forum.xda-developers.com/showpost.php?p=64337077&postcount=115
4. Extract the downloaded tar zip then open odin and use the "AP" button to point to the extracted rom tar file.
5. Once it finishes LET THE PHONE REBOOT AND ESTABLISH A DATA CONNECTION.
6. When you are ready to root, and flash a custom rom then simply use odin to flash TWRP and then flash the rom in TWRP.
Click to expand...
Click to collapse
Thank you very much for taking the time to respond with detailed instructions. Much appreciated.
I never did step 5, so I'll be trying that. And afterwards I'll be flashing your ROM.
Thanks again.
Hope you had a nice Christmas and will have an even better new years!

another important thing that should be done
One thing i forgot to mention and I highly recommended. During step 5 from from above, also turn on gps as well as the other location options in settings and get a lock using google maps. Once you do this and have a working data connection THEN you can proceed to flash a custom rom including CM/AOSP based roms. This will save you from having gps and data issues when switching to a custom rom and it only takes a couple of minutes for piece of mind.

Installing TWRP

Sorry to beat a dead horse, I come from the nexus forums and haven't used a samsung device in a while. My friend has the Note 4 with MM on it. Is flashing TWRP as simple as just flashing it via odin with his phone as is? Does he need to complete any process first, before being able to flash TWRP via odin?
Thanks all!

Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk

samep said:
Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks bud. This was really great!

hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..

CorporalCactus said:
hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..
Click to expand...
Click to collapse
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk

samep said:
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??

CorporalCactus said:
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??
Click to expand...
Click to collapse
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk

samep said:
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected

CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
Did you factory reset and wipe internal memory when restoring the backup?
Put your micro sdcard in a card reader and transfer it. If you're trying to transfer while in recovery, that currently doesn't work.
If you're trying to copy your TWRP backup to micro sdcard, the path should be: TWRP/BACKUPS/(your device s/n recognized by TWRP)/(TWRP Backup folder)
Without proper path, TWRP may not see the backup as official. When saving TWRP backups, the TWRP folder as a whole with desired backups should be saved.
If you can't restore the backup, you can flash a ROM that matches bootloader. Like I said before, factory reset and wipe internal memory and flash the ROM.
Sent from my SM-N910P using Tapatalk

CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
At this point I would just recommend flashing a new ROM man.
Sent from my SM-N910P using Tapatalk