Develop Bugs

[Q] Power Button....dead

I've looked over other forum posts, and don't see anything that would help with the Note 2 in this situation.
Power Button is dead. When the phone was ON, the phone would work, all except the power button. My dumb ass let the battery die one night, and now it will fully charge, but cannot turn on.
I bought a USB jig (quicker than me making one)...however, it will boot to ODIN, but not completely...sits at the "Downloading...Do not turn off target !!", and the Binary Download Count is still at 1.
Question: Good Plan ...or Bad Plan
My guess is the jig is just not the right type for this phone, and i should simply make my own with a 300K resistor jumped between pin 4 and 5. I thought the jig would reset the download count to 1.....if not, then it could be working just fine.
Question:When stuck in this "Downloading" mode, I can connect it to the PC and see it with ODIN 3 v1.85...currently downloading stock ATT ROM. Will I be able to drop the stock ROM onto the device while on the "Downloading" screen...(something tells me...yes...)
Question:
If the stock ROM does not reset the binary download count to 0, i see there is an app i can install that will reset it for me. However, I cannot boot the phone. Is there a way to boot the phone remotely...ie, when it is plugged into the PC?
Question:...last on i swear
Any ideas on the freakin' power button?....obviously phone is under warranty, but i don't want to send it back until its un-rooted.
thanks...and sorry for the noob questions.

closer...but still no luck.
mahjohn said:
I've looked over other forum posts, and don't see anything that would help with the Note 2 in this situation.
Power Button is dead. When the phone was ON, the phone would work, all except the power button. My dumb ass let the battery die one night, and now it will fully charge, but cannot turn on.
I bought a USB jig (quicker than me making one)...however, it will boot to ODIN, but not completely...sits at the "Downloading...Do not turn off target !!", and the Binary Download Count is still at 1.
Question: Good Plan ...or Bad Plan
My guess is the jig is just not the right type for this phone, and i should simply make my own with a 300K resistor jumped between pin 4 and 5. I thought the jig would reset the download count to 1.....if not, then it could be working just fine.
Question:When stuck in this "Downloading" mode, I can connect it to the PC and see it with ODIN 3 v1.85...currently downloading stock ATT ROM. Will I be able to drop the stock ROM onto the device while on the "Downloading" screen...(something tells me...yes...)
Question:
If the stock ROM does not reset the binary download count to 0, i see there is an app i can install that will reset it for me. However, I cannot boot the phone. Is there a way to boot the phone remotely...ie, when it is plugged into the PC?
Question:...last on i swear
Any ideas on the freakin' power button?....obviously phone is under warranty, but i don't want to send it back until its un-rooted.
thanks...and sorry for the noob questions.
Click to expand...
Click to collapse
Was able to reload the stock ROM, however, the "Binary Download Count" still shows as 1. Would I need to re-root....download Triangle Away to reset to 0, then reload stock ROM?

mahjohn said:
Was able to reload the stock ROM, however, the "Binary Download Count" still shows as 1. Would I need to re-root....download Triangle Away to reset to 0, then reload stock ROM?
Click to expand...
Click to collapse
try factory reset first.

