Long story short, I was trying to install Dynamic Kat but it wouldn't work. Each time I would try to install SS 3.72, it wouldn't boot into recovery. If I tried to flash the ROM with SS 3.70, the ROM wouldn't boot--it would just get stuck on a black screen with a blue LED. I was advised to flash Odin and start over. I've been trying to flash stock with several files, however nothing is working (N900AUCUBMI9_OneClickBin.exe). It fails everytime.
Anybody know what I can do to resolve this issue? Needless to say, my phone is soft-bricked at the moment.
Are you able to get into safe strap at all?
As in safe strap recovery.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thank you for your response.
I actually got it resolved. I was on a ROM which I thought was 4.4.2, however it was 4.3 so it was causing a bunch of problems. All sorted out now
Glad you got it figured out.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Related
I just flashed CWM 6.0.3.5, seemed to be working perfectly. On the next recovery boot I got this warning.
Root can possibly be lost. Fix?
This can not be undone
no 7 times in a row (vertically)
yes - fix root (/system/xbin/su)
no 3 more times
I selected fix root from the 11 choices, and my ROM booted just fine. So i restarted in recovery, and again the same warning message.
Another thing I noticed was on the main screen of CWM at the bottom it says
cmw v6.0.3.5
warning no file_contexts
As i said AIOP mod is working fine, just don't like the warning message every time I assess recovery.
Any ideas?
You shouldn't be getting that message every time. But your recovery is outdated. Try the newest cwm in the open of the kit kat rom it's 6.0.4.5. I haven't had any problems with it.
Sent from my SGH-T679 using xda app-developers app
Damn, I wish I remembered how I fixed that problem when it happened to me.
Did you lose root permissions?
My guess would be either SuperSU binaries need to be updated or shouldnt have been updated, causing CWM not reading root properly. Dont quote me on this, its just my guess, haha. probably go with Dvarl's answer.
If you find a fix, please post how, so I can use it for future reference.
I'll check out that update and post what I find out.
Thanks for the help guys.
Sent from my SGH-T679 using xda app-developers app
Dvarl said:
You shouldn't be getting that message every time. But your recovery is outdated. Try the newest cwm in the open of the kit kat rom it's 6.0.4.5. I haven't had any problems with it.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Thanks for pointing me in the right direction! The updated CMW totally fixed the problem I was having. Flashed the Kit Kat Rom, working perfectly so far. The integration of Hangouts as your SMS is a little strange, but easy enough to get going.
BTW, fail for the new kit Kat ROM. Everything was great until my first reboot, then the ROM hung at the Galaxy screen. Had to pull the battery.
Sent from my SGH-T679 using xda app-developers app
Hey guys I am kind of freaking out here and just made an account because I literally have no clue what to do. I just recently was running drakeys jb and upgraded to kitkat, but realized I did not follow one of the steps and that was to make put it as my stock rom. My phone rebooted and seemed to be working with some changes to it. After I attempted to flash the stockrom theme and realized I was no longer rooted? and didn't have safestrap. Now my phone boots up, it shows the samsung note 3 screen and then the screen is just black but the phone does go into recovery mode and download mode. I really don't know what to do so some guidance or solution would be amazing. Got work in the morning so the faster the help the better.
Thank you
Just restore to mj5 then follow the instructions
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
There's a thread to restore to stock maybe specify what your process was that got you to this point
Sent from my SM-N9005 using xda premium
So for the last month or so, I've been trying to get back to Jelly Bean on my Note 3. I'm on the Kit Kat leak, and yes I've read the threads for going back to MJ5, I've read the threads in this forum and pretty much every comment looking for answers. I've googled every combination of words I can think of, and nothing has worked. I've used the Heimdall method to restore a bricked Kit Kat Rom back to the Kit Kat leak, but now when I try to get it back to Jelly Bean, Heimdall says it fails to download package information, fails to end session packet, etc...It'll recognize my phone, get all the way to the download package, and fail.
My Note 3 isn't damaged or broken or anything so it's not like I'm in a rush, which is why I've taken my time going over all the options I've seen. However, I would like to have the official Kit Kat build when it gets released or at least re-root my phone and for the time being I haven't found a way to do either...
Any help or guidance would be greatly appreciated!
The restore method worked for me, coming from the KNOXRAID Kit Kat version--restored successfully to MJ5.
Are you able to flash that version (Knoxraid), then try the restore?
Edit: Heimdall took me a few tries, along with odin. Had to switch from usb3 to usb2 to even get it to be recognized.
Sent from my SAMSUNG-SM-N900A using Tapatalk
composi said:
So for the last month or so, I've been trying to get back to Jelly Bean on my Note 3. I'm on the Kit Kat leak, and yes I've read the threads for going back to MJ5, I've read the threads in this forum and pretty much every comment looking for answers. I've googled every combination of words I can think of, and nothing has worked. I've used the Heimdall method to restore a bricked Kit Kat Rom back to the Kit Kat leak, but now when I try to get it back to Jelly Bean, Heimdall says it fails to download package information, fails to end session packet, etc...It'll recognize my phone, get all the way to the download package, and fail.
My Note 3 isn't damaged or broken or anything so it's not like I'm in a rush, which is why I've taken my time going over all the options I've seen. However, I would like to have the official Kit Kat build when it gets released or at least re-root my phone and for the time being I haven't found a way to do either...
Any help or guidance would be greatly appreciated!
Click to expand...
Click to collapse
The op states that heimdal will not finish. You have to check no reboot and yank the battery and boot into recovery to flash your zips. Every time I do it l, heimdal quits at 95 percent. I've used this method at least a dozen times without fail.
i understand but it fails before even 1% is shown...ive used the method before so i am aware of the 95% that is mentioned in the op but this time nothing happens...i hit start and about 10 seconds later it fails
Sent from my iPad using Tapatalk
composi said:
i understand but it fails before even 1% is shown...ive used the method before so i am aware of the 95% that is mentioned in the op but this time nothing happens...i hit start and about 10 seconds later it fails
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
That's happened to me before. I just hit start again and it worked. Try it a few times.
Also, one time I couldn't get anything to work and I switched the USB cable I was using. Usb3 gave me that 1% error, but usb2 worked like a charm.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I'll keep that in mind when I try again later tonight.!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I thought all we have to do is Odin into safe strap and wipe your device then flash your old jellybean rom
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I think he is referring to the leak, not the ROM.
chispas117 said:
I thought all we have to do is Odin into safe strap and wipe your device then flash your old jellybean rom
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
ZOOPidy said:
I think he is referring to the leak, not the ROM.
Click to expand...
Click to collapse
Exactly
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
So you tried dvilpotatomans method to get back to stock?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Any luck?
Sent from my SM-N900A using Tapatalk
Just got my second note 3 the first one had no problems useing safestrap the second one has not been updated it hasnt had the "pre kitkat update" and for some reason i flashed xnote 7 and it said success but it wont boot it just keeps going to safestrap recovery over and over until you boot into stock rom . Then i tryed the dynamic rom and it just says failed. Any one had this trouble or am i missing a step or what .help?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
shane1981 said:
Just got my second note 3 the first one had no problems useing safestrap the second one has not been updated it hasnt had the "pre kitkat update" and for some reason i flashed xnote 7 and it said success but it wont boot it just keeps going to safestrap recovery over and over until you boot into stock rom . Then i tryed the dynamic rom and it just says failed. Any one had this trouble or am i missing a step or what .help?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Might get more help over in Q&A, but I would use the method here to return to stock mj5 and then ota update to nb4 then root and such from there.
Sent from my SM-N900A using Tapatalk
I didn't have any problem with X-Note (which is now my daily ROM) or Dynamic, but I couldn't restore my stock backup - until I deleted the slot and made the data space larger. Check your sizes.
The only differance between the two phones is that my other note 3 has none of the at&t apps that they put on there. Maybe thats what the problem is . But the other one i had the stock rom and two other roms on it at one time and had no problem .
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I was experiencing problems with my rooted mj5 so i used that popular thread on how to revert to stock mj5. Everything went smooth, but im still having the bootloop problems. The custom lock logo is gone on bootup so i know its true stock mj5 now, but my loader hangs on the ATT animation logo for a bit then keeps restarting. This process goes on and off for a few times until it manages to pull itself through. Should i call ATT for a replacement or is this fixable?
Went into recovery mode and cleared cach - didnt work
Went into recovery mode and did a factory reset - didnt work
f*ck.
Did you flash the 2400258.zip file in the stock recovery?
Sent from my SM-N900A using XDA Premium 4 mobile app
graydiggy said:
Did you flash the 2400258.zip file in the stock recovery?
Sent from my SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This. I've reverted back to mj5 multiple times and never got into a bootloop. Don't take it back to AT&T for your mess up. That's fraud.
Sent from my SAMSUNG-SM-N900A using Tapatalk
graydiggy said:
Did you flash the 2400258.zip file in the stock recovery?
Sent from my SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes i did, using the micro sd.
Do a factory reset
Sent from my SM-N900A using XDA Premium 4 mobile app
graydiggy said:
Do a factory reset
Sent from my SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As i stated above the factory reset does not work. I noticed the main problem was coming from the sd card slot. It doesnt matter what sd card is in there, it will cause the phone to lose signal and enter a weird bootloop. A few hours ago i re installed mj5 and did every step to get a 100% new stock again. The 16gb and 32gb class 10 sd card will cause my phone problems. The main problems are bootloops and if i go to make a call, the service bar will turn to an O with a slash until i end the call so i can not call anyone while my sd card is installed.
Im considering just updating to kitkat and if it has problems from there then i know the phone has hardware issues, then off to AT&T it goes...