I am not a total noob and have done alot of research lately about my problem but have not found a concrete answer. It looks like there are alot of knowledgable people here. My problem is I was trying to get my friends T999 T-Moble phone to KK (CM11) It was already on Official 4.3 so I just rooted it, put TWRP on it, then flashed CM11. Now it looks like I have no signal at all but I don't know if that is caused by not having a Sim inserted.
Did I bork the Modem? If so, What can I do to get it back to stock. Dont care about the warranty counter. Currently I have the stock 4.3 image:
T999UVUENC2_T999TMBENC2_TMB
I have Odin 3.07
I am worried about flashing back down to Official 4.3 since I read about other downgrade issue. I had also made a backup in TWRP of the Stock Rooted rom. I am going to try and restore that to see if that helps or not.
If anyone knowledgeable can help me get it back to stock or at least return signal, I would gladly donate $15 for their time and efforts. In my line of work time is money and there isn't any free IT support. Thanks Guys!
Kind Regards,
Zachariah
Please disregard, I was able to fix it with the Backup I had made of the original firmware. Sorry for any confusion.
Moderators, please close this thread.
Thanks!
About a year and a half ago, I gave my father my T999L after I upgraded the phone. Since then it appears a 4.3 update has been released and in order to use his Galaxy Gear watch that he wanted for his birthday, he needs to upgrade. He wants to stick with a stock (or stock based) ROM and I need to get it taken care of for him today. When I had the phone, I was running Dandroid. Because I rooted, installed custom recovery, etc. it reads as modified software and will not receive the OTA even though I flashed returned it to stock before I gave it to him.
Any help would be great - apparently the 4.1.2 bootloader won't work with the 4.3 ROMs? Anyone have a link to something I can just use ODIN to flash and get it all done in one step? I assume the link here can do it? Hopefully...
http://forum.xda-developers.com/showthread.php?t=1949687
Thanks in advance.
EDIT : Never mind, we're good. I got it figured out
I picked up a used AT&T S3 here in NY because I just installed an Alpine ICS-X7HD in my car. The S3 had the latest NJ1 installed. I was able to root the phone OK. My research has lead me to believe that I won't be able to get any version of Drive Link running on Android 4.4 without FCing when connecting to the Alpine Unit. Research also seems to suggest that I can't go back to the LK3 version either due to boot loader changes made from Samsung and AT&T with the 4.3 update. So I'm looking for advice from the forum experts on what I can do, if anything to get the phone downgraded to a Jelly Bean firmware. I am hoping to hear from someone who has been able to do this before. Can I go from 4.4.2 to 4.3? If so does Drive link still work for you?
I am comfortable using Odin and adb. Let me know if you need any other specific information.
The solution was so incredibly simple. I flashed the AT&T+UCMG2.ZIP through TWRP and rebooted. Now I am on 4.1.2. Drive Link working! So To Recap...I went from 4.4.2 NJ1 back to 4.1.2 and stayed on NJ1 baseband.
Dbeayon said:
I picked up a used AT&T S3 here in NY because I just installed an Alpine ICS-X7HD in my car. The S3 had the latest NJ1 installed. I was able to root the phone OK. My research has lead me to believe that I won't be able to get any version of Drive Link running on Android 4.4 without FCing when connecting to the Alpine Unit. Research also seems to suggest that I can't go back to the LK3 version either due to boot loader changes made from Samsung and AT&T with the 4.3 update. So I'm looking for advice from the forum experts on what I can do, if anything to get the phone downgraded to a Jelly Bean firmware. I am hoping to hear from someone who has been able to do this before. Can I go from 4.4.2 to 4.3? If so does Drive link still work for you?
I am comfortable using Odin and adb. Let me know if you need any other specific information.
Click to expand...
Click to collapse
How did you root on Nj1??!
To get to jelly bean, you do the hack like method above by flashing a zip in TWRP or Clockwork mod or boot a custom rom based off 4.1.x. Once you are on 4.3 or 4.4, there is no going back to a previous version, attempts result in bricking.
Hello,
I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.
Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.
So I decided to go back to latest available stock rom 4.4.2 from sammobile.
Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.
The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.
It doesn't even get to the Samsung animated logo.
Ok bottloop, no problem, try to flash again something else.
I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.
During the various attempts knox fired, but I don't care. I don't know if this could be the cause.
Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.
I really need any advice or hint.
At the moment my goal is to get at least to stock 4.3 but I cant.........
Thanks!
When you first bought your phone, did it come with Knox?
ErnestChia said:
When you first bought your phone, did it come with Knox?
Click to expand...
Click to collapse
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/showthread.php?t=2088809/[URL]
From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.
I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.
However, I don't know why 4.1.2 works when everything else doesn't work!
Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?
mysuperdonghae said:
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/sho...can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
misthero said:
I think so, there is a boot.im, anyway I also discovered that I can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.
So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.
***
So now there are 2 possible ways to reach your goal:
1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone
2) Try to restore your old bootloader
As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.
And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.
Conclusion: I don't think I can help you to solve your problem I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.
Good luck!
After noticing the only available firmware to flash was actually 4.2.2 my OP became meaningless.
If you know where I can find a stock 4.4.2 firmware
OR
If there is anyone with this device that can possibly send me a backup of the same device running 4.4.2 I may be able to fix my device.
I'm currently missing a recovery, and can only get into download mode due to misreading the version number on a firmware image. (My fault for not paying attention but I still hate knox)
If anyone is able to help me with this issue I would be really grateful.
If all else fails I'll see about sending it back to Samsung but they may tell me I'm out of luck.
Thanks
Just noticed that the firmware from sammobile is 4.2.2
No wonder its not working, doesn't explain why kies wont work though...
anyone know where to get the 4.4.2 firmware ?
I am having this issue my self. Can't believe kies doesn't have the right firmware! I wasted my entire day to find out that it was trying to install 4.2.2! Gah please if anyone has 4.4.2 please post links!!!