Develop Bugs

Galaxy Note 2 Superbork

Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/show....php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!

I have roughly the same situation. Was rooted and on an MK4 rom, battery ran down super fast yesterday and when charged, only get splash screen and slowly flashing blue light. I can get into Philz recovery but no matter what I try, no dice. Also can get into DL mode, but haven't been able to get anywhere. What the heck happened?

Well i bought another phone because of this problem of unknown baseband and 0 for everything in settings which didnt allow me to connect to sprint. Now when that happen it put me in safe mode . and i couldn't find a fix for months i ended up getting a lg g2 and let my note 2 collect dust. Well I'm using my note 2 and its up in running . my partition was messed up . if you have this issue which it sound like i can help. My phone was running fine then rebooted on its own and rebooted on safe mode with no signal
Sent from my SGH-M919 using XDA Premium 4 mobile app

[Q] Possible Brick N7100- please help

Hello guys
I just want to say i'm no where near an expert on this, and i feel i have tried to fix this issue but made it way worse in the process so please be gentle.
This morning i woke to my Samsung Note 2 N7100 just hanging on the samsung start up screen. Tried all the normal things, taking bat out, restarting many times etc. No luck, just kept hitting the samsung screen and freezing.
After some goggling i found my way to the Recovery screen (power+vol up+home) but when it was loading there was a lot of Red Error messages. It loaded the options screen and i tried to do a factory reset. A lot more error messages to basically then say failed. Tired it a few times and even tried to clear the cache but kept failing.
So i tried loading it into Kies, which didn't connect to the phone so i couldn't reinstall the software.
So i decided maybe i need to flash the phone. I downloaded a stock Rom for the phone (i was on Kitkat so found that version) Used odin and half way through the install it came up failed.
Since then the phone only displays the "Fireware upgrade encountered an issue. Please select recovery mode in Kies"
So i went back to Kies but still couldn't find the phone. It also won't let me go back into recovery mode, only into download mode.
I thought maybe i'd give the flashing another go but this time when i flashed it, it just hangs trying to find Pit but eventually fails saying no Pit.
From research it appears that the partition is buggered. All the research i've done seems to say stay away from messing with the partition. some people say its Emmc thats gone and its game over but others say there is hope still.
I can still access the Download menu and the product name is still GTn7100, Binary still samsung official so i am holding out hope there is some life left in it. I'm on my last legs now so open to all offers for solutions. Please assist if you can
Thank you in advance
Andy

If you're able to get in download mode.. Maybe try flashing a custom recovery (TWRP) which you could try full format in it then install a ROM using it.. Also, maybe trying to use a CM based one? Though you might need a external SD card to move files from PC to your phone.
I don't know if this would work, but try it.
Sent from my Galaxy Note II using Tapatalk

Note II LTE stuck on bootloader

Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?

GoonReb0rn said:
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
Click to expand...
Click to collapse
Update: I spent the past two days trying to solve this and I'm at a standstill in progress. It seems that my phone was one that suffered SDS with a corrupt eMMC chip so I've lost both my firmware and recovery but I can still get into Download mode. It also seems like I have lost my PIT table and I am just completely unable to flash the PIT file back to the phone for some reason. Does anyone have any ideas on how I could just factory reset my phone or reinstall my partition table so that i can get a simple recovery installed? Please help

Exact same issue!
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.

dkinniburgh said:
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
Click to expand...
Click to collapse
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.

GoonReb0rn said:
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
Click to expand...
Click to collapse
I was lucky having most of my info already backed up. I also had just upgraded another line, so I had a new phone to work with. It just sucks having to switch everything over to a new phone, reloading all the apps etc.

