Database Develop

[Q] cannot start galaxy s after update.zip

Hello
I am in a great panic mode.
I applied this lagfix : forum.xda-developers.com/showpost.php?p=7587405&postcount=417 and since I did it I cannot use my phone.
I am not able to start my phone. It shows me Galaxy S logo, and after that I hear the start up music but nothing on the screen (no animation). Pressing hardkeys does not do anything either.
Above all I cannot even enter my recovery mode. When I press volumedown+poweron button, the screen keeps showing me Galaxy S logo and it does not go any further.
Please help me if you know how to getaround.

Were you rooted when yoou applied update.zip?
Anyway,did you try to shutdown the phone removing battery,and then try entering recovery?

the fix did not mention I had to root my phone, it said it would self install.
Yes I did shut down after removing the battery, and then I am trying to get into recovery using volumedown+poweron button but I am not able to get into it. All I see is Galaxy logo and hear start up music after that with nothing on screen.

OK, I am able to get into recovery mode.. I was trying wrong combinations
Now what should I select I get these options:
1. reboot system now
2. apply sdcard:update.zip (will never do this again)
3. wipe data/factory reset (should I do this)
4. wipe cache partition

yes.. you should do 3.) wipe data. If that doesnt solve your problem, you need to flash firmware agian

somusingh said:
Hello
I am in a great panic mode.
I applied this lagfix : forum.xda-developers.com/showpost.php?p=7587405&postcount=417 and since I did it I cannot use my phone.
I am not able to start my phone. It shows me Galaxy S logo, and after that I hear the start up music but nothing on the screen (no animation). Pressing hardkeys does not do anything either.
Above all I cannot even enter my recovery mode. When I press volumedown+poweron button, the screen keeps showing me Galaxy S logo and it does not go any further.
Please help me if you know how to getaround.
Click to expand...
Click to collapse
Why did you choose to install something not on main page, something obviosuly not very tested and something 2 month old (god knows there are close to ten newer or more tested fixes).
If you can access download mode, than reflash. If not... Well, try the exotic methods (dont know them, as I have working 3 butons)

Hey, for a second I thought it did noy fix my problem as I did not get my animation screen and ony heard music.. But then suddenly it starts up
I think I lost my animation on start up though
I still see that MCR Scripts icon on app loader screen, How could I know if its enabled or disabled?
Thanks a lot guys.. XDA rocks .

dupel said:
Why did you choose to install something not on main page, something obviosuly not very tested and something 2 month old (god knows there are close to ten newer or more tested fixes).
If you can access download mode, than reflash. If not... Well, try the exotic methods (dont know them, as I have working 3 butons)
Click to expand...
Click to collapse
I regret doing something like that.. But it was really confusing as there are so many topics on the forum and I was really tempted to solve the lag issue I started facing recently (I installed too many apps).

hey i have the same problem.. my phone goes up into the Samsung logo and hangs there forever, occasionally blinking and making a weird vibration. i've tried factory reset but that doesn't help..
How do i flash firmware again?

glbc said:
hey i have the same problem.. my phone goes up into the Samsung logo and hangs there forever, occasionally blinking and making a weird vibration. i've tried factory reset but that doesn't help..
How do i flash firmware again?
Click to expand...
Click to collapse
Read the FAQs
Insanity cm 014/glitch

reflash the rom by odin will solve the problem
make sure your kenel is speedmod if u updated the rom from your sdcad，
enter into recovery ，do the wipe then updated ，disable all lagix ，all this work done u could updated the rom

[q] need help! Black screen on my verizon galaxy tab 7

I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......

Put it in d/l mode and flash one of the stock roms with Heimdall.
D

i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help

Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.

how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode

done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......

chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753

Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.

Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.

Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.

Help possibly bricked phone

I don't know what it is with my luck...
But I really need help.
So I flashed a custom ROM, the Hybrid Revolt Rom to be exact, and accidently disabled the recovery.
So I tried to flash TWRP via flashtool and now all I have is a blank screen when I boot up.
PLEASE HELP

I was able to solve my own problem, yet again. I apologize for panicking...
But I am willing to explain how I fixed it.
So the problem was that I had installed the Revolt Rom only to realize I wanted a different one. Unfortunately, I disabled recovery mode. So I had no form of recovery to flash it. From here, I tried to flash TWRP using flashtool, which evidently did not work and wound up leaving me with a phone that only had one display option: Blank Screen. lol And I panicked.
However, I calmed down and searched XDA. There was another form where a guy had killed his xperia almost as bad as I did. And if his Xperia Z still isn't working, then maybe this will help. (He flashed a GS3 ROM on his XZ)
I used the flashtool to flash DoomKernel, first. I had to turn of the device, forcefully, but holding the power button and volume up until it vibrated once, then three times, consecutively. From there, I got it into fastboot mode by holding down the volume up and reconnecting the device to the computer.
I was able to successfully flash the kernel, and then I powered off the device again and disconnected it from my PC. Finally, I held the volume down button down, reconnected it, getting into flashmode. From there I flashed TWRP, which somehow gave me CWM... But I'm not complaining...
Now I just did a clean wipe, installed the ROM I wanted, and am about to reboot.

Updated to CM 12.1, no recovery mode, everything else seems fine

