S3 i8190l stuck in loop after flashing CM12.1 - Galaxy S III Mini Q&A, Help & Troubleshooting

Hey everyone,
I'm having a problem after trying to flash CM12.1 on a i8190l.
The instructions I basically followed are the ones mentioned here: novafusion.pl/tutorials/installation-guide-golden/ and I used the rom Lollipop 5.0.2 (CyanogenMod 12.0) 20150428 stable with the Odin app to install it.
All went well up to the point 12. Click on Wipe, then use slider on the bottom to let process begin.
At this point I received a FAILED message with an error message saying below that /data couldn't be mounted. After that, I rebooted the phone, and it started loading the first android screen apparently. After a few minutes, Android threw up an error saying that it couldn't encrypt the data and had to reboot. After that reboot, the system won't stop going over a loop boot that flashes TeamWin over and over again.
I can still get to the download mode, what is the recommended step to take from here? Is it possible to recover the OS? Do I have to worry about the battery running out, or does it charge up while on download mode/other mode?
Thanks for your help

Related

[Q] Reboot Loop, Trying to Restore to Factory

I was running CM 9 nightly builds for the last year, and decided to upgrade to CM10. In my system settings there was a handly little "upgrade" button which I mistakenly used- and my phone got stuck in a reboot loop. I booted into recovery mode, and tried to restore the phone, but it did not work. It kept sticking at the blue circle boot image for over 20 minutes.
I tried recovery mode again, and every time I went to CW recovery I would get several lines saying can't mount SD card. OK, I broke it.
I then downloaded the factory firmware from samsung-updates.com - and flashed with Odin- just to get my phone to work. It's been 2 hours where I cna't get anything up. After rebooting (from factory firmware) I have the regular samsung s repeatedly coming up, and I'm still in a reboot circle.
Any suggestions or ideas? I need my phone for work, so I really just want to get it up at this point, with whatever will work.
I found the EZBase recovery kit thread, fixed myself Of course, it's the 101th thread I read in my search!
http://forum.xda-developers.com/showthread.php?t=2095519
Sorry, next time will keep searching. Worked to get my phone up and running,w ill now attempt CM10 again...

[Q] I bricked my Galaxy Ace...what to do?

Hey guys!
Earlier today I rooted my another Android device so I wanted to try it with my Samsung Galaxy Ace S5830. I rooted it successfully, then I wanted to install a custom ROM...well, I wanted to upgrade it to Android 4.3 since I found a tutorial for it.
I downloaded two zip files, put them on the card, booted the phone into recovery mode and during installation of files, there was an error (Status 0), something like that. When I wanted to boot my phone, it could not boot up. It would just have that splash screen saying Samsung Ace S5830 and it would stay there forever.
I got back to the recovery mode and there is error saying "E:failed to mount /system (Invalid argument).
I figured out I messed it up, so I tried to flash it with Odin. However, after reading millions of guides, I failed to do it. I put my phone into download mode and it just says "Downloading..." on a black screen, there is no picture or anything like that, and I saw in the guides there should be one, so am I in the wrong mode?
Anyway, I "managed" to flash my phone. The process took ~10 seconds then rebooted my phone and I was waiting on a countdown (4 minutes or so), then it said my phone is done and I saw a blue button saying "PASS". However, my phone was showing only a backlight during that process, there wasn't anything like a download bar.
I restarted my phone, wiped cache and did a factory reset, but it's still unable to boot.
What should I do?
Thanks a lot!
AsPeHeat said:
Hey guys!
Earlier today I rooted my another Android device so I wanted to try it with my Samsung Galaxy Ace S5830. I rooted it successfully, then I wanted to install a custom ROM...well, I wanted to upgrade it to Android 4.3 since I found a tutorial for it.
I downloaded two zip files, put them on the card, booted the phone into recovery mode and during installation of files, there was an error (Status 0), something like that. When I wanted to boot my phone, it could not boot up. It would just have that splash screen saying Samsung Ace S5830 and it would stay there forever.
I got back to the recovery mode and there is error saying "E:failed to mount /system (Invalid argument).
I figured out I messed it up, so I tried to flash it with Odin. However, after reading millions of guides, I failed to do it. I put my phone into download mode and it just says "Downloading..." on a black screen, there is no picture or anything like that, and I saw in the guides there should be one, so am I in the wrong mode?
Anyway, I "managed" to flash my phone. The process took ~10 seconds then rebooted my phone and I was waiting on a countdown (4 minutes or so), then it said my phone is done and I saw a blue button saying "PASS". However, my phone was showing only a backlight during that process, there wasn't anything like a download bar.
I restarted my phone, wiped cache and did a factory reset, but it's still unable to boot.
What should I do?
Thanks a lot!
Click to expand...
Click to collapse
Did you read rules?
Did you search for help?
Do you know that it's not the correct section to post your questions?
PLEASE USE Q&A ThREAD!! We need to keep clean general section!
Which model have you got?