WHich ROM you have flashed?
If you have flash latest ROM, then reflash some older ROM and re root using exynose abuse application. (latest ROM won't allow exynose abuse to root)
then use triangle away to reset counter
then unroot from exynose application itself
then you can send it to service station to repair.
PS : I doubt without power button how you can normal boot.
Edit : once you will flash ROM, it will auto boot normally, then same step you can install exynose abuse, root, use triangle away, it will auto enter to recovery mode and clean counter. then it should boot normally.
I think this should work.

It's really obvious is a hard ware problem. Warranty claim perhaps
Sent from my GT-N7100 using xda app-developers app

if u can boot into download mode, it shouldnt have any problem, just flash from odin, root then triangle away, if you needed, install some app that can boot into recovery like root toolbox

solved
dr.ketan said:
WHich ROM you have flashed?
If you have flash latest ROM, then reflash some older ROM and re root using exynose abuse application. (latest ROM won't allow exynose abuse to root)
then use triangle away to reset counter
then unroot from exynose application itself
then you can send it to service station to repair.
PS : I doubt without power button how you can normal boot.
Edit : once you will flash ROM, it will auto boot normally, then same step you can install exynose abuse, root, use triangle away, it will auto enter to recovery mode and clean counter. then it should boot normally.
I think this should work.
Click to expand...
Click to collapse
Thanks for the support. I was able to resolve this problem using steps below.
1. USB Jig to boot to ODIN
2. Connect to PC, run ODIN and Flash ATT Stock ROM (didn't know what would happen if i re-rooted a rooted device)
3. Booted phone with Jig again....re-rooted phone
4. Phone boots with SU. Installed Triangle Away and reset counter to 0
5. Booted phone to PC, installed stock ATT ROM and reset to factory defaults
6. Booted to jig to check ODIN still showed 0
*probably the long way around...but i had time, and it was taking that long...just wanted to be sure.
FYI: Jig $3.90 (Amazon), Triangle Away $2.90
Replacement phone is on it's way should be here tomorrow....
thanks again

unable to reroot Sprint Galaxy S3 with a failed root.

I have an S3 from sprint. it has a faild root at this point (TrevE). My guess is that an update locked up my root.. I am tring to flash back to stock so I can reroot but SU blocks everything i do. I have tried to reroot but CW wont come up, just android recovery. Everything I have found on removeing SU requires you to be rooted first.... I even tried Root Browser and Uninstall master but SU just denies permission.... All i want to do is start from scratch. Please help...

christivson said:
I have an S3 from sprint. it has a faild root at this point (TrevE). My guess is that an update locked up my root.. I am tring to flash back to stock so I can reroot but SU blocks everything i do. I have tried to reroot but CW wont come up, just android recovery. Everything I have found on removeing SU requires you to be rooted first.... I even tried Root Browser and Uninstall master but SU just denies permission.... All i want to do is start from scratch. Please help...
Click to expand...
Click to collapse
Do you are able to get to download mode?

kevinrus123 said:
Do you are able to get to download mode?
Click to expand...
Click to collapse
The problem was that i watched too many videos and went through too many how to guids. I kept working at it and finaly got it to work. i finaly found a video that told me not to let it reboot after odin was done. I turned "off" the auto reboot on Odin, which is the exact oposite of what every other video said to do, and manualy shut it down and put it straight into Recovery Mode. All of the videos I had seen said to leave Auto Reboot on so i had been doing that. after it would reboot I would shut it back down and try to go to recvery mode but got the android recvery insted of CWRecovery. I guess the reboot after Odin was enough to through it all out of wac. Manually shutting it down after Odin and then going into recovery right away got it. Unfortunatly thats the problem when there are 5,000 answers to the same question. Thanks

christivson said:
The problem was that i watched too many videos and went through too many how to guids. I kept working at it and finaly got it to work. i finaly found a video that told me not to let it reboot after odin was done. I turned "off" the auto reboot on Odin, which is the exact oposite of what every other video said to do, and manualy shut it down and put it straight into Recovery Mode. All of the videos I had seen said to leave Auto Reboot on so i had been doing that. after it would reboot I would shut it back down and try to go to recvery mode but got the android recvery insted of CWRecovery. I guess the reboot after Odin was enough to through it all out of wac. Manually shutting it down after Odin and then going into recovery right away got it. Unfortunatly thats the problem when there are 5,000 answers to the same question. Thanks
Click to expand...
Click to collapse
You may have watched some videos from before the last two official stock updates that were released several months ago - I don't recall which one, but one of those updates added a function that reinstalls the stock recovery every time the phone boots up. And since the custom recovery is the only way to flash a custom rom that doesn't revert your recovery to stock, you have to do that while the custom recovery is still installed, which means before the stock rom ever gets a chance to boot
In other words, nothing was thrown out of whack - it was all operating the way it was designed to, by developers who don't want us to be able to mess with their programming - we sure showed them, though, lol
Sent from my SPH-L710 using xda app-developers app

[Q] Stuck at boot when updating to KK

Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.

You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app

cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.

allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.

Would like to return phone to Normal State

I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-

dameware said:
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob

rlichtefeld said:
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
Click to expand...
Click to collapse
It won't read it because my phone is now too old of a device for the program (2.2.2 or whatever). Thank you very much I'm trying all this right now, finally a firmware download that doesn't take 6 hours because of horrible servers!
I will update on if this works or not, I'm guessing it will

I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?

Lopakas said:
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Click to expand...
Click to collapse
EDIT:
Done and done! It all worked out, thank you thank you!
Now to try cyanogen and my device will be back to beast mode.
Just do what he says and you should be fine; factory reset never did anything for me :/

[Q] Custom Binary blocked by Reactivation Block (Help!!! Please.)

Or... "How I was dumb".
I have a Sprint Note 4 (SM-910P) that I have had rooted for the past few months. I got interested in the new update that was release this month, so I flashed back to stock, ran the updates, and re-rooted over the weekend. I also decided to activate that new "Reactivation Lock" feature (you can see where this is going).
So it occurred to me that I had not reinstalled Cerberus, so downloaded the APK and went to boot into recovery so I could install it to root. I forgot to turn off my "Reactivation Lock", so it booted to a black screen with a yellow triangle and the message: "Custom Binary blocked by Reactivation Block. Secure Fail: Recovery". Pressing the power button turns the phone off. Trying to boot into recovery produces the same error. I can still boot into download mode.
I have been doing some research on how to fix this, and have found two suggested fixes, neither of which work for me:
Fix 1 tells me to boot into download mode, pull the battery, reinsert the battery, and the phone should boot up normally. This doesn't work.
Fix 2 tells me to boot into download mode, and flash to stock with Odin. I have downloaded the stock .tar and tried to flash it with Odin 3.10. I get a fail message. (Full Disclosure: I have only tried Fix 2 on my work test PC. It is an old Vista box that is very slow. I don't know if that is a contributing factor.)
I was hoping that some of you folks had some advice for me. I have all of my data backed up, so I'm not worried about starting over with a clean slate. I'm also not worried about tripping KNOX. That ship has sailed at this point. I just want my phone back.

thescreg said:
Or... "How I was dumb".
I have a Sprint Note 4 (SM-910P) that I have had rooted for the past few months. I got interested in the new update that was release this month, so I flashed back to stock, ran the updates, and re-rooted over the weekend. I also decided to activate that new "Reactivation Lock" feature (you can see where this is going).
So it occurred to me that I had not reinstalled Cerberus, so downloaded the APK and went to boot into recovery so I could install it to root. I forgot to turn off my "Reactivation Lock", so it booted to a black screen with a yellow triangle and the message: "Custom Binary blocked by Reactivation Block. Secure Fail: Recovery". Pressing the power button turns the phone off. Trying to boot into recovery produces the same error. I can still boot into download mode.
I have been doing some research on how to fix this, and have found two suggested fixes, neither of which work for me:
Fix 1 tells me to boot into download mode, pull the battery, reinsert the battery, and the phone should boot up normally. This doesn't work.
Fix 2 tells me to boot into download mode, and flash to stock with Odin. I have downloaded the stock .tar and tried to flash it with Odin 3.10. I get a fail message. (Full Disclosure: I have only tried Fix 2 on my work test PC. It is an old Vista box that is very slow. I don't know if that is a contributing factor.)
I was hoping that some of you folks had some advice for me. I have all of my data backed up, so I'm not worried about starting over with a clean slate. I'm also not worried about tripping KNOX. That ship has sailed at this point. I just want my phone back.
Click to expand...
Click to collapse
You updated to oe1. You need to get someones oe1 backup. As far as the lock out. Im not sure. I believe you can fix it from samsung site login to the device lock page? Not even sure it exists. But once you boot you should have the security option to enter your credentials. So just look on the thread about oe1 update. Someone posted a backup.
Sent from my SM-N910P using XDA Free mobile app

Well think ice broken through the oem bs i got 3 devs looking it a workaround the get ofin up

I FIXED IT!
Here is what I did. I got home, and reread some of the stuff that I found. I was going through a step-by-step provided by Xharky.
http://forum.xda-developers.com/showpost.php?p=53920665&postcount=25
Xharky said that it didn't really matter what you flashed in Odin, that you would probably get an error and that the phone would boot normally after a battery pull. So when I tried flashing the stock .tar with Odin 3.10, it failed, but the phone didn't boot back up; wrote off that fix.
When I got home, I sat down and thought it all out. Odin 3.09 has never worked well for me, and I had never used 3.10 before today. However, I haven't had any problems with Odin 3.07. So I fired it up, and flashed CF Auto Root. Sure enough, I got a fail result in Odin. I did a battery pull and rebooted... And my phone booted right up. I promptly got into my security settings and deactivated that damn Reactivation Block.

thescreg said:
I FIXED IT!
Here is what I did. I got home, and reread some of the stuff that I found. I was going through a step-by-step provided by Xharky.
http://forum.xda-developers.com/showpost.php?p=53920665&postcount=25
Xharky said that it didn't really matter what you flashed in Odin, that you would probably get an error and that the phone would boot normally after a battery pull. So when I tried flashing the stock .tar with Odin 3.10, it failed, but the phone didn't boot back up; wrote off that fix.
When I got home, I sat down and thought it all out. Odin 3.09 has never worked well for me, and I had never used 3.10 before today. However, I haven't had any problems with Odin 3.07. So I fired it up, and flashed CF Auto Root. Sure enough, I got a fail result in Odin. I did a battery pull and rebooted... And my phone booted right up. I promptly got into my security settings and deactivated that damn Reactivation Block.
Click to expand...
Click to collapse
Awesome bro. Thats what i like to hear. A true android heart. Im on the "beat the OE1" task in my head. Im running options and scouring. Lol.
Sent from my SM-N910P using XDA Free mobile app

Yea i beat oe1 also i downgraded

pbedard have you successfully downgraded from the OE1 update back to NK2 or OB7? I took the OE1 update two days after it came out. I didn't research it didn't make a nandroid like an idiot after I updated to OE1. Once I took it I decided I didnt like it so I Odin'd the official NK2 tar it failed then i proceeded to boot twrp recovery restore my NK2 backup I had before I odin'd the offical OB7 tar to take the OE1. Then we have Bootloop. I managed to flash the bobcat rom only I didnt flash the separate theme zip with it like you're supposed to but it's been working for now, not without bugs and a fc of apps every now and then. In my about device it states software OE1, baseband OE1, android version 4.4.4, kernel version 3.10.5-AELKernel-v5.5, and build number KTU84P.N910PVPU1ANK2. I'm guessing I'm just going to have to wait until the OE1 tar is out and just deal with the stockness of it until devs get their OE1 roms out. Thanks in advance if you have any input or thoughts on this depressing matter.

I got a new phone now from sprint i made it look like a softwsre issue

pbedard said:
I got a new phone now from sprint i made it look like a softwsre issue
Click to expand...
Click to collapse
How did you get a stock recovery. Store tried to factory reset mines and when they saw TWRP they new it was rooted, so vioded. If I can get stock recovery then i can fool them, lol. If you have any let me know, thanks in advance.

I backed it up with flashify
---------- Post added at 04:48 AM ---------- Previous post was at 04:47 AM ----------
If u know gow to use it ill give u a copy im not responsible thoigh if u hurt your device

I'd be willing to try it. I know exactly what store to take it too.

christophfloor said:
I'd be willing to try it. I know exactly what store to take it too.
Click to expand...
Click to collapse
Careful. A neighbor of mine did this once. Took about a month. His replacement after a couple of weeks stopped getting signal. He called the carrier and they said the phone he sent in was found flagged by asurion. Which they sent a note to his account. So his new phone was blacklisted until he paid for the brick. Take caution. They are catching on. Not saying this will surely happen but if people keep brick returning this will only get worse. Just a heads up. I have never returned a brick but I have returned rooted.
Sent from my SM-N910P using XDA Free mobile app

flynhawn2002 said:
How did you get a stock recovery. Store tried to factory reset mines and when they saw TWRP they new it was rooted, so vioded. If I can get stock recovery then i can fool them, lol. If you have any let me know, thanks in advance.
Click to expand...
Click to collapse
Well, here's a link to a flashable stock recovery zip for OB7 that I put together for you if it would help.
It is what it is... Flash at your own peril ...
RE-EDIT:
OB7 Stock Recovery Here
This IS a flashable ZIP
I'm still looking for the OE1 OTA update zip... Anyone have it?