Related
The problem is the phone is showing Custom when the phone is turned on. I was on MF3, had rooted via the SD card method. The custom appeared at that point. I did a factory reset and the custom went away and lost root but the superuser app was still showing in the app draw (factory reset did not delete this). I was planning on reloading the MF3 firmware via odin but lent the phone to my daughter while I replaced the screen in her note2. Well of course she got the upgrade message to 4.3 from AT&T, did it and now the unlocked custom is back. Not sure why as it was showing as official, the trip counter was still 0 (never installed a ROM on it) BUT the superuser app was there.
Now on 4.3 I've rooted/unrooted via Kingo, during the unroot it removes superuser but the custom won't go away. I installed Triangle Away while rooted and it still shows 0 on the flash counter. Is there something in this Knox security (not sure how to check this) causing the custom?
Just want to get it back to any stock AT&T firmware so I can sell it. TIA for any help
there are only certain roms you can flash while being on mf3. If you did the mk2 update there is no recovery out yet. Using vroot and kingo are unsafe methods of rooting so puts your device at risk.
rzracer2 said:
The problem is the phone is showing Custom when the phone is turned on. I was on MF3, had rooted via the SD card method. The custom appeared at that point. I did a factory reset and the custom went away and lost root but the superuser app was still showing in the app draw (factory reset did not delete this). I was planning on reloading the MF3 firmware via odin but lent the phone to my daughter while I replaced the screen in her note2. Well of course she got the upgrade message to 4.3 from AT&T, did it and now the unlocked custom is back. Not sure why as it was showing as official, the trip counter was still 0 (never installed a ROM on it) BUT the superuser app was there.
Now on 4.3 I've rooted/unrooted via Kingo, during the unroot it removes superuser but the custom won't go away. I installed Triangle Away while rooted and it still shows 0 on the flash counter. Is there something in this Knox security (not sure how to check this) causing the custom?
Just want to get it back to any stock AT&T firmware so I can sell it. TIA for any help
Click to expand...
Click to collapse
Install the Xposed framework from xda. Then, install the Wanam module and look for the Setting under "Security Hacks" that reads "Fake system status" and check the box and reboot.
The issue won't truly be resolved until you flash an official ROM, but the Custom screen will be gone at boot.
rzracer2 said:
The problem is the phone is showing Custom when the phone is turned on. I was on MF3, had rooted via the SD card method. The custom appeared at that point. I did a factory reset and the custom went away and lost root but the superuser app was still showing in the app draw (factory reset did not delete this). I was planning on reloading the MF3 firmware via odin but lent the phone to my daughter while I replaced the screen in her note2. Well of course she got the upgrade message to 4.3 from AT&T, did it and now the unlocked custom is back. Not sure why as it was showing as official, the trip counter was still 0 (never installed a ROM on it) BUT the superuser app was there.
Now on 4.3 I've rooted/unrooted via Kingo, during the unroot it removes superuser but the custom won't go away. I installed Triangle Away while rooted and it still shows 0 on the flash counter. Is there something in this Knox security (not sure how to check this) causing the custom?
Just want to get it back to any stock AT&T firmware so I can sell it. TIA for any help
Click to expand...
Click to collapse
unroot via kingo, then factory rest...worked for me on 4.3
Do you plan on a warranty exchange?
I love seeing the custom on boot, it lets me know and other everyday normal people know my phone is slightly modified.
ROOTED ATT MK2 using Tapatalk
Not sure what I'm going to do with the phone yet, probably sell it but not totally sure. Wondering with it now showing Custom on the boot screen and in the OS will it still receive OTA updates? Hoping the AT&T 4.3 or 4.4 image will be available in the future and that might help.
rzracer2 said:
Not sure what I'm going to do with the phone yet, probably sell it but not totally sure. Wondering with it now showing Custom on the boot screen and in the OS will it still receive OTA updates? Hoping the AT&T 4.3 or 4.4 image will be available in the future and that might help.
Click to expand...
Click to collapse
I was rooted custom and received my OTA no problem. Yes
ROOTED ATT MK2 using Tapatalk
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
mygadgetgeek.com said:
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
Click to expand...
Click to collapse
not yet, but i have a lot of data now on my phone. will try that though. in case that doesn't work, any other advice?
cptnappy said:
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Click to expand...
Click to collapse
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
radicalisto said:
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
Click to expand...
Click to collapse
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
Ah Ok, if it says Official it should be good to go. Seems like maybe the download has gotten corrupt due to an intermittent internet connection.
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
OK, then maybe you should learn a few things before trying to update - Knox is a security system in latest Samsung phones that is supposed to be triggered/set when you root (or install any custom kernel/recovery). Your initial (old) firmware could still let you root without triggering the Knox flag, and then you can update to the latest firmware for your region using Mobile Odin Pro and still keep your root AND without triggering the Knox flag. However once you update using Samsung OTA / Odin / Kies to a firmware more recent than MJ3 you can no longer root without also triggering your Knox warrany flag - read more about this in the Universal Root De La Vega thread!
i gave up after several tries, since i'm on 4.3 i think that would do for now. maybe it's just downloading a stability update or something? everytime i do an OTA update, it tells me that the download of the new firmware is complete then reboot. when i get to 32% the droid falls flat on its back and shows the red triangle on its chest, over and over. i don't lose my phone data or anything. just won't update. i'll wait for 4.4 Kitkat instead. hope i'll be able to update to that when it comes out.
EDIT: i tried going into recovery mode, wiping cache, and factory reset.. still no dice. maybe Odin's the only way i guess. problem is my internet connection lol
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Sent3 said:
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Click to expand...
Click to collapse
i managed to update mine using Samsung Kies3 (not Kies, but Kies3). Hope updating OTA is fixed in the future with the update i just did
My Galaxy S4 just decided to show wavy lines on the screen instead of turning on - as far as I can tell the screen and digitiser are no longer working.
**I CANNOT SEE OR DO ANYTHING ON THE SCREEN**
I have a 4.2.2 i9505 UAMDE -Stock Rom- that is rooted.
I have never flashed any other firmware to it - just rooted it.
I have Kies access and backed up my phone. Kies prompted for a firmware upgrade when I plugged in the phone.
I want to return it to stock/unroot etc so Samsung will warranty the phone without fuss (it was not dropped, just stopped working).
Some questions:
Most important:
1. Is it possible to get the phone to a state that will be warranty-ready without having a screen?
2. Do I need to Triangle away if all I have done is rooted? If so, can I do this without a working screen?
3. What is the best way to return to stock? ODIN or should I just let Kies update to latest firmware? (If either will it be enough to satisfy the first question)
4. If Kies does the update will I need access to the screen to complete it?
Thanks in advance!
1. You can flash same firmware with ODin. It will delete root access, but app will stay, so you have to uninstall it through https://play.google.com/store
2. You don't need to, unless you've made a root through Oding flash?
3. Odin
4. No, but it will udpate it to 4.3 with KNOX?
mar10o said:
1. You can flash same firmware with ODin. It will delete root access, but app will stay, so you have to uninstall it through https://play.google.com/store
2. You don't need to, unless you've made a root through Oding flash?
3. Odin
4. No, but it will udpate it to 4.3 with KNOX?
Click to expand...
Click to collapse
Thanks for the quick reply.
1. not sure which 'app will stay' you mean?
2. Actually I cannot remember how I rooted - I will have to look this up again. Something tells me cf-autoroot and maybe ODIN... All I can remember it that I still have stock ROM just with root.
4. Agree that this might not be the best idea as I am trying to stay away from KNOX but I wonder if Samsung will automatically update to the latest ROM as part of the fix?
Kies is currently sitting on backing up "preparing" for ages and ages... hope it works in the end.
Looking back I suspect I used CF-autoroot which probably mean my counter has gone up.
Any way of resetting this without a screen?
I've managed to get some screen control using adb, screencast and teamviewer.
Triangle away says:
Counter: 0
Binary: Official
System: Official
I suspect the Official comes from the fact I was running Wanam Xposed and spoofing official.
One last question -
Given all that information I should just be able to flash
4.2.2 UAMDE Stock rom from sammobile with odin
and everything will be warranty-ready?
(will this wipe all my data and programs as well? - something I WANT to happen)
It will not wipe it. On the older devices like S3, there was a special ROM for cleaning purposes with PIT file, that was repartitioning your memory. Maybe there is something like that for S4?
my galaxy s5 model number is sm-g900t, android version is 4.4.2, ..not sure what other info might help, but anyway, i cannot update the software/firmware over the air because the device is rooted through steps on here and its been rooted awhile now. so anyway, i downloaded the kies 3 from the samsung site, it says all im supposed to do is plug the phone in, a box is supposed to pop up showing an update is needed......well, the kies box does pop up, but all it shows is current firmware version and shows my internal and external storage availabilty, and so on.... no auto update thing came up. so in kies i went into tools up a t the top, i hit firmware upgrade and initialization, then a smaller box pops up saying---does not support initializing, so now what? nothing else i can do in kies except move pic files around and such. i need to update the software. any advice? i attached 2 pics.....pic 1 is the initial message when phone is plugged in, #2 is when i go into tools and hit ugrade
knight1701 said:
my galaxy s5 model number is sm-g900t, android version is 4.4.2
Click to expand...
Click to collapse
Samsung has now embedded a security flag called KNOX in it's later devices. Unfortunately after you flash a package/custom ROM or whatever with a different signature than Samsungs own it trips that KNOX flag.
When your KNOX flag is tripped you can no longer update your phone via official methods. It is just the way it is, and there is nothing to be done. Once KNOX flag is tripped, there is no way to "untrip" it, so you will never be able to update via KIES again.
Im not really sure whether flashing a stock lollipop rom via odin works when KNOX is tripped, i have never tried it, so you should wait for any other member for confirmation. As far as i know, it shouldn't be a problem.
What i can tell you, if you have the time, is that you flash a ROM that is compatible with 4.4.2 (Omega v13 or AllianceROM v5.6 etc) and then flash it's ROMs lollipop update after a full wipe. It is the only thing i personally am sure about (i have done it before).
I'm by no means an expert on the matter but I'm pretty sure that if you can't get the Ota due to being rooted, then updating vIA Kies isn't going to work either.
Go to settings> about device> status
scroll to bottom of list and respond here what it says under "device status" (it's gong to say either official, or custom).
If it says official, you could unroot, maybe check that the proper drivers are installed on your computer, and try once again to apply the update via kies.
If it says custom, then knox has been tripped and I cannot help further.
The biggest issue here is that if you take the OTA update you'll lose the option to root or downgrade so you should probably use TWRP to install a ROM that's pre-rooted rather than trying to get the OTA
Akalsemann said:
Samsung has now embedded a security flag called KNOX in it's later devices. Unfortunately after you flash a package/custom ROM or whatever with a different signature than Samsungs own it trips that KNOX flag.
When your KNOX flag is tripped you can no longer update your phone via official methods. It is just the way it is, and there is nothing to be done. Once KNOX flag is tripped, there is no way to "untrip" it, so you will never be able to update via KIES again.
Im not really sure whether flashing a stock lollipop rom via odin works when KNOX is tripped, i have never tried it, so you should wait for any other member for confirmation. As far as i know, it shouldn't be a problem.
What i can tell you, if you have the time, is that you flash a ROM that is compatible with 4.4.2 (Omega v13 or AllianceROM v5.6 etc) and then flash it's ROMs lollipop update after a full wipe. It is the only thing i personally am sure about (i have done it before).
Click to expand...
Click to collapse
well i hear what your saying, but on my other phone, same setup, rooted and all.......updated just fine---did it about a month ago...updated to android 5 from 4.4.2..just plugged in the phone and boom it did its thing............on this other phone though, daughters phone, it wont work
Swimguy14 said:
I'm by no means an expert on the matter but I'm pretty sure that if you can't get the Ota due to being rooted, then updating vIA Kies isn't going to work either.
Go to settings> about device> status
scroll to bottom of list and respond here what it says under "device status" (it's gong to say either official, or custom).
If it says official, you could unroot, maybe check that the proper drivers are installed on your computer, and try once again to apply the update via kies.
If it says custom, then knox has been tripped and I cannot help further.
The biggest issue here is that if you take the OTA update you'll lose the option to root or downgrade so you should probably use TWRP to install a ROM that's pre-rooted rather than trying to get the OTA
Click to expand...
Click to collapse
ok, on the phone in question, device status says--- custom, guess that ends that..........on my phone howerver, it says official which is why i guess i was able to update mine
just download a rom for your phone from sammobile and install with odin and your done
Hi everyone. I just flashed back to stock (Koodo official firmware) to sell my Note 3 and now my back hardware button isn't working. I have searched the web and to no avail. Could someone please give me an idea of what I can do to fix this? Thank you!!
Which note 3 is it?
SM n900W8
I have the same model. I haven't used it for a while. I powered it on a few days ago to take the update from doc4 to doh1. I just tried the back and menu buttons using the doh1 ROM and they seem to work fine.
A friend of mine has the same phone and he flashed the doh1 ROM from sammobile.com over a rooted doc4 RIM and he also has no problems.
Both of us were using custom ROMs with a 4.4.2 bootloader and we both flashed back to stock using sammobile.com's doc4 ROM before moving to doh1.
I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!
Glad you got it fixed but I'm not sure I was much help.
Partially solved..
Hi.
I have done everything trying to solve this and can confirm the next:
1st: If you go back to Kit Kat, the capacitive buttons start to work again. Then you are offered a couple of OTAs (one after the other to get you to DOH1). After the first OTA, the buttons stop working again.
So first solution: stay on Kit Kat (probably not what we want).
2nd: Flashing a custom Cyanogenmod based firmware works, I used latest temasek's build, I am testing it to see if I can keep it.
3rd: I tried erasing almost every single partition (system/cache/dalvik(art?) cache) and flashing from scratch DOH1... wont work.
According to what I have read all around there is a system file that controls the capacitive buttons, probably that file is getting weird with the upgrade, I still need to install a official rom, root it and try to edit such file.
It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.
audit13 said:
It's strange that some phones have no problem while others do. My friend and I have no problems but we weren't running custom ROMs before the doc4 or doh1 updates.
Click to expand...
Click to collapse
I wasn't running anything custom. I was on Official ROM (no root no anything, just Stock Samsung Software) as always with my Note 3. It was just that the DOH1 update make the damages.
Now I think I gotta stick to Cyanogenmod given this problem, unless Samsung says something and fix the thing.
Does this happen with TW-based custom ROMs too?
Dont know. As of now, I am trying to flash DOH1 again on top of KitKat 4.4.2
[/COLOR]http://www.askmefast.com/I_have_a_n...art_any_idea_what_can_be_done-qna1982335.html
They say clearing the Cache of the Samsung Keyboard fixes the thing. Wont be able to test by myself til tomorrow
Edited
I have N900W8 bell version, using it on Virgin network.
worked flawlessly with KitKat (either with Bell or Virgin version).
I've only experimented with Note-based custom roms (KitKat only), since I need the pen functionality.
First attempt:
I have experienced the same, not properly working menu button and not working back button.
I was on rooted stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version), rooted with Chainfire CF-auto root (Build ID:KOT49H.N900W8VLUCNB7) using Odin. (all the buttons working properly)
Upgraded to Lollipop 5.0 (N900W8VLU2DOH1) with Odin, rooted same way with CF-auto root (Build ID:LRX21V.N900W8UBU2DOL1). (Buttons do not work)
Second Attempt (No rooting involved what-so-ever):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Virgin mobile version, clean flash), all the buttons working properly.
Did OTA update through Wifi to, assuming, N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)
For both of above attempts, buttons are working properly with KitKat, whether it was rooted or not, and not with Lollipop, whether it was rooted or not. I'm thinking it's just the lollipop issue.
Third attempt (using N900W8VLUCNB7 Firmware Bell version):
Reverted back to stock KitKat 4.4.2 (N900W8VLUCNB7 Firmware Bell version, clean flash), all the buttons working properly.
Did OTA update through Wifi to N900W8VLU2DOC4. (Buttons do not work)
Another OTA update through Wifi to N900W8VLU2DOH1(confirmed). (Buttons do not work)
wy2sl0 said:
I ended up flashing a stock n9005 zip TW rom and it is fixed - but I had to install TWRP again etc. Thanks for the help though!
Click to expand...
Click to collapse
Do you have the link for the stock Tom zip?
Sent from my SM-N900W8 using XDA Free mobile app
Ok. Pretty much tried everything while staying on stock firmware.
However, everything else seems to work okay other than the touch button.
So now im gonna root the stock lollipop and use xposed and gravitybox to manually remap the 2 touch keys. Will update
Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.
rocked_out said:
Hell yeah(excuse my language, but I'm so happy), I got this working!
Before I start listing my steps, please thank wrench588 here for me to find a confirmed working solution, and
thank stew721 here for the original post!!
No root on a stock lollipop (N900W8VLU2DOH1) Virgin firmware on Bell phone
1. Clean flash with N900W8VLU2DOH1 Virgin firmware on odin. (I'm guessing you actually wouldn't even need to do this step, if you are already on lollipop (N900W8VLU2DOH1 or N900W8OYADOC4 firmware)4N900W8
- I got my stock firmware from here
2. Download idlekernel here
- For Odin flash: download idleKernel-hlte-can-6.6.5.tar.md5 (for Canadian galaxy note 3 SM-N900W8)
- For recovery flash (ie. twrp): download idleKernel-hlte-can-6.6.5.zip (for Canadian galaxy note 3 SM-N900W8)
3A. For Odin,
a. open Odin
b. load into download mode (by holding Power+Volume Down+Home key together when turning on the device)
c. Load the idleKernel-hlte-can-6.6.5.tar.md5 into the "AP" on Odin
d. "Start" on Odin
3B. For Recovery(TWRP or CWM),
a. Boot normally and copy idleKernel-hlte-can-6.6.5.zip into your phone
b. flash idleKernel-hlte-can-6.6.5.zip file in recovery
Done.
Thank you so much again, wrench588 and stew721. I could not be happier
Next step for me would be getting my stock rom to get deodexed so I can install "xposed". I need to replace the function of holding "menu" touch button to pop up google search instead of S finder.
Click to expand...
Click to collapse
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.
SS604 said:
THanks for this!!! note that some will get a "unfortunately knox has stopped working" upon bootup and nothing can be done about it to my knowledge.
Click to expand...
Click to collapse
Hey , has anyone firgured out how to get rid of the "unfortunately Knox has stopped working" ? I had the same issue with the softkeys not working. This fix works but I get this message. I was also told to try flashing a PIT file with stock firmware to fix the softkey issue, but this did not work.
Maybe flashing supersu from TWRP will allow supersu to disable knox?
not to bring back a dead thread, but this is exactly what I needed. I needed to root to fix screen mirroring so I just used root uninstaller to delete knox.