I've been running Blisspop 5.1.1 on SGS3 with TWRP as my recoverey. Lately, I've been having many issues with my battery. Yesterday evening, I suddenly got the message of encryption unsuccesful on my phone. I tried every possible thing to do get rid of that message, but the phone wouldn't budge. My only option was to hit the phone resest button and see what happens, I understand running a custom rom with root excess can inexplicably damage my phone in such situations after reading a lot of posts.
The phone now displays the S3 logo and keeps flashing at the teamwin recovery splash and blinks right there.
I need urgent help to retrieve it back and any leads on this will be greatly appreciated.
Thank you!
you need a usb/otg cable..
shreenit said:
I've been running Blisspop 5.1.1 on SGS3 with TWRP as my recoverey. Lately, I've been having many issues with my battery. Yesterday evening, I suddenly got the message of encryption unsuccesful on my phone. I tried every possible thing to do get rid of that message, but the phone wouldn't budge. My only option was to hit the phone resest button and see what happens, I understand running a custom rom with root excess can inexplicably damage my phone in such situations after reading a lot of posts.
The phone now displays the S3 logo and keeps flashing at the teamwin recovery splash and blinks right there.
I need urgent help to retrieve it back and any leads on this will be greatly appreciated.
Thank you!
Click to expand...
Click to collapse
Don t reset your phone go back to twrp and do a factory reset..after that do a format data type in yes..dont reboot ...put a custom rom to your usb/otg drive thats specific for your phone.. Then flash it this is just to get you going...
paztine said:
Don t reset your phone go back to twrp and do a factory reset..after that do a format data type in yes..dont reboot ...put a custom rom to your usb/otg drive thats specific for your phone.. Then flash it this is just to get you going...
Click to expand...
Click to collapse
I did have to reset. There was no other option. It is now stuck on the page of team recovery and constantly flashes. Is there a way out for this?
Related
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
did you try reflashing your recovery via Odin?
SuperSU
laxsrbija said:
Hello,
I've had my S3 for over a year now and it has been mostly running great. Whenever I've had issues I tried to solve them by myself, but this time I was unable to fix my phone, so I must ask for help.
Here's what happened. I left my phone on my desk today and one of my co-workers fiddled with it. He opened SuperSU and then a message popped up saying that SU binary needs to be updated. He then choose to update it via CWM. The phone then restarted and upon starting shows the startup screen then it tries to enter the recovery, but instead it just shows it for a brief moment and then it restarts again. It keeps doing that over and over again. If I remove the battery and then insert it back again, the phone will turn on by itself and continue to reboot after failing to open CWM.
I tried to enter the recovery, but had no success. The phone did enter the Download Mode though, but flasing a ROM via ODIN will remove all of the data stored on the phone and I really need it. The phone is currently running Android Revolution HD 40.
Is there a way to get my phone operational again without loosing the data stored on it?
Thanks in advance.
Click to expand...
Click to collapse
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
As the above post said flash another recovery in odin I recommend Philz recovery,backup your data in recovery then factory reset if that does not work flash another rom via recovery or return to stock with odin. You can also boot into recovery with adb but I would try above first.
Then charge your co-worker for all the time wasted trying to fix phone
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
tallman43 said:
First of all what are co workers doing messing with your phone I would seriously not be happy!! screen lock comes to mind!
Click to expand...
Click to collapse
He's actually a good guy and I'm sure he didn't do it on purpose. He told me that he was playing a game and he tried to add more coins using GameCIH. Then the prompt to allow root access to the app came up along with a notification to update the SU binary. He said he pressed that button by mistake. I wasn't mad at the guy, I was only upset that I may lose my data.
laxsrbija said:
Thank you so much for the idea, I just tried this and it worked! After flashing new recovery via ODIN, I'm now able to access my phone. There was no need to flash the ROM again, as it was fine, the only problem was with the recovery.
And I still have my data!
Thank you very much again, cheers :laugh:
Click to expand...
Click to collapse
you are welcome! glad to see that it works again.
I was using @Lysergic Acid cm-13.0-20161114. I picked my S2 to check the hour and the screen didn't turn on so naturally I held the power button to restart it. The phone didn't boot past the "Galaxy S2 etc." screen. I tried to open TWRP and the splash screen appeared but it didn't get past that, no TWRP menu. I tried to flash stock ROM with Odin, it failed. The same happened trying to flash modified kernels with custom recoveries. So now I'm stuck with a message that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've had to recover my phone many times in the past but TWRP always worked, this time it didn't.
Is there any way to solve this? I have important information inside the phone. Would a USB JIG be of any help?
Simeonico said:
I was using @Lysergic Acid cm-13.0-20161114. I picked my S2 to check the hour and the screen didn't turn on so naturally I held the power button to restart it. The phone didn't boot past the "Galaxy S2 etc." screen. I tried to open TWRP and the splash screen appeared but it didn't get past that, no TWRP menu. I tried to flash stock ROM with Odin, it failed. The same happened trying to flash modified kernels with custom recoveries. So now I'm stuck with a message that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've had to recover my phone many times in the past but TWRP always worked, this time it didn't.
Is there any way to solve this? I have important information inside the phone. Would a USB JIG be of any help?
Click to expand...
Click to collapse
Odin should be able to flash the stock firmware while on the screen that says "upgrade encountered an issue" as long as you had USB debugging enabled.
You can also try booting a debrick.img from ext sdcard if you can find the debrick.img specific for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Odin should be able to flash the stock firmware while on the screen that says "upgrade encountered an issue" as long as you had USB debugging enabled.
You can also try booting a debrick.img from ext sdcard if you can find the debrick.img specific for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Nevermind, I tried flashing a 3 part stock JB rom that worked for some people. It didn't work for me and now the phone doesn't even turn on. RIP
Now I have a white S2 (Galaxy S2 forever lol) that a friend gave me until I buy a phone next year with the Snapdragon 660, or if I get a job (I'm a student), an even better phone with the Snapdragon 835.
Simeonico said:
Nevermind, I tried flashing a 3 part stock JB rom that worked for some people. It didn't work for me and now the phone doesn't even turn on. RIP
Now I have a white S2 (Galaxy S2 forever lol) that a friend gave me until I buy a phone next year with the Snapdragon 660, or if I get a job (I'm a student), an even better phone with the Snapdragon 835.
Click to expand...
Click to collapse
If the device vibrates when you hold power but doesn't boot then the debrick.img may still work, just in case you're curious enough to attempt fixing it for learning purposes.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
If the device vibrates when you hold power but doesn't boot then the debrick.img may still work, just in case you're curious enough to attempt fixing it for learning purposes.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
The S2 doesn't vibrate when you turn it on (at least the i9100 model), but don't worry it's completely dead. No boot, no recovery, no download mode, no nothing. If I'm bored enough I might buy a new motherboard from AliExpress in the future cause they're really cheap.
I have a Coolpad 3300a that's stuck in the splash screen. I've tried a soft & hard reboot (3x). Plugged into comp and it's "recognizes" an Android device, but does not display anything on/from the phone itself. Must remove battery to shut phone off. Have done a "search" pertaining to this problem, but have not been able to obtain a "fix". There are others with the same problem (on the "net" search), so I'm hoping someone here will have an answer for me.
Appreciated:
Rick
69Rixter said:
I have a Coolpad 3300a that's stuck in the splash screen. I've tried a soft & hard reboot (3x). Plugged into comp and it's "recognizes" an Android device, but does not display anything on/from the phone itself. Must remove battery to shut phone off. Have done a "search" pertaining to this problem, but have not been able to obtain a "fix". There are others with the same problem (on the "net" search), so I'm hoping someone here will have an answer for me.
Appreciated:
Rick
Click to expand...
Click to collapse
What were you doing or what did you do before the issue?
Can you get to recovery? Even being on stock recovery can help.
ninjasinabag said:
What were you doing or what did you do before the issue?
Can you get to recovery? Even being on stock recovery can help.
Click to expand...
Click to collapse
Re: ninjainabag
Thank You for responding and my apologies for not getting back to you sooner!. I'll answer in the order of your questions.
#1. Charging the phone via the comp/USB port. #2. Yes, and have been there. However the "recovery" menu on this phone only goes as far as "wiping cache", "wipe data/factory reset", "update from SD card" and "reboot now". Wiping cache and factory reset (3x) accomplished nothing! #3. Agreed, but never installed one (secondary stock recovery). 2 questions now... could I possibly D/l and install an O.S. from the SD card?, and/or use a "recovery" program from the computer through the phone?
Appreciate your response"
Rick
You're fine homey.
Your phones not, but you are. The Coolpad avail is the budget device for people who can't afford a budget device. So there's not much in the way of documentation for the 3300a.
In my personal opinion on the subject, you'd seriously just be better off picking up a new one.
-no recovery.
-no stock firmware available
-no support on the web (xda, AF, 4PD)
What service provider are you using? If you're looking to replace the phone. I can give a couple of suggestions that would help you make sure this doesn't happen again.
Oh guys, I badly need your experties. Just as I have in the title, I have a rooted Meizu M5 Note. I rooted the phone believing that I can do much more if it is rooted. But in 6 months of trying to understand what I can do with this said rooted phone, I realized now that there are not much to do with it... Probably because of the brand, so I decided to unroot
The rooting process was from here: giving me error so if requested, i'll give the link.
I have an Android build 7.0.0.0
So here is my issue:
In the same site, I found that I can unroot.. yes, UNROOT the rooted model of phone using superSU by going to its Settings and clicking unroot (or Unroot all something..). It took a bit while, so I decided to restart the device. Yes, while SuperSU was trying to unroot my phone.
Upon restart, it now could not boot.
I allowed 30 minutes, the screen only shows Flyme logo with a spinning circle. So from here, I made up my mind to perform the factory reset/restore:
Turned off Phone > Press and hold Power key + Volume Up... until I reach the screen with options to:
-Update system.
-Wipe data.
I selected Wipe data, for it will reset the system settings. It will now show the
"Wiping data.
Please dont turn off the phone, or it may fail to boot"
It will only last for 2 seconds - and will then again reboot and stop in Flyme logo with a never ending spin below.
_________________
It was already the factory reset, which I thought should help, but it wont work.
_________________
Things I tried:
- Used ADB to flash an offcial update rom from the flymeos.com, but the ADB Flashtool would not read the device because the USB Debugging is turned OFF.
- Googling any possible solutions, but cannot find any - nor any known programs that will allow me to read the not booting phone.
- Fast boot or safe mode, which only wont proceed.
- The Recovery Menu (the un-clickable one) must be locked by the manufacturer.
Can anyone please tell me:
- Is there anyway I can access the phone's drive so I can put the Update zip folder, which will help me to use the 1st recovery option "Update system"??
- Do you have any software that can help me enable the USB debugging when the phone wont boot at all??
Thanks guys..
All the help I can get will be best appreciated.
I tried posting this to forum.FlymeOS, but no one seems to have any interest on helping.
It is now you, that i think can help.
This is my Only phone, and cant afford to lose it...
Same issue with my Meizu M5 Note. I tried a tutorial on how to unlock it's bootloader. But after going through the first step, the SP Flash tool showed some error on how it does not turn on our go recover mode or anything... In really sad
Somebody please help!
RogueDiamond195 said:
Same issue with my Meizu M5 Note. I tried a tutorial on how to unlock it's bootloader. But after going through the first step, the SP Flash tool showed some error on how it does not turn on our go recover mode or anything... In really sad
Somebody please help!
Click to expand...
Click to collapse
Looks to me that you've bricked the phone.
jwoegerbauer said:
Looks to me that you've bricked the phone.
Click to expand...
Click to collapse
Yeah... Well, atleast I can ask for new phone now! LMAO
Hi,
I tried rooting my Nord 2, but managed to screw it up somewhere. I followed the usual stepw to do this, but the first time I was unable to use my wifi/bluetooth/gps. My phone was/is at the A1 EU. Version. I tried fixing the problem, but made things worse. Now I am stuck in the red dot boot logo and after a while I get to the TWRP screen. From there I can still fastboot. I tried restoring my phone from there, but without any luck. Can someone help me fix my phone ? At this point I don't even care that much anymore about rooting my phone, i just want to be able to use it again.
Thanks in advance!
Hi,
I had the same issue, but without switch to TWRP screen, just stays on red dot boot logo and that was all. The solution for me was format of the storage with stock recovery. In your case you may follow the instructions below:
1. Boot in bootloader (volume down + power on)2. Flash the stock recovery3. Reboot to recovery4. Select English, after that Wipe and Format storage (the phone will reboot automatically after success)
Best regards and good luck!
Onacceptable said:
Hi,
I tried rooting my Nord 2, but managed to screw it up somewhere. I followed the usual stepw to do this, but the first time I was unable to use my wifi/bluetooth/gps. My phone was/is at the A1 EU. Version. I tried fixing the problem, but made things worse. Now I am stuck in the red dot boot logo and after a while I get to the TWRP screen. From there I can still fastboot. I tried restoring my phone from there, but without any luck. Can someone help me fix my phone ? At this point I don't even care that much anymore about rooting my phone, i just want to be able to use it again.
Thanks in advance!
Click to expand...
Click to collapse
Did you try to format data via twrp and then restart?