Custom roms and stuck on splash/boot animation (SOLVED) - Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help &

Hello!, my device is GT-i9305 and i seem to have a problem of some sort. (I have had three devices before this and installed lots of custom roms, but never have i encountered something like this)
Whenever i try to install a custom rom (omnirom/pacrom/cyanegenmod) i get stuck in the splash/boot screen animation, but when i flash back to stock rom (4.4.4) using odin it loads up and everything works like its supposed to.
I have tried using TWRP and CWM-recovery. (With CWM i can get omnirom to boot, but i wont be able to dial or use mobile-data etc. (Seems like my efs files or something are missing) and i also get some error message about androidcore or somethinglikethat.
Most common fixes for this in the forums are to wipe dalvic and cache after installing. Which i have done + some other odd "fixes" i found.
I am really baffled. Whats wrong?

Did you flash TWRP 2.8.7.0? That recovery is buggy and does not work. You have to stay on 2.8.5.0 for the moment. There are people already trying to fix the faulty recovery. CWM won't get any updates anymore. It does still work but you might come across some ROMs which won't work with CWM.
To start all over again with no issues: flash 4.4.4 Stock, install TWRP 2.8.5.0 and you're good to go

Thankyouthankyouthankyou
That totaly fixed it! Thank you sooooo much, no more sleepless nights because of this.

Related

[Q] Phone fails to start installing ROM

Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?
Anyone?
I guess no one is using this phone anymore?
Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo

Can't enter recovery, everything else works (sort of)

Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
samcool55 said:
Hello everyone!
I installed the liquid smooth custom rom yesterday, and it worked fine! I also tried it with the OC kernel. Was a bit of a mistake...
Now, the rom is unstable with the OC kernel on my device, but that's not really my problem.
The issue is that i can't enter recovery! I checked with CWM manager and TWRP and CWM recovery are avaliable, and i can activate them both in the app, but i can't enter the recovery.
Tried hardware buttons(vol up + home + power), rebooting from the app(cwm manager), rebooting from the power menu (i have the reboot into recovery option) but i can't get into the recovery.
It's quite annoying because the phone is unstable and the only option is odin it to stock rom and temp cwm it back to where i was, but that seems a very tough job... (last time it took me over 2 hours... don't know why but it kept failing, did work eventually...) I do have backups, one made with CWM from current rom with no-oc kernel (the stable one).
And i have another custom rom that i backed up with TWRP. Don't know if i can do something with them...
I can do stuff on the phone, so even with the unstable-ness i can do things if needed.
i am trying to get into recovery with terminal, but wifi is ruined so getting the phone working long enough to download it via mobile data, quite difficult... But i keep trying.
edit: tried terminal, no success
Does anyone has an idea how i can get recovery working again?
Click to expand...
Click to collapse
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
rog_star said:
Install Frapetis Universal Kernel Flasher and flash your non-OC kernel.
Click to expand...
Click to collapse
Tried that, but UKF says device unsupported, don't know why... I have used it before and it worked then.
Any other options?
I got it fixed. But tbh i still don't understand how. I flashed JB stock with odin and when it rebooted, i got automaticly into CWM weirdly enough... Wasn't going to waste my maybe only chance so i flashed the custom rom, wiped everything again, reboot, went again automaticly into CWM. anyway i was third time lucky and it booted as it should. Everything is working now! Anyway thanks for trying to help.

Boot loop after flashing rom

So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
re: bootloops
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
You need to ODIN flash the stock original official COG2
firmware & odin flash cf-autoroot and the twrp recovery
before flashing the zip file rom.
Once that's done you can flash any N910T zip file rom in
twrp recovery without any issues.
Make sure to do a full wipe in twrp before you flash any
zip file rom to avoid bootloops and or getting stuck on
the samsung boot logo screen and be sure to do a full
and complete wipe which includes:
"System, Data, Cache, Dalvik Cache and last but not
least do a factory reset.
Good luck,
Have a great day!
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
i dont know if we are having the same problem but try installing the original firmware via odin and see if that works. if it does not then we have the same problem and i dont know how to fix it, now i am stuck with my S4 wait for help from someone to help me fix my note 4

S3 LTE won't go past bootscreen no matter what

