Related
I just got the GN3 and naturally, the first thing I did was root it. That took a bit of time because it didn't seem to want to stock. Supersu kept force closing and i would get a pop up saying its been prevented from opening. After a bit i got it though. and used titanium to freeze all the unwanted bloat. but EVERY time i try to install a ROM i get into a boot loop. Ive tried just about every rom that is so far available to us. ive tried removing the battery, wiping cache, and doing system restore. but i just constantly get boot loops. Any thoughts?
kevinallen4325 said:
I just got the GN3 and naturally, the first thing I did was root it. That took a bit of time because it didn't seem to want to stock. Supersu kept force closing and i would get a pop up saying its been prevented from opening. After a bit i got it though. and used titanium to freeze all the unwanted bloat. but EVERY time i try to install a ROM i get into a boot loop. Ive tried just about every rom that is so far available to us. ive tried removing the battery, wiping cache, and doing system restore. but i just constantly get boot loops. Any thoughts?
Click to expand...
Click to collapse
There are three places to look, the CWM bootloop thread, the N900T TWRP bootloop thread, and it's being discussed in the Original Android Development - TWRP thread.. This post will probably get merged.. Either way, need more info, like the recovery you're using, are you able to Odin back to stock etc...
Sent from my SM-N900T using XDA Premium 4 mobile app
Steve Lazarus said:
There are three places to look, the CWM bootloop thread, the N900T TWRP bootloop thread, and it's being discussed in the Original Android Development - TWRP thread.. This post will probably get merged.. Either way, need more info, like the recovery you're using, are you able to Odin back to stock etc...
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Im using TWRP 2.6.3.2. and i am able to odin back to stock. though when i use odin to flash back it doesnt seem to get rid of everything until i restore factory again. its weird. this phone is acing different then any other phone ive used
Steve Lazarus said:
There are three places to look, the CWM bootloop thread, the N900T TWRP bootloop thread, and it's being discussed in the Original Android Development - TWRP thread.. This post will probably get merged.. Either way, need more info, like the recovery you're using, are you able to Odin back to stock etc...
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
and i cant seem to find the twrp thread. can you point me in the right direction?
kevinallen4325 said:
and i cant seem to find the twrp thread. can you point me in the right direction?
Click to expand...
Click to collapse
just to update. i odined back to stock and used the CF root method then installed TWRP 2.3.6.1 and flashed again and no bootloops this time.
ill update if i have any issues in the future.
hope this helps someone
kevinallen4325 said:
just to update. i odined back to stock and used the CF root method then installed TWRP 2.3.6.1 and flashed again and no bootloops this time.
ill update if i have any issues in the future.
hope this helps someone
Click to expand...
Click to collapse
Happy to hear it, I would read the thread, it's right below this one currently, as to avoid the bootloop issue. Also might want to get the .2 release of TWRP just in case., even though it gave you issues the first time..
http://forum.xda-developers.com/showthread.php?t=2471421
Sent from my SM-N900T using XDA Premium 4 mobile app
Steve Lazarus said:
Happy to hear it, I would read the thread, it's right below this one currently, as to avoid the bootloop issue. Also might want to get the .2 release of TWRP just in case., even though it gave you issues the first time..
http://forum.xda-developers.com/showthread.php?t=2471421
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the 2.6.3.2? i believe thats what i was using before that was giving me issues. unless theres something else im missing
kevinallen4325 said:
I just got the GN3 and naturally, the first thing I did was root it. That took a bit of time because it didn't seem to want to stock. Supersu kept force closing and i would get a pop up saying its been prevented from opening. After a bit i got it though. and used titanium to freeze all the unwanted bloat. but EVERY time i try to install a ROM i get into a boot loop. Ive tried just about every rom that is so far available to us. ive tried removing the battery, wiping cache, and doing system restore. but i just constantly get boot loops. Any thoughts?
Click to expand...
Click to collapse
Did you factory reset before Odin. If your going to Odin stock factory reset before. People don't realize Odin doesn't wipe apps/settings..... And system restore in twrp?
Sent from my SM-N900T using Tapatalk 4
---------- Post added at 10:43 AM ---------- Previous post was at 10:41 AM ----------
kevinallen4325 said:
Im using TWRP 2.6.3.2. and i am able to odin back to stock. though when i use odin to flash back it doesnt seem to get rid of everything until i restore factory again. its weird. this phone is acing different then any other phone ive used
Click to expand...
Click to collapse
Odin doesn't factory reset.
Sent from my SM-N900T using Tapatalk 4
deeznutz1977 said:
Did you factory reset before Odin. If your going to Odin stock factory reset before. People don't realize Odin doesn't wipe apps/settings..... And system restore in twrp?
Sent from my SM-N900T using Tapatalk 4
Click to expand...
Click to collapse
i did not factory reset in odin. never had to. usually these things would always wipe everything on the device and put it back completely to stock.
and i havent tried a system restore
kevinallen4325 said:
i did not factory reset in odin. never had to. usually these things would always wipe everything on the device and put it back completely to stock.
and i havent tried a system restore
Click to expand...
Click to collapse
No not in Odin. Factory reset in recovery. Be it twrp/cwm before the Odin flash or stock android recovery 3e after the.flash.....
.... Odin has never wiped apps . I've been using Odin since the vibrant..
And as for the backup restore.. I wouldn't until its all sorted out. Considering I was the first one in a boot loop. It could just be me scared lol
Sent from my SM-N900T using Tapatalk 4
Heres the back story. I flashed a rom that wasnt meant for my version of the GN2. I was excited for it and I didnt read properly. So because of that I lost my IMEI, and the phone had no cellular connection. I fixed that with the toolkit and flashing a new modem. Then I re-flashed the ROM I was using before, CleanROM ACE 5.0.
Forward to now, Anytime I try a new rom, I can get them to work until the first reboot then they bootloop. Ive done full wipes, formats, everything and they all lock up after the first reboot. The only thing Ive been able to get to work is the original CleanROM. Im not sure if Im doing or not doing something wrong, any ideas?
Only one idea ...or rather a question...
Upon the repair of the device ...did you do a full return to stock using the factory shipped rom ???
You should try ...as it will map the partitions properly ...
My thinking is...that despite your efforts ...something within your partitions is still out of whack ...
The flashing of a rom not meant for this device can be particularly damaging as you already know....and may have left a portion undone ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
I used the toolkit to reflash a stock image. The only thing I havent tried is deleting partitions. Does the TWRP offer that ability?
Don't delete partitions ...
You need them...
Run the return to stock method again....
And I mean fully stock ...with the 3e recovery ...then root again with CF autoroot ..and then ODIN flash your TWRP recovery..
Then we can attempt the different Roms...
And remember ...
Use a PC for downloads ...not the device ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Use cwm instead of twrp I had the same issues a longtime ago back in my new to this days lol
Sent from my SAMSUNG-SGH-I317 using Tapatalk
gregsarg said:
Don't delete partitions ...
You need them...
Run the return to stock method again....
And I mean fully stock ...with the 3e recovery ...then root again with CF autoroot ..and then ODIN flash your TWRP recovery..
Then we can attempt the different Roms...
And remember ...
Use a PC for downloads ...not the device ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This seems to have solved my problem, I have skynote working with only a minor issue or two.
420techcloud said:
Use cwm instead of twrp I had the same issues a longtime ago back in my new to this days lol
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
This doesnt seem to have made any affect but Ill continue using cwm just in case.
hi ive been looking around and trying stuff for the past couple days and whatever i do i cant seem to get 4.3 on my note 2. (Rogers, SGH-i317M, 4.1.2) ive tried oneclick, and some otherstuff but idk what im doing wrong
can someone link me or help me out with the easiest way for getting 4.3 on my phone
ps. im trying to do this because i want to be ready for the new DN3 rom coming out, so also if anyone knows if updating isnt even the right move for me to take or knows how to get ready for that rom let me know please and thank you!
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2551707
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
goddi2010 said:
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2551707
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
no i havent tried that yet : o
do i just flash the file the OP said to flash first in Odin under PDA and the ill have 4.3?
Give SN 4.3 a try it's smooth and stable for me no FC's, Wanam Xposed is the bomb! (Std version not the Note3 version) Not sure what carrier you're on but I can confirm that you CAN go back to 4.1.2 effortlessly by following steps listed in OP section.
I had no end of troubles installing with latest TWRP 2.6.3.1 installed it just does not seem to play well with 4.3 at this time. Philz CWM based recovery however solved all issues smoothly. Not a knock on TWRP I've used it on every device I own and still say it's the standard others aspire to!
I had the same problem. I used one click and Pilz recovery. TWRP was the issue.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
I posted a few days ago about my bootlooping in the recovery. I finally fixed it by these 3 steps.
1) Odin flashed Stock 4.4.2 complete as this sets the correct boot loader.
2) I downloaded Twrp 2.7.0 the one that list KitKat (Must say this) 4.4 version.
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
3) Right from Odin when flashing this you set it not to reboot, Once finished you then unplug the usb cable and pull the battery. Let is sit for about 10 sec. Then with the upVlm,Home and Power it will boot to the recovery. It first will post what you said but wait about 10 sec more twrp will come up.
4) Now you should be able to flash any rom you want. I am using axmans N3 for now works great. I will be trying CM 11 later.
5) make a backup once in Twrp
Hope this helps.
helterkelter said:
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
Click to expand...
Click to collapse
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
dragonstalker said:
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
Click to expand...
Click to collapse
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
helterkelter said:
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
Click to expand...
Click to collapse
The kernels you can use are listed in the general thread. A user posted a very good listing of what's what. TWRP 2.7 or Philz Touch are the 2 recoveries i would recommend using. Whichever one you decide will overwrite the other. you can never have 2 recoveries.
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
helterkelter said:
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You are already on the 4.4 bootloader so you can no longer use the Darthstalker rom, you can only use Kit Kat 4.4.2 and above roms from here on out. Next question would be have your rooted your phone since the update and have a custom recovery. If you have not rooted, then you will need to use Odin to run the CF_Autoroot, but that will trip your Knox to 0x1. Thus voiding your warranty.
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Which cwm and twrp are you trying to flash. The only 2 that will work on Kit Kat are PHilz touch latest one, and TWRP 2.7
Twrp 5.7.3
Sent from my SM-N900T using xda app-developers app
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
helterkelter said:
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
oh sorry for the late response. Just got back from boy scouts. Anyway. No you don't need to flash back to stock, Your just flashing the wrong version of TWRP. You can go to the android originial development thread and download the TWRP 2.7 and flash via recovery and you will be all good to go. Also, download the latest Wootever kernel just to make sure you have both angles covered. Both downloads are found in the same section.
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yes, odin the custom recovery and you should have no more issues. As for the bootloops with TWRP, you only had issues with that, because the version you were trying to use was outdated and does not work on Kit Kat
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You have already upgraded to Kit Kat, that part is done. and you ran CF_Autoroot correct in Odin correct? If you have done both steps all that is left is to Odin the Philz Touch Recovery that you downloaded.
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
As long as they are AOSP Roms that support both bootloaders yes, and as i've been told most if not all the AOSP Roms do support the Kit Kat bootloader that you are already on.
Ok thank you again. I will likely flash philz tonight (if hubby allows me to cuz I usually stay up all night til I got my phone the way I want it, ie no boot loops lol) I will report back to let you know if it works. This phone has been through hell and back with me but I've learned a lot!! Especially from contributors such as yourself. :thumbup:
Sent from my SM-N900T using xda app-developers app
Cool. I'm glad I read this thread. I too had same problems.
Sent from my NOTE 3 using Tapatalk
i was wondering if the DN3 rom is ported for sprint note 2?
http://forum.xda-developers.com/showthread.php?t=2504016
the link up there is the original if not can i use this method
http://forum.xda-developers.com/showthread.php?t=2086394
for it?
Ditto Note 3 featuresAir Command
Smart Scroll
Smart Pause
Signature Lock
Writting Buddy (Direct Pen Input)
One Hand Operation in All Screens
S5 Toolbox feature
S5 Power Saving Mode
S5 Ultra Power Saving Mode
S5 Lockscreen Effects
S5 System UI
S5 Launcher with Magazine & Pullup app
S5 WallpaperNote 3
IconsNote 3
MyFilesNote 3
SNoteNote 3
ScrapBookNote 3
SketchBookDual Settings (Note3 & S5) with search feature
Popup menu in many note 3 apps.
Quick Glance
Air GesturePen
Window Manager from @xperiacle
Other note 3 apps like contacts,msg etc.
Note 3 Multiwindow style
Possible to use the same app in both multiwindows
DN3 Exclusive feature called AnyApp allows you to choose custom app instead of S Finder in Air Command.and many more things that we might forget... see it yourself today.
MultiCSC thanks to @sotmax and @joeldroid
Sent from my SPH-L900 using Xparent Skyblue Tapatalk 2
sooooooooo??? is it ported?
THORMUNZ said:
sooooooooo??? is it ported?
Click to expand...
Click to collapse
From all the all roms I have seen, its not available yet...
And as for the patch I was thinking of trying it but im afraid of bricking my phone. You can flash that rom as long as the rom doesnt install two files( which are carrier related). I just cant remember what files. Just read in that thread and look for those files. when u download the rom use root explorer and check that the rom doesnt have them in there.
Let me know how it goes ?
coolwater22 said:
From all the all roms I have seen, its not available yet...
And as for the patch I was thinking of trying it but im afraid of bricking my phone. You can flash that rom as long as the rom doesnt install two files( which are carrier related). I just cant remember what files. Just read in that thread and look for those files. when u download the rom use root explorer and check that the rom doesnt have them in there.
Let me know how it goes ?
Click to expand...
Click to collapse
omg i want this rom so bad 2. some one help us!!!!
drbubbles123 said:
omg i want this rom so bad 2. some one help us!!!!
Click to expand...
Click to collapse
coolwater22 said:
From all the all roms I have seen, its not available yet...
And as for the patch I was thinking of trying it but im afraid of bricking my phone. You can flash that rom as long as the rom doesnt install two files( which are carrier related). I just cant remember what files. Just read in that thread and look for those files. when u download the rom use root explorer and check that the rom doesnt have them in there.
Let me know how it goes ?
Click to expand...
Click to collapse
I tried but never got past boot screen. Op states it needs the knox bootloader and firmware/radio. I will keep trying but it has not been an easy port.
Sent from my SPH-L900 using XDA Premium 4 mobile app
drbubbles123 said:
omg i want this rom so bad 2. some one help us!!!!
Click to expand...
Click to collapse
You're not alone. That makes two of us. Errrr
jlmancuso said:
I tried but never got past boot screen. Op states it needs the knox bootloader and firmware/radio. I will keep trying but it has not been an easy port.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you could get this working. Omg I would love you forever and ever. And ever. ?
+10!!
jlmancuso said:
I tried but never got past boot screen. Op states it needs the knox bootloader and firmware/radio. I will keep trying but it has not been an easy port.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So to confirm, you tried the patch at http://forum.xda-developers.com/showthread.php?t=2086394 and you got stuck on the flashing Samsung logo? Me being the noob that I am, I (stupidly) decided to simply go ahead and flash the N7100 version on my L900 following the instructions for the N7100 (original) varient. It of course bricked me, never got anything beyond the flashing Samsung logo, just does that forever until I pulled the battery.
However, by attempting to flash it I seem to have created other problems and here's where I'm stumped. I am now unable to restore my TWRP Nandroid I made of my stock rooted MK4 before flashing, restoring that results in getting stuck at the flashing Samsung logo (again). It doesn't matter what options I restore in TWRP (System, Boot, Data, etc) it has the same result: the flashing Samsung logo forever and ever and ever. I read somewhere that 4.4 (the DN3 ROM) messes with partitions because it enables multi user support...could that have anything to do with it? The only way I have been able to get my device back working is flashing stock unrooted MD4 TAR through Odin. I'd really rather not start from scratch though on my settings and everything though, and the only backup I have is that Nandroid, no Titaniums or anything else. Can you help me restore the Nandroid or is it a lost cause?
sweyers said:
So to confirm, you tried the patch at http://forum.xda-developers.com/showthread.php?t=2086394 and you got stuck on the flashing Samsung logo? Me being the noob that I am, I (stupidly) decided to simply go ahead and flash the N7100 version on my L900 following the instructions for the N7100 (original) varient. It of course bricked me, never got anything beyond the flashing Samsung logo, just does that forever until I pulled the battery.
However, by attempting to flash it I seem to have created other problems and here's where I'm stumped. I am now unable to restore my TWRP Nandroid I made of my stock rooted MK4 before flashing, restoring that results in getting stuck at the flashing Samsung logo (again). It doesn't matter what options I restore in TWRP (System, Boot, Data, etc) it has the same result: the flashing Samsung logo forever and ever and ever. I read somewhere that 4.4 (the DN3 ROM) messes with partitions because it enables multi user support...could that have anything to do with it? The only way I have been able to get my device back working is flashing stock unrooted MD4 TAR through Odin. I'd really rather not start from scratch though on my settings and everything though, and the only backup I have is that Nandroid, no Titaniums or anything else. Can you help me restore the Nandroid or is it a lost cause?
Click to expand...
Click to collapse
You will have to do odin back to stock. Then odin a recovery and restore your nandroid.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Did you guys see this? haven't tried it, but fyi:
https://www.youtube.com/watch?v=zJ3ViFtAAFk
jlmancuso said:
You will have to do odin back to stock. Then odin a recovery and restore your nandroid.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did that...still results in flashing Samsung logo hang up when I restore the Nandroid with TWRP . I really haven't the slightest clue why this is happening, as my phone is currently running stock unrooted MK4 flashed from ODIN just fine.
sweyers said:
Did that...still results in flashing Samsung logo hang up when I restore the Nandroid with TWRP . I really haven't the slightest clue why this is happening, as my phone is currently running stock unrooted MK4 flashed from ODIN just fine.
Click to expand...
Click to collapse
I see your problem. Twrp does not backup or restore 4.3 properly. You need to use Philz 6.07.9
Sent from my SPH-L900 using XDA Premium 4 mobile app
I'm working with eteam to port dn3 4.4.2 kitkat to AT&T tmobile and 7105, we are almost there. It's running solid. I may then consider porting it to vzw and sprint
Sent from my iPad using Tapatalk
Be patient. It's coming.
Sent from my GT-N7105 using Tapatalk
mtech5 said:
Be patient. It's coming.
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Lol I thought that was directed at me for a sec lol
Sent from my iPad using Tapatalk
eZdubzitmk4 said:
I'm working with eteam to port dn3 4.4.2 kitkat to AT&T tmobile and 7105, we are almost there. It's running solid. I may then consider porting it to vzw and sprint
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Please please port it to sprint note 2. Ive been eager to try this rom. But like they say patience is a virtue. so I cant do anything but wait...keep it up guys
jlmancuso said:
I see your problem. Twrp does not backup or restore 4.3 properly. You need to use Philz 6.07.9
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I haven't installed Philz recovery yet, but considering my Nandroid was made with TWRP will Philz even see it? The only reason I ask is because IIRC Philz is based off of TWRP, no? What I'm getting at here is that I'm pretty sure Nandroids from different recoveries, for example CWM and TWRP are completely incompatible right?
If I can't restore the backup I made from TWRP in Philz am I dead in the water? If so, I guess I learned my lesson, that is to have a contingency plan such as Titaniums in place (particularly for settings). I guess I really didn't expect a Nandroid to just fail spectacularly...if TWRP really is completely borked up with backup/restore on 4.3 it would be nice if they had a warning somewhere in the recovery or on their site. I would think that would be kind of important to know before you try to use a backup made using their recovery...
sweyers said:
Well I haven't installed Philz recovery yet, but considering my Nandroid was made with TWRP will Philz even see it? The only reason I ask is because IIRC Philz is based off of TWRP, no? What I'm getting at here is that I'm pretty sure Nandroids from different recoveries, for example CWM and TWRP are completely incompatible right?
If I can't restore the backup I made from TWRP in Philz am I dead in the water? If so, I guess I learned my lesson, that is to have a contingency plan such as Titaniums in place (particularly for settings). I guess I really didn't expect a Nandroid to just fail spectacularly...if TWRP really is completely borked up with backup/restore on 4.3 it would be nice if they had a warning somewhere in the recovery or on their site. I would think that would be kind of important to know before you try to use a backup made using their recovery...
Click to expand...
Click to collapse
Okay lets cover the backup types first. Philz will backup/restore in both twrp and cwm format but you have to select the option. Now about your backup it will still be no good since it was created with twrp.
jlmancuso said:
Okay lets cover the backup types first. Philz will backup/restore in both twrp and cwm format but you have to select the option. Now about your backup it will still be no good since it was created with twrp.
Click to expand...
Click to collapse
now that we have 4.4.2 there shouldn't be a reason we cant get this rom ported