Samsung Galaxy S3 LTE i-9305
Hello everyone, first post and I need help :crying::crying:
Today I tried backing up my rom on CWM recovery but it was always getting stuck on "Generating MD5 sum"
So I decided to switch to TWRP. I downloaded the TWRP app from the play store. I picked my device, picked the latest
version and downloaded. Then the app asked me if I wanted to reboot into recovery (something like that, I don't exactly remember what it was) and I pressed yes. The phone turned off and rebooted however I don't know what happened but now my phone is starts, shows the [Samsung Galaxy S3 LTE i-9305] screen for about 3 seconds then goes black and again shows the [Samsung Galaxy S3 LTE i-9305] screen repeatedly. I don't know what to do :crying:
My phone is rooted with CM11 flashed. So I can't give it in for a repair as they would be able to tell if I am rooted because of the KNOX warranty void: 1 thing :crying::crying: What can I do now??
NOTE: I can't reboot into recovery, only bootloader.
can you reboot into downloading mode ((home+power+volume-)?
if yes, with odin, try to flash again the recovery (i prefer PhilZ recovery on my i9305) and later try to backup your phone.
LeoDeos said:
can you reboot into downloading mode ((home+power+volume-)?
if yes, with odin, try to flash again the recovery (i prefer PhilZ recovery on my i9305) and later try to backup your phone.
Click to expand...
Click to collapse
Ok I done that but with TWRP and it works, factory reseted and flashed cm11 again. It is booting up right now thanks alot for the help
Related
Hi guys. I was hoping that maybe some of you genius's maybe be able to help me out? I will try and explain my problem as clearly as possible.
I have an I9305 and an from the UK. I have rooted my phone before and used many custom roms. But quite recently I decide to unroot my phone and go back to a normal stock rom. Last week I got the urge
to root again and install some custom roms. I quickly discovered that since I had OTA my phone that the latest OS has problems (knox) with rooting. I did manage to root my phone. However, the problem started when I tried to install
twrp through Goomanager. I tried to reboot into recovery mode and my phone was stuck on the Galaxy S III splash start screen, and I could not get into recovery mode either. I could still get into download mode. Eventually I did manage
to restore my phone using odin, and install a stock rom for Ireland. After this I tried to install a stock from for the UK, and now my phone is now back to being stuck on the splash screen, and I can not enter recover mode on my phone
using the up/home/power combo, but I can still acces download mode and conect to odin. I have been searching on line for several days for some solutions and fixes, but I seem to be getting no where. So please, if you can help my out and hopefully get my phone back to life I would
be extremely grateful.
If you can boot to download mode, then have you tried to flash a custom recovery with odin? If its twrp you want then flash the twrp tar for i9305 which you can get off the team win website and then see if you can access recovery. If you can, then you should be able to flash a samsung 4.3 rom or cm rom from external sd if you don't have one on your internal or even restore a backup if you have one.
AllianceROM I9305
Thanks for your reply. Yes, I have tried to flash cwm and twrp using odin. They seem to flash fine, but I can not enter recover mode at all. I have also tried to flash some custom roms and they also seem to flash fine, with no errors, but my phone is still stuck on the boot logo. Thanks for any more help.
daytimeKnight said:
Thanks for your reply. Yes, I have tried to flash cwm and twrp using odin. They seem to flash fine, but I can not enter recover mode at all. I have also tried to flash some custom roms and they also seem to flash fine, with no errors, but my phone is still stuck on the boot logo. Thanks for any more help.
Click to expand...
Click to collapse
im afraid like me, your stuck on 4.3... download the offical rom and odin it across to your phone, you will not be able to root your phone from now on, your stuck stuck with stock 4.3.. you cant even enter recovery mode thanks to knox.. just the download mode.. like i said in my post "UP YOURS SAMSUNG" IF I EVER SEE YOU IN THE STREET ILL KNOX YOU OUT LOL
relating btuali
Thanks for you replies and help so far. It would be good if I could flash 4.3 through odin, but unfortunately after each successful flash, my phone remains on the sIII logo screen. Maybe there is a specific rom that you guys could recommend that I try? Thanks once again.
Hi there. A big thanks for taking the time to help and give advice. I now finaly have my phone working again. I used Odin 3.7 and the latest official rom, entitled "I9305XXUENA1_I9305SIOENA1_SIO.zip" Odin froze and stalled a few times trying to install but after a few tries it worked. I can now also get back into recovery mode now. So, I was wondering might it be a good idea to do the normal wipes in recovery mode. ie wipe cache, etc. Thanks once again.
Yes keep it clean...
Raistlin1158 said:
Yes keep it clean...
Click to expand...
Click to collapse
Will do.:good:
I started with a new S3 Mini (Branding Android 4.1.2 ). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).
Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. but odin don't work Flash installed programs goldenxx_PIT_file put the boot in place. Handset is stuck on the logo. downloading mode is used, but is not recognized as a odin. Recovery dont goes. Zune does not have any drivers. Several specialists have failed. PLEASE HELP ME
Hpou said:
I started with a new S3 Mini (Branding Android 4.1.2 ). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).
Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. but odin don't work Flash installed programs goldenxx_PIT_file put the boot in place. Handset is stuck on the logo. downloading mode is used, but is not recognized as a odin. Recovery dont goes. Zune does not have any drivers. Several specialists have failed. PLEASE HELP ME
Click to expand...
Click to collapse
what version of odin have you used?
please provide the link to the pit file that you used and step by step of what you have tried so far not missing out a detail
the more information provided the better the solution
hope you didn't pay the "specialists"
efaustino84 said:
what version of odin have you used?
please provide the link to the pit file that you used and step by step of what you have tried so far not missing out a detail
the more information provided the better the solution
hope you didn't pay the "specialists"
Click to expand...
Click to collapse
thanks for reply
but here are problems:When I turn on phone it stay in the logo and that will not go to recovery. downloading mod to go but no matter how I tried a few specialized Android phone by Odin we have not even tried to know..nothing nothing
Hpou said:
thanks for reply
but here are problems:When I turn on phone it stay in the logo and that will not go to recovery. downloading mod to go but no matter how I tried a few specialized Android phone by Odin we have not even tried to know..nothing nothing
Click to expand...
Click to collapse
Can you post a log from odin?
Sent through time and space from my s3mini/CM11
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?
grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.
User_99 said:
Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?
Click to expand...
Click to collapse
I have the Stock Samsung Android 4.1.2 installed. I'll try it again with an older kernel. Thanks for your help.
nokiamodeln91 said:
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.
Click to expand...
Click to collapse
I tried it several times, also after removing the battery. no success. Is is necessary to use ODIN? I use Heimdall as I mentioned, because I am running Mac OS.
I'll try it with a different kernel and report back here about my results. Thanks a lot.
Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.
What
grosserzampano said:
Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.
Click to expand...
Click to collapse
Install terminal emulator and try the command
su
reboot recovery.
Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.
grosserzampano said:
Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.
Click to expand...
Click to collapse
May be the recovery partition is messed up due to the usage of rom manager earlier. Try to flash a stock rom.
grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
go to download mode and flash stock rom of note 1 via odin then after successful installation u can go to recovery mode and install this zip ur phone will be rooted and phliz touch will be installed
for any help u can PM me
Hi thanks for reading,
i flash my rom from virginity v14 to cm 10.2 via twrp
its now stuck on bootloop
i downloaded a origianal stock rom l8190XXAMJ2
flash it with odin 3.07
still in boot loop
then i flash a Param IB190
Still in loop
Then i flash a goldenxx-Pit-File
still in loop
it says on the download screen:
GT-I8190N
Custome binery download: YES (16 Counts)
Current Binary: custom
System Status : custom
"have i miss a file"?
the phone comes on shows samsung model number and goes off again
i can access download via pressing 3 buttons
but cant access recovery
any ideas what i can do now.
Really appreciate any help as i really luv this phone!
Thanks for reading
Kind Regards
FAM0422
It sounds very much like the same kind of problem that I am having, but the phone I am trying to fix is 100% stock.
Here is my post: Samsung Galaxy S3 Mini GT-I8190N - Stuck in bootloop
If you do find a fix for your problem please do report back.
Thanks for your time.
Best Regards.
i fix the issue by using odin 3.07 and using the firmware below
I8190NXXALL6
http://forum.xda-developers.com/showthread.php?t=2122548&highlight=root
i went to download mode
and flash the firmware.
it then booted normally then i had issue with encryption but i solve this easily by going back to custom recovery and wipe data cache etc.
Hope this works for you
TWRP
In TWRP make factory reset and clear dalvik and cache! That should do it!
Thanks for the info, but unfortunately this has not worked with the phone in question and I am still having the same issue.
Hi guys,
I was triyng to enter recovery with my SGSA 'cause I wanted to do a nandroid backup,
I pulled volume up+power+home like other times, but my phone didn't go into recovery but got stuck on "Samsung galaxy s advance" logo, and then it turned off, and rebooted, and now it's something about 1 hour that is rebooting . I can't enter recovery and now even boot, I can only enter in download mode. What should I do? I'm on Vanir by mkaluza and Mk kernel r6, and I didn't flash anything else after flashing the kernel.
P.S.: Now flashed Stock rom by Odin, same problem: the phone constantly boots, but now it enters in recovery. Please help me
edoardotavecchio said:
P.S.: Now flashed Stock rom by Odin, same problem: the phone constantly boots, but now it enters in recovery. Please help me
Click to expand...
Click to collapse
Flash one more time stock jb with Odin, and then see if it boots. If it doesn't, try to wipe data and cache.
Force said:
Flash one more time stock jb with Odin, and then see if it boots. If it doesn't, try to wipe data and cache.
Click to expand...
Click to collapse
I've tried it, but it did'nt work . I think it's something in efs, so I can't do nothing, 'cause via Odin there's no way to restore efs backups. Tomorrow I'll go buying a new phone. Anyway, thanks for your help man. Goodbye guys