Samsung GalaxyNote 2 AT&T - Always Stuck On Galaxy Note II Screen - Galaxy Note II General

Hey all,
I have read all over the place but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is 4.3 (I think; I go to About Device and I see the android version 4.3)
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.

Wrong Section for your Note II

McLaren__F1 said:
Wrong Section for your Note II
Click to expand...
Click to collapse
Thanks for letting me know. Where should I post it?

You'd get more replies here
http://forum.xda-developers.com/galaxy-note-2-att

Related

[Q] Boot Loop Frustration

I have searched around and can't seem to find a similar problem with a solution that I can understand. I used superoneclick to root my Verizon Galaxy 7" tablet. Everything seemed to go fine, but I really didn't have time to do anything "techy" with it. After a couple of weeks the tablet was acting kind of glitchy, nothing terrible, so I should have just left it alone. Instead I tried to do a complete factory reset. I tried several times, but it would never completely reset. My personalized wallpaper would show up, then all my apps were still there, settings didn't appear to change, etc.
I tried using Hemdall and loading new cache, param, system & zImage files. Now I am stuck in a boot loop. The machine will power up to the setup wizard, but every step generates multiple FCs until the setup wizard itself FC. Then it powers down and starts all over again. "Wipe data/factory reset" produces no change to the problem.
At this point I just want to restore my tablet to stock. No root, nothing fancy.
Can someone recommend a clear, easy to follow, current tutorial for me. I have downloaded Odin, but am uncertain which ROM I need to use. I really don't care which method you recommend as long as it is detailed (ie. written for a complete idiot to follow).
Thanks for any help.
2 things. Are you talking about a regular 7" galaxy or the 7.7? And this will most likely be moved because its a question and questions go in the general section.
mmcounts said:
i have searched around and can't seem to find a similar problem with a solution that i can understand. I used superoneclick to root my verizon galaxy 7" tablet. Everything seemed to go fine, but i really didn't have time to do anything "techy" with it. After a couple of weeks the tablet was acting kind of glitchy, nothing terrible, so i should have just left it alone. Instead i tried to do a complete factory reset. I tried several times, but it would never completely reset. My personalized wallpaper would show up, then all my apps were still there, settings didn't appear to change, etc.
I tried using hemdall and loading new cache, param, system & zimage files. Now i am stuck in a boot loop. The machine will power up to the setup wizard, but every step generates multiple fcs until the setup wizard itself fc. Then it powers down and starts all over again. "wipe data/factory reset" produces no change to the problem.
At this point i just want to restore my tablet to stock. No root, nothing fancy.
Can someone recommend a clear, easy to follow, current tutorial for me. I have downloaded odin, but am uncertain which rom i need to use. I really don't care which method you recommend as long as it is detailed (ie. Written for a complete idiot to follow).
Thanks for any help.
Click to expand...
Click to collapse
wrong section...please post in q&a section...........
Moving?
Should I repost in the Q&A section or will the post be moved automatically? I don't see an option to move the post myself.
Moved To General​
Please Post all questions in the General section​
7 or 7.7
Regarding the 7 or 7.7 question: I don't know which it is because I can't get it to boot up long enough to go into settings. According to the label it is an SCH-i800. It was purchased from Verizon in March 2011. I am pretty sure that it is a 7. Is there any way to tell just by looking at it?
Just determined it is a 7.0 per the Samsung webpage.
I guess I am in the wrong forum again. I am going to post in the General Galaxy Tablet forum.
Googled your model # you listed and stock rom and found this tutorial. Hope this helps you.
Thanks. I have tried that one a couple of times. It is close, but no cigar. I appreciate you thinking of me.
Some boot loop problems can be solved by letting the battery go flat overnight to get out of the loop, recharging then booting normally and doing a factory reset. If that doesn't work then re-flashing using Odin followed by a factory reset is worth trying.
You can get the firmware for flashing here:
http://www.samfirmware.com/
and a guide how to do the flashing here:
http://forum.xda-developers.com/showthread.php?t=1469635
I hope this helps and good luck
mmcounts said:
Regarding the 7 or 7.7 question: I don't know which it is because I can't get it to boot up long enough to go into settings. According to the label it is an SCH-i800. It was purchased from Verizon in March 2011. I am pretty sure that it is a 7. Is there any way to tell just by looking at it?
Just determined it is a 7.0 per the Samsung webpage.
I guess I am in the wrong forum again. I am going to post in the General Galaxy Tablet forum.
Click to expand...
Click to collapse
Verizon only sells the silver version of the 7.7, for which the model number is SCH-I815. If you have a plastic back, it's the 7, and an aluminum back is the 7.7. Of course, since posted your model I can tell you for sure it's the 7, so you might have better luck posting in the appropriate forum.
Depending on how SuperOneClick works for the tab (I have no idea personally), you might just be best taking it to Verizon and asking for a replacement. I find it unlikely that they'd be able to detect that it has been rooted if it's totally fubar'd.

