Stumped! - Samsung Galaxy Nexus

Now I know what your going to think. Oh god heres another person who's phone is in a bootloop. He hasnt read anything and is trying to get some help. Ive been on these forums since the G1 came out and I've been flashing roms since the first Cyanogenmod. Im stumped. I used the Nexus toolkit to root and unlock my freinds Nexus. Everything went well considering I was using his horrible excuse of a laptop. I accidentally dragged the wrong file onto the nexus and when I tried flashing it, it got stuck in a bootloop. I couldnt mount the sd from clockwork mod so I continued to use ODIN and flashed back to 4.0 It booted up beautifully I got the first update that puts it on 4.0.4 then the second update that puts the system on 4.1 The problem is now that after I do the ota update it gets stuck into a bootloop just as it did when I first flashed the original file by accident. It stays stuck at the X logo screen. Ive tried to ODIN back to 4.1 it wont allow it it stays at the X just as if I did the OTA update. I tried flashing cyanogenmod same problem. I checked up on the radio and although I dont have it now I remember It was compatable with the jellybean update. Im stumped. If anyone can give me a hand please do ive checked across all forums tried doing what theyve said but im always back to this damn X logo!!!!

Reflash the stock images in fastboot

http://forum.xda-developers.com/showthread.php?t=1626895

Related

Stuck at "Samsung" screen after odin flash

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 ?

(HELP) Possible soft brick

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

cyanogen mod will not come off my phone

hi guys i need some help i downloaded cyanogen 11 lastnight just because my phone kept prompting me to update and i was rooted. I installed it and immediately noticed that i can not see my sd card, after researching i saw a couple of people was having the same issue. I tried to recover from the backup i made and it make my phone get stuck in a endless loop after about 10 hours of trying to get in recovery and failing it finally let me in and started loading the rom again. I keep trying to replace the rom with other roms and the phone will not see any of roms to push i tried odin and that failed as well . can someone help me get this stupid rom off my phone i tried everything.
Darkmanx said:
hi guys i need some help i downloaded cyanogen 11 lastnight just because my phone kept prompting me to update and i was rooted. I installed it and immediately noticed that i can not see my sd card, after researching i saw a couple of people was having the same issue. I tried to recover from the backup i made and it make my phone get stuck in a endless loop after about 10 hours of trying to get in recovery and failing it finally let me in and started loading the rom again. I keep trying to replace the rom with other roms and the phone will not see any of roms to push i tried odin and that failed as well . can someone help me get this stupid rom off my phone i tried everything.
Click to expand...
Click to collapse
Which recovery are you running?
joeyhdownsouth said:
Which recovery are you running?
Click to expand...
Click to collapse
I got it, I finally got stock a rom to load via Odin but it was getting stuck on the Samsung screen so I rooted it before it even let me in. Then i did a wipe and it started up and now all is well stock 4.3 rooted. This reminded me why i always choose stock rooted roms

[Q] Stuck at boot when updating to KK

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.

I screwed up help please

Tried to go from 4.4.2 back to stock and it errored now I'm bricked and Odin keeps failing been searching and everything I find doesn't help. What now?
http://forum.xda-developers.com/showthread.php?p=53341869
So after a few hairpulling days I got the phone back up and running now im trying to get my sisters to the same rom using what i have learned .
I can get it up and running with the file from here
http://forum.xda-developers.com/showthread.php?p=53353625
Now I can do 4.4.2, but i cant seem to go back down to 4.1 and load the slim rom I wanted to load.
Tried a file called mc2 stock with counter reset and it just goes through the motions, comes up to the fake splash, says scared you , finishes this step and reboots, to infinite load, no boot loop, just hours and hours of nothing.
I can go back to 4.4.2 but thats all I can get out of it.
I am trying to put the same version on this phone due to the battery life and such that the first one has. 2 identical phones, same revision and all.
SlimRom_Build_7.8_7.28_ODEXED.zip from http://www.teamvenum.com/forum/viewtopic.php?nomobile=1&f=50&t=2008
Could not find the origianl xda thread that lead there sorry for post outside link i know it was here, thats how i found it, just cant find it now.
What have I possiblly overlooked?
bump, still need help. anyone got any advice

Categories

Resources