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
Related
I had rooted my phone a week ago and running the standard rom. Everything was fine but I wanted to try a ROM. Last night I tried CM7 and it installed but I forgot to get the gapps. I restored my backup and it was back to the way it was. Then I again used Rom Manager and this time chose to download CM7 & gapps. It worked, then I went onto the market and downloaded Titaninum backup because I couldn't find it. I set it up and restored all apps with data. BTW I had 200+ to go thru so if this isn't bricked I'm purchasing the PRO version. After I went thru all the apps, I rebooted and the screen is stuck at the cyanogen mod 7 screen with the arrow going around. It was like that for over an hour so I took out the battery and tried it again. Same thing, so I decided I'd go into hboot and restore my old backup. I took out the battery again and held down the power and vol down but nothing except a vibrate happened. I can still turn it on to the cyanogen screen but can't seen to hboot. What do I do???
Update: I pulled the battery and tried holding down the volume up and the power button but nothing happens except it vibrates. I can still hit the power and get to the cyanogen screen but it just spins. If I plug in the power the small power light comes on but doesn't stay on when I'm trying to get to hboot. Please tell me it's not bricked!!!
not sure if its bricked, but from what i do know, you never, ever restore data when you change roms. there has to be a way to get into hboot or recovery, im just not the guy who knows, but someone will tell you. if it goes to the cyanogen mod, which is a great rom, then your not bricked
BUMP,
Please someone tell me there is hope for my Droid Incredible? I was sure I followed the steps, My wife will kill me if this is bricked....
U might have to return completely back to stock by using ruu.
Dinc
Try " the ultimate get back to stock" thread, remember, dont restore data
Sent from my Incredible using XDA App
You're doing it wrong. Volume down + pwr is hboot.
Thank you for the help
I guess I was getting to hboot wrong. I was holding down the volume down and the power button and keeping them down. m6droid told me to hold the volumn down button then press and hold the power button for about 2 second and let go of the power button while continuing to hold down the volume down button.
It loaded hboot and I went to recovery. Man was that scary.
I was so nervous when I rooted my phone so I made sure I read every step. I'm going to have to read a lot more about flashing ROMs before I try that again.
Thanks for taking the time to reply
djgdroid said:
Thank you for the help
I guess I was getting to hboot wrong. I was holding down the volume down and the power button and keeping them down. m6droid told me to hold the volumn down button then press and hold the power button for about 2 second and let go of the power button while continuing to hold down the volume down button.
It loaded hboot and I went to recovery. Man was that scary.
I was so nervous when I rooted my phone so I made sure I read every step. I'm going to have to read a lot more about flashing ROMs before I try that again.
Thanks for taking the time to reply
Click to expand...
Click to collapse
You did everything fine, except for restoring data :/. That, and the getting into hboot technique lol. I'm glad its up and running now.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
Why do I feel a need for a special degree to root my dinc and add new rom's
Sniperdog said:
Why do I feel a need for a special degree to root my dinc and add new rom's
Click to expand...
Click to collapse
Cuz you're getting freaked out for no reason. It's super easy and even when you mess up you can fix it, it just takes research. I thought I bricked my phone a couple times already and I always get it back with effort and research. Fear is the mindkiller.
Sniperdog said:
Why do I feel a need for a special degree to root my dinc and add new rom's
Click to expand...
Click to collapse
Its easy; things start to make sense after a while.
phaze one said:
Cuz you're getting freaked out for no reason. It's super easy and even when you mess up you can fix it, it just takes research. I thought I bricked my phone a couple times already and I always get it back with effort and research. Fear is the mindkiller.
Click to expand...
Click to collapse
Fear is the mindkiller. Good one.
Sent from my DINC using XDA Premium
wildstang83 said:
Fear is the mindkiller. Good one.
Sent from my DINC using XDA Premium
Click to expand...
Click to collapse
Dune ftw.
sent by carrier pigeon
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
Hey guys, I've been searching all over for an answer to my problem, so I have looked...
Anyways...I was messing around with my phone (Verizon Galaxy Nexus) and decided to give MIUI a go, so I downloaded, backed up my current ROM and factory/cache/dalvik cache wiped my phone prior to install.
When It booted up, it stayed on the Google screen for a WHILE, so I just left it there thinking it would take a while as these things usually do.
Well, it won't, it sat on the google screen for over a half an hour. At this point I pulled the battery and tried to get into Recovery for a restore/sbf (Powere+Volume Down) and it won't let me navigate anywhere in the menu.
I'm stuck at Start with a notification that says "Downloading...Do not turn of target !!" The only thing I can do is press the power button which of course sends me back to the google logo and I'm at square one.
I've tried the toolkit on my desktop, but that does not work either (I've already set it up, as I used it to root in first place.) Does anyone have any ideas?
Any help would be greatly appreciated, I can normally figure these things out, but im really stuck here. Sorry if this shouldn't be here, Q/A just seemed like the right place
Thanks in advance
Dry.doc said:
Hey guys, I've been searching all over for an answer to my problem, so I have looked...
Anyways...I was messing around with my phone (Verizon Galaxy Nexus) and decided to give MIUI a go, so I downloaded, backed up my current ROM and factory/cache/dalvik cache wiped my phone prior to install.
When It booted up, it stayed on the Google screen for a WHILE, so I just left it there thinking it would take a while as these things usually do.
Well, it won't, it sat on the google screen for over a half an hour. At this point I pulled the battery and tried to get into Recovery for a restore/sbf (Powere+Volume Down) and it won't let me navigate anywhere in the menu.
I'm stuck at Start with a notification that says "Downloading...Do not turn of target !!" The only thing I can do is press the power button which of course sends me back to the google logo and I'm at square one.
I've tried the toolkit on my desktop, but that does not work either (I've already set it up, as I used it to root in first place.) Does anyone have any ideas?
Any help would be greatly appreciated, I can normally figure these things out, but im really stuck here. Sorry if this shouldn't be here, Q/A just seemed like the right place
Thanks in advance
Click to expand...
Click to collapse
To get into recovery, you need to hold volume down AND volume up and press power. (This will take to you to the bootloader, and then select recovery.)
Edit- What they said. ^^^
Have you tried booting it up after pulling the battery? It may boot fine for you now. If not you want to hold volume up + volume down + power that is how you access recovery.
Volume down + power took you to Odin mode.
Allons-y
Thanks man, I really appreciate it!
Its usually always something small...
Sent from my XOOM 2 using xda app-developers app
Oh...thats what that was. What exactly is odin?
Sent from my XOOM 2 using xda app-developers app
Dry.doc said:
Oh...thats what that was. What exactly is odin?
Sent from my XOOM 2 using xda app-developers app
Click to expand...
Click to collapse
Odin is a Samsung-specific interface that allows you to flash partitions to your device. For the most part, it is not needed on a GNex, given that we have unlockable bootloaders and can use fastboot. However, it is sometimes needed when your bootloader gets corrupt, and you can't use fastboot.
Hello guys, so today I decided to update my i747 ATT S3 to the latest Task650 Rom, I did as always with the exception that this time I needed to flash a file trough PDA in odin since there was a baseband update back in may. Everything was successful at this point, phone rebooted and went in to the current version of the Task650 ROM i had installed, everything worked great with the exception of my power button that once pressed instead of locking the phone would completely turn it off/trigget the power panel (shutdown,reboot...) so I booted again and powered it off. Tried to get into recovery to flash the latest build of the Task650 ROM without luck, the phone just powers off once trying to boot into recovery, tried the same thing with download mode. At first it went in and stayed in download mode successfully but then I tried to go into recovery again and the same story, went back into download mode and this time it would shut down after 3 or so seconds, sometimes lasts more but no matter what I do it shuts down and the battery has to be pulled in order for it to go into either mode.
At this point to me it looks like a sticked power button but I could be wrong. Any suggestions in order to attend this issue?
[Update] So apparently it really is my power button, wiggled with it for a bit and managed to make the phone boot into the ROM successfully...
Any suggestions on how to permanently fix this issue?
Oscar
Hey man,
If you were able to "wiggle" the power button to work then its definitely the power button. If you have had the phone for a year or less I'd Odin back to stock/ flash counter fix the device and return it to at&t. Back in my captivate days that was a sure sign that the power button was about to malfunction completely. If you are unable to take in for warranty then I'd suggest using the XDA search feature to find the "home remedy power button fixes" or maybe just googling fixes. Mobile tech videos does good work but I won't link to his website because I'm pretty sure its against XDA rules. Or, for even more fun; you could fix it yourself.
Anyways,
Goodluck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
SOLVED, got phone back from repair shop where power button was successfully replaced
wceoscar said:
SOLVED, got phone back from repair shop where power button was successfully replaced
Click to expand...
Click to collapse
Good to hear man
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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