Comming from stock ROM every new ROM I'm trying to flash just hangs on a boot logo (animation) of CM for example. Phone was wiped fully several times using TWRP and Cyanogenmod Recovery (/system, /data, /cache, /dalvik-cache).
Any help, please?
what version of twrp are you using? i've had the same issue with twrp 2.8.7.0. It seems to be buggy.
Try another version. 2.8.5.0 works fine for me.
// you might need to / want to / have to restore your phone to stock rom AND recovery first.
Agree with the possibility of TWRP problem.There is a version 3 out now which might work but 2.8.5 is definitely OK. Philz recovery should also work.Make sure these are the correct versions for phone.HTH.
Flash recovery via Odin. Firstly make sure you are using recovery made for our phone. To be honest, I prefer TWRP, and I am using 2.8.5 as I remember. Also, which roms you tried ? I had CM 12.1 and CM 13, and they worked totally fine, but I just loved more stock 4.4.4 so I downgraded.
Related
Hello XDA Developers!
I'm trying to install a custom rom om my i9305 bought in Denmark.
So far I have gotten the TWRP and Cyanogenmod recoveries to work, and through those I have successfully installed the two last versions of CM11 nightlies for the i9305 and the two last versions of AOSB 4.4.4 for the i9305. Yet I can't get any of them to boot past their respective logos (the phone moves nicely past the Samsung Galaxy S3 logo).
I have tried full system++ wipes, multiple Dalvik cache and cache wipes and Factory resets etc, but whatever I do my phone never gets past the CM / AOSB logo. I have waited for 20 minutes once for CM11 and once for AOSB, and 5+ minutes multiple times on both. Nothing changes.
Is there anyone out there with a 9305 that successfully installs custom ROM's that can help? Any help is greatly appreciated as I'm currently without a working phone
PS: Sorry if this is already an answered question. I googled extensively and looked at all the suggested threads before clicking "Submit" and couldn't find an answer.
Technical info:
Heimdall (latest unofficial from developer to get it working with OS X El Capitan)
Android Studio 1.4 with Platform Tools installed today
TWRP 2.8.7.0
Two latest nightlies from the official Cyanogenmod page attempted (I'm not yet allowed to post links), through TWRP as well as the recovery
Two latest versions from the AOSB website (still not allowed to post links, sorry)
MaHo_66 to the rescue
I was able to bring my phone back using the 9305N ROM posted on /galaxy-s3/development-i9305/rom-samsung-stock-4-4-4-rom-collection-t3124027
Still curious why it didn't work with the others, but at least now I have a phone again.
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
maultasche said:
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
Click to expand...
Click to collapse
Thanks for the reply! I also tried with the CyanogenMod Recovery, which ended the same way.
But installing a custom ROM based on stock worked, and is both way faster and pulls way less battery than the original ROM. So it all worked out in the end (until I can't resist the temptation and try to do it all again).
kamikaze702k said:
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
Click to expand...
Click to collapse
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
elysium7 said:
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
Click to expand...
Click to collapse
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
kamikaze702k said:
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
Click to expand...
Click to collapse
Nice, thanks! I'll try cwm next time then
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!
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.
Hi all!
I flashed my recovery to TWRP and ever since then, I always get stuck in bootloop no matter what custom ROM I try. Flashing back to stock rom via ODIN works.
It's been a while since I've tinkered with custom ROMs so I may be missing something. Any ideas on where to start?
joshbeoulve said:
Hi all!
I flashed my recovery to TWRP and ever since then, I always get stuck in bootloop no matter what custom ROM I try. Flashing back to stock rom via ODIN works.
It's been a while since I've tinkered with custom ROMs so I may be missing something. Any ideas on where to start?
Click to expand...
Click to collapse
Hi,
Which phone ? i9305 or i9300 ?
Which version of TWRP do you use ?
You should try latest version of TWRP (2.8.7.3).
Or try Philz touch Recovery 6.48.4 or 6.59.
1.Repeat ODIN step to stock rom
2.Root the phone by kingroot (as it's doesn't required pc)
3.After rooting, Download Cwm rom manager
4.Install Cwm by selecting your phone model and etc
5.flash it directly from the apps
6.now you can flash any rom ( please backup your system for your safety)
Hello, just bought an used i8190. Since last friday i have been trying to flash a custom recovery on this phone via Odin, but after i flash it returns to the default recovery on next boot.
Yes, i have unchecked the "Auto-reboot" option on Odin. I turn off the phone and then manually enter recovery but with no results. I rooted the phone pretty easily and installed both TWRP and CWM apps to flash from android, but they don't work either (twrp crashes always and CWM just gives me an error.
Mi baseband model is XXAll2
kernel is 3.0.31 [email protected] (root name seems weird)
I searched the forum and found similar cases with the baseband, but even so i haven't found a concrete solution.
I even flashed a new pre-rooted rom from this thread: https://forum.xda-developers.com/showthread.php?t=2030282
Mi compilation number has changed to XXAMG1 but the baseband remains the same. I can't flash a recovery whatever i try.
I hope someone can give me an answer, cause i really want to use this phone feautures to it's fullest
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Glass_Arcana said:
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Click to expand...
Click to collapse
Flash the stock rom as it will fix bootloops and bricked devices. Make sure to have the right ROM and flash it with Odin. The os may take longer on first boot and make sure to factory reset it as data may cause bootloops, then try flashing the recovery.
I flashed twrp 3.1.1 through Odin