Today I've updated from CM 11 (KitKit 4.4.4) to CM 12.1 (Lollipop 5.1.1). I made a backup, a factory reset and then flashed the latest nightly and Google apps. Everything was fine so I continued installing apps, restoring data etc. When everything seemed to be finished and the phone was as I want it to be, I wanted to make a new backup.
But now I can't enter recovery mode. When I boot the phone and press the volume button, the LED turns yellow as it's supposed to, but the screen stays black and nothing more happens. If I press the power button the phone reboots. So everything seems fine, the phone is working and I've got root access, but I can't enter recovery mode. I've tried to use ADB and fastboot but I can't connect to my phone so I can't flash a new recovery image. I can boot into fastboot mode with the LED turned blue but ADB stays on <waiting for device>. I've tried to update drivers etc and also tried another computer but with the same result so it seems there's something wrong with the phone.
In developer settings there's an option for CyanogenMod to update the recovery when flashing a new nightly - but I don't know if I can flash a new nightly when I can't enter recovery mode.
Any advices?

Update: With the CM Updater I downloaded todays nightly and applied it. The phone rebooted, apparently into recovery (yellow LED but still black screen). I left it in a few minutes, then it automatically rebooted and when it was ready to use, the nightly was updated.
So maybe there is some kind of recovery working on the phone - but I still can't access it...

Try this
http://forum.xda-developers.com/showpost.php?p=62296602&postcount=1037

Thank you, but as mentioned in my first post I can't get a connection to my phone with fastboot, so I can't flash a recovery image through ADB. I've also tried different apps to flash a new recovery like TWRP Manager, Rashr and Flashify but even if most of them reboot the phone into recovery mode, nothing more happens.
Is it safe to flash and older nightly e.g. the one from 8th August when I'm now running with a newer version?

Even if your answer in the first way didn't seem to help me, it guided me in the right way, and now finally it seems to be working
First I tried another computer. I thought fastboot really should be working and it did on the other computer, so the next thing is to fix a driver issue on my own - but that's another story... With fastboot working I flashed a TRWP recovery. The only difference now was that when booting in recovery mode the Sony text didn't disappear, but still a black screen and no recovery...
Then I followed your link, downloaded an older nightly and flashed boot.img, and now finally it seems that everything is fine.
So thank you :good:

Did you not use flashtool?
I' m back to stock..
Maybe later CM again
Sent from my C6903 using Xda portal

No I downloaded drivers from Sony and then flashed with ADB.

bootloop (starting, charging mode and also, with pc) z3c how to solve?

Hi guys, first of all sorry for my bad english
anyway, when I tryed to restart my phone, it was going to infinite bootloop... so, I tryed to lauch twrp and swipe all data also reinstalling the rom with adb/pc.. but in this moment happened the inaspected.. it go, to bootloop even if it was off, (changer screenshot, bootloop)
How Can I lauch adb, if my pc doesnt finds my z3c , because it goes to bootloop even if is off?

Xalein said:
Hi guys, first of all sorry for my bad english
anyway, when I tryed to restart my phone, it was going to infinite bootloop... so, I tryed to lauch twrp and swipe all data also reinstalling the rom with adb/pc.. but in this moment happened the inaspected.. it go, to bootloop even if it was off, (changer screenshot, bootloop)
How Can I lauch adb, if my pc doesnt finds my z3c , because it goes to bootloop even if is off?
Click to expand...
Click to collapse
So it won't stay off, even if you press power and volume up together for a few seconds? Which rom were you using, what did you do before it bootlooped, bootloader unlocked, etc...?

levone1 said:
So it won't stay off, even if you press power and volume up together for a few seconds? Which rom were you using, what did you do before it bootlooped, bootloader unlocked, etc...?
Click to expand...
Click to collapse
even it wont stay off, always bootloop;
If I remember well, first I unlock the phone with the code from sony; after launch the twrp with adp on pc (for a strange motive it (the phone) doesnt load the twrp without pc) , clean cache and co, like 2/3 times, after installing the new rom
it seems to me the omni rom 7.1.2

Xalein said:
even it wont stay off, always bootloop;
If I remember well, first I unlock the phone with the code from sony; after launch the twrp with adp on pc (for a strange motive it (the phone) doesnt load the twrp without pc) , clean cache and co, like 2/3 times, after installing the new rom
it seems to me the omni rom 7.1.2
Click to expand...
Click to collapse
Sorry to repeat, but just to be clear - when you press and hold power and volume up, what happens? Are you saying it turns off, and then automatically turns back on, and bootloops?

levone1 said:
Sorry to repeat, but just to be clear - when you press and hold power and volume up, what happens? Are you saying it turns off, and then automatically turns back on, and bootloops?
Click to expand...
Click to collapse
strangely this time go, it go on twrp..
but since I have encrypted, twrp request me the pass.. but, inserting the right pass, it always failed.. there is a way, to bipass this process (even with formatting the phone) to acess to twrp?

Xalein said:
strangely this time go, it go on twrp..
but since I have encrypted, twrp request me the pass.. but, inserting the right pass, it always failed.. there is a way, to bipass this process (even with formatting the phone) to acess to twrp?
Click to expand...
Click to collapse
Try fastboot flash, (different kernel or different recovery...), or flash stock rom with FT.

levone1 said:
Try fastboot flash, (different kernel or different recovery...), or flash stock rom with FT.
Click to expand...
Click to collapse
I solved with format data.. thanks
I have to re-installed the rom.. but I just to have wait to understand if it is still a bootloop or the classic installation phase..

Xalein said:
I solved with format data.. thanks
I have to re-installed the rom.. but I just to have wait to understand if it is still a bootloop or the classic installation phase..
Click to expand...
Click to collapse
10+ minutes is not unusual for first boot for stock rom.

levone1 said:
10+ minutes is not unusual for first boot for stock rom.
Click to expand...
Click to collapse
solved
but futhermore, another problem (hardware problem, I don't want to open another post):
today I open my cell phone because the screen had stuck, discovering that the connector had disconnected.. ok solved.. but the cellphone seems electrically charged, I mean more than 5 (I think) time I got the shock
any solution?/possible causes? (isnt the first time that I open the phone)