Develop Bugs

[Q] primoc cdma kernel crash (all kernels)

RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
Original post:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?

wendall911 said:
I'm getting a consistent kernel crash on all kernels, stock, etc. after the latest HTC update for sprint-vm cdma. Basically, I can get any rom to boot, after about 10-30 seconds, kernel crashes causing the phone to reboot.
I've attached the dmsg log that contains the crash information.
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
Try stock kernel if that crashes then custom rom
Sent from my One V using xda app-developers app

cybervibin said:
Try stock kernel if that crashes then custom rom
Click to expand...
Click to collapse
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.

wendall911 said:
Stock kernel and all custom roms, ICS and JB have the same exact result. This is why I'm suspicious that this was a bad firmware update. I've read several posts about spontaneous reboots, but most people don't know about dmesg, so I don't have anything to compare to.
Click to expand...
Click to collapse
Does it happen like this?
http://www.youtube.com/watch?v=IIqT-xd0AqU&feature=youtu.be
I have the same issue man. It's bizarre.

patbushnell said:
Does it happen like this?
I have the same issue man. It's bizarre.
Click to expand...
Click to collapse
Yes, this is the same behaviour. I'm not sure if you're able to dump the dmsg stuff from adb, but certainly same crash. Typically the phone network status shows a little x, right before the reboot. But the lagginess starts happening when the 5 second kernel reboot is issued.
I've tried to change to airplane mode, disable sdcard and everything else I can think of, still crashing and I'm not able to make much of the logging info

When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain

aaronrw said:
When you applied the OTA were you completely back to stock. Like locked bootloader and stock recovery?
sentfromybrain
Click to expand...
Click to collapse
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.

wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
You will surely get the RUU to make your phone working perfectly. That's what I did.

patbushnell said:
You will surely get the RUU to make your phone working perfectly. That's what I did.
Click to expand...
Click to collapse
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!

I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
wendall911 said:
Confirmed RUU -> Update worked the second time. This is probably the safest method. This appeared to work initially, but clearly did not. Thanks for all the feedback!
Click to expand...
Click to collapse
So are you able to run any other roms without reboots? Or are you only on stock?

MasterTec said:
I can't get any non-stock rom to boot after applying the OTA update. Well ok it boots but loops after about 10-15 seconds.
I have to RUU it and not apply the update to get any non-stock rom to work.
CDMA/VMUSA here.
---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------
So are you able to run any other roms without reboots? Or are you only on stock?
Click to expand...
Click to collapse
I applied the OTA update. Only the stock kernel (after update) will boot now. Any non-stock kernel crashes - always seems the last line is rmt_storage, which the IPC to shared memory of the boot loader I believe.

Noob question
wendall911 said:
Yes, completely back to stock. Unfortunately, I didn't create a backup of the stock image that booted after the OTA update was applied I just restored pre-OTA rom, cwm recovery and boot.img. Everything appeared to be working fine after the update on the stock ROM. However, I didn't leave it on long enough to confirm if the crash issue existed then. Just checked the version info to confirm the update had been applied and rebooted.
UPDATE
I'm going to go through the process again with the RUU and see if I can boot something stable.
Click to expand...
Click to collapse
Can you link me to a working RUU?

i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...

jetfactor said:
i got my one v primoc back in the beginning of summer, but then something fell on it and cracked the screen super bad but i loved the phone so much that i bought another at the end of october. i unlocked, wiped, and flashed JB roms... which seemed to work fine for a while & then would have issues of staying stuck in roaming. i've tried different roms. i never had this issue with my first one v... could my new one have the update already when i bought it? i ran the RUU football posted and was able to boot the stock rom... but right away it goes into roaming again, with my phone not even recognizing that it's using a VM service.
real confused...
Click to expand...
Click to collapse
Yes it's possible that you got one with the update already on it however the problem you are having is completely different than the problem we're describing in this thread and could be caused by many other things - not necessarily the OTA update.
Seems a bit off topic for this thread...

More of the rebooting problem
I have 2 phones one with this problem, the other without it. My friend got one of these phones after i installed jelly bean on mine. He had it long enough to have updated the firmware using the stock image. I made a backup of the stock image, but it seems to have been corrupted (zero byte .zip file). I need to get the phone working (stock or updated, at this point there is no preference so long as it works)
In the bootloader, the radio version of the crashing one is:
1.00.00.0928
The working one is:
1.00.00.0521_2
As far I can tell, this is the only difference. I Used the same SD card and the same procedure for wipe/installing the OS with the same files.
Have you found a solution to this? If so, can you point me to the downloads/instructions for how to fix it?