[Q] Nexus 6 not booting up after random shut down

Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.

Infinite bootloop on Cyanogen modded S3 Mini... help!

I'm a complete newbie to android phone modding, and I was really proud of myself when I was able to install the Cyanogen 12.1 and Google Apps onto my Samsung S3 Mini. However, I made the mistake of trying to put my work email on it, which requires that my phone be encrypted. Well, I guess the encryption and rooted phone didn't want to play nice together, so I got the error message that my phone would be factory reset. Boo! Well, it got worse. Instead of a factory reset, my rooted phone now is stuck in what I have now learned is called a bootloop. Basically I turn my phone on, and the Cyanogen start screen (with the text "TEAMWIN") just infinitely flashes on the screen until I pull the battery.
I have tried using Odin 3.07 and cm12.1_golden.nova.20160210.ODIN_TWRP.tar.md5. I do the three button system boot, connect the usb, run Odin, get the phone recognized, and then install the .md5 in the PDA section of Odin. It tells me that it succeeded, but when I restart my phone it's still the same bootloop. I also tried swearing, but that didn't help either.
Has anyone else out there had experience with Cyanogen and this particular error? I would love to get this phone working again... preferably with either a Lollipop version of android or back to Cyanogen 12.1.
Any info would be greatly appreciated! Thanks everyone.
So I've got an update if anyone's interested... I can't call it progress, but it's a different problem now.
I was able to download and use Odin to do what was shown on this link: http://forum.xda-developers.com/showthread.php?t=2122548&highlight=root
Everything worked in Odin, the phone rebooted, and went to the Team Win Recovery Project diagnostics screen, rebooted again, and then to the samsung logo. However, it immediately goes to the "Encryption Failed" error screen, and the only option is to 'reset device'. Of course, doing this just reboots the phone and it then has the Team Win loading screen, Team Win Recovery Project diags screen, Samsung logo, and back to the 'Encryption Failed' screen again. So now I have a new infinite loop to solve. *sigh*
any thoughts?
Have you been able to get into TWRP? If you are, maybe you could wipe everything from there and flash the recovery version of your ROM.
I was able to put the stock bootloader onto the phone using Odin, download the original tar from here: http://live.samsung-updates.com/index.php?device=GT-I8190, then used the stock bootloader to install it from the sd card. Everything went fine, but now when I boot the phone it just hangs on the Samsung Galaxy S3 mini GT-i18190 start screen indefinitely. Is this progress, or have I created a new problem now?
You're playing around with heavy stuff. I won't recommend using an upgrade flash (CM over Odin) as an full flash. Please try flashing a stock image.
If you did something wrong to the partitioning, then it's likely to not allow you to do a successfull factory reset. Maybe you can try re-flashing a stock Odin image with PIT repartitioning.
Remember to try to backup the EFS folder, doing that kind of flash might wipe it.

From RR5.1 -> stock fail.. 'soft brick' now

I'm having problem with I-8190 (s3 mini) that used to run Resurrection remix (android 5.1). I followed these instructions: https://forum.xda-developers.com/showthread.php?t=2429169 to install stock android
but the stock android did not work, it didn't have wifi available so it's stuck on 'google login' stuff and phone also spams "com.google.process.gapps" error.
That happened with few different stock android images. Then I decided to try install RR 5.1 (with odin) again, it phone remains in bootloop doing the 'optimizing application x/xx' part.
Then I re-installed twrp and tried flashing RR5.1 but install gives error, "Error executing updater binary in zip '/extern" (line break, dunno how it continues)
Could someone give some pointers on how to make phone run some operating system again..?
seegge said:
phone remains in bootloop doing the 'optimizing application x/xx' part.
Click to expand...
Click to collapse
That's not a bootloop, it's optimizing every app in the ROM. Do it again, then go watch TV until it's time to go to sleep and see if it's finished. (If not, plug in the charger and go to sleep and it should be finished by morning.)

Categories

Resources