My 1st Rooting of Galaxy TAB 2 '5113' 4.0.4

I have researched and followed the rooting guide and have found that even though I have 4.0.4 I did not need to do any work around. I just wanted to let others know what I have done in case they are still having problems.
I downloaded all files as the guide stated (on here, just search it) and then followed the steps. I at first missed the work around due to it being on post 310 not 350 (due to deleted posts). Basically I never stopped the auto reboot inside Odin.
I tried a basic root check and no root access was found. Instead of starting over I downloaded 'superuser' and 'superuser elite' (bought with other devices).
After installing these from the play store, I rechecked and had a rooted device. I tested also Rom Toolbox, which is limited on functionality due to the Galaxy software. I have been able to remove bloat as well as freeze it with Titanium Backup.
I hope this helps anyone still having problems, also my tablet never did the 'blue flash'. I let go of power at logo and counted to 10 then released power button, went to recovery.
I want to say thanks to all the devs out there with your help and knowledge I have rooted an SGS4G, HTC Amaze, Acer A200, Toshiba Thrive, and now my Galaxy tab 2 10.1. I have never had a hard brick or soft brick, the HTC people know what I'm talking about especially.
Just remember to read and reread before you go at it and always make back ups. Thanks again to every developer and for everyone else if you can donate to these people or at least say thanks and donate to to this forum, they all work hard to help everyone.
This is why I am here loving android devices over others.

I want my s4 looking like my nexus 4