Looking for help
wendall911 said:
RESOLVED
I ran the RUU for my phone, re-ran the update and am stable on 1.08.652.11 710RD
I'm not sure what I can do to fix this issue, as it appears to be a firmware problem. Thoughts?
Click to expand...
Click to collapse
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!

madhephaestus said:
This may be a bit noob-ish, but can you please add instructions with links for any downloads. I am new to android hacking and have not yet picked up all of the short hand.
Thanks!
Click to expand...
Click to collapse
hey can i please know how to fix the radio on my phone i have the same problem, my phone will boot and turn on but after 10 seconds in turns off again and boots again? can i please get help ?

[Q] Blue LED and no screen :(

tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?

Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app

CrfEpic4g said:
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by that? Which stock tar?

I think the latest tar we have is still Lj7 but idk. just flash the lj7 tar in odin and update to the latest ill try and find it for you
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Theres a link to lj7 just download that flash it in odin and youll be back to stock. Then all you have to do is update to mb1.
Sent from my SPH-L710 using xda app-developers app

Saturn2888 said:
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Click to expand...
Click to collapse
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.

topherk said:
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
Click to expand...
Click to collapse
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?

Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?

Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2

Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
If you dirty flash the rom over whatever you had before, it should not affect any settings

CNexus said:
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
If you dirty flash the rom over whatever you had before, it should not affect any settings
Click to expand...
Click to collapse
MB1 as of now. What do you mean by dirty flash the rom?
edfunkycold said:
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!

Saturn2888 said:
MB1 as of now. What do you mean by dirty flash the rom?
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Click to expand...
Click to collapse
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible

CNexus said:
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
Click to expand...
Click to collapse
Yeah, last time I did that, the system wouldn't boot.

[Q] I think I may have jacked my phone up

I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!

'Sider said:
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
Click to expand...
Click to collapse
ODIN back to stock.

Question
Did you try using ODIN or did you find a factory ROM to flash?

'Sider said:
I had previously tried to root my phone and decided to flash it back to factory. I downloaded last nights OTA 4.3 update and after it installed, now my ATT S3 SGHi1747 gets stuck at the ATT logo AFTER the Samsung logo appears then disappears. My pc is no longer recognizing the device nor do I know how to get in there to at least get it up and running to try and flash it back to factory THEN download 4.3.
Any suggestions on how to get this fixed would be appreciated!
Click to expand...
Click to collapse
Try booting into recovery and factory resetting, this usually fixes this problem.

polobunny said:
ODIN back to stock.
Click to expand...
Click to collapse
Downloaded ODIN, still a little fuzzy on how to operate it
Cadle said:
Did you try using ODIN or did you find a factory ROM to flash?
Click to expand...
Click to collapse
Im not too tech savvy obviously lol, can you point me in the direction of a factory ROM
dntesinfrno said:
Try booting into recovery and factory resetting, this usually fixes this problem.
Click to expand...
Click to collapse
Tried this twice, no luck.
Im assuming once I get this thing flashed back, I can download that app that will reset the counter?

'Sider said:
Downloaded ODIN, still a little fuzzy on how to operate it
Click to expand...
Click to collapse
If you google for "odin flash rom" there's lot of good tutorials out there, many on this forum alone. As for stock, i'm not sure where to find it since I flashed custom the day after I got my phone and never looked back...can't stand stock touchwiz. You could also try flashing any custom ROM you happen to have layin around...worth a shot until you find a custom one. I use BeanStalk ROM, which has 4.3 and 4.4 versions out now.
Best of luck to ya!

goombah88 said:
If you google for "odin flash rom" there's lot of good tutorials out there, many on this forum alone. As for stock, i'm not sure where to find it since I flashed custom the day after I got my phone and never looked back...can't stand stock touchwiz. You could also try flashing any custom ROM you happen to have layin around...worth a shot until you find a custom one. I use BeanStalk ROM, which has 4.3 and 4.4 versions out now.
Best of luck to ya!
Click to expand...
Click to collapse
I suggest here that everyone here read some of the other threads here on XDA, and see all the problems people are having flashing and rooting after taking this latest 4.3 OTA before advising the next person on how to make ANOTHER paper weight.
As for Sider,
You might be out of luck here, as there is no official 4.3 firmware yet available to flash back to stock, and also AT&T has done something with the new software update, where trying to downgrade it back to a previous version is going to either fail or brick phones.
Also, I haven't read yet where anyone has been successful flashing a custom recovery to fix any issues, but the posts are going up so fast right now that I might have easily missed it.
Edit: OK, someone was able to get TWRP installed, but is also having issues with root.

polobunny said:
ODIN back to stock.
Click to expand...
Click to collapse
DO NOT ODIN after last update (OTA 4.3) installed on phone. You will brick your phone.

norbarb said:
DO NOT ODIN after last update (OTA 4.3) installed on phone. You will brick your phone.
Click to expand...
Click to collapse
You're right. I completely forgot about that.

[Q] Frequent Mobile Data Drops on CM11 Nightly (Especially After Ending Phone Calls)

I have been using Cyanogenmod 11 Nightlies for my device for about as long as they have been out, so I know it is still a work in progress, and most of the issues I have faced have gone away as newer nightly builds have been released, so I have not reported any issues as of yet.
Within the last month or so, I have noticed a new issue. The mobile data has been randomly cutting out, allowing only emergency phone calls. It only goes out for about a minute or two, but it is still a huge inconvenience. It seems to happen randomly, except after I finish a phone call -- it almost always cuts out immediately after (very frustrating for when calls are dropped, because I need to wait a minute or two before I can call back).
Has anyone else experienced this or know of a fix? I just tried re-flashing the latest radio and that did not seem to help. I have also tried full system/data wipes as well and none of the Nightly builds for the last month or so have been able to fix it.
Thanks, everyone.

You need to flash any touchwiz rom in order reset your nvram.

Corvetrims77 said:
You need to flash any touchwiz rom in order reset your nvram.
Click to expand...
Click to collapse
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.

pravus87 said:
Is that even possible? I thought there were issues with going from 4.4.x back to 4.3?
Also, how would I go about locating the latest stock firmware and flashing it? I haven't even thought about touching stock since flashing CM.
Click to expand...
Click to collapse
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).

