Develop Bugs

[Q] Root for SM-P605 kitkat

Hey
I been looking in the forums, but I havent be able to finde if there is a root for kitkat.
Do anyone know if that is one and if so, can you plz link to the thread
Thaning you in advance

Yes: http://autoroot.chainfire.eu
Although I have a p600 and his method worked fine for JB and KK.

Don't use the P6700/601 cf-autoroot on your P605. It will brick it...
The old cf-autoroot is for JB and doesn't work on KK...
Go to the Original developement thread and look at the TWRP 2.7.0.1 thread. It will supply answers and links...

ultramag69 said:
Don't use the P6700/601 cf-autoroot on your P605. It will brick it...
The old cf-autoroot is for JB and doesn't work on KK...
Go to the Original developement thread and look at the TWRP 2.7.0.1 thread. It will supply answers and links...
Click to expand...
Click to collapse
Hi,
TWRP 2.7.0.1 not work to P605XXUCNE2 !!!
What recovery works?
@+
Pyrana

Root p605kitkat 4.4.2
Hi All, hope I'm posting this is the right forum .Im quite a beginner in Android terms so please be patient with me ...
I have a Galaxy Note 10.1 2014 sm-p605 and use it while travelling , i dont have a computer with me most of the time so i rely on the tablet for most of what i do , yesterday i have updated to android 4.4.2 kitkat , whitout knowing i would loose full access to my 32 Gb SD card...well that made me quite furious as most people...so i decided try rooting it , after backing up all my files i used CF Auto Root ( CF-Auto-Root-lt03lte-lt03ltexx-smp605.zip , well that didnt quite work as i was getting
the boot loopwith the message RECOVERY IS NOT SEANDROID ENFORCING, after much reading i was able to recover the tablet to boot back , no rooting was done but im pretty sure i triggered knox and voided the warranty ....anyway i still want to try getting full access to my SD card, either by rooting it or any other way ,if there is a valid file explorer app without root i am keen to know, or if anyone can show me the way to root this device I will really appreciate.Device Details:
AP605ZSUCNE3
CP: P605ZSUCNE1
csc605OZSUCNE3
KitKat 4.4.2

With all do respect TWRP 2.7.0.1 does work on 4.4.2
I have it working myself.
Now To gain root on 4.4.2, install Autoroot - Chainfire for the SM P905
Then search the forums for a P605 recovery (Its somewhere here)
Youll get full root with original stock recovery. Then flash TWRP 2.7.0.1 and then youll be fine.
Remember the current TWRP version on the main post isnt the correct version...Further into the thread there is the correct version.
Need any help. as per always im on Facebook and Am happy to teamviewer in

fkofilee said:
With all do respect TWRP 2.7.0.1 does work on 4.4.2
I have it working myself.
Now To gain root on 4.4.2, install Autoroot - Chainfire for the SM P905
Then search the forums for a P605 recovery (Its somewhere here)
Youll get full root with original stock recovery. Then flash TWRP 2.7.0.1 and then youll be fine.
Remember the current TWRP version on the main post isnt the correct version...Further into the thread there is the correct version.
Need any help. as per always im on Facebook and Am happy to teamviewer in
Click to expand...
Click to collapse
No need to flash auto root for P905 just flash supersu from recovery TWRP 2.7.0.1 WORKS on 4.4.2!!!!

alex_72gr said:
No need to flash auto root for P905 just flash supersu from recovery TWRP 2.7.0.1 WORKS on 4.4.2!!!!
Click to expand...
Click to collapse
Hi,
Test TWRP 2.7.0.1 and no found !! to Kitkat
Big problem screen fully striped and very difficult to restore! And autoroot is a disaster!

Alan-B said:
Hi,
Test TWRP 2.7.0.1 and no found !! to Kitkat
Big problem screen fully striped and very difficult to restore! And autoroot is a disaster!
Click to expand...
Click to collapse
Mate, you were told cf-autoroot DOESN'T work and will screw things up... Why did you flash over something not working right?
You needed to find the stock recovery first, then flash 2.7.0.1 (not 2.7.0.0) to get TWRP installed. You then flash latest supersu using TWRP. This will root your device and give you a custom recovery..
The only thing is TWRP can't make a backup to the External sd card if you have it formatted exFAT...
Best advice, flash stock rom (kitkat only) again using PC ODIN, try again...

ultramag69 said:
Mate, you were told cf-autoroot DOESN'T work and will screw things up... Why did you flash over something not working right?
You needed to find the stock recovery first, then flash 2.7.0.1 (not 2.7.0.0) to get TWRP installed. You then flash latest supersu using TWRP. This will root your device and give you a custom recovery..
The only thing is TWRP can't make a backup to the External sd card if you have it formatted exFAT...
Click to expand...
Click to collapse
Yep, autoroot for P605 hasnt been updated yet to 4.4.2
Yes you can flash twrp and then SU , I came from the full firmware reflash... I t was the only way to put root on at the time.

Alan-B said:
Hi,
Test TWRP 2.7.0.1 and no found !! to Kitkat
Big problem screen fully striped and very difficult to restore! And autoroot is a disaster!
Click to expand...
Click to collapse
You can follow those links to get what you need.
http://forum.xda-developers.com/showpost.php?p=53236030&postcount=19

alex_72gr said:
You can follow those links to get what you need.
http://forum.xda-developers.com/showpost.php?p=53236030&postcount=19
Click to expand...
Click to collapse
Hi,
Having installed TWRP 2.7.0.1 on P605XXUCNE2 everything planted me! over the boot rom recovery mode and more !!!!
I spent two hours to get to switch back download.J 'thought my Note2 LTE 2014 was dead!
Sorry for the translation, I'm French

Alan-B said:
Hi,
Test TWRP 2.7.0.1 and no found !! to Kitkat
Big problem screen fully striped and very difficult to restore! And autoroot is a disaster!
Click to expand...
Click to collapse
0. If you screwed something up, flashed a wrong recovery, flash the stock rom again. If you are stuck in a boot loop, there is plenty of thread about how to boot into odin mode from there.
1. Download attached TWRP 2.7.0.1, it works with P605. I have it myself.
2. Start the tablet, download SuperSU-v1.99r4.zip, place on SD Card.
3. Reboot into Odin mode, (VolDown+Home), flash TWRP. If your recovery is being restored, don't tick Auto Reboot in Odin and turn off manually after flashing, then boot into TWRP.
4. Boot into TWRP, reset to factory settings. You will be asked if you want Root at some point. I think it's when you reboot, I don't remember.
5. When booted into Android, see if SuperSU downloader app is there. If no - boot TWRP and look around, because you missed something.
If yes, reboot into TWRP again and flash UPDATE-SuperSU-v1.99r4.zip.
Congrats, you are now rooted.

xda_user_p600 said:
0. If you screwed something up, flashed a wrong recovery, flash the stock rom again. If you are stuck in a boot loop, there is plenty of thread about how to boot into odin mode from there.
1. Download attached TWRP 2.7.0.1, it works with P605. I have it myself.
2. Start the tablet, download SuperSU-v1.99r4.zip, place on SD Card.
3. Reboot into Odin mode, (VolDown+Home), flash TWRP. If your recovery is being restored, don't tick Auto Reboot in Odin and turn off manually after flashing, then boot into TWRP.
4. Boot into TWRP, reset to factory settings. You will be asked if you want Root at some point. I think it's when you reboot, I don't remember.
5. When booted into Android, see if SuperSU downloader app is there. If no - boot TWRP and look around, because you missed something.
If yes, reboot into TWRP again and flash UPDATE-SuperSU-v1.99r4.zip.
Congrats, you are now rooted.
Click to expand...
Click to collapse
Re hello,
he problem is that just after the flash TWRP nothing boot! or recovery (zebra screen) and reboot loop and very difficult to switch back to download due to the reboot loop!
Just TWRP 2.7.0.0 works with Version 4.3 Note: The 2.7.0.1 works with 4.3 rom or not ? just to test !
Thank you for the helps

Alan-B said:
Re hello,
he problem is that just after the flash TWRP nothing boot! or recovery (zebra screen) and reboot loop and very difficult to switch back to download due to the reboot loop!
Just TWRP 2.7.0.0 works with Version 4.3 Note: The 2.7.0.1 works with 4.3 rom or not ? just to test !
Thank you for the helps
Click to expand...
Click to collapse
Attached version works with 4.4.2 Nordic.
After you flashed wrong recovery and have "zebra screen", Make sure you flashed stock firmware after that. Don't try flashing anything else before you flash stock.

xda_user_p600 said:
Attached version works with 4.4.2 Nordic.
After you flashed wrong recovery and have "zebra screen", Make sure you flashed stock firmware after that. Don't try flashing anything else before you flash stock.
Click to expand...
Click to collapse
re...
I just tested a flash TWRP from your link, but it boot and stuck on the TAB 10.1 lte logo

Mate, flash Kitkat rom 1st then flash TWRP... Doing anything else is gonna get you in trouble...
2.7.0.1 TWRP has Kitkat recovery, not Jellybean so you will have issues if you flash on a Jellybean rom...

ultramag69 said:
Mate, flash Kitkat rom 1st then flash TWRP... Doing anything else is gonna get you in trouble...
2.7.0.1 TWRP has Kitkat recovery, not Jellybean so you will have issues if you flash on a Jellybean rom...
Click to expand...
Click to collapse
Re hello, and always attempts to boot and TWRP stuck on 10.1 NOTE and the red and blue lines jaune.testé logo with flash P605XXUCNE2_P605OXACNE2_P605XXUCNE2_HOME.tarre, boot in download mod and flash TWRP without reboot, then reboot manual recovery (stuck) Same with auto reboot and there is nothing not to have the display of recovery!

I understand you. Are you sure you're not missing anything? It might help to flash stock NEE again. In my case I ticked "Update boot loader", do you mind trying that?
Remember, TWRP is VolUp+Home. It should display colored text in the right upper corner on 2014 logo when booting, if it's entering recovery mode.

Hi,
Solved it is Ok....
Thanks

[ROM][d802] Recovery Flashable PURE STOCK EUR OPEN 80220f (+ root)

Made this from the new 80220f open EUR kdz.
This is the complete LG KK 20f ROM - nothing missing or messed with.
You can flash SuperSU and get root if you wish - your choice.
I provide this assuming you have an understanding of the terminology used below and appreciate that any flashing activity has some risk.
I strongly advise against using any form of restore from previous backups, such as TB or Nandroid.
Once the process is complete, custom recovery will be lost.
Method:
Download both the ROM zip file linked below and SuperSU zip file (if you want root) and copy to your SD card.
You need to be already on Rooted JB, Rooted KK or PURE CM11 with either TWRP 2.6.3.3 or 2.6.3.4 or TWRP 2.7.0.0 (nothing else).
Reboot to TWRP recovery
Wipe: System, Data, Cache. Dalvik (nothing else)
Flash the ROM zip - ignore any "FAIL" warnings.
Wipe Cache and Dalvik (nothing else)
Go to the Mount page in TWRP and select System (leave the other defaults alone)
Flash the SuperSU zip - ignore any "FAIL" warnings
Reboot
Done
Don't use AutoRec to flash TWRP - you will lose Knock code.
Alternatively - if you have flashed TWRP on another KK Stock ROM (using AutoRec), you can full wipe (not SDCard) and flash this directly without going back to JB.
Download from here:
https://drive.google.com/file/d/0B_ESvfVtZzEwaWRaTjRNUEdDOEE/edit?usp=sharing
Credit to Chainfire for the rooting method.

good job. but you don't put the download ?

paglop said:
good job. but you don't put the download ?
Click to expand...
Click to collapse
Link is there....!

why use AutoRec ? the recovery is lost ?

how do i acquire custom recovery once i flash 20f? flashify app?

zekurosu said:
how do i acquire custom recovery once i flash 20f? flashify app?
Click to expand...
Click to collapse
if we just edit the updater script and remove the recovery partition , our recovery wont be wiped just note that you should never take any OTA while u have custom recovery.

paglop said:
why use AutoRec ? the recovery is lost ?
Click to expand...
Click to collapse
Yes,you will lose your custom recovery if you install this stock rom. But don't care about it.You may use AutoRec and your recovery will be back :good:
Edit : Hmm i think knock code will unusable if we flash TWRP with AutoRec.
Edit 2 : Aarghh i misunderstood. After using AutoRec and we will install any kernel with knock code support.

Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this.

Art Vanderlay said:
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this. If you want to have a pure stock ROM, kernel and all, its easiest to use the alternative method to keep your recovery (at the bottom of the op)
Click to expand...
Click to collapse
If i'm not wrong,the alternative method is not addicted to keep custom recovery. The custom recovery (whatever you have) won't be there after flashing this rom all the way mate.:good:

Art Vanderlay said:
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this.
Click to expand...
Click to collapse
Precisely!
If someone already has Custom Recovery, and isn't overly bothered about preserving it, then this is potentially quicker and easier that then kdz method. And with easy root. Big plus point.
If you want a completely Stock experience of course.
What we don't know is how much development LG have done with the kernel. So, if one uses Autorec, any benefits of a later LG stock kernel will be lost.
Enjoy!

I am on v20d stock kit kat rooted with ioroot. D802 model. Does this flashabel rom include bootloader? Cause to have a custom recovery, I will have to use autorec app, which will dowgrade my bootloader. So will this rom work if the recovery has been flashed with autorec?
And also flashing this rom means that stock recovery will be flashed too?

I installed this 20f. it corrects problems ratio with slimport on small screen.

Just updated to D80220F. I can confirm that there is a Google Folder pre created. Havent noticed much else yet. will keep you updated.
Whole system feels super fast. Is it just me or is this faster than 802D/802B?
Knock on seems more reliable. Senses it way better and ignores ghost touches better.. Auto brightness seems to be managing brightness better too.

i have twrp 2.7.0.0 custom recovery, and i'm on d802b firmware (kk stock) with dorimanx kernel...
just 1 question to be sure (because i didn't quite get the OP):
- will i lose twrp if i flash this zip? (if yes, how do i get custom recovery back and safely?)
thanks in advance

Not option for ART
---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------
60nine yes you lose twrp. It is for return to official.

ok, thanks... and how do i get twrp back? is it even possible?
on that matter - can "recovery.bin" from this zip be replaced by custom recovery .bin file?

shriom_manerker said:
if we just edit the updater script and remove the recovery partition , our recovery wont be wiped just note that you should never take any OTA while u have custom recovery.
Click to expand...
Click to collapse
Can you make a tutorial or write it down how you did it??? Because I wan't stock rom but don't want to lose recovery....

First root, and autorec for instal recovery. But you need a custom kernel .
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
read a little before

ok, so autorec works for 20f... all i wanted to know... (i don't care for knock code, i just want knock on to work)
the OP was a bit confusing - maybe it needs to be updated with a basic FAQ...
if anyone tried to flash this, then used autorec for custom recovery and flashed latest dorimanx 5.7 kernel - please confirm if knock on works (not knock code)
thanks in advance

Not kernel just autorec

[Q] How to flash CWM on Xperia S Stock JB?

Hi all,
I'm messing around with my girlfriends Xperia S and śtuck on installing a custom recovery (CWM seems to be the preferred one on the S).
The System:
Stock Sony JB
Build 6.2.B.1.96
What I already did:
Root
Backup TA
Unlocked Bootloader (official way via Sony website)
What I already tried to install custom recovery:
RecoverX App on PlayStore -> Recovery not booting when tapping the sony logo while booting (black screen for some seconds then reboot to Android)
Xperia S Dual Recovery (Linux script) -> Installation successful but no chance to boot one of the recoveries via Vol +/-, no blue LED, boots directly to Android
What I'm trying to achieve:
Install CM 11 with root access
I'm kind of experienced with HTC phones and my OnePlus One so not a complete noob but it looks like Sony phones are a different thing.
I read about the need to flash a custom kernel which includes the recovery but there are seperate recovery threads on the other hand. The sticky role up threads seem out of date.
Been reading since yesterday but this only lead to more confusion.
I hope someone can help me out getting CWM (or any other recommended recovery) on this phone to install CM 11.
And how to remove the recoveries I already installed and don't work?
EDIT 13:58
After further reading this looks like the way to go:
[RECOVERY] CWM-Based Recovery 6.0.2.7 for Xperia S (UnlockedBootLoader){JB}[20130824]
Correct? I don't want to end up bricking the device by trying different things. Can I flash CM11 ROMS using this recovery? The post says "do not use this for flashing CM10.1 (u will need to use the CM kernel for that)" which keeps confusing me ...
And how do I remove the recoveries already installed (list above) but not working?

real_sl4cker said:
Hi all,
I'm messing around with my girlfriends Xperia S and śtuck on installing a custom recovery (CWM seems to be the preferred one on the S).
The System:
Stock Sony JB
Build 6.2.B.1.96
What I'm trying to achieve:
Install CM 11 with root access
I'm kind of experienced with HTC phones and my OnePlus One so not a complete noob but it looks like Sony phones are a different thing.
I read about the need to flash a custom kernel which includes the recovery but there are seperate recovery threads on the other hand. The sticky role up threads seem out of date.
Been reading since yesterday but this only lead to more confusion.
I hope someone can help me out getting CWM (or any other recommended recovery) on this phone to install CM 11.
And how to remove the recoveries I already installed and don't work?
Click to expand...
Click to collapse
First copy the zip of CM11 ROM to the phone.
Then on PC, extract the boot.img (this is the custom kernel with recovery for the ROM) from the ROM zip and flash it via fastboot using the flashtool software. Then You will have a twrp installed in Your phone due to it. Now boot into twrp and flash the ROM.
Note, after You flash the boot.img, You won't be able to boot into stock firmware. You will have to flash the CM11 ROM.
Also, if the recovery are not accessible, they are probably not installed, so no need to remove them.

Mirhawk said:
First copy the zip of CM11 ROM to the phone.
Then on PC, extract the boot.img (this is the custom kernel with recovery for the ROM) from the ROM zip and flash it via fastboot using the flashtool software. Then You will have a twrp installed in Your phone due to it. Now boot into twrp and flash the ROM.
Note, after You flash the boot.img, You won't be able to boot into stock firmware. You will have to flash the CM11 ROM.
Also, if the recovery are not accessible, they are probably not installed, so no need to remove them.
Click to expand...
Click to collapse
Thank you very much for the instructions, now there's less confusion :good:
So let's see how it works with Paranoid Android. I'll report back afterwards.
Any Android 4.4 ROM recommendation as a stable daily driver?
Looks like there is no up to date standard CM11 build for the Xperia S

real_sl4cker said:
Thank you very much for the instructions, now there's less confusion :good:
So let's see how it works with Paranoid Android. I'll report back afterwards.
Any Android 4.4 ROM recommendation as a stable daily driver?
Looks like there is no up to date standard CM11 build for the Xperia S
Click to expand...
Click to collapse
From what I have been reading, PA does seem to be stable enough to be a daily driver, just find the correct build of it. I don't know which one is as I don't use it much, do ask in the thread.
I would suggest Carbon ROM too, but it is currently having some battery drain issues, the battery works for hardly an entire day.

Mirhawk said:
From what I have been reading, PA does seem to be stable enough to be a daily driver, just find the correct build of it. I don't know which one is as I don't use it much, do ask in the thread.
I would suggest Carbon ROM too, but it is currently having some battery drain issues, the battery works for hardly an entire day.
Click to expand...
Click to collapse
Thanks. I already found the current PA build in the thread (4.5 beta2) and apart from German translations missing in PA settings up to now it performs well [emoji3]

[Q] Total noob here, need (probably very basic) help

Hello, first time poster here!
I bought Samsung Galaxy Ace 2 GT-I8160 and I want to flash CM 11 on it, because the stock Samsung's ROM is very bloated and slow.
I am looking at CM 11 from NovaFusion, which can be found novafusion.pl website.
I have currently downloaded:
cm11.0_codina.nova.20141215.zip
pa_gapps-modular-pico-4.4.4-20150106-signed.zip
I chose pico gapps because I want as less bloat as possible (only actually need Play Store).
The problem is, I don't know what to do next...
Now, I have a few questions:
Can I just flash CM trough the stock/default recovery mode that is already on the phone?
Can I use Odin to flash CM? If so, where is a trusted Odin download?
How do I restore the stock ROM that came with the phone if something goes (terribly :silly wrong?
Is it possible to reset flash counter and any other traces of root & custom ROMs on this phone in case I want to return it to warranty?
I added the "About device" info in the attachment!

1. flash it trough cwm temporary
2. no, you can't. novafusion didn't release Odin package for codina now.
3. backup your stockrom using cwm temporary
4. flashing rom trough cwm not increase flash counter

ekky21 said:
1. flash it trough cwm temporary
2. no, you can't. novafusion didn't release Odin package for codina now.
3. backup your stockrom using cwm temporary
4. flashing rom trough cwm not increase flash counter
Click to expand...
Click to collapse
Thanks a lot for responding!
Can you link me to CWM for this phone?
Also, how does the "temporary" mode work? Does it load up recovery from the microSD card? Just curious.

MrDinner said:
Hello, first time poster here!
I bought Samsung Galaxy Ace 2 GT-I8160 and I want to flash CM 11 on it, because the stock Samsung's ROM is very bloated and slow.
I am looking at CM 11 from NovaFusion, which can be found novafusion.pl website.
I have currently downloaded:
cm11.0_codina.nova.20141215.zip
pa_gapps-modular-pico-4.4.4-20150106-signed.zip
I chose pico gapps because I want as less bloat as possible (only actually need Play Store).
The problem is, I don't know what to do next...
Now, I have a few questions:
Can I just flash CM trough the stock/default recovery mode that is already on the phone?
Can I use Odin to flash CM? If so, where is a trusted Odin download?
How do I restore the stock ROM that came with the phone if something goes (terribly :silly wrong?
Is it possible to reset flash counter and any other traces of root & custom ROMs on this phone in case I want to return it to warranty?
I added the "About device" info in the attachment!
Click to expand...
Click to collapse
1. Well, I think the stock recovery doesn't allow you to install zip from sdcard. That's why we use CWM instead (plus it does more things than stock recovery). I recommend CWM
2. No, Custom ROM should be flashed through CWM, I think...
3. You can backup your current ROM (includes apps installed) through CWM and if something goes wrong, you can easily restore it from CWM again. BUT, if somehow you can't get to CWM, you can use ODIN to flash stock ROM and your phone should be back to its original state
4. Yup, it can be done from CWM or ODIN.. same method as in my 3rd answer
PS. I only gave answers to stuff I've done before.. basically, my answers are based on self-experience hope it helps!
---------- Post added at 12:46 PM ---------- Previous post was at 12:42 PM ----------
MrDinner said:
Thanks a lot for responding!
Can you link me to CWM for this phone?
Also, how does the "temporary" mode work? Does it load up recovery from the microSD card? Just curious.
Click to expand...
Click to collapse
Mm.. from what I remember... Temporary CWM will not replace your stock recovery, and you will need to flash the CWM everytime you want to get into CWM Recovery .-.

MrDinner said:
Thanks a lot for responding!
Can you link me to CWM for this phone?
Also, how does the "temporary" mode work? Does it load up recovery from the microSD card? Just curious.
Click to expand...
Click to collapse
Here : Temporary CWM.

Thank you everyone, I got CM 11 working easy and nice! :good:
Also, looks like the NovaFusion CM 11 ROM did something to the recovery, now it always boots to CWM even without a microSD card.
Does that mean that I can't get back to old recovery? Can I just flash stock ROM and get it back?
P. S. everything is so damn fast and smooth compared to stock ROM!!!

MrDinner said:
Thank you everyone, I got CM 11 working easy and nice! :good:
Also, looks like the NovaFusion CM 11 ROM did something to the recovery, now it always boots to CWM even without a microSD card.
Does that mean that I can't get back to old recovery? Can I just flash stock ROM and get it back?
Click to expand...
Click to collapse
Yes, Custom ROMs like CM 11 have CWM Recovery or TWRP instead of Stock Recovery because they have functions such as backup your system and more. If you really want to have Stock Recovery then you have to flash Stock ROM using Odin.
MrDinner said:
P. S. everything is so damn fast and smooth compared to stock ROM!!!
Click to expand...
Click to collapse
Right. Probably that's why most of the people here use Custom ROMs.

[SOLVED] SGH-i317 Custom Rom Installation (No Rom Works)

Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help

are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105

I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.

yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
I m not sure about it. Do they actually differ ? i317 and n7105 (My thoughts they are same, Actually ALL Canadian versions of note 2 are same)

xtacydima said:
I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.
Click to expand...
Click to collapse
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.

First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
lsdhillon said:
Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
Click to expand...
Click to collapse

yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
majicmazo said:
First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
Click to expand...
Click to collapse
I m gonna go to twrp 2.8.5. Hopefully it works. Will be back with results soon.

i get this error after installation (Using twrp 2.8.5.0 now)
"unmount of /system failed; no such volume"
Probably this is cause?
How to fix it?
and
I m using twrp for t0lte (i have SGH-i317m) I hope its all right with that.

lsdhillon said:
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.
Click to expand...
Click to collapse
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.

that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane

xtacydima said:
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.
Click to expand...
Click to collapse
Could you please guide me to stable risk-free custom kernel for my sgh-i317

yaro666 said:
that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane
Click to expand...
Click to collapse
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
lsdhillon said:
Could you please guide me to stable risk-free custom kernel for my sgh-i317
Click to expand...
Click to collapse
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp

xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
Click to expand...
Click to collapse
really stock kernel with MJ5 modem and old bootloader up until this year january, as I updated to RR 5.1.1 and then updated bl, modem to OC and flashed CM13

xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp
Click to expand...
Click to collapse
I flashed AGNI kernel but the results were still same. Now gonna flash http://d-h.st/JUm as xtacydima suggested(Thanks).
Hope it works.
Will be back with results soon.
Do i need to update modem? to install RR (Marshmallow)?

With http://d-h.st/JUm as xtacydima suggested
It doesnt pass note 2 logo
Just goes blank after note 2 logo, So i think it isnt supported.
i m on 4.4.2 stock now.
Another thing i note is that my baseband is "unknown".
Any suggestions?

I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help