Related
Guys need some help here,
I have a vibrant and there has been times that I have flashed a 2.2 froyo rom to repair the data partition on my internal sd card from a bad flash when a lag fix is applied.
I talked a friend into getting a captivate because he loved my vibrant so much. I had him running a stock rom, with unhelpful lax fix kernel and everything ewas gravy for two days until today. he said he got a sd card error, and the phone wont boot past the galaxy s logo, I tried one click odin from this forum, now the phone wont boot past the att logo, because it fails to wipe the data partition.
Can we use the vibrant fix for the captivate? I could try to lash that froyo thru odin and see if it helps, the phone doesnt need to boot up, I just need to flash and wipe the internal sd tru odin. any suggestions
Thanks in advance
Devin5277 said:
Guys need some help here,
I have a vibrant and there has been times that I have flashed a 2.2 froyo rom to repair the data partition on my internal sd card from a bad flash when a lag fix is applied.
I talked a friend into getting a captivate because he loved my vibrant so much. I had him running a stock rom, with unhelpful lax fix kernel and everything ewas gravy for two days until today. he said he got a sd card error, and the phone wont boot past the galaxy s logo, I tried one click odin from this forum, now the phone wont boot past the att logo, because it fails to wipe the data partition.
Can we use the vibrant fix for the captivate? I could try to lash that froyo thru odin and see if it helps, the phone doesnt need to boot up, I just need to flash and wipe the internal sd tru odin. any suggestions
Thanks in advance
Click to expand...
Click to collapse
Have you tried flashing in the plain voodoo kernel (atinms thread is around here somewhere) to see if you can get the thing to boot at least?
I have already tried to odin to stock, which didnt work and I knew that. The problem is I cant disable the lag fix, because the phone wont boot all the way up.
What we did in the vibrant forums was to flash a 2.2 thru odin. ( it automatically wipes internal sd and formats it back to original state.) then flash stock reroot and we are all happy again.
Is there anything like this for the captivate?
Unless i am missing something, which I could very well be flashing a kernel wont help the data partition problem will it?
what if you took the stock firmware from samfirmware.com and did a normal odin flash with the repartition selected?
I'm a noob but that seemed like a logical thing to try.
Devin5277 said:
I have already tried to odin to stock, which didnt work and I knew that. The problem is I cant disable the lag fix, because the phone wont boot all the way up.
What we did in the vibrant forums was to flash a 2.2 thru odin. ( it automatically wipes internal sd and formats it back to original state.) then flash stock reroot and we are all happy again.
Is there anything like this for the captivate?
Unless i am missing something, which I could very well be flashing a kernel wont help the data partition problem will it?
Click to expand...
Click to collapse
That doesn't really answer my question... I asked if you had tried booting it again with a plain voodoo kernel. Obviously the full flash didn't work for some reason, and now your internal SD isn't being detected... which is strange. You could conceivably try flashing pretty much anything you've used on the vibrant though to see if that helps.
Did you do the Master Clear before flashing with Odin?
nooomoto said:
Did you do the Master Clear before flashing with Odin?
Click to expand...
Click to collapse
no, my phone wont boot up to do a master clear. After doing some research it seems that the internal sd card got currupted. when I tried to clear data it failed on me, and gave me a cant mount data error in stock recovery
Devin5277 said:
no, my phone wont boot up to do a master clear. After doing some research it seems that the internal sd card got currupted. when I tried to clear data it failed on me, and gave me a cant mount data error in stock recovery
Click to expand...
Click to collapse
you can master clear with the one click odin. Its the big button to the right of start that says master clear
xetrev said:
you can master clear with the one click odin. Its the big button to the right of start that says master clear
Click to expand...
Click to collapse
I tried 3 times, It just hangs. I think the internal sd got unmounted somehow.
xetrev said:
you can master clear with the one click odin. Its the big button to the right of start that says master clear
Click to expand...
Click to collapse
You have to have the phone booted and in USB Debug mode for the odin master clear to work, this person can't get the phone to boot. Is there another way to put the phone in USB Debug mode when it will not boot?
So repartition doesn't work?
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm having the same issue
h t t p:/ /forum.xda-developers. com/showthread.php?p=8340023#post8340023
I did try flashing in a voodoo complient kernal (although not atinm's) but it still won't boot...
Isn't there an i9000 2.2 rom that can be flashed to captivate?
Try the jpk tomorrow on the i9000 forum. I was able to go back from it to 2.1.
Sent from my GT-I9000 using XDA App
http://forum.xda-developers.com/showthread.php?t=790637
You may be able to just grab the 803 pit from samfirmware and then put it all back with the 512 when your done *shrug*
yadda yadda yadda not responsible for your phone blah blah blah
Sherpa
I did some experimenting on my friends captivate, only because he was going to take it back anyway . It was stuck in the bootloop because of the ota software update, then had a failed to mount error.
If you dont have a failed to mount error, your internal sd is not corrupted, it just needs to be repartitioned.
The way I was able to get my internal sd repartitioned, so I COULD flash back to original 2.1 stock was to odin flash a 2.2 rom, then odin the stock. So if you can find one that is ok for the captivate try it.
now let me make myself clear, you dont have to have the 2.2 reboot fully, you just need it to repartition the internal SD. As a matter of fact, the one in the vibrant forums doesnt even boot all the way at all, its just a tool for us to get back to 21. original firmware.
so try it out.
1. odin flash the 2.2 rom let odin do its business,
2. get back into downloader mode and odin flash back to stock.
it worked for me on my vibrant. I hope it can work for others.
flashed xxjpk and back to stock. Still get mount errors.
kakalaky said:
flashed xxjpk and back to stock. Still get mount errors.
Click to expand...
Click to collapse
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
this might shed some light on the failed to mount error. Its definately an SD card issue.
@devin5277 will the parted linked to in the post you linked to work with the captivate? If its just a generic linux partitioning tool thats run through adb i think it should.
parted works fine on the captivate. In my case it didn't help though. Rooted then tried ffdisk and parted. Both give I/O read errors on /dev/block/mmcblk0. Looks like the internal sdcard no longer works.
I was out today, minding my own business.
In the middle, my phone just shut off. Restarting it, it would not boot past the kernel boot screen, not even into CWM. When I got home, I oneclicked it to stock in an attempt to return to my nandroid CM7 from right before the full-9 package was released. I encountered an issue.
CWM3 said "Error: Can't mount /sdcard". Booted the phone up in JF6, and the storage menu shows both my External and internals reading with total and available space as "Unavailable", and both the mount and format options on both are greyed out. Internal phone storage is normal, however, and reads 1.73GB.
Don't ask me to flash Froyo or something. Standard 2e recovery does not allow me to use a ROM Manager flashable CWM2, thus I cannot flash Froyo or CM7's package. CM7's initial kernel returns the "Can't mount /sdcard" error, so that's also inadequate.
So, anyone have any idea what I'm dealing with here? How would I be able to go about fixing it? If it helps, my IMEI number and all that jazz is still present.
EDIT: I just realised a perplexing quality. The phone will ONLY boot with an external SD in it... Doesn't matter if I remove it after, it just needs an external in it to boot. Once the phone boots, it's dead weight. Funny, as I always flash without it in there...
EDIT2: Found some info from Supercurio on the Bell Vibrant while searching, I wonder if this is relevant...
supercurio said:
On #project-voodoo IRC I helped a user who had issues with his SDcard on a Bell I9000M
Turns out that his internal SD MoviNAND chip was dead!
The system automatically used his external SD as a backup for /data, as the "mmcblk1" device become "mmcblk0".
The internal SD was so dead that the Linux Kernel didn't detected any existence of it anymore.
The symptom that the phone was working (using the external SD) but he couldn't mount his SD card anywhere.
Eventually he had a replacement from Bell in a few days.
What killed the sdcard ? An old Ext2 lagfix when creating the giant 1GB+ loop files.
But it wasn't the lagfix fault. It just acted as accelerator.
Click to expand...
Click to collapse
But I've never used that lagfix. I've been on Speedmod then CM7 the entire time.
Maybe flash a kernel with CWM in it, such as speedmod with Odin though I'm clueless as to what happened to your phone. I guess do this, flash a new ROM go from there... Sorry this is my only idea.
emcnelly said:
Maybe flash a kernel with CWM in it, such as speedmod with Odin though I'm clueless as to what happened to your phone. I guess do this, flash a new ROM go from there... Sorry this is my only idea.
Click to expand...
Click to collapse
Already said, CWM returns "Can't mount /sdcard" in CM7's CWM3 from the initial kernel... I can't flash Froyo, so Speedmod is out of the question.
Thread moved.
I'd try flashing a full odin stock rom and a .pit with it with repartition checked. I heard someone else with this sort of problem, he used odin one click but still got the same thing, flashed stock gb with a .pit and it worked.
studacris said:
I'd try flashing a full odin stock rom and a .pit with it with repartition checked. I heard someone else with this sort of problem, he used odin one click but still got the same thing, flashed stock gb with a .pit and it worked.
Click to expand...
Click to collapse
Did not work; tried flashing JH7, KB1 and JF6, all 3 do not boot past the kernel screen. Only OCD JF6 gets the phone in a working way. I found some other threads, but it's looking worse and worse by the second.
ATT is probably getting a call tomorrow...
Same happened to me, I managed to get JI6 working somewhat. Flash the one click ODIN JI6, wait till bootanimation ends, ROM will not boot up completely so go back into download mode, then flashed speedmod with three button ODIN, let boot up complete then go into recovery and delete user data, wipe cache and dalvik cache.
Still don't have an mnt/sdcard but at least I can make a phone call.
Also, I lost data connection so I had to manually enter APN in settings, wireless and networks, mobile networks, Access point names and create a new APN, I just googled AT&T APN for the values.
Hope it works out as I'm probably going to contact AT&T as well.
I had that happen kinda with "cognadian bacon" it fried my sd card and I flashed odin one click then master cleared in odin. After that I booted up and got my format option back ..... If that doesn't work you could probably hook it to computer (windows) and go under device management and format from there but don't know if will support fat32.. Just a suggestion though.... That what I did for my external sd when it wouldn't recognize it
Sent from my GT-I9000 using XDA Premium App
So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.
Can someone help i was running cm9 for a year then i decided to update to jellybean(cm10.1) it was working fine for a few day then out of nowhere the phone turned off and would only boot into recovery so i tried to factory reset it passed but it still would'nt boot into rom so i tried to install cm9 back but that was a no go. i decided to flash back to jvu. after i did that it booted into recovery it said failed to mount /sdcard. can anyone help?
sorry for a lack of punctuation, im panicking.
original issue idk.
current issue : ics bootloaders with non ics rom.
go back to stock bootloader.
to the jvu bootloader?
http://www.youtube.com/watch?v=1RoZU5ZPMS4
try this see if it fixes it goodluck
Did you manage to fix this I have a second SGS like this too.
Seems the internal memory is unmounted the only way to get it to boot was to partition SDCard and boot from that.
Nope I'm just gonna buy a a SD card class 10 and use it
flash darky ROM 10.2 through odi will get it to boot worked for mine
Jesus, third person I've told this to tonight lol
Its not bootloader.
If it happened straight after you flashed back to gingerbread then all you need(ed) to do was flash dbdata.rfs in Odin as PDA and you're done... All good again... Reboot...
No need to go buying SD cards heh
Sent from my GT-I9000 using Tapatalk 2
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7
PHP:
MaHo_66 said:
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7
Click to expand...
Click to collapse
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?
likeasir said:
PHP:
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?
Click to expand...
Click to collapse
Hmm... Good question. I understand your issue here but im afraid i cant answer this.. While it was working what firmware was running on it? What baseband? If you have any kind of info of the working firmware, analyze it with firmwares on those sites and try to find the one you need.
Sent from my GT-I9305 using XDA Premium 4 mobile app
likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days
likeasir said:
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days
Click to expand...
Click to collapse
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.
likeasir said:
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.
Click to expand...
Click to collapse
Cheers on getting ur phone fixed but after wiping all directories a stock rom flash would have cleared all the problems
lol i just did this to my phone, time to find a stock firmware.