Corvetrims77 said:
I can't find the original post, I don't have time to look for it right now, it was discussed frequently in Quantumroms thread. I needed to do this as I was experiencing the same issue. I restored the stock firmware on my device via samsungKise ( http://forum.xda-developers.com/showthread.php?t=2390147).
Click to expand...
Click to collapse
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.

pravus87 said:
I will take your word for it. But I have read elsewhere that the MJB bootloader makes it impossible to downgrade, which after checking, is the one that I have installed.
I have done the research on how to install stock firmware. I am just a little hesitant to do so. Any re-assurances would be great.
Click to expand...
Click to collapse
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.

Corvetrims77 said:
From what I have read you are correct, but you just need to install any Touchwiz Rom, search through the quantum posts you will find your answers.
Click to expand...
Click to collapse
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.

pravus87 said:
Thanks for your help. I was able to flash stock 4.1.1 and then reinstall CM11. So far, looks like the mobile data issue has been resoled.
Click to expand...
Click to collapse
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.

mreadshaw said:
I'm having the same issue, would you mind giving a quick run through of what you did? I'm downloading the I747MVLUEMK5 firmware to flash in Odin right now. Don't want to do something I shouldn't.
Click to expand...
Click to collapse
I actually did not use Odin at all. I was able to find a thread that posted a 4.1.1 stock .zip, a .zip to keep root, and a .zip to keep custom recovery. (I have tried searching for the thread to share with you but am unable to find it). I was definitely over-thinking it. Just install the .zips from TWRP or CWM as you would any other custom ROM -- just make sure you do not have the 4.3 bootloader installed. That's it.
Sorry for the delayed response!

note 3 running 4.4.4 issues

ok guys, i have a question for you. keep in mind that im new to the phone world lol. ok so a bout a month ago i wanted to unroot my phone but for some reason the tar files on sammobile wasnt working right. so i came on here and downloaded what i believed to be the file that i needed to go back to stock. after i used odin and the phone rebooted it automatically notified me that i had a update. after i accepted the update and it rebooted, it again notified me that i have yet another update. so after this happened i noticed that my phone was updated to 4.4.4 kitkat which would be great exept for the fact that it keeps freezing and when i am on wifi i have a problem getting phone calls aswell as text messages. also when i disconnect from wifi i have to restart the phone to get any data back. is there anything that i can do? is it possible to go back to 4.3 or even 4.2.2? any help would be very much appreciated.

hellrazr209 said:
ok guys, i have a question for you. keep in mind that im new to the phone world lol. ok so a bout a month ago i wanted to unroot my phone but for some reason the tar files on sammobile wasnt working right. so i came on here and downloaded what i believed to be the file that i needed to go back to stock. after i used odin and the phone rebooted it automatically notified me that i had a update. after i accepted the update and it rebooted, it again notified me that i have yet another update. so after this happened i noticed that my phone was updated to 4.4.4 kitkat which would be great exept for the fact that it keeps freezing and when i am on wifi i have a problem getting phone calls aswell as text messages. also when i disconnect from wifi i have to restart the phone to get any data back. is there anything that i can do? is it possible to go back to 4.3 or even 4.2.2? any help would be very much appreciated.
Click to expand...
Click to collapse
Hello! Did you make a back up of your phone before you started the update? That would be the easiest way to go back to how it was. If you used Odin and didn't install a recovery like TWRP or Clockwork you may not have done so. I believe you can reload from Odin with an older ROM it will just erase everything you did. There are stock ROMS here at XDA and galaxynote3root.com as well. Let me know it this helps, sorry for your troubles.

5225
Jedidanno said:
Hello! Did you make a back up of your phone before you started the update? That would be the easiest way to go back to how it was. If you used Odin and didn't install a recovery like TWRP or Clockwork you may not have done so. I believe you can reload from Odin with an older ROM it will just erase everything you did. There are stock ROMS here at XDA and galaxynote3root.com as well. Let me know it this helps, sorry for your troubles.
Click to expand...
Click to collapse
Thanks for the reply, so i wont have any problem downgradeing? I think i read somewhere that i could brick my phone. And if it is possible what version am i able to go back to?

Oh and to answer your question, i have never has a custom recovery on this phone and i didnt make a back up.

Can you post a screenshot of your about phone page?

Techniques said:
Can you post a screenshot of your about phone page?
Click to expand...
Click to collapse
is this good

I'm actually surprised that you did get an update to 4.4.4... You could try going back to NF9. The safest route I see that you can take is to install a custom recovery and make a backup before doing this. If you odin NF9 and it doesn't boot then you're kinda screwed because we technically don't have the 4.4.4 update yet, so if anything goes wrong, you can install a recovery again and restore the 4.4.4 backup.

Techniques said:
I'm actually surprised that you did get an update to 4.4.4... You could try going back to NF9. The safest route I see that you can take is to install a custom recovery and make a backup before doing this. If you odin NF9 and it doesn't boot then you're kinda screwed because we technically don't have the 4.4.4 update yet, so if anything goes wrong, you can install a recovery again and restore the 4.4.4 backup.
Click to expand...
Click to collapse
haha i was surprised to, i cant find anyone else that has it with this phone either, i was kinda wondering if i maybe downloaded the wrong file maybe for a different country or carrier. im not sure how to do the hole backup and custom recovery thing.

hellrazr209 said:
haha i was surprised to, i cant find anyone else that has it with this phone either, i was kinda wondering if i maybe downloaded the wrong file maybe for a different country or carrier. im not sure how to do the hole backup and custom recovery thing.
Click to expand...
Click to collapse
You can get the latest TWRP recovery here : http://www.techerrata.com/file/twrp2/hltetmo/openrecovery-twrp-2.8.1.0-hltetmo-4.4.img.tar
Just odin that and after it's done, go into recovery by doing Vol down + Home and do a backup either in your internal or external storage. After that finishes, you can go back in download mode and odin NF9.

ok thanks for all you help man,

hellrazr209 said:
is this good
Click to expand...
Click to collapse
iam surprised as well how did you get the latest tar on tmobile note 3?

chipis said:
iam surprised as well how did you get the latest tar on tmobile note 3?
Click to expand...
Click to collapse
I got it on here, it was a tar for 4.4.2 i believe and after i downloaded it, it said i had a update. After that i had another update lol which brought me to the hell im in now lol 4.4.4

hellrazr209 said:
I got it on here, it was a tar for 4.4.2 i believe and after i downloaded it, it said i had a update. After that i had another update lol which brought me to the hell im in now lol 4.4.4
Click to expand...
Click to collapse
Well i believe if iam right samobile had not release it for tmo yet

chipis said:
Well i believe if iam right samobile had not release it for tmo yet
Click to expand...
Click to collapse
Yeah its not on their website. I have know idea what i got then lol anyway to fine out if i have something i shouldnt?