Related
Try to flash to JH2 (and repartition 512) - the stock B model firmware.
If it fails - try to push one of complete roms (doc_kalpik) and install it using clockwork.
Otherwise have no idea what is wrong.
.....
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Did you perform a repartition when you reflashed ?
ignore me wrong thread!
inshadesofgrey said:
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Click to expand...
Click to collapse
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
i did......still didnt work
Sounds like what mine was doing when the internal SD died.
dupel said:
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
Click to expand...
Click to collapse
will this work even if i didnt have clockwork on my phone?
I flashed the stock JH2 with 512.pit and reparition checked, but the phone goes to the samsung logo, and flash animation and to a blank screen with only the buttons lit up........ah, am losing all hopes really fast.
Now that you are on jh2 take out sim leave external sd inside charge it til full, turn on while and it will boot, saying no memory going internal or external.
So far that would be doa, unless someone found a way to fix or reformat external card but most people that sent it for repair with these symptoms had done doa exchange like me twice or samsung replaced external module meaning it was hardware issue. Sorry.
Sent from my i9000M
it's a long shot, but can I buy an external SD card and run android from there?
I am guessing the only hope is to buy a new phone then?
inshadesofgrey said:
Hi guys, I have been a silent observer of XDA for a while now and you guys have helped through the past 4-5 phones that I've had - but now, I am stuck, so I thought I'll ask for help.
I have a galaxy S (i90000-GT) - originally from Bell, Canada but unlocked. I was running the XJPH with lag-fix and two days ago, when the phone rebooted, it got stuck in a boot loop, samsung logo with black screen comes on, and it starts all over again. Now, I can get into download mode and I followed the process to install JM8, and the stock file (the US Vibrant stock file) and I tried this as well:howto-froyo-fw-i9000xxjpm-upgrade-via-odin-root-recovery-2e-lagfix/[
But to no avail. The boot loop is still there. With JM8, the phone boots up and the goes beyond the flash samsung logo (with the music) but loads to a black screen, with the lights on.
Am really frustrated as this is my only work phone (and I go back to work tomorrow). Without the phone, I am pretty much screwed. I dont care about the Data on the phone (have performed 3-4 data wipes during installing the above mentioned roms) . So anything you can advise, will help!
any ideas?
Click to expand...
Click to collapse
Have you wiped your data/factory reset & wiped your cache? Many phones get stuck at startup because of them.
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Same thing just happened to me, thi is the second time
lighthammerhh said:
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Click to expand...
Click to collapse
Firstly when you get bootloops or any other problem do NOT do a nandroid as it backs up EVERYTHING, including the problem.
When you "wiped everything" did you go to mounts and storage and format system, cache and data?
If not then you didn't do a proper full wipe.
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
econometrician said:
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
Click to expand...
Click to collapse
For 3 weeks... exactly 3 weeks, 21 days?
I can tell you that my first boot loop brick was 20 days after I bought the phone. The second was later that day. But the third one was... again, 20 days after the last successful restore. Is there something magical about the 3-week mark???
I am currently taking nightly nandroid backups, so when I had my third boot loop brick my backup was just under a day old. If this is ultimately a hardware problem that can be warrantied, I guess I'll have to try that next time. I would have to make sure I return it with the bootloader locked, stock recovery, but without the wipe because it has to still be boot looping to prove there's an issue!
Anyway, things I will point out:
- It's the complete wipe in bootloader that blanks the internal storage.
- If you have CWM installed, you can back up the internal storage over USB via adb pull /sdcard/ ./sdcard/ (correct me if I got the syntax wrong)
- When the boot loop brick has happened, CWM is not capable of properly reformatting or restoring to the data partition. I have not found a way to repair it without blanking /sdcard (which on the GN is actually in /data/media), so if you don't want to lose those files the only way to keep them is to pipe them out, blank the phone, and then pipe them back in afterwards.
- After a complete wipe in bootloader (either by flashing userdata.img or by relocking/unlocking bootloader), you must boot the phone once into the OS in order to complete the reformatting of /data. If you try booting straight into recovery after a wipe in the bootloader, CWM cannot read or write from that partition.
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
econometrician said:
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
Click to expand...
Click to collapse
I'll warranty it through my carrier next time as they do exchanges on site. The trouble is, once I've recovered the phone, there's no evidence of the problem anymore. The best way to prove it is to show it fritzing out.
Sent from my Galaxy Nexus using Tapatalk
I think this is a known problem. You shouldn't have to prove it to them. They should be aware of it.
It bricked again today so I warrantied it in-store at my carrier. They gave me a brand new one after being unable to find a solution when fiddling with it. As a bonus, all the little hairline scratches on my screen are gone too
The store guy said he's never seen this issue, and it's one of only two warranty locations for my carrier in the Vancouver area. So I can only hope this was a rare hardware problem and not something that pervades every GN they're going to sell.
I can tell this one is from a different batch because it came preloaded with 4.0.2.
Good for you. hopefully my new phone will behave
Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.
invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.
Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem
same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally
woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop
I have sold my n7105 on ebay running an actual Carbon ROM (4.4.x). (did a factory reset - booted into Android and checked if all personal user data was deleted and sold it that way)
The buyer is now complaining that the device is not starting and stucks at Note 2-device screen. The auction is a month ago and I got the device back yesterday...
In TWRP recovery I see that no OS is installed anymore. Even my microSD is not detected.
In PC Odin I tried to flash newest Samsung 4.3 stock ROM , but Odin tells that PIT partitions is missing!
What has happened to the device? Could an exhaustively discharged battery (and an electric shock) has led to a sudden death syndrome?
TazZHD said:
I have sold my n7105 on ebay running an actual Carbon ROM (4.4.x). (did a factory reset - booted into Android and checked if all personal user data was deleted and sold it that way)
The buyer is now complaining that the device is not starting and stucks at Note 2-device screen. The auction is a month ago and I got the device back yesterday...
In TWRP recovery I see that no OS is installed anymore. Even my microSD is not detected.
In PC Odin I tried to flash newest Samsung 4.3 stock ROM , but Odin tells that PIT partitions is missing!
What has happened to the device? Could an exhaustively discharged battery (and an electric shock) has led to a sudden death syndrome?
Click to expand...
Click to collapse
My only guess, did you run the partition remapper tool found in the N7105 thread?
He made a flash able zip to revert now, if that's the case.
sry, I cant find it..
Is it a tool for repartitioning? Do I need a PIT file then?
Look man, I have Lost my phone Recently Like that
The problem as i thought first, Is in The EMMC card (Sudden death syndrome)
so I have do A JTAG JIG Unbrick for my NOTE 2
But I think that was a big ERROR, because JTAG has failled simply and the EMMC card is gone too...
So I'm now trying to change the Main board but it is too high price for me....
I thing that the loosing PIT Repartition means that the internal MEMORY is dead,
and I'm working hard to find the cause because so many members complain of this problem recently
but what did you do?
I`ve finally managed to mess up my kernel after flashing numerous roms on my galaxy s3 T999. The problem is that my device has bootlooped and I can`t enter recovery mode (due to messed up kernel) and I don`t know where to find a Kernel which can be flashed with Odin.
Can someone please share a link to any kernel for s3 T-999 (it must be in .Tar form please) so that I can fix my phone. Thanks in advance.
I suggest flashing the latest stock ROM via Odin to solve the bootloop issue.
audit13 said:
I suggest flashing the latest stock ROM via Odin to solve the bootloop issue.
Click to expand...
Click to collapse
Thanks for trying to help. The problem is that I can`t find any other S3 rom (in Tar form so that it can be flashed with Odin) other than T999UVUEOH1 (Jelly Bean 4.3). It bootloops over & over no matter how many times I flash it (I think it`s because I cannot wipe cache due to no recovery).
You used ROMs from sammobile.com or updato.com?
audit13 said:
You used ROMs from sammobile.com or updato.com?
Click to expand...
Click to collapse
I tried one ROM from sammobile and another from androidfilehost (uploaded by a developer). Neither of them work because Odin gets stuck at Setup connection. I saw a video in which a guy fixed it by cleaning cache & delvik cache. This is the main issue because my kernel is messed up and I can`t clean cache because the phone just won`t go into recovery mode (neither custom recovery nor stock recovery).
Ashaz93 said:
Thanks for trying to help. The problem is that I can`t find any other S3 rom (in Tar form so that it can be flashed with Odin) other than T999UVUEOH1 (Jelly Bean 4.3). It bootloops over & over no matter how many times I flash it (I think it`s because I cannot wipe cache due to no recovery).
Click to expand...
Click to collapse
Ashaz93 said:
I tried one ROM from sammobile and another from androidfilehost (uploaded by a developer). Neither of them work because Odin gets stuck at Setup connection. I saw a video in which a guy fixed it by cleaning cache & delvik cache. This is the main issue because my kernel is messed up and I can`t clean cache because the phone just won`t go into recovery mode (neither custom recovery nor stock recovery).
Click to expand...
Click to collapse
Flashing the stock 4.3 rom was or wasn't successful?
audit13 said:
Flashing the stock 4.3 rom was or wasn't successful?
Click to expand...
Click to collapse
It was successful every time i`ve done it in the past but it was a mistake to flash it via odin after knowing the recovery is messed up and disappears a few minutes after flashing (doesn`t matter which one I flash, I`ve tried multiple recoveries but they all behave the same due to problems with kernel). I believe that is what caused it to bootloop. I then went on to flash stock 4.3 several times but it bootloops on the samsung logo every time. Now finally i`ve encountered a new error which doesn`t lets odin to flash ROMs or Recovery. It remains stuck at SetupConnection the entire time.
BTW This phone is a 5 year old device and is not my primary device (Ever since I got the LG g5) but still it`s very dear to me so I started this thread. I don`t use it as much as I used to before but I still want to keep it alive (as long as it doesn`t dies on it`s own).
I need to find a way to clean cache from PC. I don`t think there`s any other way to save a phone in this kind of situation.
Try this: open Odin, uncheck everything except F reset time, flash. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use key combination to get into stock recovery, factory wipe, reboot.
If this still doesn't work, the phone's internal memory chip may be defective.
audit13 said:
Try this: open Odin, uncheck everything except F reset time, flash. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use key combination to get into stock recovery, factory wipe, reboot.
If this still doesn't work, the phone's internal memory chip may be defective.
Click to expand...
Click to collapse
IT WORKED!!! :victory:
Unchecking everything except F reset time did the trick. How did you come with that ? You saved the day with that man. Thank you so much for showing up and taking the time trying to help me. I would not have been able to fix it without your help.
You should make an instructional thread for people facing this issue with Odin on any phone. I`m pretty sure it will help a lot of people who are stuck at SetupConnection when trying to flash ROMs. Thanks a lot for helping me out. I`d give you 500 if I had more accounts
Take care of yourself and keep up the good work audit13. :good:
Glad you got it working. We're here to help and learn from each other.
I learned the "uncheck" trick years ago when I started flashing the galaxy s2.