[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?

Note 4 looping on first start up screen

Hoping for some advice how to get Sprint Note 4 running again. The phone has never been rooted. Up until a couple of weeks ago most of the OTA updates had been received and applied no problem. A couple of weeks ago my wife pulled it out of her bag and showed me it was on the update screen and had been for a couple of hours eventually the batter went dead. We took out the dead battery charged it and tried to restart. It goes to the Samsung Galaxy Note 4 white on black screen vibrates twice then the screen goes black and it repeats the same thing over and over.
Now i'm not sure how to proceed. I'm familiar with Odin and rooting my own phones but leave my wifes stock normally.
First i tried reset in recovery - When i boot to recovery after a few seconds the android robot lies on its back with a red triangle over it. At the top of the recovery screen it says Android system recovery - LRX22C.N910PVPU3BOF5. I tried wipe data/factory reset and wipe cache partion and rebooting but makes no difference.
I thought install official firmware manually
I put the phone in download mode it displays
current binary: samsung official
system status: official
reactivation lock: off
knox warranty void: 0x0
I downloaded a stock firmware N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5
installed Odin3 v3.10.6.exe
installed F/W this using Odin.
Odin finishes normally, box turns green and PASS! but the phone just restarts and does the boot looping thing.
I don't know what to do next - suggestions? Thanks

Have you tried booting to safe mode, you'll have to Google it as I'm not sure of the procedure for stock phone. What your describing doesn't sound good, I would have thought the odin flash would have worked.
You could always try to odin OG5 Stock tar, can be downloaded from kies. Sorry i cannot offer more but it sounds like you're doing all the right things.
Sent from my SM-G925P using Tapatalk

Yes, I agree, that's good advice. I'd say try KIES first, then safe mode if KIES doesn't yield results.
Did you get to safe mode? From power off, hold power until 2nd splash screen, release and press-hold power plus volume up until it boots or vibrates. I think if you continue to hold, it loops until you release but boots into safe mode.
Unlock screen and go into security (if it boots) and uncheck Reactivation lock, Knox active protection and make sure device isn't encrypted. Finger scanner; remove registered finger prints, and change lock-screen to swipe. Then factory reset or try whichever you prefer to try next. If normal reboot still fails, then factory reset in safe mode and reboot. If still loops, try the KIES or Odin flash. I'm not too familiar with stock and default security but looking at OG5 security options, seems there's redundancies that could potentially be in play preventing Odin flash as if the phone thinks the phone is in the hands of someone other than the registered owner. You may need to bypass it all to boot or flash.
Typically, it's data corruption that causes a loop that stock tar doesn't fix in tars OF5 and below. OG5 has frequent reports of wiping user data but I've seen occasional reports of inability to flash OG5 tar from OF5. I saw another today that reported having to Odin OF5 tar again and take OTA to get to OG5. I asked what the failure indications were but so far only know his rooted phone couldn't get there without taking those steps. So perhaps you're on the right track, it's just the security and our security that's being a hindrance.
Sent from my SM-N910P using Tapatalk

thanks for the suggestions. I tried booting into safe mode but i can never get past the first white on black Samsung Note 4 powered by android screen. No matter how long i hold just the power button it just goes black and back to this screen every few seconds. I never get to the second boot splash screen. Any other way to force the phone into Safe mode?
I've installed kies and smart switch. The phone is not recognized by either whilst boot looping. If i put it in download mode and connect it kies3 displays unsupported device. How do i get Kies let me download a copy of OG5 firmware to my pc to try with Odin? I can't figure this out. I connected my own Note 4 to kies and it recognizes it fine and displays This is the latest firmware Current og5 latest og5 but i still don't see how to download a fresh copy of OG5 to the PC? In Kies i go to Tools, Firmware upgrade and initialisation. I'm entering the model name SM-N910P and then it wants a serial number. How do i determine this? I tried the Dec and Hex numbers from the back of the phone, i tried the Hex number plus a 1 and plus a 9 - i read this is the imei and this is confirmed from looking in settings on my other note 4. I'd really like to get a clean download of sprint OG5 from Kies i've searched for instructions without success.
Suggestions what i can try next? Thanks

waroo14 said:
thanks for the suggestions. I tried booting into safe mode but i can never get past the first white on black Samsung Note 4 powered by android screen. No matter how long i hold just the power button it just goes black and back to this screen every few seconds. I never get to the second boot splash screen. Any other way to force the phone into Safe mode?
I've installed kies and smart switch. The phone is not recognized by either whilst boot looping. If i put it in download mode and connect it kies3 displays unsupported device. How do i get Kies let me download a copy of OG5 firmware to my pc to try with Odin? I can't figure this out. I connected my own Note 4 to kies and it recognizes it fine and displays This is the latest firmware Current og5 latest og5 but i still don't see how to download a fresh copy of OG5 to the PC? In Kies i go to Tools, Firmware upgrade and initialisation. I'm entering the model name SM-N910P and then it wants a serial number. How do i determine this? I tried the Dec and Hex numbers from the back of the phone, i tried the Hex number plus a 1 and plus a 9 - i read this is the imei and this is confirmed from looking in settings on my other note 4. I'd really like to get a clean download of sprint OG5 from Kies i've searched for instructions without success.
Suggestions what i can try next? Thanks
Click to expand...
Click to collapse
This may help your PC detect the phone better in recovery mode for KIES. Can't say it gets past unsupported device but it was a problem I had with adb in recovery on my Windows 8.1 machine. Read the OP and post 14 to see if it applies to you. Try detecting phone in recovery.
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I've always found safe mode a little difficult to get into but once I found my phone had went there when I was carrying something wrapped around the phone while in a belt pouch. Holding both buttons must have been the way it accidentally got there.
That unsatisfied s/n inquiry has puzzled some of us here and we haven't found a solution AFAIK.
I'm not sure but you may have to also Odin OF5 and take OTA like some others have had to do. There are some tar files in general forum that others succeeded with. Sorry but that's about all I can think of. Unless you can get it to Best Buy Samsung Experience or Sprint service center and explain what happened. They should be able to flash stock back on it. That may be best solution since there was no doubt about root or void warranty on that one.
Sent from my SM-N910P using Tapatalk

Thanks for the suggestions.
I found more instruction for getting into safe mode which work on my other note 4 but no success with this one.
I was trying to Odin OF5 it goes all the way through in Odin and displays success but never actually boots.
Would it be possible to replace the stock recovery with something else that might have additional features to get a working f/w to install and then downgrade back to stock or will i risk just making things more screwed up? I wouldn't care about taking OTA updates if i could just get a working F/W back onto this phone.
Encryption and security were not enabled on the phone.
So without S/N what is the work around to use Kies with Sprint phones?

Since you're pure stock and given the problems I'd stay away from a custom recovery at this point. Your reporting a successful odin flash of stock OF5 then rebooting right back to the same boot loop problem is sounding more and more like something has seriously failed in the phone, I'd start thinking replacement.
Sent from my SM-G925P using Tapatalk