So last time my phone was stuck on the device name and model number screen. I solved that issue by flashing TWRP using Odin.
but now the phone would not go past the boot screen no matter what I do. I re-flashed CM11 4 times now, factory reseted and wipe cache and dalvik cache. What should I do?
1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
maultasche said:
1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
So I should flash TWRP 2.8.5.0 and flash CM11 again? (because I don't have stock rom for S3 LTE)
Where can I get stock rom fro S3 LTE I can't seem to find it all, I find is firmwares.
Also, a few questions
1) If I give it into my phone carrier (Optus) would they know that it is rooted?
2) If they know it is rooted and with a custom rom and don't fix it for free is it possible to get it fixed by paying money??
The firmware provided by Samsung is the stock ROM I'm talking about
No, since you tried to flash a ROM through the faulty recovery you need to flash either official firmware from Samsung or a custom ROM based on Samsung stock like AMCHA or N4 Elite. I'd recommend to go with official Samsung firmware. After that go to stock recovery (it will come when you flash official firmware), do a factory reset and let the phone boot once. After that you can flash TWRP 2.8.5.0 and flash any ROM you want.
The new recovery from TWRP is too big for the S3. The S3 recovery is a little over 8MB, the new one needs more and messes up partitions etc. You won't be able to mount /system, /data and the recovery can't read your internal partitions as it should. Go with the way I provided. It seems like a lot of work but it's done in a few minutes.
For your two questions: yes and yes. But you can fix that on your own and don't need your operator or Samsung to get your phone fixed.
Thanks a lot for helping. I was scared to death cause if something happened I would've had to start using a old brick Nokia phones
Is it possible that after I flash the stock firmware, my phone still doesn't boot up?
I am basically a level above newbie, so I don't get what is happening. I see tutorials and do what they tell me to do. sometime I get what I am doing sometime I don't
as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then
maultasche said:
as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then
Click to expand...
Click to collapse
Ok sorry for doubting you! My phone is working now, thanks a lot for your help
Glad it's working now, you're welcome
I have rooted my s3 via odin and now i wont to flash twrp via flashify. Now i have a bootloop on my s3. How can i recover the phone. i am a noob on s3 and i don*t know how i could go into fastbootmode. Please help me.
what S3 do you have? Which recovery did you flash?
maultasche said:
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
I had this problem too! Flashed stock rom, then flashed TWRP 2.8.5.0 (I was using 2.8.7.0) and then flashed cyanogenmod 12 and boom it booted and worked!
Thank you very much!

Issues with latest official TWRP 2.8.7.0 for Galaxy S3 4G I9305 and how to fix it

Hi everyone,
some who frequently read the forum may know already that there are issues with the latest official TWRP for the Galaxy S3 LTE. The recovery partition on the Galaxy S3 LTE is too small for the latest recovery provided by TWRP. The partitions are messed up, you won't be able to mount /system and /data. Some users couldn't even flash their preferred ROM. As of now the buggy recovery is getting fixed.
I am not responsible for any damage, losing data or weird behavior you encounter while doing one of the following steps. As reported by several users step 1 was the way for them to fix their phone. Be sure of what you're doing. Make sure you know how to boot into recovery/Download Mode to do these things mentioned here and how to use odin. If not, XDA users have provided several guides. Use the search.
If you already flashed the faulty recovery, flashed a custom ROM with it and your phone ends up in a bootloop there are several ways to fix this issue.
1. Via odin and official stock firmware - please note: You might lose all your data you have on your internal storage
Download the latest official Samsung firmware from sammobile or look on XDA for provided stock ROMs by the AMCHA team. Boot your phone into Download Mode and flash the official firmware via odin. If you're done, reboot into stock recovery (which will be provided after flashing the stock firmware), perform a factory reset and let your phone boot up once. First boot might take some time, so be patient. Although the first boot might not be needed, do it anyway to see if your phone is still in a bootloop or suffers from other damage. If the phone boots up fine reboot into Download Mode again, flash TWRP 2.8.5.0 or any other latest custom recovery (preferably the recovery the maintainers recommend in their development threads) and flash your preferred ROM. Your phone should now work as it should.
2. Via stock based custom ROM (if you haven't flashed any ROM via TWRP 2.8.7.0 already - please note: You might lose all your data in this process as well
Some users managed to get their phone working by flashing a stock based custom ROM like AMCHA or N4 Elite. If you only flashed the buggy recovery and didn't flash a custom ROM this way should be the step you should try first. Download any stock based custom ROM and flash it via the faulty one. If your phone boots up fine, boot into Download Mode and downgrade recovery or use any other recovery recommended for the ROM you're using. If you encounter issues or weird behavior with your phone go with step 1.
3. Via flashing a fixed TWRP 2.8.7.0 - please note: You might as well lose data
In this option you can flash a fixed version of TWRP which an user of XDA has provided. Many thanks to StdBarbarossa for his work. Unfortunately in his build you cannot mound your SD card via PC as it's not working at the moment. Make sure you have all the needed files already on your SD card. For some users this way was working for them. Boot your phone into recovery, click on install, change from .zip to .image, choose the Alpha17.img, install it by swiping and reboot your phone into recovery. Perform a wipe (preferably a factory reset, cache and dalvik cache might be working too) and see if your phone boots up fine. Here the same: if you're still facing issues go with step 1.
Link for the TWRP Alpha17 2.8.7.0 https://drive.google.com/file/d/0B-tlso-zNf9NMWlMMFpiYmYwTzA/view
I have gone through the same issue. In my case I only managed to get my phone working again with step one as I had flashed a custom ROM via the buggy recovery and ended up in a bootloop. As stated, others have managed to fix their phone with either option 2 or 3.
Link for the fixed TWRP is provided in the spoiler.
If you're not sure about something ask here first before you might brick your phone. If you know any other way to fix this issue feel free to post it here.

Categories

Resources