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
Related
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 ?
I rooted my phone with GALAXY NOTE 2 Toolkit. It was working fine for few months. Recently I noticed a problem when I tried to reboot it, but I pulled the battery out and after reinserting all went OK. then Next day or two another time when I tried to reboot, I got to the point where I cannot boo the phone anymore. I get to the initial T-MOBILE screen and that's where it gets stuck.
I tried to upload a recent ROM through Odin. It worked fine, no errors, no problems, but when I try to boo the same thing happens.
I also tried to get to the other menu ( Power+Home+VolumeUp). It shows the menu with some options but I'm not sure how can I use those. I treid few things but it does not work.
I need to use the phone for work every day so I am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
SAME HERE!!!
aklisiewicz said:
i rooted my phone with galaxy note 2 toolkit. It was working fine for few months. Recently i noticed a problem when i tried to reboot it, but i pulled the battery out and after reinserting all went ok. Then next day or two another time when i tried to reboot, i got to the point where i cannot boo the phone anymore. I get to the initial t-mobile screen and that's where it gets stuck.
I tried to upload a recent rom through odin. It worked fine, no errors, no problems, but when i try to boo the same thing happens.
I also tried to get to the other menu ( power+home+volumeup). It shows the menu with some options but i'm not sure how can i use those. I treid few things but it does not work.
I need to use the phone for work every day so i am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
Click to expand...
Click to collapse
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
go to recovery mode if you can
kim621973 said:
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
Click to expand...
Click to collapse
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
kim621973 said:
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
Click to expand...
Click to collapse
While Knox is a problem, the bootloader is the booger that won't allow return to 4.1.2. Sammy hosed us on that little bit of trickery.
If my wife didn't have a GS3 that I maintain I might have OTA'd. I have been watching their "upgrade" process for a while and knew that there was trouble in the OTA.
It will be painful for a while as people migrate in with problems that have been covered several times. We'll get through it.
Hastily spouted for your befuddlement
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 my issue is pretty similar, see what you guys think. i been trying everything i can think of.
i updated from xtrestolite 2.1 to 2.2 with out wiping. everything worked fine except when i would make calls, the other people could not hear me. so i updated the bootloader and modem again (i had done it before) and the problem persisted. i flashed back to stock and was getting stuck at the s6 edge screen. the only way to get around this was and get my phone to boot was to flash aou kernel. i was still having a similar issue with calling so I download a modem from a diffrent server and all of a sudden, it was working again on stock firmware... AWESOME!
now that i had all that done and my phone working as it should, i reset my phone for the first time and i got the FRP lock, wont boot phone because custom kernel. GREAT
I then flashed stock of6 again, the tar ball, and the 4 piece version. no dice
i then found of8, tried to flash that still no dice.
id love to flash twrp and load a rom on, but FRP is a alsjdflajs.
the phone will flash successfully, but upon reboot, it will go into recovery, run its course, reboot, and get stuck that the galaxy s6 edge screen.
i use the vol and power click during recovery to see what its doing and everything seems to go fine. it will then say failed to mount /data. im hoping flashing this with the pit file will work, but i cannot download the pit file from my work computer (hahah its blocks on 4shard and mega).
anyone have any other advice? i will update if i figure it out.
Regards team,
-Mad
p.s. none of this is xtrestolite's fault, that rom has been nothing but good to me.. my phone has been picky though. after 5.1.1 i had to flash a custom kernel in order for the digitizer to function properly.... any help is appriciated guys.
SO UPDATE!
nothing good, i tried the pit with of6 and of8, no dice. still stuck.
anyone got a s6 edge w a broken screen? you can claim it lost for all i care.
no one?
i guess if anything past flash stock firmware people dont know? was hoping for alittle more insight.
im sure if i could flash a kernel i could get it to turn on, but FRP has be at bay...
no help for you bro...Samsung just needs to release there software fixing for this comunity...I'm looking a for a dev to answer my question in this section about just flashing zip files in twrp instead of using odin or whatever other methods that can avoid all these problems that are all similar...hopefully in next few months it will be addressed
Hey mate, try this...
http://forum.xda-developers.com/showthread.php?p=61531848
Sent from my SM-G925T using Tapatalk 2
holy... fu34%# /S45it.... IT BOOT?!
after flashing every firmware 100000 times...
THANK YOU!
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
Well I am truly stumped, I'm not new to flashing phones I've been flashing rooting and repairing androids for 6 years but have never seen this happen. Came across a tmobile t889 note 2 that had Jedi Master on it and it was bootlooping. (not sure which jedi master I think x2) first I tried to boot into recovery, saw the twrp logo then it just rebooted went back to booting jedi. So I tried to reflash twrp through odin... Nothing, same thing. So then I tried to flash cwm, odin said success no errors but goes right back to twrp, tried philz, same thing. Tried the stock 4.1 rom, 4.3 rom basically every stock rom available, each time odin says success and yet each time jedi master and twrp remain. I tried every single version of odin from 1.85-3.12. I just don't know what else to try, I can't find any threds with even a similar problem except one from an s3 and the solution was only return to samsung... Anyone have sny ideas? Note:it's s not a power button issue the phone doesn't turn off when booting jedi master just syayscon the jedi master bootscreen indefinitely.
Just an update my problem remains, but I found the t889 pit that didn't work, tried to uncheck auto reboot and manually reboot that didn't work. Gave up on odin and tried heimdall with both the command line and the user interface, same thing flashed successfully but nothing really flashed. If anyone has ever used the windows program "deep freeze" It seems like as if that's what happened to the phone... No matter what you flash it just reverts back. I even went as far as trying to purposely brick it by flashing an impropper kernel, I know what that would have done but I just had to see, but nope... Didn't brick... Did nothing... Still has twrp still has jedi master still boot loops
If anyone is interested in seeing a visual of the problem I made a video https://www.youtube.com/watch?v=W3zL069w8io
were you able to solve this?
Just went through this
I was changing roms
And this happened.
Odin the latest Twrp for your phone and do all the rules
Flash the exact Rom that was on it before.
That worked on my t889
You'll probably get partition mount problems..wasn't an issue for me....couldn't flash anything but that Rom.
I'm on jedi x2
It probably had a dual boot