Database Develop

[Q] Help! - Need to restore phone! No rainbow screen

First off, I've read/tried using software from thread: http://forum.xda-developers.com/showthread.php?t=442480
I found the phone in the subway. when i power it up it goes to the default boot menu.
I don't know anything about the phone. Could be UK, US, AUS, PVT, or DVT.
I can't get to the rainbow screen (fastboot) found when pressing while device is off (holding camera + pwr button (end)). So i can't flash DREAIMG.nbh. (RC 29) assuming the phone is american.
I do get the default restore menu though. I press alt+L to get the menu. After if i try to flash anything it says that it doesn't pass verification.
So I need to know what file(s) I can flash from the default boot menu that can fix the phone that will pass verification.
Also forgot to mention when i am in the default boot menu and press alt+L, in yellow at the bottom phone displays following error message: "E: Can't open /cache/recovery/command"
Thanks...

Sorta sounds like someone used an app that kills the phone if they lose it or they knew it was bricked and just left it there.
is there any water damage to this phone at all?
why not try posting an ad on craigslist and see if anyone lost it ~.~

All water dmg indicators do not show they were wet at any time. Also how would i make sure i would be returning it back to the correct user? it was found with no SIM, can't even check for addtl' info.
Also if there was ever an app that would brick the phone when someone looses it, thats the first about me hearing it.
Anyone with some actual technical/dev input?

So i found some information at http://android-dls.com/wiki/index.php?title=OTA_Updates#RC28
When I go to install the update, it says thats its opening the package, then verifying the update, finally it trys to install the update and about 70% through it aborts.
Is there any kind of RUU i can use to completely reinstall the software up? If so where could i find it?
Any thoughts?

[Q] I bricked my Galaxy Ace...what to do?

Hey guys!
Earlier today I rooted my another Android device so I wanted to try it with my Samsung Galaxy Ace S5830. I rooted it successfully, then I wanted to install a custom ROM...well, I wanted to upgrade it to Android 4.3 since I found a tutorial for it.
I downloaded two zip files, put them on the card, booted the phone into recovery mode and during installation of files, there was an error (Status 0), something like that. When I wanted to boot my phone, it could not boot up. It would just have that splash screen saying Samsung Ace S5830 and it would stay there forever.
I got back to the recovery mode and there is error saying "E:failed to mount /system (Invalid argument).
I figured out I messed it up, so I tried to flash it with Odin. However, after reading millions of guides, I failed to do it. I put my phone into download mode and it just says "Downloading..." on a black screen, there is no picture or anything like that, and I saw in the guides there should be one, so am I in the wrong mode?
Anyway, I "managed" to flash my phone. The process took ~10 seconds then rebooted my phone and I was waiting on a countdown (4 minutes or so), then it said my phone is done and I saw a blue button saying "PASS". However, my phone was showing only a backlight during that process, there wasn't anything like a download bar.
I restarted my phone, wiped cache and did a factory reset, but it's still unable to boot.
What should I do?
Thanks a lot!

AsPeHeat said:
Hey guys!
Earlier today I rooted my another Android device so I wanted to try it with my Samsung Galaxy Ace S5830. I rooted it successfully, then I wanted to install a custom ROM...well, I wanted to upgrade it to Android 4.3 since I found a tutorial for it.
I downloaded two zip files, put them on the card, booted the phone into recovery mode and during installation of files, there was an error (Status 0), something like that. When I wanted to boot my phone, it could not boot up. It would just have that splash screen saying Samsung Ace S5830 and it would stay there forever.
I got back to the recovery mode and there is error saying "E:failed to mount /system (Invalid argument).
I figured out I messed it up, so I tried to flash it with Odin. However, after reading millions of guides, I failed to do it. I put my phone into download mode and it just says "Downloading..." on a black screen, there is no picture or anything like that, and I saw in the guides there should be one, so am I in the wrong mode?
Anyway, I "managed" to flash my phone. The process took ~10 seconds then rebooted my phone and I was waiting on a countdown (4 minutes or so), then it said my phone is done and I saw a blue button saying "PASS". However, my phone was showing only a backlight during that process, there wasn't anything like a download bar.
I restarted my phone, wiped cache and did a factory reset, but it's still unable to boot.
What should I do?
Thanks a lot!
Click to expand...
Click to collapse
Did you read rules?
Did you search for help?
Do you know that it's not the correct section to post your questions?
PLEASE USE Q&A ThREAD!! We need to keep clean general section!
Which model have you got?

Phone bricked - Stock, not rooted

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.

please help a person who doesn't know much about ROMs, kernels, root and so on.

i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.

also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying:

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.