Related
Hi
I've upgraded to 2.3.3 and my camera doesnt work anymore. The screen comes black for a few seconds and then the message "Camera error. Cannot connect to camera" appears. The flashlight is also doesnt work. I have some MoDaCo firmware HTC Sense before, as I remember...
Help me to fix it, please.
Thanks
Flash newer radio.
Jack_R1 said:
Flash newer radio.
Click to expand...
Click to collapse
Could you tell me how to do it, pls? What is the last version of radio? How to check it?
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Jack_R1 said:
Settings / About / Baseband
If the version is 4.06 / 5.08 / 5.12 (the version is in the middle of the long string there) - then there's some other problem in the system. If the version is 4.02 or 4.04 - then you need to go to Developers forum, open any Gingerbread ROM thread, and see the instructions for flashing Radio. Or look at my signature.
Click to expand...
Click to collapse
The Baseband Version is 32.41.00.32U_5.08.00.04
What I'm thinking is could it be the problem because my Nexus had non original firmware before the GB update, and maybe I didnt make some important thing which blocking my camera now? Maybe I need to re-flash the radio with some original image? I'm totally NOOB in all these things...
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Jack_R1 said:
Your radio is 5.08 - which means it's updated and the problem is elsewhere.
If you didn't upgrade to Gingerbread from a clean FRG83G build, but from some other build - you'll need to reflash the ROM. You can do it if you have unlocked bootloader. Read Wiki, it has the guide for installing custom ROMs - execute it, and use Gingerbread stock build from one of the threads in Development forum.
Click to expand...
Click to collapse
Thanks for your advices. Just upgraded the radio to 5.12 via fastboot. The camera still not work Will try to flash to original state...
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
P0MkA said:
ok, i've tried to rollback to original FRG83, se-flashed boot, recovery, but no luck - camera didnt started. Hovewer, i tried the flashlight torch and it started to work (it didn't like a camera before), so I'm sure now the camera issue is the software now - not a hardware.
Does anybody have some advices?
Click to expand...
Click to collapse
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
k_myk said:
How did you flash frg83? via passimg or you flashed rooted rom from dev section? If you didn't use passimg method you should try wiping everything (cache, dalvik, factory reset) from the recovery.
BTW, if you have custom recovery you should be able to restore nandroid backup (which I assume you did;P ) and see if there is this problem too.
Cheers!
Click to expand...
Click to collapse
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
P0MkA said:
i've flashed frg83 using fastboot. And updated to 2.3.3 via recovery (RA-passion-v2.2.1). And yes, I wiped everything using the recovery. Unfortunately, I do not know what is nandroid backup, so I didnt do it
Hope there is a way to get my camera back to work... Could you tell me what to do, step by step, to make my Nexus fully functional with the 2.3.3 firmware, please!
Click to expand...
Click to collapse
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
k_myk said:
I'd love to, but unfortunately I don't know what causes this problem at the moment I think it wouldn't hurt to try loging what is going on when you open camera.apk. Try adb logcat from your pc or install "alogcat" from market, start camera app and paste here the log file.
Lesson for future always do nandroid backup You can do this from recovery, it will do phone's memory image Then you can always revert back to what you had before flashing new rom
Click to expand...
Click to collapse
Yeah... backuping is a cool thing.... It is just my first experience with the Android phone... Maybe will find some kind of solution for this...
Well... Problem stays... However I've found few interesting things. As I've mentioned above, after the 2.3.3 update the camera and flashlight doesnt work enymore. But I've installed Z-DeviceTest and found that after the reboot this app (which provides the hardware test) sees the camera and flashlight! But, unfirtunately, doesnt able to test it. Moreover, if to start some torchlight widget directly after the reboot, the flashlight works!!! But it is not after the camera start... So, maybe someone will find this information useful.
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
sevensaints said:
@Pomka
have you found the Satu Solution yet ?
mmm. i guess you borrow from somebody the nandroid back up and restore it...
then u will know whether it is a hardware issue or Software Issue.
Logic ?
Click to expand...
Click to collapse
Stupid actually. Its stay the same, not working....
found the solution!
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
You have go go back to stock ROM.....then camera Happy Trigger Finger!
yeah...
1. Go back to stock through HBOOT
2. Flash back ur fav ROM - mine-MIUI AU
pls click thanks
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.
Hello !
So I successfully rooted my wifes Sony Xperia Z1 3 weeks ago, after that Sony has released several firmware updates, and I have never had a problem with this. I have always followed this guide: http://forum.xda-developers.com/showthread.php?t=2711982
And it has worked well. The phones bootloader is unlocked and It has runned all versions up to 14.3.A.0.681 without any problems. (I also have the XZDualrecovery mentioned in that thread).
So last time, the new 14.3.A.0.757 upgrade was released, and as always I did everything in the thread as usual. Root and upgrade went smoothly without any problems, or so I thought. Now, if using the normal camera for taking photos, if you touch the "take photo" button the flashlight goes on, but no picture is taken, also the camera can't focus on anything. The whole app freezes, and you need to force close it and try again. The front-face camera works without any problems. This happends every time, so reproducing is really easy. I have tried to wipe the cache-partition, I have tried to clear the data and cache from all camera-related apps too, nothing of this helps.
So, I downgraded to 681 sussessfully with root and everything, all boots fine without problems... But.... The camera app is still broken in the very same way .
I red somewhere that people with OTHER cameraproblems have flashed the ported camera from Z2 to fix problems, but I doubt this could help?
I am a bit desperate, I really want my wifes camera to work again, any tip would be wonderful.
If unrooting and running stock is the only solution, so be it, but If you have any other ideas, I would be so grateful
Thank you again
If you have unlocked your bootloader it is as simple as flashing a stock FTF then DooMLoRDs advanced stock kernel, or DooMKerneL, or [NUT]s kernel with dual recovery in it for the 757 FW
The latest version of any of these three will give you root and recovery and your phone
Also, have you tried clearing the data in ALL the camera apps in
settings/apps
That may just do the trick
Also, don't worry, I have already reported this thread to get it moved to the Q&A section so you do not have to bother, but next time you ask a question please do it in the Q&A thread.
gregbradley said:
If you have unlocked your bootloader it is as simple as flashing a stock FTF then DooMLoRDs advanced stock kernel, or DooMKerneL, or [NUT]s kernel with dual recovery in it for the 757 FW
The latest version of any of these three will give you root and recovery and your phone
Also, have you tried clearing the data in ALL the camera apps in
settings/apps
That may just do the trick
Also, don't worry, I have already reported this thread to get it moved to the Q&A section so you do not have to bother, but next time you ask a question please do it in the Q&A thread.
Click to expand...
Click to collapse
Thank you for good suggestions, I just remembered that I did not try to do a wipe data/factory reset, maybe this will help, also I tried to move my topic to Q&A but didn't know how to do
My wifes phone will be in my hands tomorrow, I hope to do magic then ...
G870A, Soft Bricked, Need 4.4.4 or 5.1.1 completely stock "Unrooted" firmware file
EDITED 12-27-15:
XDA Assist has sent me to this forum (Thanx). Info and questions follow, here are the basic details:
G870A variant of the samsung S5 (Active)
Stock, unrooted, carrier locked
interrupted power during OTA update from AT&T (most likely 5.1.1)
forced phone into "download mode" and attempted to flash 4.4.2 (NE4) instead of update (actual file used: G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5)
Phone stuck in bootloop with freeze/repeat at AT&T logo
unable to locate completely stock firmware file for 4.4.4 (G870AUCU1AOA1 or OA2) to flash back to most recent functional OS.
still currently able to force recovery mode or download mode.
**update:
As far as i know, the OTA for 5.1.1 did completely download but i dont think it "installed" because i removed battery during initial auto-reboot. The existing ROM would have been 4.4.4 mentioned above, updated and active official firmware from AT&T.
Basic Explanation of actions: I do fully realize that my actions and subsequent "incomplete" attempt to patch the software were unwise but i was merely weeks away from paying off the phone, owning it, having it unlocked by AT&T, properly rooting and installing a custom ROM (as i had successfully done to my wife's G900A). In a moment of panic, not wanting to be locked out of my phone forever by Lolipop, I ripped out the battery during the reboot that was loading Lolipop... every time I put the battery back in and hit power, the phone still attempted to load and write 5.1.1. So I thought maybe, the official firmware copy from 4.4.2, which my phone shipped with in 2014, might flash, even though i was not rooted or unlocked. Clearly i was mistaken but it was all i could think of under pressure.
At this point, I am Completely unconcerned about almost all data on phone or even the hardware EXCEPT for some extensive "memo" notes, which i desperately want to recover. I also dont care anymore about avoiding Lolipop because the memo data is more important to me. I am literally willing to rip the internal memory from this phone and send the SD to a data forensics company if that's what it takes, i no longer care about the phone at all... Having said that, recovering it myself and keeping the phone might be nice also.
Question: where might i find a completely stock firmware for 4.4.4 factory, UN-rooted,to flash; or what procedure might i use to directly pull data from the phone, while soft bricked, before doing a full factory reset?
Alternately, any advice on directions i may not have thought of yet?
I have looked pretty deep into the existing XDA forums for this info but i am only finding "custom ROMs" which are rooted or factory stock ROMS for 4.4.2 and most advice deals with rooting, then flashing. I am not rooting but simply flashing fully unrooted stock firmware AND starting in a bootloop/soft brick state. This is why i did a fresh thread.
Thanks in advance to anyone who might be able to help!
rtlarkin said:
Hello XDA Assist! After reading the stickies, i see that you may be able to direct me to the correct forum in which to post my main question. Here are the basic details:
G870A variant of the samsung S5 (Active)
Stock, unrooted, carrier locked
interrupted power during OTA update from AT&T (most likely 5.1.1)
forced phone into "download mode" and attempted to flash 4.4.2 (NE4) instead of update (actual file used: G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5)
Phone stuck in bootloop with freeze/repeat at AT&T logo
unable to locate completely stock firmware file for 4.4.4 (G870AUCU1AOA1 or OA2) to flash back to most recent functional OS.
still currently able to force recovery mode or download mode.
Completely unconcerned about all data on phone or even the hardware EXCEPT for some extensive "memo" notes, which i want to recover.
Question: where might i find a completely stock firmware for 4.4.4 to flash; or what procedure might i use to directly pull data from the phone before doing a full factory reset?
Alternately, advice on directions i may not have thought of yet.
Thanks a bunch!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to the most relevant Q&A forum for your device. Good luck!
Hello,
I am not an expert or anywhere close but I understand the basics of Android flashing / rooting, etc.
I happened to have rooted my G870A from AT&T successfully using a thread from XDA and I noticed they also provided the original firmware for G870A in case of problems:
http://forum.xda-developers.com/att...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
So I thought this may help you considering you're looking for an original firmware for your G870A.
What I suggest is to try to flash "G870AUCU1ANE4_Full_Odin.tar" (available from the thread I linked above, I didn't want to rip the links out of the thread) using Odin v3.09+.
I did not use this firmware to root my G870A (only used the updates) but everything worked on the first try.
Follow instructions in the thread I provided. If that still doesn't work, you may need an Android expert on the case.
I wish you good luck in your data recovery. And yes, I registered just to post a reply to your thread.
(also: if you want to root your G870A, the thread explains the proper way to do it!)
Appreciate the thought
dapr0b said:
I happened to have rooted my G870A from AT&T successfully using a thread from XDA and I noticed they also provided the original firmware for G870A in case of problems:
http://forum.xda-developers.com/att...to-root-g870aucu1aoa1-4-4-4-2-7-2015-t3025119
So I thought this may help you considering you're looking for an original firmware for your G870A.
What I suggest is to try to flash "G870AUCU1ANE4_Full_Odin.tar"
Click to expand...
Click to collapse
Really appreciate the thought, however, that particular file is the file that i had originally used before posting. i think since my phone was factory locked and unrooted i did not have the permissions needed to basically "roll back" my phone to 4.4.2 but i am not educated enough to be sure of the exact problem flashing that file.
Thanks again for suggesting it though! I am nearing the time when I will just have to give up and send off the internal memory for physical extraction and data recovery
Hello,
I am also not an expert or anywhere close but I understand the basics of Android flashing / rooting, etc.
With that said: Let the OTA happen. You will not lose the files unless you already started a factory reset. Then your sol. You will not be able to root but you have a better chance of retrieving the files you are looking for. The phone is not like a computer. You can't just pull the HD and sent it out. You either already had the 5.0 kernel or the 5.1 kernel loaded before you stopped the process. This makes it impossible to go back. You can only go forward.
Good luck and let us know how you make out.
re: take the OTA
Sgt.CM said:
With that said: Let the OTA happen. You will not lose the files unless you already started a factory reset.
Click to expand...
Click to collapse
Thanks for that idea. the trouble at this point is that im stuck in a bootloop that catches on the att logo. I agree that the only option now is to continue forward. i just need a fully official software newer than 4.4.4 to load through kies or odin. at least i "hope" the newer file will work.
so far i have only been able to find stock ROMs that are rooted, and i dont think i can load a rooted stock ROM onto a carrier locked un-rooted phone.
The part you mentioned about the kernal is probably true. i had not thought of that before.
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....