So I have this phone (SM-N920P) that a few days ago just went black in the midst of operation... the power button alone would not turn it back on... eventually the power and volume down did power it back up (if it was ever really even off) but at that point it stuck at the boot screen.
So I have went though what I think is every possible option... but I willing to see if there is anything else..
I have used Odin to load various flavors of stock ROMS (it was stock when it went into this condition so it was locked down before it "died:
no developer tools and FRP lock is on.... I tried some Roms that said they could bypass the FRP lock and allow some custom Rom.. thinking that would help but at this point I am not sure that would even matter considering where I am with this unit, regardless they would not load.. or get past the FRP lock..
there are tons of files out there and some seem to come from questionable repositories.. this is my first foray into android issues.. but no one makes it really easy or "safe" feeling..
Anyway the last thing I tried was loading one of the frp unlock roms which fail and cause the phone to boot to a bad load blue screen... then I unpacked an md5 file and took just the recovery.img out... renamed as tar and loaded that...
At that point the phone does boot past the bad load, but I am right back to just that splash screen.. and no matter what I cannot get it to go to an Android screen to use the recovery.img I believe I just loaded.
I loaded fastboot and adb but at this point they do not see a device.. so something beyond Odin.. or some "special" file may be the only hope? Or it is just shot? seems like it should be able to be fixed though... I have spent like 12 hours trying different things so far.
I did get one ROM to load that showed some android output at the top of the boot screen.. and when I did the normal vol up, power, home.. it did go into another screen.. which looked like Recovery... but it just said turn off auto reboot and the Hard Reset the device...
but I could not do anything but reset the device using vol down and power...
The power alone still never does anything... those are the 2 keys.. power alone does nothing... and I cannot get into the android recovery screen.. any help would be great.. thanks.:good:
Hold the power + home + vol down buttons for 7-10 seconds until screen goes off. Then boot into download mode and flash TWRP which you'll then use to flash a working ROM.
Blocked by FRP Lock
duckynawal said:
Hold the power + home + vol down buttons for 7-10 seconds until screen goes off. Then boot into download mode and flash TWRP which you'll then use to flash a working ROM.
Click to expand...
Click to collapse
I can get to that point... but load fails with the Custom Binary(Recovery) Blocked by FRP Lock.. I tried every version of twrp available..
and since the phone cannot get to anything except the download and boot screen I cannot alter any normal usb debug or OEM setting...
MagicNote said:
I can get to that point... but load fails with the Custom Binary(Recovery) Blocked by FRP Lock.. I tried every version of twrp available..
and since the phone cannot get to anything except the download and boot screen I cannot alter any normal usb debug or OEM setting...
Click to expand...
Click to collapse
Since you can boot into download mode, flash TWRP using Odin, then boot into recovery.
Hope this brings some clarity to your current predicament. Wish I had good news.
I've ran into this problem twice now either using .img to .tar tool that isn't set up properly with an incompatable version of stock rom or a corrupt dump of a stock rom or even using a proper stock rom. Or if you just so happen to accidently turn off O..E.M unlock... and your phone died or you restarted it.... Download mode spits out some red code usually or fails or even can complete but not in any case I've ever seen and boot sucessfully.... usually if you try to many times with odin you'll end up with a blue screen that comes up stating something went wrong during update process and to use Samsung's smart switch program on a pc. Only problem is at this point you've already tripped Knox and your warranty is now void so downloading smart switch and typing in your serial and one I will only give you another error stating that your phone is not comparable with smart switch due to Knox being tripped at 0x1......
At that point there are a couple options claim insurance if you have it, $200 or if you don't have insurance. Samsung will give you a spill about how your 1yr warranty is over and even if it isn't when they get your phone they will see your Knox status of 0x1 and tell you sorry your warranty is void due to end user tampering. So they offer a reflash for a cool $80 without warranty and that will reset your phone back to O.E.M specs with a Knox of 0x0 fix it for a mere $80. Smartswitch won't reflash firmware do to Knox being tripped. Sorry. You are more than welcome to try....
COLOR="red"]NEVER, I REPEAT, NEVER TURN OFF O.E.M. UNLOCK UNDER ANY CIRCUMSTANCES IF YOU HAVE ROOTED YOUR PHONE, OR PUT A CUSTOM KERNEL OR FLASH A CUSTOM RECOVERY OR YOUR FAIL TO BOOT.[/COLOR]If you turned off O.E.M unlocking. Basically O.E.M unlocking is telling your phone it's okay that Knox is tripped. O.E.M unlock allows the skipping verified samsung signature checks on the first rom based bootloade rduring the boot sequence alowing it to bypass into the secondary bootloader and kernel.
O.E.M. stands for "Original Equipment Manafacturer" i.e. being Samsung in this case so when you have not done anything to your phone when it comes brand new out of the package. Developer mode is hidden and unacessable for a reason.... O.E.M unlock means that in download mode you can flash unofficial code, i.e. C.W.M., TWRP, Other unsigned code from various developers. With no hassle due to Samsung being so kind to us developers and allowing us the option to manually unlock our bootloaders.
Usually what happens specifically is Samsung has a secure bootloader which uses digital certificates to ensure that the software loaded before the operating system is trusted to boot the linux kernel shell we all know and love as android OS when you load a custom bootloader such as anything not signed by Samsung it fails to pass the signature checks and that's exactly what turning off O.E.M unlock did.
But with us all being blessed with the option to manually unlock our Bootloaders through O.E.M unlock now so many options are open to us so as but not limited to.: Roms, MODS, Hacks, Busybox, Root, Xposed, Various Root Applications, Magisk, Kingoroot, GeoHots stuff, HashCodes stuff, even have the oppourtunity to create and test various of our own creations.
Once upon a time Bootloaders were locked, meaning, No Roms, No kernels, etc, etc... Very, Very difficult to even root phone's. The reason I go into all of that is Because with great power comes great responsibility. Always back up your eds partition, and always always if you root and like to run custom rom Roms and all the development for this scene that only continues to grow and evolve Make sure you do one thing if nothing else and that is to read, read, read and know your phone inside and out. I am a developer and I work with software as much as I do hardware. I can afford to make mistakes as these aren't my daily drivers. I suggest if you like to unlock the full potential of your devices then please heed my warning about reading and knowing all the dos and dont's for what your devices is capable of and what will turn it into a very expensive paper weight. I'm not being a **** I'm trying to help. Because you have now tripped your Knox counter meaning it is permanently stuck in the state of your phone now having a void warranty and there is no going back.
Once you turn O.E.M mode off you lock your bootloader and if you've already tripped Knox you can't flash a stock bootloader or Rom because your phone's hardware is preventing anything unauthorized from making it past the kernel checks..... clear some things up for You? I don't care the people say they have work around forCOLOR="red"]"custom binary frp lock"[/COLOR]because I have yet to see a phone recover. P.S. word to the wise that is one error you never, and I mean never want to see on your boot screen...
I came back from it once with a zeroed out serial number and a null one I. Once and that's a whole nother ball of wax. Claim warranty, play stupid if still covered if not Sammy will know so just shell out the $80 send it to them. They will reflash it and that's the end of that.
P.S. MODS, Why can't I just indent the first letter or word of my paragraphs? It's really bothering me. I tried for like 20 minutes. Everything from highlighting my whole paragraph, to highlighting the first word or letter. Even went as far as editing the hypertext php to no avail...COLOR="red"]What Am I Doing Wrong?[/COLOR]
---------- Post added at 03:11 AM ---------- Previous post was at 02:29 AM ----------
[/COLOR]
MagicNote said:
So I have this phone (SM-N920P) that a few days ago just went black in the midst of operation... the power button alone would not turn it back on... eventually the power and volume down did power it back up (if it was ever really even off) but at that point it stuck at the boot screen.
So I have went though what I think is every possible option... but I willing to see if there is anything else..
I have used Odin to load various flavors of stock ROMS (it was stock when it went into this condition so it was locked down before it "died:
no developer tools and FRP lock is on.... I tried some Roms that said they could bypass the FRP lock and allow some custom Rom.. thinking that would help but at this point I am not sure that would even matter considering where I am with this unit, regardless they would not load.. or get past the FRP lock..
there are tons of files out there and some seem to come from questionable repositories.. this is my first foray into android issues.. but no one makes it really easy or "safe" feeling..
Anyway the last thing I tried was loading one of the frp unlock roms which fail and cause the phone to boot to a bad load blue screen... then I unpacked an md5 file and took just the recovery.img out... renamed as tar and loaded that...
At that point the phone does boot past the bad load, but I am right back to just that splash screen.. and no matter what I cannot get it to go to an Android screen to use the recovery.img I believe I just loaded.
I loaded fastboot and adb but at this point they do not see a device.. so something beyond Odin.. or some "special" file may be the only hope? Or it is just shot? seems like it should be able to be fixed though... I have spent like 12 hours trying different things so far.
I did get one ROM to load that showed some android output at the top of the boot screen.. and when I did the normal vol up, power, home.. it did go into another screen.. which looked like Recovery... but it just said turn off auto reboot and the Hard Reset the device...
but I could not do anything but reset the device using vol down and power...
The power alone still never does anything... those are the 2 keys.. power alone does nothing... and I cannot get into the android recovery screen.. any help would be great.. thanks.:good:
Click to expand...
Click to collapse
Related
...Brick an *UNROOTED* G1...?!
I attempted a soft factory reset (which I have done on many occasions previously successfully) but on this occasion I've run into the bootloop. Hitting Camera+Power button results in bootloop also.
One thing to mention is I removed my SD card before running the factory reset?
I've tried leaving the battery out over night and trying again in the morning.
I've tried placing the SD card back in and booting up the phone.
I've tried holding Home+Power to get into recovery but results in bootloop
I've tried holding Camera+Power to get into Bootloader but results in bootloop.
Any suggestions please?
Thanks!
No, this should not happen. With Bootloop do you mean there is just the G1 logo and nothing else, or does it get past the logo and reboots then?
Another thought, has this phone ever been rooted and unrooted again?
If you are still under warranty and the phone is completely stock, I'd return it.
Nope. Phone has never been rooted then unrooted.
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Warranty is only for a single year, right? So then that's not an option.
Thanks for suggestions.
Jignesh Sutar said:
Warranty is only for a single year, right? So then that's not an option.
Click to expand...
Click to collapse
Depends on where you are: http://www.htc.com/www/support/warranty.html
It looks like you phone either fails to boot, thus tries to boot recovery (box picture is the background of the recovery) and then reboots (best case, i guess) or the boot to recovery flag is set, recovery fails, reboot (you might seriously be screwed).
You are sure that you can't enter the bootloader? Also try Back+PowerOn. That would make things alot more easy.
How long does it stay with the box picture? Long enough to get adb connected? If yes you could try "adb shell reboot bootloader".
Tried all combinations of buttons to try get into bootloader or recovery, nothing!
Definitely no chance of being able to ADB, the phone switches off very quickly...
Also, have ensured the battery is fully charged, in case that has an impact?
I really looks like you are the first all stock bricked guy I ever heard of.
The boot recovery flag seems to be set for some reason (is this set during a normal hardreset?) as all boottime commands are ignored.
The recovery fails improperly (sounds strange, but if it failed properly, you would end up in bootloader or your system).
-> That really looks like a brick...
Options:
- Warrenty
- JTAG
- perhaps someone else has another idea / sees something I missed...
Good luck with it.
Jignesh Sutar said:
By bootloop, I mean, G1 T-Mobile logo shows followed by a picture of a open box with the phone just outside animation and then seconds later the phone reboots itself running into this loop again and again.
Click to expand...
Click to collapse
What where you flashing? It probably had a radio and something got copied incorrectly into the staging area of ram.. if the radio passes recovery's validation but not the current radios validation you can get stuck.. this shouldn't be possible but I've seen it before.. my bet is a bit error at the wrong point in time.
Hello everyone. In my attempt to experiment with custom ROMS yesterday, I seem to have sort of soft bricked my phone. When I install the stock OS, it installs fine, and I can start the phone. However, after it boots up, there are no apps. Just the clock at the top, the background, and the menu button in the bottom center (but pressing this button doesn't do anything). I can pull down the top menu and go to settings, but I don’t have access to anything else. Furthermore, after a couple minutes, the phone restarts itself. After this first restart, when its gets done booting, there is simply an empty black screen. The only way to get to the state mentioned before is to boot into bootloader, turn the phone off, and then turn it back on.
I’m wholly lost and out of ideas on how to go about troubleshooting this. Here is what I did yesterday to get to this point:
1. Unlocked the bootloader.
2. Flashed the latest Viper rom. It didn’t work; after booting up the phone was forever stuck on the Viper splash screen.
3. Flashed the stock Sprint HTC One rom. Again, after booting up the phone was forever stuck on the HTC splash screen.
4. Used TWRP to format all the data.
5. Flashed the stock Sprint HTC One rom again. This time it worked just fine. At this point, I thought I had discovered a valid method for fixing my soft bricked phone, so I decided to experiment with Viper and Android Revolutions roms to see if I could get them to work. I followed the process of installing a custom rom, getting stuck on the splash screen, formatting the data, then reinstalling the stock rom 3 times. On all three times the stock rom worked when I installed it. However, on the 4th iteration of this cycle, I reached the state I described above.
I tried using the RUU utility, but it doesn’t work (I get a signature verification error). I can enter bootloader and recovery without issue.
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
jclark11 said:
I've had this happen to me, Make sure that you re-lock your bootloader before the RUU
fastboot oem lock
I believe this will allow the RUU to start up right and repair. Lemme know how that goes.
Click to expand...
Click to collapse
Do you mean you have had the same blank screen problam as well? Or RUU wouldn't work for you?
I'm pretty sure i relocked the bootloader when I tried doing the RUU, but I will definitely try again. Unfortunately, I'm on a trip at the moment, so I'm not sure when I'll be able to look at it again (hopefully Saturday or Tuesday).
So when I boot my phone up, it get a myriad of interesting popups. I get the Galaxy Note logo, and it says "Custom" with an unlocked icon, and then I get a few lines, first - "Set Warranty Bit - Kernal" and then "Secure Fail - Kernal" with a white box. At one point I got a screen that told me "System software not authorized by AT&T" But I've not gotten to that screen since the one time it popped up.
Phone is not, nor has it ever been, rooted or modified. It had a screen freeze last time I looked at it, and I had to pull the battery to get it to respond again, and the phone hasn't worked since.
Thoughts? The repair store is about 300 miles for me, so I'd rather not make that drive...
Edit: Thought I'd try this out myself. Found the thread about NC2 recovery, followed all the instructions. Now I can't get into recovery, (Stuck on loading bootloader) and I bootloop on the Note 3 logo. Can still load download mode.
Prior to this, I was on the most current OTA. I feel like I'm majorly screwed. Knox tripped itself, and so I don't think I can get it fixed by ATT
http://forum.xda-developers.com/showthread.php?t=2703006
Please report back on the failure or success of this.
graydiggy said:
http://forum.xda-developers.com/showthread.php?t=2703006
Please report back on the failure or success of this.
Click to expand...
Click to collapse
Actually been trying that all night. I was able to flash it, (Properly, as far as I could tell) with and without the PIT file. After either attempt, it tried to reboot and load into recovery mode. ODIN would say "Reboot" and the phone would say "Loading recovery mode" and stick there permanently. I found a trick where you could get it past that by loading DL mode and selecting cancel. At that point, it boot looped on the Note 3 screen, and also boot looped trying to load recovery.
Currently, after 4-5 battery pulls, it's back to the original problem. Secure Fail: Kernel on regular boot, and Secure Fail: Recovery on recovery boot. Here's a picture of what it looks like, but on a note 3. (Can't take pictures, phone is my only camera. Lol)
Did my NAND fail? It's just so weird that my problem changes after reboots.
And **** me, I just rebooted it and it loaded the Samsung animation, no special text, and it got to the ATT logo... and then rebooted. Boot looped at note 3 screen 4-5 times, and now... (Each dash is a reboot)
Android is upgrading-Optimizing Apps screen-Note 3 Logo-Optimising-ATT Ready to go App (Froze)-Note 3 Logo-Note 3 Logo-Att Logo-Note 3 Logo-Att Logo-Samsung Logo-Att Logo. 20 more reboots now, not a single got past the Note 3 Logo
I can kind of load Recovery now though. It shows the little Android guy, and a loading bar. It usually resets at some point during the loading bar. I've yet to get into the recovery menu, but I've had results that range from loading recovery for 1 second and forced rebooting, to a 5 min loading bar, which I gave up on and pulled battery.
Looks like an EMMC failure. You are going to have to call AT&T or Samsung to get your device replaced.
graydiggy said:
Looks like an EMMC failure. You are going to have to call AT&T or Samsung to get your device replaced.
Click to expand...
Click to collapse
Knox tripped itself as well. Am I screwed? Haha.
Thanks for the help, BTW.
Not entirely.
Just to be clear.
In download you should see 2 Knox related flags
One that is kernel
One that is warranty
If either on says 0x0
Knox is not tripped.
Some people see anything related to Knox and think it's tripped.
I have a Blu R1 HD that I have been on again off again fiddling with for a few months that is soft bricked. It will turn on but it will hang on the second "Bold like us" splash screen after the animation ends. It had no recovery installed to it prior to the bricking, I have attempted flashing a stock rom to it with SPFT but It gets interrupted less then 3 seconds in. From my reading It seems like I have the 6.6 preloader that stopped spft from working.
Is there anything that could be done with this to get it working once again?
kamikazisolly said:
I have a Blu R1 HD that I have been on again off again fiddling with for a few months that is soft bricked. It will turn on but it will hang on the second "Bold like us" splash screen after the animation ends. It had no recovery installed to it prior to the bricking, I have attempted flashing a stock rom to it with SPFT but It gets interrupted less then 3 seconds in. From my reading It seems like I have the 6.6 preloader that stopped spft from working.
Is there anything that could be done with this to get it working once again?
Click to expand...
Click to collapse
Depends on few things.
Do you know what was last thing done before this brick?
Have you tried holding volume up when powering on, to enter recovery(stock, i know you mentioned no custom recovery installed)?
It goes to and past the animation , so i don't think it is a secure boot type of failure. But maybe a bad data problem. See above statement about recovery.
mrmazak said:
Depends on few things.
Do you know what was last thing done before this brick?
Have you tried holding volume up when powering on, to enter recovery(stock, i know you mentioned no custom recovery installed)?
It goes to and past the animation , so i don't think it is a secure boot type of failure. But maybe a bad data problem. See above statement about recovery.
Click to expand...
Click to collapse
I have gone into the stock recovery menu, And i have attempted factory data reset, clearing the cache, and a root integrity check. The integrity check says one item fails the check and that is "/system/lib/libLLVM.so"
The last thing that I recall happening is that I had a pop up saying that an app had stopped working, But it reappeared immediately after closing it again several times. I thought rebooting it would stop whatever was happening, but it never came back to the OS.
The device has a small crack on the bottom right hand side of the screen that happened when it fell from my pocket on top of a ladder. A family member who also works with electronics as a hobby thinks that may have something to do with it but the phone worked for weeks after the break happened.
kamikazisolly said:
I have gone into the stock recovery menu, And i have attempted factory data reset, clearing the cache, and a root integrity check. The integrity check says one item fails the check and that is "/system/lib/libLLVM.so"
The last thing that I recall happening is that I had a pop up saying that an app had stopped working, But it reappeared immediately after closing it again several times. I thought rebooting it would stop whatever was happening, but it never came back to the OS.
The device has a small crack on the bottom right hand side of the screen that happened when it fell from my pocket on top of a ladder. A family member who also works with electronics as a hobby thinks that may have something to do with it but the phone worked for weeks after the break happened.
Click to expand...
Click to collapse
I do not know if there will be any way forward with this.
As you are not bootloader unlocked, sp flash refuses to connect, and only thing that can be done on stock is "factory reset" did not help, you might be done , other that see if can send to Blu.
mrmazak said:
I do not know if there will be any way forward with this.
As you are not bootloader unlocked, sp flash refuses to connect, and only thing that can be done on stock is "factory reset" did not help, you might be done , other that see if can send to Blu.
Click to expand...
Click to collapse
Sending to blu isnt an option. Out of waranty period, And I also opened it to make sure there was nothing obviously physically wrong.
I also tried using the dirty cow tool, But i cant seem to see the device in ADB. Fast boot however, can see it.
Update over ADB/SD in the stock recovery wouldn't lead me anywhere would they?
I do apologise if I give too much information; I try to be thorough in documenting my methods and include as much information as possible so we can maybe skip some of the "what does it do when you ..." and the "did you try this" questions.
So I have been reading through these forums for the past few hours... Earlier today a friend gave me her AT&T Galaxy S5 to try and fix. When I received it, it would boot straight into recovery. She was on version G900AUCS4DQD1. I can say for nearly 100% certain that this lady knows nothing about modding her devices, so I am absolutely confident that this problem doesn't stem from her attempting to root the 6.0.1 firmware she was on, install custom recovery, or anything anywhere close to that. She said she had taken it to an AT&T Store and they were unable to fix the device; although I'm sure all they did was do a factory reset through recovery and when that didn't work they just said "Well, it's broke, come buy a new device." Either way, the information in bootloader mode doesn't show anything outside of what it's supposed to ... Current Binary is Samsung Official, System Status is Official, Reactivation Lock is off, and most importantly the KNOX Warranty Void flag is showing 0x0.
As I said, when I got it, the phone would boot straight to recovery by only person the power button to turn it on; but download mode was accessible via the option in recovery and by holding Vol-Down + Home during boot. Attempting to boot into safe mode, holding Vol-Down during boot results in nothing different than if I don't hold Vol-Down... sometimes it boots all the way to system where it reboots on Optimizing Apps, and sometimes it doesn't even clear the colorful animated Samsung Boot logo. While in recovery, the device is not visible in Windows Explorer. If I open my command line and type "adb devices" the S5 doesn't how up. However, if I select "Apply update from ADB", THEN type adb devices, it shows up as <device serial #> sideload. Attempting to issue the command "adb shell" while visible to adb results in "error: closed" being returned. Now, because I've been using the OnePlus 3T I have become somewhat familiar with bootloader mode and the fastboot command, and I don't know if Samsung devices are SUPPOSED to respond to the command "fastboot devices" while in bootloader/download mode, but I can say for 100% certain this one doesn't.
Remembering everything I learned when I owned the S4 AND after doing research on what firmware versions I could safely flash if my device was on 6.0.1, the first thing I went searching for was Odin and the factory firmware. I used the thread "G900AUCS4DQD1 ** FULL ODIN UPDATE ** v6.0.1 by toutanje to find the firmwares to download. I have also used the method and files in the thread "[Unbrick] Fix All For Samsung S5 AT&T (SM-G900A) Lollipop 5.1.1 by Birkyjon. Whichever method I use, all the files load and flash without incident in Odin. Before I attempt to boot to system, I boot into recovery and wipe cache and do a factory reset. (I have attempted do boot both with and without a factory reset after flashing the firmware in Odin) After doing that, obviously I hit reboot now... the phone passes the initial Galaxy S5 Logo, it goes to the multicolored Samsung Logo, then the AT&T screen, and SOMETIMES it boots into system, where it sits at the "Optimizing Apps, x out of 210." It will count up to around 30-40 or so, then reboot. After that initial boot where it gets to Optimizing Apps, all boots after that are unpredictable... as in, maybe it will make it back to Optimizing Apps, maybe it won't even make it to the AT&T boot screen before it restarts itself. Once it does that, I can boot back to recovery, do another factory reset, and it will make it to Optimizing Apps again every time. About the only thing I haven't tried was to attempt to flash the firmware via the "Apply update from ADB" option, though I honest don't see the point after everything else which has failed.
One last thing I have seen in my research so far but am unable to test: could these issues be caused by a bad battery? Being that I have no idea how the battery life on this particular device has been, I have no reference as to whether it has been draining incredibly fast, acting normal, or even just flat out dropping massive amounts or so at once.. I seem to remember noticing when I placed it on charge this afternoon, the device only had around 6%, and while connected to only a 1A charging brick, the percentage had magically jumped from 6% to upwards of 35% in what seemed like 3-4 minutes. I can't confirm for certain how long it was charging as I was also wrangling my two toddlers at the time and could have possibly just lost track of how much time had actually gone by...
Any ideas as to the issue I am facing? Any help would be much appreciated! Thanks guys!
I have this exact game problem with my wife's s5. I never got any type of response, I hope you do. I'm still having this problem as well.