I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
jay-red said:
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
Click to expand...
Click to collapse
Im stuck in the same boat with my S4
which ODIN version are you using and are you using the links from SAMMOBILE to get the firmware you need ? also what are your methods of procedure and is odin giving out any errors or saying pass and still no boot ?
Related
So, i have a Samsung Galaxy S III i747... Flashed it with CyanogenMod, and saw horrible battery life, and the phone stayed hot... Flashed back to an older version of CyanogenMod, and it was just unstable and a mess, so i formatted everything from recovery, and installed the stock ROM via Odin... Stock ROM worked, but i wanted back to Cyanogen, so i rooted the phone, downloaded the ROM manager, downloaded the ROM, and installed it... And it failed. So, i figured i'd hit the NAND Erase All button in Odin, and then repartition the phone, thinking the buttons wouldn't blow up the world... Now i'm stuck at the Samsung logo at boot. I've tried several different versions of the stock ROM, i can still get into recovery, and i can still get into download mode, but it always get stuck at the Samsung Logo after the AT&T carrier video.
Anyone have any ideas? I'm really hoping i didn't brick my phone... Odin sees it, and everything still works, i just can't boot the stock ROM, which means i can't get anywhere else.
try a factory reset in recovery after flashing rom
PhoneTamer said:
So, i have a Samsung Galaxy S III i747... Flashed it with CyanogenMod, and saw horrible battery life, and the phone stayed hot... Flashed back to an older version of CyanogenMod, and it was just unstable and a mess, so i formatted everything from recovery, and installed the stock ROM via Odin... Stock ROM worked, but i wanted back to Cyanogen, so i rooted the phone, downloaded the ROM manager, downloaded the ROM, and installed it... And it failed. So, i figured i'd hit the NAND Erase All button in Odin, and then repartition the phone, thinking the buttons wouldn't blow up the world... Now i'm stuck at the Samsung logo at boot. I've tried several different versions of the stock ROM, i can still get into recovery, and i can still get into download mode, but it always get stuck at the Samsung Logo after the AT&T carrier video.
Anyone have any ideas? I'm really hoping i didn't brick my phone... Odin sees it, and everything still works, i just can't boot the stock ROM, which means i can't get anywhere else.
Click to expand...
Click to collapse
I Odin'd to stock a couple days ago and was at the Samsung Logo for a WHILE (over and hour). It did just go eventually.
Not sure what did it... Got a PIT file, and then did the NAND Erase All bit again when i installed the stock ROM again. Wiped data as soon as install finished, and it booted right up. I'm happy again
Now if i can just figure out the LTE glitch...
Okay here is the problem guys. I have my note three for three weeks now. Rooted it day one. But It seems with every phone I have addiction with flashing roms. I change around a lot. I have owned four devices this year. S4, note 3, nexus 4 and galaxy nexus. Rooted every device never had an issue that couldn't be fixed by flashing the stock tar via odin. The other day I flashed compulsion kernel and put me in a boot loop. So I did the natural thing and download the stock tar and flash via odin. First time was a bust. It said it was successful. Still put me in boot loop so I downloaded the stock tar from another location and tried again. Still no dice and still have boot loop. Tried flashing a custom rom after flashing the stock tar. Nothing still boot loop and I've also tried different recoveries and still nothing. I know its not hard bricked because I can still boot into recovery. I am actually a sales rep at a corporate tmobile store and did a warrarnty exchange and they are overnighting me another note three and I am going to send this one back. Little concerned as to having the rooted status on the device is going to go over. A couple times after I flashed the stock tar I got it to boot but then it would say "process system stopped responding wait or ok" then after clicked okay it reboots. I really hope there is someone out there with a solution.
HELP
This isnt your usual soft brick. If someone could please help I would appreciate it!!
Dude my phone out of nowhere bricklooped today like literally. I installed different roms no dice. 3 backups including the stock one and nothing still bootlooped I tried the brickloop fixer on jovys darthstalker v6 and I'm back up and running but if I reboot or turn off phone and reboot it goes into same bootloop he's a smart, brilliant dev I'm sure he can help me out as well as you
Sent from my SM-N900T using xda app-developers app
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.
allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.
So here's the back story. I'm usually good with roms/recovery/flashing. Even did some custom rom work on my old Galaxy S 4G, so not a noob. I have a Wind T999V.
Had Touch-CWM installed, ran a few 4.4 ROM's for a while, tried LP, Liquid smooth. Liked it ok, but wanted to try OctoROM LP. It needs TWRP. Had a few problems with TWRP before on my phone, the Wind variant seems somewhat different in small ways, but figured I'd give it a try again to flash OctoROM since it needs TWRP. Thought maybe the TWRP has improved since I tried last, so installed TWRP, tried to flash Octo, but TWRP wouldn't see my internal SD card at all. The same problem I had before. I didn't feel like digging out a SD card from my camera to put Octo on, so rebooted the phone, installed CWM back, rebooted again, got a bootloop somewhere along the way.
Figured I'd go with Odin back to stock and start over. Grabbed odin (hard now, lots of spam/scam copies) and my stock firmware for the Wind version from Doc's thread. Flash the tar, which took forever (used a sort of crappy cable) and it auto rebooted after like 20 mins of flashing, just stuck at the sammy logo for like 20 mins. Too long, still looped I think.
Grabbed a different cable and a newer version of a good odin I know from my network I had laying around, 3.09, and tried again. At the pulsing samsung logo again, going to wait, but if I did softbrick it, do I need to repartition and a pit file to get the FS back to something different than any of the KK or LP rom's I ran?
EDIT:
Read some threads and took doc's advice and booted into stock recovery and wiped data and cache, and it finally booted. Phew.
I unrooted my phone ages ago, havent done anything to it since, but yesterday my phone just decided to cut out, started with apps not loading, then my phone wouldn't turn on, now my phone just gets stuck into bootloop
How do I determine which stock firmware to go back to via Odin?
My phone is UK, and unlocked
When i try to go into recovery, I get the following
RECOVERY BOOTING....
SET Warranty Bit: Recovery
and it's driving me nuts, Ive tried installing a UK firmware that I believe might be the one, and Odin doesn't come back with any errors, but the same damn message applies, as far as I know, once you can get recovery working and clear cache, you should be fine, but I just cant get it to work
I've tried installed custom bootloaders, but same ol same message
Gimba89 said:
I unrooted my phone ages ago, havent done anything to it since, but yesterday my phone just decided to cut out, started with apps not loading, then my phone wouldn't turn on, now my phone just gets stuck into bootloop
How do I determine which stock firmware to go back to via Odin?
My phone is UK, and unlocked
When i try to go into recovery, I get the following
RECOVERY BOOTING....
SET Warranty Bit: Recovery
and it's driving me nuts, Ive tried installing a UK firmware that I believe might be the one, and Odin doesn't come back with any errors, but the same damn message applies, as far as I know, once you can get recovery working and clear cache, you should be fine, but I just cant get it to work
I've tried installed custom bootloaders, but same ol same message
Click to expand...
Click to collapse
Did you tried to make an custom ROM on your SD-Card?
Your right Firmware is on Sammobile by the way