Hi,
I flashed kitkat 4.4.2 stock firmware today using Odin, After the mobile booted successfully the touch screen stopped working completely, also the option and back button stopped also, I tried reflashing multiple times the same thing.
I have replaced this screen and the digitizer 10 days ago after it crashed, it was working normally before upgrade.
What could be the problem.
Regards
Are you sure your using the right odin model?
Run in administration mode, and disable all virus pc programs.
Also, after flash reboot into stock recovery and data reset/ Wipe.
If that doesn't work the most likely you have a bad piece of hardware or something is unperfectivley seated. Try reconnecting the ribbon cables.
Reflash
Yes4g4me said:
Are you sure your using the right odin model?
Run in administration mode, and disable all virus pc programs.
Also, after flash reboot into stock recovery and data reset/ Wipe.
If that doesn't work the most likely you have a bad piece of hardware or something is unperfectivley seated. Try reconnecting the ribbon cables.
Click to expand...
Click to collapse
I did what you said, I tried reflashing with another jellybeans stock version but the same results, I took it to the mobile center where I changed the screen and he told me he can revert it to jellybeans.
I will tell you what he did when he finish.
samirkal said:
I did what you said, I tried reflashing with another jellybeans stock version but the same results, I took it to the mobile center where I changed the screen and he told me he can revert it to jellybeans.
I will tell you what he did when he finish.
Click to expand...
Click to collapse
It will be interesting to see how they could revert firmware from KK to JB... IMO this is impossible because of new bootloader in KK. Anyway let they make phone usable on ANY firmware.
Probably jigg it right?
Yes4g4me said:
Probably jigg it right?
Click to expand...
Click to collapse
It is unclear for now but there may be involved e-fuses technology - that means physically burning connections inside chip during firmware upgrade, so in that case it impossible to bring back previous state.
The main problem is why replaced screen doesn't work after flashing KK. I do not know what version of Mega do you have, but i red on this forum so some versions required exclusively Samsung original parts. People who changed screens by themself obtained i.e. from ebay had problems after upgrading to KK. Lets prove the source of parts in service where was replaced your screen.
EDIT// You can read about it here
http://forum.xda-developers.com/showthread.php?p=55189673
successfully downgraded
Successfully downgraded to jellybeans but didn't tell me how. He performed rooting and flashing which led to baseband loss, but then he returned the baseband, great.
Congratulations. Can you post sreenshot of the Informations about unit?
samirkal said:
Successfully downgraded to jellybeans but didn't tell me how. He performed rooting and flashing which led to baseband loss, but then he returned the baseband, great.
Click to expand...
Click to collapse
Which version do you own? i527?
Would love to know howbyou downgraded back to jb
Sent from my LG-LS980 using XDA Free mobile app
argggg
samirkal said:
Successfully downgraded to jellybeans but didn't tell me how. He performed rooting and flashing which led to baseband loss, but then he returned the baseband, great.
Click to expand...
Click to collapse
hi
my touch after ota does not vvork....
hovv you repair your baseband?
my basebandd is novv unknovvn !!
i9200
samirkal said:
Hi,
I flashed kitkat 4.4.2 stock firmware today using Odin, After the mobile booted successfully the touch screen stopped working completely, also the option and back button stopped also, I tried reflashing multiple times the same thing.
I have replaced this screen and the digitizer 10 days ago after it crashed, it was working normally before upgrade.
What could be the problem.
Regards
Click to expand...
Click to collapse
I have a samsung mobile, Galaxy Mega 6.3 (GT-I9200).
I updated my 4.2.2 android to 4.4.2 by OTA, last month in my Settings and About menu and Check for Update...
This update completed successfully, but after update my touch screen does not work at all, and I don't know what shall I do right now... my phone is completly unusable...
Solved.. Use this
http://forum.xda-developers.com/showthread.php?t=2922542
Useful information
Good deal glad you got your phone working again
Related
I purchased an AT&T SGH-i717 and was told everything worked. When I checked it out, everything seemed fine too. After using it for a couple hours I realized it just seemed to reboot at random. I rebooted into recovery and did a factory reset and wiped the cache. After rebooting it...it would get stuck at the AT&T screen. I then installed the latest stock rom 4.4.2 using Odin and it booted up fine but I got the no sim card error. I put in an AT&T sim card and rebooted but got a sim not provisioned error. I then tried a T-Mobile card and I didn't get the error and it showed signal bars but when I tried to dial it said emergency calls only. I tried a Verizon sim card just to see what kind of error I would get but it was just the same as the T-Mobile sim. I thought it might a corrupted rom so I tried installing the latest nightly CyanogenMod using CWM but got error status 7. I then tried various custom and stock roms including AOKP, BeanStalk, and several different versions of CyanogenMod but always got the same error status 7 msg. I then came across a forum posts stating that CWM no longer works for the SGH-i717. I downloaded the latest TWRP touch recovery and was able install the latest stable CyanogenMod but it would not boot past the animated CyanogenMod logo even after sitting for over an hour. At that point I gave up and decided to just go back to the stock rom. I rebooted into TWRP and the slide to unlock would not work anymore. I had to install CWM using Odin which allowed me to flash back to the stock 4.4.2 rom. After doing another factory reset and wiping the cache then rebooting...the touch screen stopped working. I then flashed it back to the stock 4.0.4 rom but the touch screen still does not work. While trying to figure out what happened I realized the pen still works and touch screen buttons on the bottom but thats it. Also the pen only works on the screen and not on the touch screen buttons. I've been messing with this for 3 days and will probably just sell it for parts but wanted to post this problem so if anyone else had this problem they would know what I've already tried. I did also take apart the phone and clean the connections but that didn't help either.
If anyone has a suggestion for something I haven't tried...please let me know. My last attempt will be install the Padawan JB rom from this post:
http://forum.xda-developers.com/showthread.php?t=1907203
Thanks
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
well my friend, you had the phone apart once already, I am no expert, but my guess is this is no software issue. maybe some connections came loose. in my time here, I have not come across this issue. I do not have the brain pan nor the courage to take my phone apart.
good luck to you.
maybe someone else will mosey on by.
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
My guess is the digitizer has gone bad if odin &/or kies can't fix the issue at hand.
Hi,
Firstly thanks for time and sorry if this is a noob question but I only have a fairly small amount of experience regarding custom roms.
Here goes...
I have changed the rom on my phone about 5 times over the last couple of years and never had a problem. I have the latest version of teamwin and I'm currently running Android Revolution HD 50.0 by mike1986. This rom works great as have all the other I have used in the past ie Cyanogenmod, Omega etc but the problem I am having is over the last 4 months I am completely losing network and even if I try to search for a mobile operator my phone can't find any unless I run a full power cycle.
I have been reading as much online mainly xda-developers to find a solution to this problem but I'm afraid I'm now just running into a brick wall. I understand this could just be a hardware fault but I have read somewhere that I may have the wrong modem installed for my phone.
How likely is this? Can having the wrong modem cause intermittent problems? Also if this is the case where the I find a tutorial on correcting this issue. Plus which modem should I be using in the UK?
Again thanks for you time and any help would be much appreciated.
Mike
Do a full wipe and flash the latest stock firmware for your country, then factory reset.
Test fully before you install or restore anything. If it is still the same then probably hardware.
Sent from my GT-I9300 using Tapatalk
ok, Will do. I am just waiting for the UK stock firmware to download. I left it downloading while I was out this afternoon and for some reason it failed and now is asking me to wait an hour before retrying
I'll let you know if this solves my problem.
Thanks
ok..
I managed to get hold of the stock firmware from another site. I first installed a version of ICS so I could run triangle away properly after rooting with CF auto root as without doing this I couldn't reset my binary counter even after flashing stock recovery. Then I installed the latest version of JB and ran the official Samsung update to get my phone up to the very latest Official software with device status official.
So now my phone is completely back to if it just came out of the box. I finished late last night and installed nothing but WhatsApp. Then at about 3pm today again I completely lost network and couldn't restore in without a full power cycle. Even searching for Network operators in settings couldn't restore the connection. I can't think of anything else to try.
Any ideas what to try next please?
P.S. The firmware I installed is as far as I can tell for my location. I'm in the U.K. and I'm using the stock BTU version on baseband version I9300XXUGMK6
the same i9300 problem
Mike_aMPLe said:
ok..
I managed to get hold of the stock firmware from another site. I first installed a version of ICS so I could run triangle away properly after rooting with CF auto root as without doing this I couldn't reset my binary counter even after flashing stock recovery. Then I installed the latest version of JB and ran the official Samsung update to get my phone up to the very latest Official software with device status official.
So now my phone is completely back to if it just came out of the box. I finished late last night and installed nothing but WhatsApp. Then at about 3pm today again I completely lost network and couldn't restore in without a full power cycle. Even searching for Network operators in settings couldn't restore the connection. I can't think of anything else to try.
Any ideas what to try next please?
P.S. The firmware I installed is as far as I can tell for my location. I'm in the U.K. and I'm using the stock BTU version on baseband version I9300XXUGMK6
Click to expand...
Click to collapse
Hi I am have the same problem.. I've tried 2x reapir store.. but just can say: "you need put new main board".
But I have trust that its not better solution (at least for me).
So if you find some solution, please dont forget reply here.
Thanks
O2 by any chance? .. if so it's a network issue. It happened to me a while back but cleared up after a day or two.
shivadow said:
O2 by any chance? .. if so it's a network issue. It happened to me a while back but cleared up after a day or two.
Click to expand...
Click to collapse
This is exactly the issue I have now - I can get some signal, but can't get anything in terms of using 3G/Mobile data :/
Hy everybody. I'm here to took with you about a common problem on samsung s3. One week ago i notice that i can't receive calls, messages etc and i found the "not registered on network" problem. What actually i want to say, is the fact that it appear suddenly, my phone always have 4.3, i didn't upgrade nothing....the problem persist, i changed sim, modem.bin, flash 4.1, modified network connections from setting....nothing work!!! I always have signal but that's all....what can i do more? (and my imei has changed to this: 00499*******
international variant
Perseus said:
Can you please let us know if you have international variant or US Variant ? If US then which carrier please ?
Click to expand...
Click to collapse
My phone is a international variant, made in Vietnam, i also tryed to flash 4.1.2 I9300XXEMG4, so then i can flash MG4 modem which can still read the modified EFS...if it is modified, but didn't work.., i think i need to send the phone to a gsm/service, but maybe you guys can help me without cost me money..
Perseus said:
I will request to have your thread moved to appropriate forum.
Click to expand...
Click to collapse
thx man, i hope someone knows how can i solve the problem.
What had you done before you got to this issue of no cellular signal?
Did you flash a custom ROM etc..? Which version were you on before? 4.3?
What did you do after you found out about this issue? Did you by any chance flash an older version?
Because that tends to do that, atleast that's what happened to me.
I had a wrong/fake IMEI ("0049..."), which caused that I had no cell reception and couldn't use the phone to call or send/receive sms etc...
I googled a lot and I tried some of the TUT on the web, but nothing helped. Until I found a thread on the xda that said one could try to flash a newer stock ROM (don't know the exact thread).
So I went ahead and checked the version I was on...luckily it was 4.0.4
I then downloaded a newer stock ROM 4.3 for my region and flashed that using ODIN...once it passed I went to recovery: wiped cache and factory reset.
and voila...when I checked the IMEI code again, it was back to the original one.
If that doesn't help check the following thread on xda: here
I suspect he allowed the battery to run out, which corrupted the efs partition, as he says his phone was on 4.3 and didn't change anything until after the problem happened.
Flashing latest stock firmware is the first step, as suggested above, but I think the OP may have to pay for a repair. Make sure it works on 4.3 before you accept the bill.
I forgot to say, my battery got bigger before that happened, i can't fit it in my phone, is double than a normal one, i buy other battery, have this something to deal with the problem?
Sent from my GT-I9300 using XDA Free mobile app
contactmsd said:
What had you done before you got to this issue of no cellular signal?
Did you flash a custom ROM etc..? Which version were you on before? 4.3?
What did you do after you found out about this issue? Did you by any chance flash an older version?
Because that tends to do that, atleast that's what happened to me.
I had a wrong/fake IMEI ("0049..."), which caused that I had no cell reception and couldn't use the phone to call or send/receive sms etc...
I googled a lot and I tried some of the TUT on the web, but nothing helped. Until I found a thread on the xda that said one could try to flash a newer stock ROM (don't know the exact thread).
So I went ahead and checked the version I was on...luckily it was 4.0.4
I then downloaded a newer stock ROM 4.3 for my region and flashed that using ODIN...once it passed I went to recovery: wiped cache and factory reset.
and voila...when I checked the IMEI code again, it was back to the original one.
If that doesn't help check the following thread on xda: here
Click to expand...
Click to collapse
I was on 4.3 version, i didn't do nothing, i even not installed the root/cwm....the problem appeared from nothing...right before i change my battery. I tried with my region stock rom (4.1.2;romania) and with 4.3 stock ROM but didn't work.
Today i let the phone on a service....i told her what is the problem and i hope there's nothing to do with motherboard. Anyway, please let me know if there's something else to do while i wait 3-4 days for the answer
Spike97 said:
I forgot to say, my battery got bigger before that happened, i can't fit it in my phone, is double than a normal one, i buy other battery, have this something to deal with the problem?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
That's not good...bulging/expanding battery is a very bad thing and should be replaced asap.
Why it happens, is another thing...could be due to various reason such as thermal runaway or even acid leakage.
Fix that first before you move to any flashing and/or other stuff...
contactmsd said:
That's not good...bulging/expanding battery is a very bad thing and should be replaced asap.
Why it happens, is another thing...could be due to various reason such as thermal runaway or even acid leakage.
Fix that first before you move to any flashing and/or other stuff...
Click to expand...
Click to collapse
I already replaced it.
Fixed
Hi everybody, i finally sent the phone to service and they fixed it for 17€; everything ok, no problem occurred...i flashed stock 4.3 ROM, then CWM and SU, but....then....after one day of use, i forgot to shut down the phone and, again, removed the battery with the screen on....i connected quickly the battery and the phone started without press any button.....and then, surprise!!! Me trying to make a phone call: "Not registered to network"...fu**...but IMEI was still alright(w t f?). Third day i sent again the phone to the service and they told me that i am playing whit the soft (what man? just because i flashed CWM and SU? damn), i told them again what i do with the battery and they said is not true (now what i am supposed to do? they don't trust me) but fixed it again free..for first and last time. Now here is the question: what i need to back up in case that will happen again? It can't be fixed with a backup of IMEI/Modem file...
Go read the sticky thread in general forum.
When I flash a rooted 4.4.2 ROM and BL , I upgrade to I527MVLUCNE5 but my phone touch panel doesn't work.
So I flash back to I527MVLUBNA3 , then I got a unknown baseband version and have no wifi & bluetooth & mobile network signal.
How can I restore my phone to a usable status?
dsanke said:
When I flash a rooted 4.4.2 ROM and BL , I upgrade to I527MVLUCNE5 but my phone touch panel doesn't work.
So I flash back to I527MVLUBNA3 , then I got a unknown baseband version and have no wifi & bluetooth & mobile network signal.
How can I restore my phone to a usable status?
Click to expand...
Click to collapse
Hi..try this rom by @krazykipa as it is a NA3 rom and is rooted already..just flash with odin and see if this will get you back up and running normally again..link below.
ROOT_JDQ39.I527MVLUBNA3.tar
starmaster10 said:
Hi..try this rom by @krazykipa as it is a NA3 rom and is rooted already..just flash with odin and see if this will get you back up and running normally again..link below.
ROOT_JDQ39.I527MVLUBNA3.tar
Click to expand...
Click to collapse
I tried this before this thread and I got a unknown baseband.
Now I flash this but without its baseband , and I got mobile network and bluetooth work , but WIFI doesn't work.
When I flash to 4.4.2 , I only cannot touch. I use a otg mouse , and I find it WIFI, mobile network, bluetooth all work well.
dsanke said:
I tried this before this thread and I got a unknown baseband.
Now I flash this but without its baseband , and I got mobile network and bluetooth work , but WIFI doesn't work.
When I flash to 4.4.2 , I only cannot touch. I use a otg mouse , and I find it WIFI, mobile network, bluetooth all work well.
Click to expand...
Click to collapse
Did you change your screen on your phone as it sounds like that kind of problem..if you do change a screen and it is not an original screen the touch part will not work if you upgrade to 4.4.2, and when you try to go back to 4.2.2 you will have these other problems like wifi, mobile data, etc not working as the knox security will do this as once you upgrade to 4.4.2 there is no way of getting back to 4.2.2 with everything working again..not that i know of anyways.
If you did change your screen then the only way to get the touch part working again is to get a original screen..unless some kind of driver/s will come out to make it work as with the newer 4.4.2 kitkat the screen does not use anymore third party drivers anymore..and this is why if not an original screen the touch will not work anymore.
If you did not change the screen then this is kinda weird to why you do not have any touch on the screen and if your phone and rom is all original stock..then i would get in contact with samsung as they are the ones who put out this kitkat update..but with companies you never know which way they will go on something like this either.
starmaster10 said:
Hi..try this rom by @krazykipa as it is a NA3 rom and is rooted already..just flash with odin and see if this will get you back up and running normally again..link below.
ROOT_JDQ39.I527MVLUBNA3.tar
Click to expand...
Click to collapse
Thanks you , I did changed my screen before.And I don't want to change it again,so is there another solve to this problem?
dsanke said:
Thanks you , I did changed my screen before.And I don't want to change it again,so is there another solve to this problem?
Click to expand...
Click to collapse
Unfortunately there is no fix at this time that i know of...sorry.
Screen not working on Mega Phone
starmaster10 said:
Did you change your screen on your phone as it sounds like that kind of problem..if you do change a screen and it is not an original screen the touch part will not work if you upgrade to 4.4.2, and when you try to go back to 4.2.2 you will have these other problems like wifi, mobile data, etc not working as the knox security will do this as once you upgrade to 4.4.2 there is no way of getting back to 4.2.2 with everything working again..not that i know of anyways.
If you did change your screen then the only way to get the touch part working again is to get a original screen..unless some kind of driver/s will come out to make it work as with the newer 4.4.2 kitkat the screen does not use anymore third party drivers anymore..and this is why if not an original screen the touch will not work anymore.
If you did not change the screen then this is kinda weird to why you do not have any touch on the screen and if your phone and rom is all original stock..then i would get in contact with samsung as they are the ones who put out this kitkat update..but with companies you never know which way they will go on something like this either.
Click to expand...
Click to collapse
That is exactly what happened to me. I replaced my broken screen and it worked fine. I was elated. It soon asked me if I wanted to update. As soon as I did I could not get the screen to work. What a piss off.
Until now, I have not even figured out how to go back so I could at least have the limited functionality.
I will contact the supplier of the screen and see what suggestions they have. I doubt there is any hope of getting my money back.
Richard
For anybody that wants to go back to 4.4.4 from 5.0 I can confirm it works great, I just flashed back with Odin. The 4.4.4 firmware is at sammobile right below the lollipop firmware. The 4.4.4 flash put it into a bootloop to which I then factory reset and it started up perfectly with none of the completely unusable issues I was having.
Bummed out that I can't use lollipop for the time being, but more than relieved that I have a usable phone again, I thought it was toast.Lollipop made my phone worthless, literally couldn't do anything, major bootloops and constant crashes.
I made another thread about it here
http://forum.xda-developers.com/verizon-galaxy-note-3/help/reboots-lollipop-t3090421
You should retry the upgrade, it's faster and more stable. You just had a corrupted file or something, if you really want the best is worth a try. It's 40% faster. There was just something wrong with your install.
Did you do a factory reset when you upgraded? A lot of Note 4 users who upgraded had similar issues which a factory reset corrected.
I took the upgrade and found it to be faster and more reliable as well. Still fingers crossed for a root exploit. At least we know if an exploit ever happens for 4.4.4 then we can downgrade to get it. Good to know!
Oh really? I thought we couldn't roll back after taking 5.0. I am having a hard time a stable host to download 4.4.4
Can someone help me out with this? <confused>
@ lost perfections:
Success! The 4.4.4 firmware took forever to download but worth it! Thank for this!
KruseLudsMobile said:
You should retry the upgrade, it's faster and more stable. You just had a corrupted file or something, if you really want the best is worth a try. It's 40% faster. There was just something wrong with your install.
Click to expand...
Click to collapse
Trust me I really wanted it and tried all the usual steps. I think something is wrong with my phones hardware that works mostly ok on this version. I actually stayed on an old version for a very long time, I rooted "root de la vega" and took one ota using the supersu option to keep root when using an ota. The next update after that would not work for me, I would have had to wipe and odin to update, so I held off thinking I wasn't missing anything. Till about a week or less after 4.4.4 came out then my phone started crashing the moment I received or made a call. I hadn't gotten any new apps or anything like that but just in case I factory reset to see if it fixed with no luck. So I finally upgraded via odin, no root now, but miraculously my phone could make calls again. I am giving you this essay because I have a feeling this issue is related. It seems it's my phones hardware that is messed up and i'm just lucky that 4.4.4 works at all. I still have issues every couple days where I make or receive a call and hear nothing, with a reboot needed to fix, that is confirmed still after a fresh install of 4.4.4 after all the 5.0 stuff I tried. Anyways thats why I think it's my phone. I wish I had an extended warranty so I could just update and make a claim.
As for everything I tried in the update, I took the ota, which was literally unusable by anybodys standard, I could use the phone for about 5-20ish seconds before it would crash, turning the sound to mute would help, but still crash at a couple minutes of use. I downloaded the firmware and flashed via Odin, same exact issues, changed nothing. Did several factory resets between all these steps. I kind of walked through the process on that thread I posted in the OP.
After making this thread I did try it one last time and flashed via odin, knowing that I had a workable fix, but same exact thing again. If they release another update I'll try then, but looks like I'm stuck till then at least.
Reilly1812 said:
Did you do a factory reset when you upgraded? A lot of Note 4 users who upgraded had similar issues which a factory reset corrected.
Click to expand...
Click to collapse
Yeah I did anything and everything I could, no luck. I think my phone itself is the problem.
sameog said:
@ lost perfections:
Success! The 4.4.4 firmware took forever to download but worth it! Thank for this!
Click to expand...
Click to collapse
Awesome, glad it helped. I'm SO glad they didn't block the ability to do this, I'd have been out a phone if they had.
LostPerfections said:
Awesome, glad it helped. I'm SO glad they didn't block the ability to do this, I'd have been out a phone if they had.
Click to expand...
Click to collapse
Can you be more specific? There are two firmware versions that are 4.4.4-NJ6 and NK1. I assume you used NK1? I'm a newb and sort of know how to use Odin/download mode. What version of Odin did you use?
I want to rollback to the previous build until they sort out the radio issues. My phone was fine on NK1 but on lollipop it drops LTE indoors frequently. Aside from the radio issue, lollipop runs great. I factory reset after the update, didn't make a difference.
YayNote said:
Can you be more specific? There are two firmware versions that are 4.4.4-NJ6 and NK1. I assume you used NK1? I'm a newb and sort of know how to use Odin/download mode. What version of Odin did you use?
I want to rollback to the previous build until they sort out the radio issues. My phone was fine on NK1 but on lollipop it drops LTE indoors frequently. Aside from the radio issue, lollipop runs great. I factory reset after the update, didn't make a difference.
Click to expand...
Click to collapse
You can use any radio with any rom. Just flash the modem file via flash app or Odin.
thornev said:
You can use any radio with any rom. Just flash the modem file via flash app or Odin.
Click to expand...
Click to collapse
Are you certain I can use a KitKat radio on lollipop? Verizon Note 3. If so, I'll do that right now.
Sent from my SM-N900V using XDA Free mobile app
YayNote said:
Are you certain I can use a KitKat radio on lollipop? Verizon Note 3. If so, I'll do that right now.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
I haven't done it, but I have mixed radios and roms before for example kitkat radio with JB rom.
Well, I'd still rather 4.4.4.. it's too bad. When I have strong LTE it's amazing. Did this speedtest today - kilobytes per sec. Incredible.
Sent from my SM-N900V using XDA Free mobile app
YayNote said:
Well, I'd still rather 4.4.4.. it's too bad. When I have strong LTE it's amazing. Did this speedtest today - kilobytes per sec. Incredible.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
No matter what....once you go to lollipop, you can NOT go back to any earlier version.
Sent from my Note 3 via Tapatalk
Doesn't the OP state that you can revert back?
YayNote said:
Can you be more specific? There are two firmware versions that are 4.4.4-NJ6 and NK1. I assume you used NK1? I'm a newb and sort of know how to use Odin/download mode. What version of Odin did you use?.
Click to expand...
Click to collapse
Yep. The OP did. Hell that's the title of the topic and there's two confirmed posters that did it successfully. I only wanted to know if they flashed NJ6 or NK1 and what build of Odin they used..
YayNote said:
Yep. The OP did. Hell that's the title of the topic and there's two confirmed posters that did it successfully. I only wanted to know if they flashed NJ6 or NK1 and what build of Odin they used..
Click to expand...
Click to collapse
Okay, to anyone whose interested: I used Odin 3.09 & NK1 (most current VZW build of 4.4.4) and it worked. Phone went into a bootloop, started recovery did a factory reset an it's back to normal.
Lollipop ran fine on my phone-probably because I reset it as soon as I updated...BUT, my data signal was halved. I get a weak LTE signal at work and by weak I mean 1 or 2 bars 105-115DB at best. Old brick building and I work in the basement. On lollipop, it wouldn't hold onto LTE anymore. It'd flip between 1x/3g..usually settling on 3G. Voice was unaffected. Hopefully they sort this out but this sort of signal performance (especially when it was fine on KK) is unacceptable.
Rolling back to NK1 has solved that. Thanks to the OP!
I can also confirm that flashing 4.4.4 NK1 from 5.0.0 OB6 works.
Tried it myself, but after I got done playing with it I went back to 5.0.0 OB6 afterwards.
I didn't look to see if it kept the 5.0.0 radio when downgrading to 4.4.4, but it kept the 5.0.0 boot loader.
I did not test the radio (as I didn't have a usable sim card at the time.)
Also, don't try to run URDLV on the 4.4.4 firmware before flashing, it will not boot (even with a factory reset.)
But I didn't try to flash a modified 4.4.4 firmware after 4.4.4 was already on there.
so just so I understand there's no root for 4.4.4 or 5.0 but it's possible to go back to 4.4.4 from 5.0 ?