Hi. So I got the Note 4 (SM-N910T) and it came with stock NK4. I rooted it and used it for a few days. Last weekend I tried to upgrade to stock LP COD6, but everything went wrong - boot loops, freezes, some T-mobile "unsupported custom software - take it to a dealer" message, bricked except for download mode, etc
Using ODIN 3.09, Eventually I got the stock NK4 back on, but I wanted to make sure it's all correct -
Code:
Kitkat 4.4.4
Baseband N910TUVU1UNK4
Kernel: 3.10.0-2796035
[email protected] #1
Build #: KTU84P.N910TUVU1UNK4
SE for Android: Enforcing
MDF v1.1 r5
VPN v1.4 r2
Knox 2.2
I have TWRP v2.8.7.0 and it's rooted.
- I keep getting random restarts and this weird thing happens with the screen being half the boot animation and half static and it will stay that way until the display is turned off and then it takes a little while to get the display back on.
- Photos are being corrupted - the thumbnail looks fine but the photo isn't complete or is a gray box. This is in gallery, but it uploads to dropbox corrupted too.
Anyway, the obvious thing is to re-flash with some factory resets, but I wanted to check to see if anyone knows what these problems are from - bad flash? Wrong kernel? I'm pretty confused, should I stick on NK4 or try to go to COD6? I have looked through the troubleshooting guides and done searches, but usually the answers are a bit too shorthand for me to really get what to do. Any suggestions?
I don't get it. I odin -
N910TUVU1COD6_N910TTMB1COD6_N910TUVU1COD6_HOME.tar.md5
And the phone just doesn't reboot. It stays black screen no lights. I pull the battery and it boot loops, can only get to download mode.
First, I'd try a new download of the firmware, possibly from another source. I know it shouldn't work if it was corrupted due to the md5 check, but you never know.
hAvAAck said:
Hi. So I got the Note 4 (SM-N910T) and it came with stock NK4. I rooted it and used it for a few days. Last weekend I tried to upgrade to stock LP COD6, but everything went wrong - boot loops, freezes, some T-mobile "unsupported custom software - take it to a dealer" message, bricked except for download mode, etc
Using ODIN 3.09, Eventually I got the stock NK4 back on, but I wanted to make sure it's all correct -
Code:
Kitkat 4.4.4
Baseband N910TUVU1UNK4
Kernel: 3.10.0-2796035
[email protected] #1
Build #: KTU84P.N910TUVU1UNK4
SE for Android: Enforcing
MDF v1.1 r5
VPN v1.4 r2
Knox 2.2
I have TWRP v2.8.7.0 and it's rooted.
- I keep getting random restarts and this weird thing happens with the screen being half the boot animation and half static and it will stay that way until the display is turned off and then it takes a little while to get the display back on.
- Photos are being corrupted - the thumbnail looks fine but the photo isn't complete or is a gray box. This is in gallery, but it uploads to dropbox corrupted too.
Anyway, the obvious thing is to re-flash with some factory resets, but I wanted to check to see if anyone knows what these problems are from - bad flash? Wrong kernel? I'm pretty confused, should I stick on NK4 or try to go to COD6? I have looked through the troubleshooting guides and done searches, but usually the answers are a bit too shorthand for me to really get what to do. Any suggestions?
Click to expand...
Click to collapse
Was it unk4?? That's not right. Should be ank4 http://www.sammobile.com/firmwares/download/39224/N910TUVU1ANK4_N910TTMB1ANK4_TMB/
Sent from my SM-N910T using XDA Free mobile app
Where did you get the phone from? Possible that it is a knock off (fake)? As Nine5raptor stated, there isn't a firmware ending with "unk4" but ank4 is correct. I'm not sure how you would have gotten a firmware version of unk4 unless it wasn't legit
Related
I have searched thoroughly through the various CWM and OC Kernel threads but it's not clear to me if I can achieve having ClockworkMod Recovery and an Overclocked Kernel running on a Sprint (CDMA) Tab without any issues with the GPS or Camera.
I am perfectly fine running the stock Samsung ROM, but want to be able to overclock to 1.4GHz and be able to run CWM so that I can at least be able to do nandroid backups. From what I gather some of these CWM solutions and OC kernels (which may be really designed for Verizon Tabs and not Sprint Tabs) may cause issues with the GPS and/or Camera. I cannot afford to lose those two functions of the Tab.
So for those Sprint owners out there, what has worked for you to get a working CWM and OC kernel without sacrificing the GPS and Camera? Thanks!
apparently this isn't possible? it's a shame...as if a CDMA Tab were bad enough, it looks like the Sprint one is the true ugly stepchild of the bunch.
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
ad720 said:
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
Click to expand...
Click to collapse
Awesome! So you are using a Sprint Tab? And you can run Google Maps or Navigation and it locks your location using GPS? I just want to be sure before I proceed down this path, since I've read about some users not being able to get their GPS to operate once they've borked it.
And if you don't mind me asking, how did you get the VooDoo CDMA Kernel on there? Did you first install v4 through SGS Kernel Flasher or perhaps Heimdall? And then you installed v5 through CWM?
Thanks!
Yes, Sprint Tab (I just got it from the most recent woot sale).
Google Maps locked to my location within 20 meters inside of my office, and then dead on my front door just now. I turned my WIFI off to make sure it was really the GPS. I started up Navagation and it showed waiting for GPS for a about 2 seconds before starting with the turn by turn.
I have taken pictures with the RF and FF camera but I haven't tried a video chat so that might not work. When I take a picture the preview does glitch out on the screen a bit but the picture is just fine.
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
The issue that I had was my auto-rotation wasn't working. I found the file to replace in the thread but root explorer wasn't recognizing my SD card until I turned off the VooDoo enhancements in CWM and then turned them back on as specified by the troubleshooting section of the OP. At that time I was able to replace the file to restore auto-rotate.
Please keep in mind that while I am not new to Android I am quite new to the SGS so do plenty of reading and keep in mind that this is just my experience (or inexperience) with it and I may just have gotten lucky.
Also, I do NOT have data services through Sprint, I am using WIFI only so I can't speak to the effects of the Kernel on that.
Good luck!
Thats pretty awesome, atleast we have an alternative until Samsung hopefully release the 3.34 for all G tab owners.
ad720 said:
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
Click to expand...
Click to collapse
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
onlinespending said:
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
Click to expand...
Click to collapse
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
ad720 said:
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
Click to expand...
Click to collapse
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
onlinespending said:
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
Click to expand...
Click to collapse
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
ad720 said:
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
Click to expand...
Click to collapse
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
The first OTA on my device is downloaded, but not installed, and I'm curious if I should even take them at all?
I currently have the following:
Hardware version: SPH-P100.08
Model number: SPH-P100
Firmware version: 2.2
Baseband version: S100.08 S.DJ29
Kernel version: 2.6.32.9
Build number: SPH-P100.DJ30
I'd like some type of recovery and eventually HC... boy these Sprint tabs, and tabs in general, are funky compared to my Incredible.
onlinespending said:
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
Click to expand...
Click to collapse
That is identical to mine.
I wish I knew more about the tab so I could be a help.
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
onlinespending said:
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
Click to expand...
Click to collapse
Maybe a format issue? That's interesting...
I had a similar issue with the 16gb card. put a 2gb card in, and was able to flash the kernel and then get into CWM. sadly once I got that far it didn't seem to matter what rom/kernel i tried it wouldn't boot past the samsung logo anymore. So back to stock rooted for now I guess.. Really want to play with the HC port, but not sure why it won't work. Also can't seem to get Heimdall to recognize my Tab, Odin works fine however.
another new Sprint SGT owner from Woot sale here. Also just flashed the Voodoo OC kernel last night, all seems well camera and GPS etc, I have no idea if 3g works as there is no Sprint in my state.
I flash the V5 using a guide I found over on the unlocker site. took several tries before I got it to go, lots of command line stuff and I think I had a few typos along the way.
Another woot sprint tab user here... I also have "KhasMek Voodoo Plus v5" installed on my tab but GPS does not work for me. Well, it has never worked for me even with stock kernel and EA24 ROM.
Any other woot user with a none working GPS straight out of box?
Update: GPS will not lock if Sprint tab is in airplane mode. Even though by the window works for my HTC hero phone but not the tab. It needs to be outdoor in order to get proper GPS signal.
Hey folks new to this house and it seems like you folks know what you are doing. Big thanks to the developers of the Paranoid (2) devs. and all of the support peeps out there through the post. Read through themes and roms section but I not seeing answers to my confusion. Looking for some help understanding the features described above and how to get the most out of it..very cool though..just would like to know how to really put it to the test! I was able to get this far from the original FW to gingerbreak, to ICS to Paranoid based on the threads her and I appreciate it much folks..now I seem to be at a brick wall..need help trying to figure this out. I appreciate that the phone isn;t the latest thing on the market but it what I have right now. Would appreciate any and all help just trying to get a grip on this puppy! Thanks Smitty
Oh, every time I see something that looks like it should work on my phone besides not knowing how to install..LOL why does it come up Nexus! Are they similar phones or something!! Thanks again
What's on the phone as of now!
Samsung captivate SGH I897
Android Ver. 4.11
Baseband 19000XXJVU
Kernal: 3.0-.31-01749-gf84bc96
Cyanogen Mod: 10.0.0-RCO-capitvatemid
Paranoid Ver. 2.16
Build# pa-capativate-userdebug 4.1.1 JR003R eng.
Now my question is I want to load on different roms to the phone and be able to go back and forth between these ROMS as I like. I have attempted to use Goo Manager ..that was loaded when I installed Pananooid Ver. 2.16. When I boot into recovery it states that mt recovery ver. is : CWM-based Recovery v. 6.0.1.4.
I was trying to load some of the roms that are a part of the Paranoid install and I when I choose from one of these options:
Browse compatiable rom
Browse all files
check for updates..(says there are no updates)
Download gapps packages
Root recovery
flash roms
Copatiable roms:
aokp/devs/aokp
BAKED /devs/BAKED
cm/devs/cm
LronLyons/dev/IronLyon
If I choose any of them you get another list and then another list..it says:
EX: aokp_captivatemid_jb_build-4.zip..just one example ..there are many listed below that as well for each of the roms listed above.
Then I see the file name as above and below that : Begin download and then below that Download Gapps..how do I know which one to download?
Under browse all files :
devs/devs
gapps/gapps
ruu/ruu
stock/stock..choose the first one and get a list of all these different names ..such as adhvanit/devs/advanit..in these cases are these all the groups who produce ROMS?
I also attempted to use ROM Manager( no clue) and it kept saying that I must have clockwork-recovery installed in order to flash a rom..I choose yes and it say I don't have it..but on my phone it says I have as listed above for the phone and what is on it: CWM-based Recovery v. 6.0.1.4. ..is this not what they are asking for..or is it that it is looking for one that is not CWM "based" but the really official ver. of CWM Recovery.
What I am looking for is an explanation of what I can now do with this phone the way it is and also how to load ROMS of different kinds that stay on my phone and how I go back and forth from one to another with ease. Additionally, how to put different themes on the phone and any other tricks that can trick the phone out. My bro and sister all went out and purchased new Galaxy S3 phones..I am keeping mine and want to "trick" it out as much as possible to" one up them"
Any and all help would be greatly appreciated folks..thanks in adv.!! Smitty
Thanks for the hlp bobbylx and TRusselo
Thanks bobbylx and TRusselo.....wanted folks to know that these bros. helped without hesitation and didn't give me a lot of BS when I had this emergency! I didn't get it fixed yet but they lent a hand and gave me some incentive and FYI..has a noob that means a lot to me! Thanks guys!!!! Smitty!!:laugh::victory: almost!!!
Smitty,
I no longer have the captivate so I'm not current on everything that's going on. If you can get into download mode I would find one of the stock roms that can be flashed via Odin and start over.
You'll have better luck post this in the QA section for captivate. Good luck,
Bobby
Quote:
Originally Posted by thinkpolitics
Read your post and before I did anything I was able to get my AT&T Samsung captivate to show the little lime green guy digging says downloading ..do not turn off target..what do I do know though. I was running Panranoid 2 which was running fine and cym 10..attempted to switch to Lanight 6.55 datadata and that installed well too..decided I liked the other better and had a backup and went to restore seemed all to work well..but I didn't go and wipe everyhting before I went to restore..perhaps that is why I am having this problem. If you can tell me what to know that I have the download mode up would greatly appreciate it..thanks! Smitty
DEVICE: ATT HTC One X
ROM: Who knows?
Re: Re: Captivate with download icon visible
Quote:
Originally Posted by thinkpolitics
Hey mate..went through the post and especially yours but all of them assume that I can get a zip file onto the phone. I was running this:
Samsung captivate SGH I897
Android Ver. 4.11
Baseband 19000XXJVU
Kernal: 3.0-.31-01749-gf84bc96
Cyanogen Mod: 10.0.0-RCO-capitvatemid
Paranoid Ver. 2.16
Build# pa-capativate-userdebug 4.1.1 JR003R eng.
Then I attempted successively to try Lanight 6.55 datadata and that went well too. I didn't like it and I thought I would go back to what I first had. I just went to restore and I didn't wipe anything clean from the Lanight and devil kernel that was apart of that installation. When I rebooted the phone has been stuck at the AT&T Logo and that's all I have. I can able to get to the icon with the lime green android digging a whole..however mate I have no clue what to do next because all of what I read says I need to get a file onto the phone ( the file from the forum you suggested) in the first or second state. I hate to bother you mate but I have know clue as what to do know. This is the first time I have even done this to a phone and felt pretty confident..but stuck now mate. Any help would be greatly appreciated..thank you Smitty. I need that phone just for my kids in order to get them..thank you and I would appreciate you getting back to me as soon as you can ..Smitty!
Boot into recovery, go to mounts and storage, then select usb storage, plug in phone, copy files. If that option isn't there, Odin flash back to stock.
Sent from my SGH-I747M using xda premium
Re: Re: Re: Captivate with download icon visible
Quote:
Originally Posted by thinkpolitics
Thanks for the quick reply mate....I got Odin Odin3. [Android + SLP] and Odin one click downloader and I don't see anything on either of the apps. I can't get to recovery mode..I attempted with the 3 buttons and would usually release and the pwr. and there I am..can only get to download with oe without it pulled into the USB..could you be more specific as to what to do if I am doing something wrong with Odin or if I haven't done something I should...thry say this phone is unbrickable..LOL ex...should the SIm card or external SD card be in the phone.just as an example..since I can get to download ....you think I should be able to get to recovery..correct ..so maybe I am not doing something that would help me get there..like the proper way but I been there before..no problems! Thanks again for the quick reply..Smitty
Quote:
Originally Posted by TRusselo
Quote:
Originally Posted by thinkpolitics
Hey mate..went through the post and especially yours but all of them assume that I can get a zip file onto the phone. I was running this:
Samsung captivate SGH I897
Android Ver. 4.11
Baseband 19000XXJVU
Kernal: 3.0-.31-01749-gf84bc96
Cyanogen Mod: 10.0.0-RCO-capitvatemid
Paranoid Ver. 2.16
Build# pa-capativate-userdebug 4.1.1 JR003R eng.
Then I attempted successively to try Lanight 6.55 datadata and that went well too. I didn't like it and I thought I would go back to what I first had. I just went to restore and I didn't wipe anything clean from the Lanight and devil kernel that was apart of that installation. When I rebooted the phone has been stuck at the AT&T Logo and that's all I have. I can able to get to the icon with the lime green android digging a whole..however mate I have no clue what to do next because all of what I read says I need to get a file onto the phone ( the file from the forum you suggested) in the first or second state. I hate to bother you mate but I have know clue as what to do know. This is the first time I have even done this to a phone and felt pretty confident..but stuck now mate. Any help would be greatly appreciated..thank you Smitty. I need that phone just for my kids in order to get them..thank you and I would appreciate you getting back to me as soon as you can ..Smitty!
Boot into recovery, go to mounts and storage, then select usb storage, plug in phone, copy files. If that option isn't there, Odin flash back to stock.
Sent from my SGH-I747M using xda premium
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Philpro said:
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Click to expand...
Click to collapse
I think you need to find the lollipop kernel. But I'm not 100 percent sure.
try opening kies with your phone connected and look for a menu option to the effect of restore/repair device
sent from my galaxy a5 (SM-G900AZ) on Cricket
I'm not sure if this helps you or not, but I did the same thing, trying to downgrade. I did not take the OTA update when I went from KitKat to Lollipop, instead I flashed one of the Lollipop ROMs, so be wary of that. If you took the OTA update, I don't know if this will work for you.
Anyways, I spent the better half of a day trying different kernels and stock ROMs using the factory recovery etc and nothing was working, each time I would either end up frozen at the Samsung screen or the initial splash screen when you power the phone on. I found this thread here:
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
Under "notes", step 4 I downloaded the file G900A_Downgrade_to_NCE.tar and flashed through Odin. This is the file that got me out of this hole, so maybe it will work for you as well. After flashing, it rebooted and went past the Samsung screen to the initial first time setup screen. Looks like this put me back at stock UNrooted 4.4.2.
Good luck, hope this helps someone else out.
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Its_Tim said:
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Click to expand...
Click to collapse
I flashed through Odin, but yes I was rooted when I went from KK to LP.
I purchased an AT&T sm-g900a that was supposed to come with 4.4.2 according to info on site and sticker on the box indicated it originally had 4.4.2 on it too. I have no way of knowing if someone flashed it with the whole 5.0 file or just updated it. It was sold to me as a new and unlocked phone, and I got a good deal. The phone looks new with an AT&T screen cover attached, packaging, etc. and contents were still in sealed packaging. Will this work? https://www.androidpit.com/how-to-downgrade-galaxy-s5-from-lollipop-to-kitkat ? Is this the same file as the downgrade one referred to? Sammobile only has the 4.4.2 file. There is a significant cost difference in this model and the t-mobile version. Otherwise, I would just return it. I do not like the newer software at all.
I had the same thing happen today with my g870a. I tried 5.0, and 4.4.2 kernels, 4.4.2 firmware (which I knew wasn't corrupt) in Odin but nothing worked. The whole reason was to go redo my Alliance Rom and use FF beside Safestrap (the LP kernal would get rid of the SS). What I ended up doing was going into stock recovery and went to where it says "install update from ext SD". Then I went into my FF backup and found twrp.zip and selected it. It's did some things, said some stuff failed, then booted up enough to get me to FF to get it straight. One problem...my g870a thinks it's a 900, wtf?
Sent from my SAMSUNG-SM-G900A using Tapatalk
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
PanchoPlanet said:
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
Click to expand...
Click to collapse
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
jackler1 said:
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
Click to expand...
Click to collapse
Ok, I think I have found it but now I need to know how to fix it. Currently I have as follows in the about device screen:
Model SN-N910T
AHHA ------!!!!! - ANDROID VERSION 5.0
Baseband - N910TU1ANK4
Kernal version - 3.10.0-2796035 [email protected] #1 Thu Nov 13 18:01:07 KST 2014
Build number - KTU84P.N910TUVU1ANK4
So it seems the android version is wrong. Again forgive my stupidity but what exactly IS the android version. Meaning is that the baseband, the modem, what part of the stock rom is flashed wrong and where do I find that part to flash it correctly. I think I am making some progress just need input. Thanks Pp for getting me on track, now I just need a little shove to get this train rolling and maybe learn something in the process. If I fix it I then intend to write a proper write up for those lost souls out there who don't have to spend days....
So why does it say my android version is 5.0 when it should say 4.4.4?
Thank,
Freddy is getting nervous
First verify what version of the note 4 you have, Sm-N910T or Sm-N910T3 and flash proper firmware. Look under your battery.
Once you root you jumble up the phones ability to install firmware properly, and flashing stock firmware once with odin does not always secure components thus leaving you with unofficial status, "custom" and you think you went back to stock with no root but not official yet.
You need to make sure everything flashes and sticks, Model nunber, Android version, Basedand version, Kernel version, Build number.
Any of the modified components can stick and not be overwritten by stock odin flash.
Sometimes multiple flashes, or individual component flashes are required to go back to "official" stock form.
At this point you can verify that your fingerprint scanner works properly and leave it alone or proceed cautiously if root is really required ??? .
I only run stock and save myself all the headaches, I used to root back when Samsung phones where simple and less complicated without kernel security from Samsung.
I suggest latest 5.1.1 lollipop update, kitkat is primitive and outdated, you will be amazed at how well your note will run with latest firmware (with junk apps disabled).
Pp.
Here's a sample of my stock Note 4 running latest update.
Pp.
PanchoPlanet said:
Here's a sample of my stock Note 4 running latest update.
Pp.
Click to expand...
Click to collapse
Nope, I have wiped this phone a million times, reinstalled factory rom over the top of itself a dozen times, installed the baseband and bootloader separately after that and NOTHING changes it still will not work. I have read the complete internet from front to back and it seems nobody knows but the shadow.....Thanks for taking the time for trying to help me out though...
When you say wipe, do you mean factory reset?
Several resets in a row should wipe it clean. Something is stuck, could be the kernel, that will prevent a clean install.
You need to find a way to wipe partitions individually using ADB on the PC, that should allow for a clean install.
Pp.
jackler1 said:
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
Click to expand...
Click to collapse
try doing this...
1st - run chainfire triangle away v3.26
2nd - boot into recovery and wipe everything 3 times except external sdcard.. especially data...
3rd - boot in download mode and ODIN whatever firmware u wanna use... 2 times...
happened to me when the note 4 first came out... I had to exchange to a new note 4...
also whenever u do a nandroid.. U MUST REMOVE ANY SAVED FINGERPRINTS... so u can use that backup again..
if u restore a nandroid with a saved frintprints, it won't work, u must delete data and start fresh..
I don't know if u messed it up by restoring a nandroid from a previous phone and with saved fingerprints stored...
will do thanks for the advice will advise
Nope, nothing I do including stock or otherwise works. When you hit +#0*# it says null and 0.0.0.0 unless someone knows something I don't, it's borked. The thing is even if I used a nandroid and it overwrote my fingerprints where the ones in the nandroid so you would think it would work. Chalk it up to who knows....thanks anyway. Still looking if anyone finds solution....
Going back to stock from my rooted PopRocksV14. Haven't flashed ROMs in a while, so super rusty. Input welcome. TIA!
Questions:
1 Any faster mirror for N910TUVU2EQI2 than https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/TMB/?
2 How is the latest stock FW? Any reason not to upgrade? I'm just looking to get a stable phone and decent battery life, don't care about bloat
3 I'm looking to overwrite any Kernel and partition changes that PopRocks might have made, so is flashing back to stock rom going to do this?
Steps:
1 Make sure Samsung drivers installed
2 Download Odin 3.13 - https://odindownload.com/download/#.WyvXuCAnbAQ
3 Download EQI2 rom
4 Factory reset N910T
5 Run Odin as Admin
6 Start N910T in Download mode
7 Connect phone to PC via USB cable
8 Check Odin that COM is connected
9 Click PDA and select EQI2 tar file
10 Make sure Auto Reboot and F.Reset Time are checked, all other options disabled
11 Click start and wait for update to complete and phone to reboot
12 Factory reset N910T
I went ahead and tried it after the Sammobile download completed and it worked!
sfsilicon said:
I went ahead and tried it after the Sammobile download completed and it worked!
Click to expand...
Click to collapse
@sfsilicon - hope you're still monitoring this old thread. I'm trying to revive my old Note 4 I found in a junk drawer - for my 6yo boy. It had some custom rom on it, and I've now attempted with Odin to restore the image EQ12 you had listed - it appears to be the most recent.
Oden gets about 99% done then fails and now the phone is stuck in some sort of emergency mode. I can get into download, but not recovery. I assume I hosed it - maybe the bootloader was the wrong kind from the prior custom rom (and I didn't take note of what it was since I was just wiping it out).
Bummer.
Sorry to hear about your problems. It has been a while since I reflashed back to stock. Did it on two note 4s. From your description only thing I can think of would be that you flashed from a rom that was from an earlier Android version to the latest and it is missing some files or partitions that would normally be part of that type of transition. E.g. if you had done all the updates via OTA vs gone from your custom rom to the latest stock TMO release.
So try to figure out what Android revision your custom rom was before this latest flash. Then check the posts about moving from that revision to the next latest one and see if there is anything special in between. You can then look for the stock TMO rom that matches your custom ROM then flash back to that. Once you have a ROM working, even an older you can flash the next updates till you reach the final/latest TMO version or just OTA it.
One other thing to check is if your custom ROM did any changes to the kernel files or other stuff. Then check with the old custom ROM how to reverse them. Not sure if flashing a stock TMO rom undos all this. Its been a while but would think so but its still a step to check.
Hope this helps and good luck! I'm actually using my N4 currently. I use it to hold a foreign SIM when I am travelling. Sort of a glorified hotspot. Gave my 2nd one to my mom where the large screen helps with reading text. Its still a nice phone.
Thanks for getting back with me. I was under the impression that regardless of what custom rom may have been on the phone, Odin was a way to wipe the slate clean and put it back to day-1 state. I have no idea what OS was on there, but I do recall a warning about the bootloader being modified and it may be impossible to roll back. That's going off of memory (which has a very low confidence level).
Now I can't even get it to power up at all. I think I'm going to bail and just get a cheap Chinese android phablet - don't need cell service. It's getting to the point that my time and patience is worth more than what I'm spending to rehab this thing. Sucks too... When I first got the N4, I was pretty proficient at swapping roms... But since I've not played with them in years, I've all but forgotten the basics.
Thanks for the suggestions, tho...
E