Please help.
What I wanted
I was on sling v2.1 rom (mod of official LG kitkat rom) and it brought its on LGViet recovery. So I just downloaded a CM11 rom, and flashed it through recovery.
What I got
Every boot, I started getting
Code:
Secure Booting Error!
Cause : boot certification verify
And phone kept on rebooting into same LGViet recovery.
luckily, I had sling v2.1 flashable zip file so I flashed that back. I booted into android but the error kept there on boot up LG logo screen. I thought that this recovery is some borked screwed up version of clockwork mod with custom signatures etc, I installed PhilZ recovery.
Still couldnt get rid of the error and now phone always stays at LG logo screen. I can't put phone to download mode because my phone's Volume Up button is @#$%ed up and I am not sure if its pressed even though I press both buttons with all the might and force I have in the world to put it into download mode to flash official kdz and get rid of this crap.
Can anybody help me with this soft / hard brick I have got?
I know this category is made to be ignored by majority of the people. I'll really appreciate it if somebody helps me get outa this mess. Thank you
For me was very similar, it was third month of using LGE975, and i sent my G to warranty i said "i tried to do factory reset and my phone was bricked on this screen", they accepted phone and changed motherboard I tried to do hard reset, go to bootloader but still get this error, but i didin't tried go to donwload mode. I really don't know how to repair this error. I guess if you can't go to download mode, you shoud sent phone to warranty.
Sorry if my english grammar was poor
I think all you need to do is keep trying to go on download mode. If you cant, go to any repair shops to fix that buttons
dark_prince said:
Please help.
Click to expand...
Click to collapse
Shutdown the phone completely (hold power for 15-20s). Hold both vol buttons then plug the usb cable to a power source (could be your computer or your charger). DO NOT PRESS ANYTHING ELSE.
I know it doesn't sound very helpful but it's very hard to get the combination right. Took me 20 tries every time.
I got it in like 50th try. Almost all the finger tips of my both hands hurt so bad.
Reverted to offical GB, FreeGee'd, CWM'd and installed MOKEE right away...
The horrible button behavior is a pain in the ***!
My kind thanks to all of ya for keeping me motivated to press them damn buttons
dark_prince said:
I got it in like 50th try. Almost all the finger tips of my both hands hurt so bad.
Reverted to offical GB, FreeGee'd, CWM'd and installed MOKEE right away...
The horrible button behavior is a pain in the ***!
My kind thanks to all of ya for keeping me motivated to press them damn buttons
Click to expand...
Click to collapse
Quick and easy solution for secure booting error is teenybin. It unbricks your device in like 20 seconds, no need to flash kdz.
Sent from my LG-E975 using XDA Premium 4 mobile app
Related
So, after trying out a few firmwares (JM2, JG8, JM5) and kernels (Samset&OC) I can't no longer boot to recovery with Vol UP + Home + power. I can't really say when this problem first occurred, but maybe with JG8 flash. The strange thing is that I can get to recovery with adb reboot recovery and through android console with reboot recovery (when rooted ofc). Also download mode works great.
Things I have tried:
-flash again to JM2 and JM5 with re-partition checked (512 PIT)
-cleared cache+data through recovery
-factory reset through phone code (this also cleared the internal SD)
-took out the battery multiple times
-booted phone without sim
-flashed phone without sim
-changed CSC with phone code
-restore a nandroid backup of JM2. Recovery worked with this one when I took the backup
-there's no external flash card inserted
Soooo..does anyone have any idea about this kind of problem?
i had a similar problem after trying few ROMs. In my case, when i pres the key combi i get the boot logo and then few seconds later the screen goes black and then i see the boot logo again, and this goes forever. and then i tried pressing the same key combination simultaneously and once i see the boot logo i let go the power button and keep the vol up and home pressed, and then only it went into the recovery mode.
hope it works the same for you
Cheers
Agreed, 99.9% chance you are doing it wrong.
Sent from my GT-I9000 using XDA App
mmthabet: I had the exact same experience. Letting go of the power button when the logo appears lets me enter recovery.
or you may need to take out the battery first for a few seconds... after that, you can reinsert it back and try recovery mode...
at least this work for me...
Thanks for replies but none of the solutions work. The recovery mode button combination DID work for a few weeks, but then just stopped working.
I know that I'm doing it right. I have always pressed vol up and home down until the phone loaded recovery and only briefly pressed power button just at the start. I have also tried to remove battery multiple times and once waited 30 mins before re-inserting it.
Trust me, I'm not doing it wrong :s And recovery is working great through adb reboot recovery and shell.
Darkstriker said:
Agreed, 99.9% chance you are doing it wrong.
Click to expand...
Click to collapse
More so a timing issue. Buttons not pressed at the same time.
I get it all the time for all combo's.
Just keep trying.
You might already have this however just in case you dont, check out Quick Boot.
http://www.appbrain.com/app/com.siriusapplications.quickboot
With this app you can boot into recovery mode. Have to be rooted though.
odyssey61 said:
You might already have this however just in case you dont, check out Quick Boot.
http://www.appbrain.com/app/com.siriusapplications.quickboot
With this app you can boot into recovery mode. Have to be rooted though.
Click to expand...
Click to collapse
this wont work, if you bricked the phone in a bad flash situation.
in times when this app works, you can easily do adb reboot recover
so this app still doesn't address the real issue of how to get the 3 buttons press hardware recovery mode
Laum said:
I know that I'm doing it right. I have always pressed vol up and home down until the phone loaded recovery and only briefly pressed power button just at the start.
Click to expand...
Click to collapse
I release the buttons right when the first Samsung texts comes on the screen. It will take it to Recovery mode. I also had a "boot loop" few times, if I keep pressing the buttons all the time.
Have you tried release your fingers right in the first texts? I really don`t know what is exactly the right way to press the buttons, but this always have took it to Recovery.
Looks like my latest full wipe with *2767*3855# cured it. Flashed JM5-->full wipe-->samset1.9b-->samset kernel and now it works. It must've got stuck somehow in my previous JM5 installation.
I cant get into the download- or recovery-mode by using these keys... so i am not able to flash a new firmware! can anybody help me please? is there a chance to get into the download mode by using an adb-command?
please help i just cant get into the download mode!
Igor02 said:
I cant get into the download- or recovery-mode by using these keys... so i am not able to flash a new firmware! can anybody help me please? is there a chance to get into the download mode by using an adb-command?
please help i just cant get into the download mode!
Click to expand...
Click to collapse
yes
adb reboot download
but it is dangerous, as you can not recover from a bricked state, if your flash is not compatible or if something went wrong with odin, etc.
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
arch3rm said:
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
Click to expand...
Click to collapse
AHHHHHHHHH OMG, WHY DIDN'T YOU SAY THIS SOONER, like 5 hours ago...
i could have tried that, and not had to send my phone back for "repair"
well i'm sure i'll see that screen again in the future, i'll try that next time
AllGamer said:
AHHHHHHHHH OMG, WHY DIDN'T YOU SAY THIS SOONER, like 5 hours ago...
i could have tried that, and not had to send my phone back for "repair"
well i'm sure i'll see that screen again in the future, i'll try that next time
Click to expand...
Click to collapse
Well I did just get the phone 2 days ago,
Had that problem the same day, discovered the fix two hrs of horror later
Same Problem here i contact samsung here in mexico and a technical aggent tell me if we make a repair our phones we need a jtag and this is so bad alllready contact many people jtag manufacturers in china and honkong trow alibaba.com and no luck don't have other source i try is contact to nspro and z3x and no support for this repairand only hope still have is a reply from the people in the forum SMTi Jtag Repair Tool
Its hard to me go to UK Samsung Service Center i'm in mexico like i said
and i'm waith for a solve this i;m so very sad
http://www.youtube.com/watch?v=g8AIvalzBvY
Darkstriker said:
Agreed, 99.9% chance you are doing it wrong.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I usually release the power button on the boot screen first and then the other two buttons
arch3rm said:
I you're bricked and can't get into Download or recovery mode, leave the device to boot, it will just show a black screen for a while then will turn its self off, once this happens you should be able to use the key combo.
Click to expand...
Click to collapse
Any idea how long you waited? Been waiting 5 minutes, hasn't shut off. Mine's a Bell though so I'm guessing I won't have any luck.
The way i do it (no chance of doing it wrong and timing):
hold down+home and then also press the power button for a little more then 10 seconds (so all 3 buttons for 10 seconds). The phone will reset into download mode, never fails in whatever mode the phone originaly was..
Alright, so I have an i-747 (AT&T GS3) running AOKP Jellybean (8.28 build) with the KT747 kernel. I just tried to install Chainfire 3D using the automated installer, and when the phone rebooted, it stuck at the Samsung Galaxy S3 logo until I pulled battery. So I tried rebooting into CWM - same problem. And again with download mode. Even after pulling the battery for a good 5 minutes, nothing works. Am I bricked, or is there some fix for this?
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
g2tegg said:
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I made a nandroid just this afternoon, but I can't actually boot into CWM at all. As in, I turn on the phone (power+home+volume up), it gets to the Galaxy S3 logo and just hangs there. If I could get into CWM (or download mode) this would be about a 10 minute fix, but I'm kind of out of luck here.
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
HELP I have the same issue
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
Hi, sorry to say but sounds like its bricked
Thanks
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
I doubt it's bricked if he got it into download mode. I'm sure he's flashed it and even got his wallpaper back up by now. Please let us know of you've managed to solve this or not MrPhantom.
Sent from my SGS3 i747m (Bell) on CM10 using TapaTalk2
delete post please
Curious?
I know its technically "Solved" but does anyone have any idea why this is happening? I have a Verizon GS3 and it's happening to me. I try to boot and it vibrates once and doesn't turn on. Recovery does the same thing. But going into Download mode works. Odin back to stock as we speak but I'm just curious what went wrong. I just did a clean install of a rom, set it all up (working at the time), set it down for the night and woke up to it like this.
rrrs444230 said:
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
Click to expand...
Click to collapse
Same thing happned to me but your not bricked. You can get into bolth download and boot mode easy
Here is how you do it.
RECOVERY MODE
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
[edit]Download Mode
Save that somewhere. Make sure do it right. I got stuck also and thought I couldn't get into recovery but I had to do it right (it hit recovery mode first try) I have learned that most people do it slightly wrong. Make sure follow directions
Download mode
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
To get out of Download Mode, simply press and hold the power button until the phone restarts
if helps hit thanks.
Just save that to a text file somewhere
I have also soft bricked when I deleted my rom once on accident. I dunno how I did it but I would get stuck at the TWRP screen. It wouldn't go to download or anything however when I plugged it into odin it saw it .... I even had a soft brick when screen went black from a bad boot animation and same thing.. and I had one bad soft brick where it took about 100 trys to get it into download mode (black screen) but odin detected it. I spent like 4 hours working on it.
I think
1. People don't follow directions correct (they do it a little wrong) which is enough if your phones messed up for it not to work.
when your phones normal it can get into recovery or download easy but when its sick you got to do it perfect.
2. I think something wrong with the phones (my s2 never had any issues in 2 years of owning it) S3 has tons of issues from usb, to bluetooth, to these soft bricks I have had)
3. Roms play a big part
4. I also think the way storage works in this new phone causes lots issues I dunno why just what I think
anyway Like I said now when I have a isssue I open text and read it and make sure I do it right and 95 percent of the time it was my fault I wasn't doing it right. K just my thoughts
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
phatchef1 said:
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
Click to expand...
Click to collapse
That's most likely cause you're not in the right section..: http://forum.xda-developers.com/forumdisplay.php?f=1708
Hi, so I believe that I have hardbricked my phone. I just want to make sure that it's not a soft brick that I can fix before I get it repaired/replaced.
What happened was I have a stock rom which was pre-rooted flashed, and I've had that for a while with no issues. It was a stock root from the "No Tripping Flash Counter" thread. I just wanted to create a backup, through Clockwork Recovery, and it was about halfway through, but taking a really long time so I set the phone down (plugged in) and when I came back, the screen was dead. All that happens when I try to turn it on, put it into recovery mode, plug it into my computer, or anything else is just give a little vibration.
I've checked through several fixes for softbricked phones, but since I can't get to recovery mode, I haven't had any luck yet. Is this a hardbrick? Is it possible to fix it myself or does this need to be professionally repaired? And finally, is it possible to have it replaced by ATT or Samsung if I can't fix it myself?
Can you get it into Download mode (Power + Home + Volume Down)
??
Sianspheric said:
Can you get it into Download mode (Power + Home + Volume Down)
??
Click to expand...
Click to collapse
Nope, can't get anything out of it but a small vibration every time. Download mode combo doesn't do anything.
Did you try battery pull before download mode
Sent from my SGH-I747M using xda app-developers app
Maybe its a bad battery?
Edit: after reading what I said over again I now realized that could be a stupid suggestion. Sorry.
Not exactly sure what was wrong, but I managed to fix it.
Used a jig to force it into download mode, and reloaded a rooted stock. Everything's perfectly fine now. Thanks for the suggestions from everyone!
Ok so I installed Liquid Smooths new beta rom, it was running fine but didn't have GAPPS, so i went and flashed GAPPS and now my phone is stuck......
When it loads the rom it keeps saying "unfortunetly setup wizard has stopped working" i keep clicking ok but the same message keeps popping up over and over again.....
I have tried the vol down, powre and home button to get into recovery but all it does is turn off the phone
Pulled battery and tried holding VOL DOWN+power to get intro recover but all it does is vibrate every few seconds.....
I am stuck and have been trying to get my phone operational for three hours, anyone care to help me? I have tried ADB but it cant find my device and i can't get into the settings of my phone to turn on debugging mode
raul602 said:
Ok so I installed Liquid Smooths new beta rom, it was running fine but didn't have GAPPS, so i went and flashed GAPPS and now my phone is stuck......
When it loads the rom it keeps saying "unfortunetly setup wizard has stopped working" i keep clicking ok but the same message keeps popping up over and over again.....
I have tried the vol down, powre and home button to get into recovery but all it does is turn off the phone
Pulled battery and tried holding VOL DOWN+power to get intro recover but all it does is vibrate every few seconds.....
I am stuck and have been trying to get my phone operational for three hours, anyone care to help me? I have tried ADB but it cant find my device and i can't get into the settings of my phone to turn on debugging mode
Click to expand...
Click to collapse
First, did you flash the correct gapps? You have to make sure what you are flashing is correct for the ROM before you flash it.
Second, you need to turn the phone off, then press power + volume up + home until it vibrates and then release to access recovery. To access download mode, its the same thing only with volume down.
Third, a bit of advice. I don't mean to belittle you, but it doesn't sound like you did your homework before you started flashing things to your phone. You need to read around a bit and get a good grasp of the basics, or you will end up in trouble, whether it be as simple as a bootloop or as bad as a hard brick. I hope you get it fixed quickly. Good luck!
Thetenthdr said:
First, did you flash the correct gapps? You have to make sure what you are flashing is correct for the ROM before you flash it.
Second, you need to turn the phone off, then press power + volume up + home until it vibrates and then release to access recovery. To access download mode, its the same thing only with volume down.
Third, a bit of advice. I don't mean to belittle you, but it doesn't sound like you did your homework before you started flashing things to your phone. You need to read around a bit and get a good grasp of the basics, or you will end up in trouble, whether it be as simple as a bootloop or as bad as a hard brick. I hope you get it fixed quickly. Good luck!
Click to expand...
Click to collapse
Thanks, I finally got into recovery mode by holding the three buttons then letting go right after it vibrated and pressing again.... weird..
For the most part, i read every single post in a thread before i flash a rom, I have been flashing roms for years now ....... I guess i got comfortable and flashed this "beta" rom(stupidly) not thinking anything of it..... and no i didn't even check if it was the right gapp, i knew it was for 4.2.1 and i figured the beta was the same.
I am not back to a working rom, but now my phone is only able to get Edge speed, is that a modem issue?
That's an imei issue. Look around there is a thread about it. Happened to me but that got it all fixed. Under phone settings about phone if your imei is 0 you need to inject it back. Hope this helps
Sent from my SGH-T999 using xda app-developers app
tylerholbrook said:
That's an imei issue. Look around there is a thread about it. Happened to me but that got it all fixed. Under phone settings about phone if your imei is 0 you need to inject it back. Hope this helps
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I can't thank you enough for pointing me in the right direction, took me HOURS but finally got it working. Thanks!
Glad you got it back up and running.
No problem. Lol yeah I had to buy a PC because I couldn't fix it with a Mac
Sent from my SGH-T999 using xda app-developers app
tylerholbrook said:
No problem. Lol yeah I had to buy a PC because I couldn't fix it with a Mac
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ouch. But on a positive note, you now have a PC
Hey guys
I've problem with my Note so... Hope you can help me :/
I recently installed last CM10.2 nightly from get.cm. So I restored all my apps and after that I applied the nav bar trough Pimp My ROM...
Everything was going good up to here. When I tried to boot into Recovery Mode to wipe cache (Because the tablet won't boot) a message popped up saying that I was in "SDCARD MODE" (The hell is that!) followed by something like coping to EMCC... Like if it was coping something from the SD to EMCC
After that the tablet got (Bricked?)... No vibration, no Samsung logo, no nothing
Any suggestions? Did I ****ed it up?
Any help would be appreciated guys
Cheers
rena14 said:
Hey guys
I've problem with my Note so... Hope you can help me :/
I recently installed last CM10.2 nightly from get.cm. So I restored all my apps and after that I applied the nav bar trough Pimp My ROM...
Everything was going good up to here. When I tried to boot into Recovery Mode to wipe cache (Because the tablet won't boot) a message popped up saying that I was in "SDCARD MODE" (The hell is that!) followed by something like coping to EMCC... Like if it was coping something from the SD to EMCC
After that the tablet got (Bricked?)... No vibration, no Samsung logo, no nothing
Any suggestions? Did I ****ed it up?
Any help would be appreciated guys
Cheers
Click to expand...
Click to collapse
Can you enter download mode? If you can, flash a stock fw with odin. (Home + Volume Down + Power)
Go to sammobile.com for a stock FW.
Always better to start over from stock when things goes wrong like that IMO.
Bl00DGuY said:
Can you enter download mode? If you can, flash a stock fw with odin. (Home + Volume Down + Power)
Go to sammobile.com for a stock FW.
Always better to start over from stock when things goes wrong like that IMO.
Click to expand...
Click to collapse
I can't do anything dawg.... The tablet is like dead
Wether I try to enter download mode or recovery mode, nothing happens
Btw, y' know what's EMCC?
So if you hold the power button and volume down at the same time for between 5 to 10 seconds, you get no Samsung logo at all?
If you get absolutely no logo (and the battery isn't dead) then it sounds like you totally bricked your bootloader somehow.
If that's the case, I'd send it in for service.