Related
Hello Brothers...
I Have GT-N8000 Soft Bricked ( I think ) And it stuck at samsung logo foever...
In download mode it show me the following :
ODIN MODE
PRODUCT NAME : GT-N8000
CURRENT BINARY: Samsung Official
SYSTEM STATUS : Official
RP SWREV: A2
i tried to flash a lot of stock firmware from Sammobile.com but seem hopeless..
this is what Odin show me after tried to flash each files ( the result is exactly the same )
Code:
<ID:0/024> Added!!
<ID:0/024> Odin v.3 engine (ID:24)..
<ID:0/024> File analysis..
<ID:0/024> SetupConnection..
<ID:0/024> Initialzation..
<ID:0/024> Get PIT for mapping..
<ID:0/024> Firmware update start..
<ID:0/024> SingleDownload.
<ID:0/024> boot.img
<ID:0/024> NAND Write Start!!
<ID:0/024> FAIL!
<ID:0/024>
<ID:0/024> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
here are the name of firmware that i already flash it, just in case that i miss and latest bootloader and any working firmware :
N8000ZCCMH1_N8000CHNCMH1_N8000ZCCMH1_HOME.tar
N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar
N8000XXUDNH2_N8000OJVDNH1_N8000XXUDNH1_HOME.tar
N8000XXUDNH2_N8000OXXDNJ1_N8000XXUDNH1_HOME.tar
Please help me ASAP because i really need it working... i have a lot of work to do with it
Any help will be much appreciated...
Best Regards...
cdobia majority
No option to help me out sir?... Please help me...
I wish I could help but I have the same issue. I fear once you try (and fail..) to flash to 4.4 upwards you have problems. I have tried a mix of stock roms from 4.0-4.4 and always get the same results as you.
Some forums suggest using a different USB cable, different version of ODIN and also a different USB port.
I have tried all these things with no luck, but maybe it will help you out. I know have a samsung branded paperweight until someone (much smarter than me!) works out how to fix this problem with the Note.
force reboot to odin mode
flash a known working recovery [custom] for your device making sure automatic reboot is checked.
after tab reboots force reboot to recovery mode with button combo.
in recovery mode adb push known working custom rom.zip.
reboot to recovery from recovery.
flash custom rom.
as long as you haven't done anything damaging like flashing bad/wrong bootloader/firmware
you will be able to get odin to reboot.
if odin is telling your that you pit file is missing/damaged then you're done.
haven't heard of anyone successfully flashing/repartitioning with pit file in a long time.
or those who do are the kind who say "okay i fixed it" and never provide the details.
lastly and no offense, don't keep flashing like a spaz, you will just make the situation worse.
so long as you have an intact/functioning kernel in boot or recovery you can revive your device.
m
Hello..
i'm already Tried Flashing both Stock and custom Recovery.. but they are FAILED in Odin app while it flashing...
Do u have any working stock or custom recovery Links?...
UPD : is that RP SWREV: A2 Meanings is the bootloader have been locked sir?...
and if it locked... how can i unlock it ( with looping Tab and cant get in to recovery )
Much Appreciated
Rattanak
forget stock.
as for odin try version 3.07 http://d-h.st/4VU
been using this version for years. devices flashed gt-p5210 gt-n8013 sm-t210r gt-p3113 sm-t530nu
for recovery search forums and read OP's completely as well as threads.
as a thought goto the gnabo rom thread and follow complete instructions.
again read the OP completely as well as the thread
Maybe this post over on the S4 page could help us:
http://forum.xda-developers.com/showthread.php?t=2744061
I will be giving this a try tomorrow.
I tried odin 3.07 and have tried most of the roms here. The issue is with the failed kitkat updates as the bootloader is locked - from that point forward going anywhere seems to be the issue. This downgrade might bring the device back to life - watch this space I guess.
Progress
well it was because of the EMMC It self..
i try to JTAG it with z3x JTAG and it not responding... im working on it and will back for more detail...
Regards
If this happened after a failed KitKat update then only KitKat Roms will work for you, officially it can't be dowgraded, I just need to know if your device is branded or unlocked, as far as I can tell, you flashed a Rom that is not meant specifically for your device, it flashed the boot.img then failed to flash system.img, later on when you tried to fix it,you get failure at the boot.img stage as you can't downgrade it anymore through Odin, if your device is unlocked you should be able to flash any KitKat stock rom from Sammobile for any region not necessarily your region.
Sent from my SM-G800H using XDA Free mobile app
Ahmedivx said:
If this happened after a failed KitKat update then only KitKat Roms will work for you, officially it can't be dowgraded, I just need to know if your device is branded or unlocked, as far as I can tell, you flashed a Rom that is not meant specifically for your device, it flashed the boot.img then failed to flash system.img, later on when you tried to fix it,you get failure at the boot.img stage as you can't downgrade it anymore through Odin, if your device is unlocked you should be able to flash any KitKat stock rom from Sammobile for any region not necessarily your region.
Sent from my SM-G800H using XDA Free mobile app
Click to expand...
Click to collapse
so you are going to tell me that this N8000 is Locked?...
Regards
Rattanak said:
so you are going to tell me that this N8000 is Locked?...
Regards
Click to expand...
Click to collapse
No I'm not saying that it's locked, I'm asking you whether it's locked or not, do you have to use a certain network/carrier at your country ? If you can use sim cards from different carriers / service providers then your device is not locked
Sent from my SM-G800H using XDA Free mobile app
Ahmedivx said:
No I'm not saying that it's locked, I'm asking you whether it's locked or not, do you have to use a certain network/carrier at your country ? If you can use sim cards from different carriers / service providers then your device is not locked
Sent from my SM-G800H using XDA Free mobile app
Click to expand...
Click to collapse
Well i dont think that it was locked because i can use any carrier in my country here. Plus.. i think it was international version that you can put any SIM Card in it...
Regards...
Rattanak said:
Well i dont think that it was locked because i can use any carrier in my country here. Plus.. i think it was international version that you can put any SIM Card in it...
Regards...
Click to expand...
Click to collapse
OK great then you have no problem using any of sammobile firmwares for the GT-N8000 international version.
So totally non committal, but I managed to fix my Note 10.1 today I hope it works for you.
I had been trying to upgrade to android 4.4.2 using a custom rooted rom but got stuck in a boot loop with my only option as download mode (no CWM, no reset, nothing just bootloop download only).
As a last resort I downloaded a Note 10.1Android 4.0.4 pit file and flashed it from odin 3.07 (pit file selected, Auto Reboot ticked, Re-partition ticked, F.Reset Time ticked - everything else unticked). Flashed the pit file, let the tablet reset and then it picked up the android update as though all was fine. The device is now working fine and without issue.
The .pit file i used is attached. Cant promise it will work, but I hope you have the same luck I do.
Rattanak said:
Hello Brothers...
I Have GT-N8000 Soft Bricked ( I think ) And it stuck at samsung logo foever...
In download mode it show me the following :
ODIN MODE
PRODUCT NAME : GT-N8000
CURRENT BINARY: Samsung Official
SYSTEM STATUS : Official
RP SWREV: A2
i tried to flash a lot of stock firmware from Sammobile.com but seem hopeless..
this is what Odin show me after tried to flash each files ( the result is exactly the same )
Code:
<ID:0/024> Added!!
<ID:0/024> Odin v.3 engine (ID:24)..
<ID:0/024> File analysis..
<ID:0/024> SetupConnection..
<ID:0/024> Initialzation..
<ID:0/024> Get PIT for mapping..
<ID:0/024> Firmware update start..
<ID:0/024> SingleDownload.
<ID:0/024> boot.img
<ID:0/024> NAND Write Start!!
<ID:0/024> FAIL!
<ID:0/024>
<ID:0/024> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
here are the name of firmware that i already flash it, just in case that i miss and latest bootloader and any working firmware :
N8000ZCCMH1_N8000CHNCMH1_N8000ZCCMH1_HOME.tar
N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar
N8000XXUDNH2_N8000OJVDNH1_N8000XXUDNH1_HOME.tar
N8000XXUDNH2_N8000OXXDNJ1_N8000XXUDNH1_HOME.tar
Please help me ASAP because i really need it working... i have a lot of work to do with it
Any help will be much appreciated...
Best Regards...
Click to expand...
Click to collapse
Hi Ratanak,
I think you're Cambodian and me too. I got the problem like you. Since I flashed the cm12 for about 1 week, it sudddently auto reboot and stuck in " Samsung Galaxy note 10.1 GT-N8000" logo. I've tried many ways.. Different version of odin, Sammobile web.. nothing work.. How about you?? Have you fix it yet? I hope to hear from you back.
regard,
Tony
---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------
geekyhawkes said:
So totally non committal, but I managed to fix my Note 10.1 today I hope it works for you.
I had been trying to upgrade to android 4.4.2 using a custom rooted rom but got stuck in a boot loop with my only option as download mode (no CWM, no reset, nothing just bootloop download only).
As a last resort I downloaded a Note 10.1Android 4.0.4 pit file and flashed it from odin 3.07 (pit file selected, Auto Reboot ticked, Re-partition ticked, F.Reset Time ticked - everything else unticked). Flashed the pit file, let the tablet reset and then it picked up the android update as though all was fine. The device is now working fine and without issue.
The .pit file i used is attached. Cant promise it will work, but I hope you have the same luck I do.
Click to expand...
Click to collapse
Thanks for your shares..
it doesn't work for me..
tonykhatthy said:
Hi Ratanak,
I think you're Cambodian and me too. I got the problem like you. Since I flashed the cm12 for about 1 week, it sudddently auto reboot and stuck in " Samsung Galaxy note 10.1 GT-N8000" logo. I've tried many ways.. Different version of odin, Sammobile web.. nothing work.. How about you?? Have you fix it yet? I hope to hear from you back.
regard,
Tony
---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------
Thanks for your shares..
it doesn't work for me..
Click to expand...
Click to collapse
Hello, I am in the same situation with my Note n8000 from China, It only can access to download mode. I have tried everything, using all version odin, Heimdall and adb, and the results are: nand write error, failed to unpack recived packet and device offline. Still on samsung logo all the time, even charging it. I unplugged the battery cable even for more than two hours and nothing. I tried many roms, from sammobile, cwd... I don't know what else I can do... please help.
Judged by your post and NAND write failure means you have damaged the NAND memory and require probably a new motherboard .
But search for Nand failure fixes first .
Hello sorry for super late reply... i left XDA for like half a year ...
i finally sort that problem out on changing its EMMC works for me...
Regards...
Rattanak said:
Hello sorry for super late reply... i left XDA for like half a year ...
i finally sort that problem out on changing its EMMC works for me...
Regards...
Click to expand...
Click to collapse
how much did the change of EMMC chip costed you?
I also have same problem
Hi. I got my S6 (G920F) with Vietnam CSC which is XXV. I wanted to flash a different region CSC like XTC but there's an error with Odin: "write Nand.. FAIL" and on my device it says "SW REV Check fail Device 4 Binary 3". What does it mean? Thanks.
Anyone?
It means "not compatible" check update for your device..
SW REV Check fail Device 4 Binary 3 means that fw you are trying to flash is older than the one currently on the phone, and of course downgrade is not possible with most Samsung Android versions.
Hello I have an issue. Up until now I have not have any issues with Download Mode, but not it shows "RPMB fuse is blown" and "RPMB Provision". I was trying to flash stock Android 7.0 but it always fails, usually the phone displays the message "sw rev check fail fused 2 binary 1". If anyone could give me some guidance on how to fix this or just the info for what RPMB fuse blown means that would be great! The model of the phone is SM-G950U, and yes I used the correct firmware for the flashing. I have also tried to use different varients of Odin.
Try searching on Google.... There are boatload of answers there... I just checked
I've been on forums enough to know that this will be an annoying question, but I'm having a hard time figuring this out. I just got my friends SM-G930A, an AT&T version of the phone. I have been reading and it appears that the two versions of the phone are the exact same hardware, so that means if we could simply flash the Verizon software on this phone everything would sunshine and rainbows. How would I go about doing this? What would prevent me from doing this? Please any suggestions are welcome!
It'll flash without issue, but network performance may vary using one carriers phone on another's network due to band support.
You can get the G930V firmware from sites like updato.com, sammobile.com, or using samfirmtool, G930U is also an option.
You'll need a patched Odin to get around mismatch errors https://forum.xda-developers.com/and...-13-1-t3762572
Some flash guides:
https://android.gadgethacks.com/how-to/use-odin-flash-samsung-galaxy-stock-firmware-0182037/
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
I was originally under the impression they're all identical, but according to this thread there are some modem differences https://forum.xda-developers.com/galaxy-s7/help/att-sm-s930a-to-sprint-sm-s930u-t3913347 so YMMV
Beanvee7 said:
It'll flash without issue, but network performance may vary using one carriers phone on another's network due to band support.
You can get the G930V firmware from sites like updato.com, sammobile.com, or using samfirmtool, G930U is also an option.
You'll need a patched Odin to get around mismatch errors https://forum.xda-developers.com/and...-13-1-t3762572
Some flash guides:
https://android.gadgethacks.com/how-to/use-odin-flash-samsung-galaxy-stock-firmware-0182037/
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
I was originally under the impression they're all identical, but according to this thread there are some modem differences https://forum.xda-developers.com/galaxy-s7/help/att-sm-s930a-to-sprint-sm-s930u-t3913347 so YMMV
Click to expand...
Click to collapse
You are awesome! Looks like that first link to the patched Odin doesn't work anymore, would you be able to give me a working one? Thank you so much though this is good to hear! Even if it doesn't work I have another phone I could use.
Beanvee7 said:
It'll flash without issue, but network performance may vary using one carriers phone on another's network due to band support.
You can get the G930V firmware from sites like updato.com, sammobile.com, or using samfirmtool, G930U is also an option.
You'll need a patched Odin to get around mismatch errors https://forum.xda-developers.com/and...-13-1-t3762572
Some flash guides:
https://android.gadgethacks.com/how-to/use-odin-flash-samsung-galaxy-stock-firmware-0182037/
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
I was originally under the impression they're all identical, but according to this thread there are some modem differences https://forum.xda-developers.com/galaxy-s7/help/att-sm-s930a-to-sprint-sm-s930u-t3913347 so YMMV
Click to expand...
Click to collapse
Never mind on the link, I went and looked through your posts and found it. One more thing I need to bother you about is, when I flash it it says "Unsupport dev_type" on the phone, and Complete(Write) operation failed on ODIN. Any ideas?
From a google search that seems to be most commonly cause by flashing firmware for the wrong SoC, which firmware did you download and from where?
Other posts say make sure you run Odin as admin, and also on your phone go to setting> security and turn off 'reactivation lock'.
Beanvee7 said:
From a google search that seems to be most commonly cause by flashing firmware for the wrong SoC, which firmware did you download and from where?
Other posts say make sure you run Odin as admin, and also on your phone go to setting> security and turn off 'reactivation lock'.
Click to expand...
Click to collapse
By 'reactivation lock' do you by chance mean OEM unlock? And should I allow the device to be OEM unlocked or should I not allow that?
Different to OEM lock, its a security setting that will trigger FRP lock if you flash. But it's not an option on my own device, I just found it online.
Beanvee7 said:
Different to OEM lock, its a security setting that will trigger FRP lock if you flash. But it's not an option on my own device, I just found it online.
Click to expand...
Click to collapse
Yeah I can't find anything like that but when I'm in download mode it does say:
FRP LOCK : ON
So I assume that is something I need to address.
EDIT:
I'm using the patched 3.13 version of ODIN and it gets stuck on boot.img, but I assume that has something to do with FRP LOCK : ON
EDIT 2:
I might have soft bricked my phone actually. It appears that by flashing the new operating system while FRP LOCK was ON, it won't boot, recovery mode creates a boot loop, and ODIN is the only function I can effectively access. What would you suggest?
I might have soft bricked my phone actually. It appears that by flashing the new operating system while FRP LOCK was ON, it won't boot, recovery mode creates a boot loop, and ODIN is the only function I can effectively access. What would you suggest?
Try again the stock firmware the original carrier of the phone (AT&T?), or restoring with Samsung Kies/Smart Switch
This thread has a few other methods https://forum.xda-developers.com/note5/help/frp-lock-odin-firmware-lord-help-t3191927 (although for a different model, so dont try the linked firmware)
Beanvee7 said:
Try again the stock firmware the original carrier of the phone (AT&T?), or restoring with Samsung Kies/Smart Switch
This thread has a few other methods https://forum.xda-developers.com/note5/help/frp-lock-odin-firmware-lord-help-t3191927 (although for a different model, so dont try the linked firmware)
Click to expand...
Click to collapse
The only AT&T firmware I can find is this one:
https://forum.xda-developers.com/at...-g930a-stock-oreo-odin-g930aucu4cre4-t3803858
But the issue is the AP isn't in md5 format, and the BL is not wanting to cooperate.
Got it to go into a mode that says:
"Use the Emergency recovery function in the Smart Switch PC software."
So I downloaded both Kies and Smart Switch, but they both say "Unsupported Device" so I'm not quite sure why it has me use the software when it's not supported.
I also tried at downloading Samfirm but it wants the serial number of the phone, which I do not have.
What would be your next move?
EDIT: This might help the diagnosis, when I flash the full firmware I get an error on the phone that says, "SW REV CHECK FAIL : [aboot]Fused 8 > Binary 4, [1] eMMC write fail: aboot" and that seems to be the primary issue going on. I found another firmware for the USA AT&T and this keeps happening so that appears to be the main issue. A quick Google search tells me that my phone is a 8 binary and the ROM I'm flashing is a 4 binary. I honestly don't know what that means but I understand that the two numbers being different are the issue. Could you point me in the right direction for finding the right firmware?
I've used sideload before, any chance we can use sideload or does that require we be able to mount /system and have a ROM already installed and all that?
Thank you for your help!
Samfirmtool should work, I only ever recall having to enter the model number
Otherwise you can get it from
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/ATT/
or
https://updato.com/firmware-archive-select-model?q=SM-G930U&rpp=15&r=ATT&order=date&dir=desc&exact=1
The G930A now uses G930U firmware releases
That binary error I believe is because you're trying to flash a BL file older than what your phone has, and you can't downgrade bootloader
Beanvee7 said:
Samfirmtool should work, I only ever recall having to enter the model number
Otherwise you can get it from
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/ATT/
or
https://updato.com/firmware-archive-select-model?q=SM-G930U&rpp=15&r=ATT&order=date&dir=desc&exact=1
The G930A now uses G930U firmware releases
That binary error I believe is because you're trying to flash a BL file older than what your phone has, and you can't downgrade bootloader
Click to expand...
Click to collapse
I was able to get all of them to flash but AP, which hangs up on system.img.ext4 when flashed individually, with just AP checked. The model number has changed to SM-G930U, instead of SM-G930A, which it was before. So I know we're moving in the right direction, but I still can't get the AP to flash, and it either gets hung up on recovery.img or system.img.ext4, depending on what version of ODIN I use. It no longer gives me any mismatched model number errors though because of the new model number. We're heading in the right direction. Any ideas on it being held up though?
To confirm what you said earlier, you're using this patched Odin? https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Beanvee7 said:
To confirm what you said earlier, you're using this patched Odin? https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
I believe so but I went ahead and re-downloaded it and tried it again just to make sure I wasn't having a lapse in memory. I set it all up and ran it again and this is my log so far:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5418 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> pmic.elf
<ID:0/003> rpm.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> keymaster.mbn
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> sec.dat
<ID:0/003> NON-HLOS.bin
and then it hangs there for what seems like forever. The model number has changed to G930U instead of G930A like it was so we're moving in the right direction. But it sits at that NON-HLOS.bin forever.
And just in case it matters my screen on my phone says:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930U
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B9(2, 1, 1, 1, 1) K9 S9
SECURE DOWNLOAD : ENABLE
So i bought this refurbished note 8 (SM-950U) T-mobile varient.
at first everything ran fine until i signed in my google account, thats when the phone starting doing random stuff, like opening playstore and downloading apps without notifying.
well that was the least of my concern, when i tried to update my device, it gave an error "Processing failed" as it failed to register the device.
This is what is in my device right now.
AP: N950USQS4CRE1
CP: N950USQU5CRG7
CSC: N9500ZZH2CRD5
AP and CP seemed ok as both are from the same models, but that CSC file is from SM-N9500 model and as far as i know that is from chinese region and from dual sim models.
The next thing i tried was flashing it through odin with stock firmware that i downloaded from Sammobile.
The files i download are these "
Build date:Thu, 26 Jul 2018 04:01:45 +0000
Security Patch Level: 2018-07-01
Product code: TMB
PDA:N950USQU5CRG7
CSC :N950UOYN5CRG7 "
cant post the links here
i tried to match atleast the build number of my device to the files i downloaded.
After loading the file in odin, connected my phone (turned on debugging mode and removed all of my accounts),
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4857 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
so after researching the internet i found that there were reports of malware in samsung devices in certain regions, and i am certain that i have got one in my phone, so i am really scared to put my passwords or data in it technically rendering it useless.
i cant return the phone, so im stuck with this.
Dude, try flashing TWRP and delete everything, the entire OS and then try to reflash stock ROM with Odin or just flash a custom ROM with TWRP, hope it'll help!
DankMemz said:
Dude, try flashing TWRP and delete everything, the entire OS and then try to reflash stock ROM with Odin or just flash a custom ROM with TWRP, hope it'll help!
Click to expand...
Click to collapse
thanks for the input bro, there was problem with kies and drivers, tried on other computer with same odin version and firmware and everything worked like a charm.
abidhaidary said:
thanks for the input bro, there was problem with kies and drivers, tried on other computer with same odin version and firmware and everything worked like a charm.
Click to expand...
Click to collapse
Glad to help!
hello there,
i've bought a refurbished Galaxy Note 8 and encountered similar problem (missmatch between AP, CP, and CSC)
and my camera results is really really poor, at first i think there were hardware problem and i've tried to change it with the new galaxy note 8 camera and the results is still same.
is there any suggestion regarding this issue ?
did i need to flash my device to its stock firmware ? if it so, what is the correct firmware for my device ?
this is information that shown when i dialed *#1234#:
AP : N9500ZHU4DSD1
CP : N950USQU5DSC1
CSC : N9500ZZH4DSD1
thank you for your helps,
is there a fix were you guys able to flash original OS n950U rom? I also noticed my phone can't run 4g