Database Develop

Is it possible to...

...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.

July OTA Update Bricked my Phone -- AT&T refusing to replace. Help!

Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!

LiquidArrogance said:
Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!
Click to expand...
Click to collapse
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.

muniz_ri said:
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.
Click to expand...
Click to collapse
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop

Is there physical damage on the phone, thus why att didn't do the warranty?
Sent from my HTC One_M8 using Tapatalk

LiquidArrogance said:
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop
Click to expand...
Click to collapse
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck

muniz_ri said:
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck
Click to expand...
Click to collapse
No idea what just happened. I've been messing around throwing the kernel you recommended at it as well as the stock partitions. Kept getting back to boot loop but at one point it stuck out, said it was upgrading, optimizing apps, and now it's running. So weird.
I'm way too scared to do the factory reset at this point, though.
Thank you again for your help, I really appreciate it!
Edit: Unplugged the USB cable and it immediately shut off and went back into boot loop. Wow.

this sounds like a hardware problem.. i sent my phone to Samsung and they actually repaired it, it was the pba board, i had the same problem.. i flashed everything it needed to recover from a bootloop. and sometimes it would become non responsive. go to best buy and see what they tell you.
Sent from my UNROOTED SAMSUNG-SM-G900A on OF2

Update:
Thanks to everyone for their replies. I was able to get the phone to boot thanks to everyone's help. Did this by flashing kernel then partitions which would allow the phone to boot.
I finally figured out that the phone would only boot if plugged directly into a power source. As soon as I disconnected the power cable, it would send it right back into the boot loop. I ran some battery "repair" and "calibration" tools but these did not fix the issue. Whenever I would run a battery drain tool, the stress on the battery would cause the phone to shut down.
All of this led me to believe it was an issue with the battery. I held my wife's S4 battery to the contacts on the S5, and it works just fine, even disconnected, and even with the stress test on the battery.
SO -- I'm going to buy a new battery and see if this fixes my problems. I think I just had the perfect storm of battery issues coupled with firmware problems.
I'm pretty sure I know what caused the battery to go haywire. I work in a max security prison and have to leave my phone in the car all day. Outside temperatures regularly hit 105F+ during the summer, so who knows how hot it's getting in the car. Obviously I always leave the phone turned off, but I suspect the high temperatures caused the damage.
Going to try to find a new battery today. Will keep everyone posted! Thank you again for all of the replies.

I had the same issue and would just like to thank you for the files! They helped me unbrick my phone! Much appreciated.

Stuck on AT&T logo and cannot enter recovery mode

This is my first post, but I've had my phone rooted for a few months now with no problems until today out of the blue. What I've done to root my phone in the first place was flash to 4.4.2 NE3, root it, then upgrade to 5.0.1 OC 7 DeOdexed while keeping the root according to the link below. And then I put Xposed framework on it.
https://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
And this has worked well for me for a few months since that was back at the end of December. Flash forward to today when my phone was being rather slow to respond to my actions so I decided to restart it. And upon restarting it, it's been stuck on the AT&T logo screen for a very long time. I can power it down with the power button, but think it actually just restarts it because then it boot ups again on its own. I cannot enter recovery mode with power+home+volume up, but I can get to the custom OS screen with power+volume down. My computer cannot see it as an adb device either. I've also tried removing the SIM card and the SD card and it's still gets stuck at the AT&T logo.
I've done nothing different with the OS or Xposed recently. The only new thing was about 2 hours prior to restarting it, I connected it to my computer to transfer some video files to the sd card. While I had it connecting to the computer and looking at the files on it through the phone's My Apps, it was sluggish to respond to my actions. But after disconnecting it, it was fine. I don't know if this is related, but I haven't done anything else different with it. Is there anyway to get my phone to boot up correctly? Or am I going to have to reflash it all over again? Thank you for any help.
Edit: I can enter recovery mode and I tried wiping the cache. It still gets stuck at the AT&T logo screen. I should also note that it no longer shows the Samsung "custom" boot screen anymore like it used to after rooting, now it just has the default Samsung boot screen, so it would certainly seem like my OS has been corrupted.

100% Bone Stock S5 Bootlooping

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.

Stuck at powered by Android screen.. cannot get into recovery mode.

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