[solved]
Edit.
The Vol Down button was stuck. I functioned it over and over, both together then up/down for a few minutes and it became unstuck. What a PITA!!
/Edit
The phone has been fine for months. Then while driving the GPS wasn't locking so I rebooted, and since then it only boots into safe mode for a few seconds then reboots.
I tried going back to a backup from just after I flashed, but the problem remained. So I took the SD card out, no joy. Then I tried a factory reset (SD card out), still the same.
I reinstalled Windows recently but was able to connect long enough to get the driver install complete. Booted to download mode, pressed vol up but no response from anything. I had to pull the battery.
I have on occasion seen the error pop up "samsung.com has stopped working" then it reboots.
I have the blue Kuban ROM
Any idea what my problem is and how to continue trying to fix it?
Edit
Just flashed the original Blue Kuban ROM I still had on the SD card, but it's booted into safe mode again!!
syco123 said:
[solved]
Edit.
The Vol Down button was stuck. I functioned it over and over, both together then up/down for a few minutes and it became unstuck. What a PITA!!
/Edit
The phone has been fine for months. Then while driving the GPS wasn't locking so I rebooted, and since then it only boots into safe mode for a few seconds then reboots.
I tried going back to a backup from just after I flashed, but the problem remained. So I took the SD card out, no joy. Then I tried a factory reset (SD card out), still the same.
I reinstalled Windows recently but was able to connect long enough to get the driver install complete. Booted to download mode, pressed vol up but no response from anything. I had to pull the battery.
I have on occasion seen the error pop up "samsung.com has stopped working" then it reboots.
I have the blue Kuban ROM
Any idea what my problem is and how to continue trying to fix it?
Edit
Just flashed the original Blue Kuban ROM I still had on the SD card, but it's booted into safe mode again!!
Click to expand...
Click to collapse
I'm new to this, but from a quick search. I would say you have a button stuck or a bad app installed. Since you just flashed the cuban, and I assume you had to do this on a computer. I would think you wouldnt have any of the recent downloaded apps. But if you do,start with the most recent app installed and clear cache,data,and delete. Then reboot, repeat until you find the app. Only user apps........ not system apps.
Gil81 said:
I'm new to this, but from a quick search. I would say you have a button stuck or a bad app installed. Since you just flashed the cuban, and I assume you had to do this on a computer. I would think you wouldnt have any of the recent downloaded apps. But if you do,start with the most recent app installed and clear cache,data,and delete. Then reboot, repeat until you find the app. Only user apps........ not system apps.
Click to expand...
Click to collapse
Thanks for the reply mate, but so as to not waste anyones time I marked the thread solved. It was a button, I did add the info to the post shortly after finding the problem.
syco123 said:
Thanks for the reply mate, but so as to not waste anyones time I marked the thread solved. It was a button, I did add the info to the post shortly after finding the problem.
Click to expand...
Click to collapse
Wow...didn't even see that...lol. Top of the page..If it had been a snake I'd been had...
Gil81 said:
Wow...didn't even see that...lol. Top of the page..If it had been a snake I'd been had...
Click to expand...
Click to collapse
I made it bold now
Tanks again for taking the time to reply.
Related
My Gmail emails weren't coming into my HTC EVO 4G so I tried to power cycled it (my non-Gmail emails were coming in just fine). When I powered it back it on nothing came on the screen, nothing happened. It is rooted (Unrevoked) so I tried holding the power button and volume up button, but it just vibrated three times, nothing came on the screen and nothing happen. I tried power button and volume down button and it boots in HBOOT. Seconds later it runs something and there's a message saying something about wrong image. I stopped here as I haven't used HBOOT before.
What's going on here? How do I get my phone to boot normally again?
P.S. - it's not the battery, because its been charging all night.
DiGiTY said:
My Gmail emails weren't coming into my HTC EVO 4G so I tried to power cycled it (my non-Gmail emails were coming in just fine). When I powered it back it on nothing came on the screen, nothing happened. It is rooted (Unrevoked) so I tried holding the power button and volume up button, but it just vibrated three times, nothing came on the screen and nothing happen. I tried power button and volume down button and it boots in HBOOT. Seconds later it runs something and there's a message saying something about wrong image. I stopped here as I haven't used HBOOT before.
What's going on here? How do I get my phone to boot normally again?
P.S. - it's not the battery, because its been charging all night.
Click to expand...
Click to collapse
It is normal for it to scan and give you that 'wrong image' message. If you had a PC36IMG on your sd card, that's when the bootloader would find it, and ask you to update. Since you dont have a PC36IMG on your card, it scans and finds nothing, so it says 'no image or wrong image'. No worries. What were you trying to accomplish by holding power and volume up? Its power and volume down that puts you to the bootloader. What were your intentions once you got to the bootloader? Were you trying to get to recovery, to clear cache or reflash a rom or something? If you want to reboot your phone without really doing anything, from where you're at in the bootloader, you'll see an option that says 'fastboot'. Select that. Once at the fastboot screen, you'll now see an option to reboot phone, and to power phone off. Select reboot, and see if she powers up for you. Shouldn't be any issues
Weird. So in HBOOT I chose "reboot" from the FASTBOOT main menu and the phone restarted and got back to the desktop/launcher successfully. Everything looks normal.
My Gmail inbox just now began updating from yesterday (even though the phone was on up until a couple of hours ago). Also the apps I set up to install yesterday from market.android.com just started to download and install too.
What's going on here? Is the internal storage/memory/ROM dying or something (come to think of it I did have this Gmail issue last week too, but that power cycle was successful)?
DiGiTY said:
Weird. So in HBOOT I chose "reboot" from the FASTBOOT main menu and the phone restarted and got back to the desktop/launcher successfully. Everything looks normal.
My Gmail inbox just now began updating from yesterday (even though the phone was on up until a couple of hours ago). Also the apps I set up to install yesterday from market.android.com just started to download and install too.
What's going on here? Is the internal storage/memory/ROM dying or something (come to think of it I did have this Gmail issue last week too, but that power cycle was successful)?
Click to expand...
Click to collapse
I'm not sure what would cause the problems you're describing. What ROM are you currently on? Have you tried wiping cache and dalvik cache? Perhaps it's an issue with the Gmail app itself. In any case, I'd first try wiping cache and dalvik. If that works, great. If it fails, I'd probably do a complete wipe and fresh install. That usually solves any issues for me.
Sorry, I saw your initial post after my second post.
I just realize what the confusion may have been. When I powered off the phone I figured I might as well take the opportunity and do a full backup with nandroid. So I proceeded to get into clockworkmod recovery with power + vol. up button (this is when it vibrates 3 times and does nothing). The confusion, I think, is that I've been installing/flashing various ROMs for my new Viewsonic G Tablet for the past 2 days straight (with very lil' sleep) and thought the recovery method (power + vol. up) for the G Tablet was also the method for the EVO.
Anyhoo, at this point I'm very confused. I could of sworn I installed clockworkmod recovery on my EVO and I used power + vol. up to get to it when rooting. I even see the clockworkmod folder on my EVO's microSD card. Weirdness.
My EVO is working now so I guess I shouldn't stress it. I'll just figure out how to do a full backup later.
Thanks!
DiGiTY said:
Sorry, I saw your initial post after my second post.
I just realize what the confusion may have been. When I powered off the phone I figured I might as well take the opportunity and do a full backup with nandroid. So I proceeded to get into clockworkmod recovery with power + vol. up button (this is when it vibrates 3 times and does nothing). The confusion, I think, is that I've been installing/flashing various ROMs for my new Viewsonic G Tablet for the past 2 days straight (with very lil' sleep) and thought the recovery method (power + vol. up) for the G Tablet was also the method for the EVO.
Anyhoo, at this point I'm very confused. I could of sworn I installed clockworkmod recovery on my EVO and I used power + vol. up to get to it when rooting. I even see the clockworkmod folder on my EVO's microSD card. Weirdness.
My EVO is working now so I guess I shouldn't stress it. I'll just figure out how to do a full backup later.
Thanks!
Click to expand...
Click to collapse
Yea, its power down and volume that takes you to the bootloader. You wont get directly to recovery unless your rom has the 4 option quickboot, then u can select recovery. Anyways, so once youre at the bootloader, you just need to select recovery. Then youll boot to clockwork. From there, you can make a new backup, flash a new rom, wipe caches etc.
Sent from my PC36100 using XDA App
Oh, okay. Thanks again!
DiGiTY said:
Oh, okay. Thanks again!
Click to expand...
Click to collapse
You're welcome. I'm glad to help out
Hi guys:
I have this phone from about 10 months ago. I have always it rooted and with CyanogenMod, actually with CM7.
Today I was using my browser, and then it closed, the phone begin giving me a lot of errors, any application worked and I decided to reset it, because sometimes that work.
For my surprise, when I reseted it, It was bootlooping, It start booting (cyanogen logo doing circles), then freezes and then reset.
I know how to work with this problems and I reseted it on recovery and when I entered to the recovery everything seems to be fine, but I only see the menu, when I try to install zip from sd card, go to mount & stored, go to clear cache, or enable USB the screen just get empty but its ON.
Im very frustrated, I don't know how to proceed in this situation, I have looked in the Troubleshooting thread but have not found anything that worked for me with boot looping.
I hope someone can help me, sorry for my english, it's not my main language.
what button are you pressing to select the menus? Power?
Yes Im using power button.
Before I used the power button but now tried using the middle button and it worked.
Lets see if it recover correctly.
Yes because power button turns off the screen.
Hey guys, I"m new to the forums (as well as android).. Got my S3 yesterday (ditched my iPhone 5 for it and found touch wiz to be gruesome) So I rooted my i747 device, and installed the latest CWM, and put the new paranoidkangdroid ROM on my S3. I had it working all day, and it's incredible! I love every aspect of it. However, my phone just recently after trying to set a passcode rebooted itself and is stuck in the boot screen.. (the glowing pink android)..
I've tried rebooting, removing the battery, connecting to my computer, and tried to boot into the CWM screen without any success. Any suggestions for how I can get this thing to work again?
Thanks a lot for your time
- Ryan
Volume up+home button+power button until it disappears, let go of power and keep hokding other two. Yoh will see samsung screen with blue letters in top left for a brief second.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Jammol said:
Volume up+home button+power button until it disappears, let go of power and keep hokding other two. Yoh will see samsung screen with blue letters in top left for a brief second.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply, tried your advice.. screen went black, vibrated every few seconds, showed the samsung logo quickly, restarted itself again, and is still stuck in the boot loop...
Any other ideas?'
[update] : got my phone into the CWM recovery (v6.0.1.4) Any ideas on my next step? I cleared my cache and rebooted, it restarted and a screen popped up saying "updating android" and it was updating all my apps, gave me a little bit of hope. But then it proceeded to go back into the boot loop. This is getting really frustrating, if anyone has any other suggestions I'd really appreciate it
thecartographersden said:
Thanks for the quick reply, tried your advice.. screen went black, vibrated every few seconds, showed the samsung logo quickly, restarted itself again, and is still stuck in the boot loop...
Any other ideas?'
[update] : got my phone into the CWM recovery (v6.0.1.4) Any ideas on my next step? I cleared my cache and rebooted, it restarted and a screen popped up saying "updating android" and it was updating all my apps, gave me a little bit of hope. But then it proceeded to go back into the boot loop. This is getting really frustrating, if anyone has any other suggestions I'd really appreciate it
Click to expand...
Click to collapse
sorry for the double post - screen is all black no... getting no response at all now from the device, asides from an occasional vibration when I hold down the volume up + home + power...
please help
I just noticed the post for that ROM today so it is obviously fairly new, bugs are to be expected. Can you get to download mode, same process as recovery except substitute vol down for vol up. If so you can flash the stock rooted ROM of your choice and either try again or use a different ROM until they work the bug out. I would also suggest posting in the ROM OP so the dev is aware of the problem, or incase he has any suggestions.
EDIT - Just noticed you only have 3 posts, the forums require 10 to post in the development sub forums.
thecartographersden said:
sorry for the double post - screen is all black no... getting no response at all now from the device, asides from an occasional vibration when I hold down the volume up + home + power...
please help
Click to expand...
Click to collapse
That happened to me. For that rom to work, don't change any settings.
Make sure it's disconnected from the power wire. Hold, Volume Up and Home button then hold the power button. Wipe both caches, and factory reset. Reflash PK and Gapps. Wipe caches again and reboot. It should work. If not flash back to PA like I did. I'm gonna wait for the next update.
Sent from my SAMSUNG-SGH-I747 using xda premium
thecartographersden said:
Thanks for the quick reply, tried your advice.. screen went black, vibrated every few seconds, showed the samsung logo quickly, restarted itself again, and is still stuck in the boot loop...
Any other ideas?'
[update] : got my phone into the CWM recovery (v6.0.1.4) Any ideas on my next step? I cleared my cache and rebooted, it restarted and a screen popped up saying "updating android" and it was updating all my apps, gave me a little bit of hope. But then it proceeded to go back into the boot loop. This is getting really frustrating, if anyone has any other suggestions I'd really appreciate it
Click to expand...
Click to collapse
Wipe "cache" AND "dalvik cache" found under advanced tab. If that fails, try a more stable rom. Cm10 nightlies maybe, which are more mature with less problems.
Also, you didn't flash a different kernel did you? From what I read only the kernel provided will work. Furthermore, make sure you flash the proper gaaps. That also will cause problems.
And of course. Welcome to XDA and Android. Once you get the hang of flashing you will be obsessed and never go back to iFail. Trust me.
Sent from my SGH-I747 using xda app-developers app
thanks a lot everyone above - I managed to reset all caches earlier, wiped the device, and then re-installed the ROM and gapps and everything is working fine now. I'll take your advice and not alter too many of the settings on this ROM (asides from this error, this OS runs beautifully!) I tried to post this problem in the post for this specific ROM but wasn't allowed as I have less than ten posts.. haha.
Again, thanks for all the help. I'm loving the device, iOS doesn't come close to what I've experienced so far.. And I've only been using it for a couple days.
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
EDIT: For the solution to this particular issue, head to this post.
Hi, yesterday I successfully did a clean install of OOS 4.0, including Magisk and systemless root. I had everything set up as I wanted it.
Today, I tried the 4.0.1 OTA, after using a Canadian VPN server. It downloaded fine (the full zip), and I launched the OTA.
Phone reboots... into nothing. Now the phone won't boot into recovery mode, or start the system. I thought it was odd, so I flashed stock recovery again (which is what was installed). Still can't boot. Then tried just booting into recovery over fastboot mode. Still no luck.
Then I managed to boot into a modded TWRP. That's something... But tried flashing the OTA from its temp location in TWRP. A couple of "command log" errors, but appeared to patch nonetheless.
Reboot to system though: black screen of nothing, again.
Anyone know what might be the issue, and why it happened after just launching an OTA through the stock dialogue?
Cheers :/
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
abobobilly said:
same problem here. i don't want to wipe the phone. Really a BIG problem to do it all over again for me :S and i don't even have a backup man. wtf.
Click to expand...
Click to collapse
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
ememeh said:
I feel your pain, brother! Can you get into fastboot mode okay?
I'm lucky that I have a 3.2.8 Nandroid backup on my Mac (if I can push it to the sd card -- had some issues doing that over adb lately!). I also have my app data backed up separately. So I'm happy to do a clean install of OOS 4.0/4.0.1, but as yet I can't even launch stock recovery to do so.
Weird.
Click to expand...
Click to collapse
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
abobobilly said:
Fastboot works just fine. I also tried flashing that blu-spark twrp recovery, hoping it would atleast decrypt data, so i could take some backup or something. But nothing is working. The phone keeps booting back in recovery no matter what i do, and when it doesn't ... it just stucks at 1+ logo.
Click to expand...
Click to collapse
I can get to a point of backing up if I want to. Though at the moment, I don't know what I'd backup (maybe just the system partition? I dunno).
I have the same thing: Can get the white 1+ logo, both capacitative button backlights show, the android text logo, but then black screen. Very frustrating. Let me know if you have any luck! I'll update here too.
wierd
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
canceric said:
i got the boot.img from the zip file flashed it in recovery, not in boot , it worked, but since then while flashing messed up recovery,somehow i have stock recovery now, i can boot into bootloader and recovery but device doesnt get recognised in bootloader ,cant flash twrp modified nor can flash supersu 2.79SR1:crying::crying:
Click to expand...
Click to collapse
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
abobobilly said:
Hokay, so let me recap a little.
I updated to OOS 4.0 from 3.2.8, and the only problem after a successful flash was that TWRP was not decrypting the storage, hence i wasn't able to root. I didn't touch anything after that, and kept the phone on same TWRP.
Just now, when i downloaded 4.0.1 OTA (using TurboVPN > Germany), i updated it right away, thinking it'd flash the stock recovery itself. Except, it didn't ... and what happened afterwards, we both know well.
Anyway, after trying A LOT of recoveries, this recovery seemed to work. Search for "recovery_OBT8N.img" ... its the stock recovery for oneplus 3. I flashed it in fastboot, then used 'fastboot boot recovery_OBT8N.img" command to directly boot the recovery. It worked, as the phone continued to update normally. Yay ... i guess.
Then later it was showing "Decrypting" message (after entering my PIN, ofcourse) ... but remained stuck upon completion. So I hard rebooted via long pressing power button ... and voila ... the phone booted just fine after that.
Well, here's my story. I really don't want to get into the trouble of rooting this sh*t for now. I have work tomorrow and i am already 4 hours late for sleep lol. So ... Good Night my friend. Thanks for your support.
Click to expand...
Click to collapse
good thing it worked for you, it bugs me that i cant root the phone since the device doesnt get recognised in fastboot ,reinstalled all the drivers and all, nothing works
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
ememeh said:
So latest update:
Following @abobobilly 's advice, I found this version of the stock recovery: https://www.androidfilehost.com/?fid=385035244224405665
Flashed it in fastboot mode
Then booted it from fastboot mode.*
From there, I chose to update via sideload, and flashed the update 4.0 over adb.
"Install success"!
I've booted up into the system now, and everything is as I left it! Such a relief. (Don't have root anymore, but can sort that out.)
*At that point, the stock recovery loads (thank the lord...) and informed me that the update failed. Fine, don't care!
Click to expand...
Click to collapse
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Shayded said:
How did you actually reboot? i get the message that says success, and then when i select reboot, it says reboot now and i get no option other than "no"
Click to expand...
Click to collapse
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
ememeh said:
I had the same issue. The recovery seems to be a bit weird. I did it the old fashioned way: hold the power button till it forces itself off, then boot up
Click to expand...
Click to collapse
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Shayded said:
Tried this, now the phone wont turn on at all, slow red LED (battery was at 70%). Holding the power button results in the PC its connected to recognizing it with a sound, but nothing else happens
Click to expand...
Click to collapse
Weird. Could be a different problem...
Did you get the install success message?
ememeh said:
Weird. Could be a different problem...
Did you get the install success message?
Click to expand...
Click to collapse
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Shayded said:
Yes, then when it wouldnt let me reboot i forced the shut down and now the phone is unresponsive
Click to expand...
Click to collapse
Can you still boot back into fastboot and/or recovery?
ememeh said:
Can you still boot back into fastboot and/or recovery?
Click to expand...
Click to collapse
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Shayded said:
It's unresponsive. It doesn't turn on, it doesn't vibrate and it doesn't give a charging LED.
This is as bricked of a phone as I've ever seen
Click to expand...
Click to collapse
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Shayded said:
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
Edit: Nevermind? After playing around with button combinations it booted back into recovery somehow. Guess it's salvageable
Click to expand...
Click to collapse
Just seen the edit. Okay, makes sense. Good luck :good:
ememeh said:
Sorry to hear that. It's unlikely, but could be a battery issue if there was a major drain. So keep it on charge. (It may well be charging without the LED anyway.)
If not tried already, try launching fastboot mode manually with the power/volume key (can't recall which, Google it if you don't know)
Lastly, how long have you held the power key down for? A 30-second hold should launch it.
Other than any of these options, best bet is to make a separate thread asking for help or to follow a hard brick guide for the OP3.
Click to expand...
Click to collapse
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Shayded said:
I tried holding power for 40+ seconds and nothing, everything was totally dead. Then I clicked the power button about a minute later and it popped into recovery, gave me the option to derypt and wipe everything so I did and now I'm into a fresh 4.0.1 install.
Seriously, no damn clue how it happened or what could have caused any part of it but it works now. So for anyone with a bricked OP3: Just mash buttons
Click to expand...
Click to collapse
Luckily for you, it doesn't sound like a true hard brick. Sometimes power buttons are just funny like this. In my experience at least (I've come back from near death experiences in a similar way to you before).
In any event, well done! Always such a relief to get things working again.