[Q] question about software of s4 into nexus 4
Ive never hacked a phone before but I know my way around computers.
Im sorry if this question isnt in the right section.
I just upgraded from a nexus 4 to a galaxy s4 and I am really hating the user interface.
Is there any step by step instructions on how to get my s4 software looking just like my nexus 4?
I have an unlocked s4 i9505 from the middle east
Ive searched all over the intenret and I cant seem to find it.
I would also like to be able to update the software as soon as google comes out with new ones.
Thanks in advance for your help.
fast6666 said:
[Q] question about software of s4 into nexus 4
Ive never hacked a phone before but I know my way around computers.
Im sorry if this question isnt in the right section.
I just upgraded from a nexus 4 to a galaxy s4 and I am really hating the user interface.
Is there any step by step instructions on how to get my s4 software looking just like my nexus 4?
I have an unlocked s4 i9505 from the middle east
Ive searched all over the intenret and I cant seem to find it.
I would also like to be able to update the software as soon as google comes out with new ones.
Thanks in advance for your help.
Click to expand...
Click to collapse
Check the android development subsection on methods for rooting your device. From there, install a custom recovery, and research the process of flashing custom ROMs.
That's the gist of it. I would recommend spending a couple hours reading thoroughly before jumping in to it. There are countless threads around here answering any questions you will have. Research them.
First I want to say I'm not a rocket surgeon, I've done this successfully before but I've also bricked a device (not the GS4) this will void your warranty and there is the possibility that your phone may become unusable. Just be careful, have fun and read up!
http://forum.xda-developers.com/showthread.php?p=39901375
That link will help you out with getting root access. After you have root access download Rom Toolbox from the play store. After you'vedownloaded and gone through the introduction you will be in the main menu, go Tools>Rom Management>Manage>Flash Recovery. A few options for recoveries will probably pop up I now use TWRP it is a great touch interface but in the past I have used CWR and it is fine as well, it's all personal preferance but for the most part my directionswill be for TWRP. Click one and it will flash it and reboot. If you ever want to get into recovery after this you simply hold down volume up and home while rebooting or powering up (there will be blue text in the top corner of the splash screen when button combo is successful)
Next you will want to look through the xda forums for your device, in the original developement section you will find threads labeled [ROM] anything that is built from CM10.1 (Cyanogenmod) or AOSP (Android open source project) or AOKP (Android open kang project) will all have a very stock Android, minimalist interface. You download one of these along with the Gapps files (google addons) and put it on your SD card where you can easily find it later.
Reboot into recovery and MAKE A BACKUP! It will be in the backup and restore option. Then you will want to wipe some of the partitions the steps for that are a little bit recovery specific, but I recommend a full wipe if you are going from touch wiz to source built. That means I would wipe /system, /data, cache, and dalvik cache (in TWRP it's easy just put x in the box beside those options in advanced wipe)
Now go back to main menu and click install, navigate to the ROM you put on your sd card select it and swipe to flash. Then do the same with Gapps. After all is done and it is reported as installation successful reboot the phone. First boot might hang for a while on the boot animation after the splash screen (some times it's over 10 minutes) be patient it will eventually fire up.
If something goes wrong or you don't like it you can always boot back into recovery and Restore the old software with the backup (nandroid) you made n before flashing.
Hopefully this was helpful.
You would think be able to update it as soon as google releases it. You will have to wait for it to be ported over. This is not a nexus. You will have ever to wait for developers also if it is the exynos device there will always be issues that can't be fixed with aosp roms. S
Wayne Tech Nexus

[Q] gt-i9500 and kitkat custom roms incompatibility? HUH?

As the title says I have an International GT_I9500 unlocked
Until now I was always able to install any custom rom I wanted , no problem, just wipe and install and away we went.
Now with KitKat, I AM COMPLETELY UNABLE TO INSTALL ANY OF THE CUSTOM ROMS FOR 4.4.2 -0 NONE WORKS. I can't believe i am jinxed.
I wiped everything, cache, dalvik, system and internal and also did a full wipe - NOTHING WORKED, There are 3 custom roms for 4.4.2 so far and NONE = NOT A SINGLE ONE WANTS TO INSTALL.
I downloaded one of Samsung original 4.4.2 firmware and using Odin I WAS ABLE TO INSTALL AND MAKE IT WORK, yet after doing this, I tried to install any of the 3 customs roms and BOOM, COMPLETE FAILURE
Can anyone help PLEASE GUYS, I feel like BROOMHILDA LONE PERSON WITH A CLOUD ONLY ON MY HEAD
I am curious as to why this is happening
maybe its a i9505 or i9506 rom
provide the Odin messages here.
custom roms failure, huh?
spamtrash said:
provide the Odin messages here.
Click to expand...
Click to collapse
I loaded the custom roms via recovery, not via odin,
so i go into recovery mode via TeamWin, wipe everything and load the custom rom, message says "successful" and i reboot system, that's it
the phone hangs into one of the boot animations and never finishes, left it for longer than 30 minutes, all of them , nothing loads.
go back the same custom roms but with android 4.3 and first shot, loads fine, all of them, same ones that won't load the 4.4.2 load the 4.3
most custom roms load via recovery not odin -
last try was load samsung original firmware 4.4.2 via download Odin, then root then install teamwin recovery. - worked fine
now removed it and reinstalled Thor 4.3 (thor 4.4.2 doesn't work) but tomorrow i'll wipe it and reinstall the samsung 4.4.2 unless you have an idea
*i hope)
sorry about the capitals - NO IT IS AN EXYNOS UNLOCKED GT-I9500 - almost a year after playing with nova settings, xposed and about a dozen custom roms, i THINK i know it's a 9500 - skip the silly suggestions - we're all noobs but not necessarily all boobs
thanks for your help - appreciated if we can solve it
custom roms failure, huh?
KingOfDope said:
maybe its a i9505 or i9506 rom
Click to expand...
Click to collapse
roms were downloaded exclusively from GT=I9500 AREA -
i don't go anywhere else because i know beforehand that they won't work - so why bother
thanks for your suggestion but obviously out of context - i don't live in the US in addition
Maybe wrong recovery ¿?
funny 4.4.2 roms
robertostorm said:
Maybe wrong recovery ¿?
Click to expand...
Click to collapse
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version
exlaval said:
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version
Click to expand...
Click to collapse
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?
custom roms failure, huh?
robertostorm said:
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?
Click to expand...
Click to collapse
as i said in a previous message - i used odin in download mode and flashed an original samsung 4.4.2 and it worked, i rooted and reinstalled teamwin
AFTER ALL THIS I tried to install one of the 4.4.2 custom roms - IT FAILED CONSISTENTLY - BY THIS I MEAN ALL ROMS DIED AT BOOTANIMATIONS - AND ALL FAILED TO START
thanks so much
Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone
custom roms failure, huh?
ayedarts said:
Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone
Click to expand...
Click to collapse
just downloaded cwm version 6.0.4.6 installed via recovery. launched recovery installed latest wanamlite for 4.4.2 - message was "installed successfully" please reboot
i rebooted and for the last 15 minutes all i have is a BIG SAMSUNG on the screen - nothing beyond
just another hitch with kitkat - i have a SONY XPERIA Z TABLET with wifi and sim - a couple of weeks ago i rooted it but the cwm version is not good because it's on the vertical side and you cannot see the bottom of the menu so it's useless - anyhow. i rooted it and left it at that.
i got notice from sony that a new os version (kitkat) was ready for install - so I just told the tablet to start - and the os install screwed the tablet,
there was no way to reload and it completely deleted the memory , it went to sony to reload - so i have a big hunch there is something not right somewhere -
anyway the phone still has the SAMSUNG and it ain't going anywhere while i am writing all this
very discouraging = sure as heck i ain't buying no more galaxys of any sort, i was ready to preorder the s5 at 455british pound, unlocked - but since this i am dropping samsung, i like very very much the xperia tablet it's faster than the s4 so perhaps i'll jump to the sony xperia fone and bbye korea
maybe i9505 rom
custom roms failure, huh?
i know you're trying to help - but if you read all the previous (long and boring) messages - there's no mistakes, there's no 9505
ALL THE ROMS I DOWNLOAD AND USE - ALL OF THEM WITHOUT EXCEPTION come for the i9500 development area, I DON'T BOTHER WITH
9505 - MOSTLY BECAUSE I DON'T HAVE A 9505
UPDATE - today after loading the latest cwm recovery i got lucky to be able to load ONE - READ IT - ONE CUSTOM ROM ( rom from HASAN)
this is the very only that i got to work, the other two just refuse to finish the boot - i don't know where they freeze.
even the wanamlite custom rom for 4.4.2 freezes - this is really annoying and a puzzle - this is my fourth samsung fone and never ever did i
find the bug that freeze everything. I hope that some of the other developers will come up with new kitkat versions for the 9500 and see if the bug persists or not -
any help will absolutely be appreciated, guys, some sort of boot log that can help pinpoint,
thanks again
You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.
custom roms failure, huh?
pinktheater said:
You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.
Click to expand...
Click to collapse
-------------------------------------------------------
First - The capitals I used were ONLY to emphasize certain aspects and not intended as screaming, which is the usual sense - That was not my intention,
Second - I have being using Samsung for the last 7 years, I was not intending to leave until I hit this brick and further I nearly went to Clove, UK (where I usually pre-ordered my last 3 Galaxy's - months ahead of delivery) so thumping me by saying I am looking for an excuse to dump Samsung, is way off base, so much so, that if that indeed was my intention, why for all heavens would i bother to find a solution, and waste so much time and effort to make it work
Third - I have being as polite as any person can be, with or without, this hitch, don't judge, about being angry or not, you don't know me well enough to know the difference, just stick to the point in question without getting personal.
Fourth - What I have described is EXACTLY to a tee what is happening to me, what happened to YOU , is IRRELEVANT, you may be one of the lucky ones who has no issues installing the roms in questions. so unless you do have a suggestion as to finding the reason the fone loops on boot, skip what you did or didn't do, they are IRRELEVANT, because they don't provide a solution.
Fifth - If you read my descriptions you will notice the many times I installed customs roms on the many galaxy's and Note's I have/had.That ought to clue you that i know a basic way on how to do the installations (Odin, recovery, teamwin. cmw,) you name it I've done it, and i've unbricked more than once my fones. so yes i do know how to use Odin
Sixth - For some reason I was able to install the "HASSAN" rom (the ONLY and ONLY) 4.4.2 custom that worked. the others they just won't, PERIOD
So if you have a technical solution as to how to get a log of the looping so we can tell exactly at what point the fone loops. or some other technical solutions, please let me know them asap I am dying to see my fone with a custom 4.4.2,
Seventh - Yes I am extremely disappointed that the S5 is just not fantastic enough to lay 455GBP to pre-order. there are a few more advances but it is "ALMOST" good = the bezel didn't disappear - the 2K display isn't there - the sharper casing is still missing - the better battery is still not there - the wireless charging - To have 2000 horse power engine under the hood of a beat up VW beatle. doesn't make you good looking enough to go cruising on a saturday nite and brag about your "car" -
BTW = I am absolutely no fan of the Iphone (yuk) nor of Sony (which is as restricted as apple)
Can you help solve my issue - thanks

Stuck on Recovery Boot Loop after Rooting

Hello there,
I am having a little bit of an issue with a new Galaxy Note 4 that i got for my wife. We both bought our devices yesterday, mine from Three, and hers from EE (we are in the UK), both SM-N910F, so i proceeded to root my device and it worked all great. So earlier today i started the exact same procedure, unfortunately, my wifes Note 4 got stuck in a Recovery Boot Loop, and i genuinely don't understand what is happening.
As for the rooting method, i went with the [SM-N910*] CF-Auto-Root and choose the right .tar file, or else it wouldn't of had worked on the first device.
I have read quite a few posts, saw a few videos on youtube, but it far beyond me. I have seen a few people mention that i need to download the German (?) version of the Stock firmware, and then flash it. I seem to have found a link for it on SamMobile but it's gonna take 5 hours to finish, and i don't understand why i would download the German Stock firmware, is that the correct one for her device ?
At this point, is there any way around it ? Why did my device which is the same work perfectly, but not hers ?
I would appreciate any and all help, if you could make it quite detailed for me i would appreciate it even more.
Thank you!
Hi @Vaskie!
Can you enter in download mode?
Hello there @_mone, the following has happened since i posted:
Went ahead and flashed the following: N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.tar and it made the device reach the home screen, from there i attempted to root using the same method which worked, but it ended installing a few extra applications, which i don't understand how. I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
On the other hand, most things seem to be working perfect, but i am having some issues with the front camera. I have two Note 4s, both bought yesterday from the same place, but one was flashed with the Stock rom (N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.ta r) due to being stuck in a boot loop. The front camera seems to be massively over exposed compared to the other Note 4, not just a little bit either, making it almost unusable.
Would anyone be able to help ?
Vaskie said:
I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
Click to expand...
Click to collapse
That's because you "dirty" flashed a new ROM on top of the old one.. it was like an "update".
What I suggest you (because you already rooted your phone and your knox is 0x1) is to flash TeamWin Recovery Project from ODIN and then flash a TW ROM from the Galaxy Note 4 Android Development (Snapdragon) page
To do so download "twrp-2.8.7.0-trltexx.img.tar" from here, put your phone in download mode, connect it to the pc via usb, from the pc launch odin, let it recognize your phone, add the downloaded .img.tar file on the pda button, click on the "start" button and let it flash the recovery.
Now download a TW ROM like _alexndr's DevBase from here and this modem and this bootloader.
Then put the downloaded ROM (N910FXXU1POF2_DevBase_alexndr.zip) in your external SDcard. Reboot your phone in recovery mode. From TWRP go Wipe/AdwancedWipe/ and tick DalickCache, System, Data, Internal Storage, Cache and "Swipe to Wipe". After go back to the first page, hit "Install" search "N910FXXU1POF2_DevBase_alexndr.zip" in "/external_sd" and install it. Wipe Dalvick and Cache again and reboot into download mode. Again connect your phone to the PC and launch ODIN now put the downloaded modem "CP_N910FXXU1POF1.tar.md5" in the CP button and the bootloader "BL_N910FXXU1POF2.tar.md5" in the BL button and click on the "start".
Once it is done switch off and on your phone and start again with the latest samsung rom for N910F already with root, busy box and all the fixes by _alexndr
And let us know if you still have problems.
Thank you very, very much for the very well detailed reply @_mone
I will attempt to go ahead with your explanation tomorrow. Would that somehow fix the camera, and i guess the other question is.. is the front camera issue that i explained myself above to do with me "dirty flashing" ?
Is there anything inherently wrong with "dirty flashing" ?
Thank you yet again!
Nothing wrong with dirty flashing.. but sometimes doing so you can create conflicts between old and new rom or leaving "bugs" from the old to the new generating problems in your new os that may wont be there if you performed a clean install. :good:

Categories

Resources