Hello, im new here but not new in rooting Phones or Tablets !
I am Familar with all the rooting Procedures like CF-Autoroot files and Odin, how to prepare the Mobiles or Tablets with USB-Debugging security measures etc. but with one Phone now i have a big Problem and i can not solve it since i am working now over one week on that, googling reading hunderts of threads to this Problem, seeing lots of youtube videos, trying everything i see and learn, but with no results. Also here over XDA i could not find any resolution to the Problem so perhaps someone can help me in this because i think to give with this up !
So the Problem is that i have an Unrooted Samsung Note 3 Following Data:
Modelname: SM-N9005
Android Version: 5.0 (i guess Lollipop)
Basebandversion: N9005XXUEOF1
Kernel-Version: 3.4.0-4445722
[email protected] #1
Thu Juli 16 21:44:32 KST 2015
Buildnumber: LRX21V.N9005XXUEOF1
Hardwareversion: N900V.7
For Flashing: CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 + Odin 3.10 + Original Note 3 USB Cable + USB Drivers Note 3 Installed + Developer Option Activated = USB Debugging + Reactivating Lock = Disabled
After i enter in Note 3 Bootloader (odin) is written Following:
ODIN MODE
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: OFF
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A4, P1
Secure Download: Enable
UDC Start
So far i think everything seam to be O.K.
Then i start the Flashprocedure after it starts O.K. it stops in Odin with the Following Error/Fail:
<ID:0/014> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD%.. Do not unplug the cable..
<OSM> Please Wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is val
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Odin engine v(ID:3.1005)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> recovery.img
<ID:0/014> NAND Write Sart!!
<ID:0/014> FAIL! (Auth)
<ID:0/014>
Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the Note 3 Bootloader is written under UDC START two more Error lines:
SYS REV CHECK FAIL : No Version
SECURE MAGICCODE CHECK FAIL : recovery
So perhaps that is helping !? I have read in some Article that i have first with Odin to Flash an "PIT" File and after that then the normal CF-Auto-Root File !? But where too get the right PIT, and is this really need (i never had to use this procedure before) !?
Also i have read to use King-Root for PC that it will go everything in one way automatically, but i don't know as i use it or not, like i sayd before all other rootings where going with no Problems. Even a Downgrade and then rooting a Note 4 from Android 5.0 to 4.4.2 KitKat and it works since some Month like a charme !
Perhaps i make somthing wrong !?
I hope someone can help me !?
Thank's
The phone's motherboard is from a 900v, not a 9005.
Where did you get the phone?
I bought it from Amerzone Germany ! It was also send from there.
It's a brand new one !
I seen that also and was wondering that under Settings-Information there was standing a different Modelnumber (SM-N9005....) to the Odin Phone Bootloader where was standing: Product Name: SM-N900V
On the other Rooted Note 4 when there was Standing in Settings-Information: Modell SM-N9005..... then also the same was standing in the Odin Phone Bootloader information.
Do you think it will give a way to root, because like i think to understand your question is that i perhaps use the wrong CF-Autoroot tar !?
I just got from someone the advise to use: Root Samsung Galaxy Note 3 Verizon ( SM-N900V ) Lollipop 5.0 !
(the complete to downloadfile was written and uploaded 05.2016 seam to be quite new)
In the given description there are only view point's to follow after downloading zip.
They say something to Flash first one RAR1 with Odin, after that the phone seam to restart itself and goes back to Odin so that i can flash RAR2, after that the phone seam to reboot itself and then i should wait up King root (like super su apk is installed, then it should be done !?
Because like i understand now the answer from audit13 i do not have a n9005 like i belived (even written as Modelnumber SM-N9005) as that i have a n900v at that seam to be an Verizon Note 3 Model !?
Does someone knows about this or did it already !?
Is that right as normaly everywhere is written in the internet, that it is very difficult up to not possible to root a Verizon Note 3 and that it is not existing any cf-auto-root file for this !? And the XDA thread "[ROOT GUIDE] KNOX 0x0 NOTE 3 LTE (SM-N9005) LOLLIPOP DB 5.0 KNOX 0x0 [ROOT GUIDE]"seam to be very difficult and only for N9005 Models.
I have a note 3, refurbished. Kingroot did not work on my device, does anyone have a link that will allow me to root. I'm trying to recover accidentally deleted music files.
In download mode, it should say n9005, not n900v. I believe the n900v is a completely different model and was made for Verizon in the USA: http://www.cnet.com/products/samsun...a-gsm-android-smartphone-smn900vzwevzw/specs/
I would contact the seller right away.
O.K. audit13 that seam slowly also to me that there something is going on !
Like i rooted quite a lot different Models i was just thinking that it cannot be that i am not able in one week to get a note rooted.
The thing is in the phone setup it says n9005 in the Bootloader n900v and i looked now at the Samsung label under Battery to see what is standing there and it says: "Model SM-N9005" !
When i check this with my Note 4 it stands in Settings Model n910F... and in the Bootloader also n910F and on the Samsung Label Model: SM-N910F.
So there is all the same, i also took a Note 4 from my Family i also rooted some time ago and it also all three was showing the same.
So i believe it will give for me no chance to get it rooted, and then the Phone is useless for me. So i can not contact the supplier for what reason !? The Phone is in Perfect working Condition Unblocked i try three German Providers (Vodafone, O2, EPlus) all of them are working ! And i think i could not rechange the phone by the supplier with the reason that the Modelnumbers are all different and i could not root it !
I think the Supplier will laugh at me !
I will reset the Phone to "0" pack everything back in the Samsungbox and will try to sell it in eBay for a good Price ! Because i now that it gives people they use the Phone without root and they even don't want to root it !
Thank's anyway for time and help on this matter !
My first Phone what i could not root
Does the phone imei match the label on box or label under the battery?
Yes ! It Matches the imei number ! Like i said i bought it brand new and it was sealed in the Samsung Box ! All seam to be Original like i am used to know this from other Boxings of Samsung.
Nothing looks like a fake ore false ! Then i remember that a Friend of me came approx 2 Years ago back from Holiday (Hongkong) he brought to that time the first Note 3 with him and like i remember that it was to cheap, not working in German Network and you could feel and see that it where an Fake, like bad backlight and screen resolution the Android i have never seen and it was very slow in working.
So i can tell definitely that i have here an Original Samsung Note 3 !
Why do you ask ? Do you think it still will give an possible solution !
I have looked already in the Internet to buy a new other Note 3 ! Perhaps i will have with this more luck !? Then i can not believe that it will in general not be possible to root Note 3 phones !? It has to bee absolutely an Note 3 it is an wish from someone out of my Family (i own myself a Note 4 rooted).
Otherwise i would buy an Note 4 and root it !
I think the big question is what for a Phonemodel i have here a 9005 or a 900v (verizon) !?
And like courtie82 wrote he also could not root his Note 3 with Kingroot because it is Refurbished ??????
I am very mutch confused ! I am rooting Phones, even Flashing Custom roms, Unbranding after Contract from provider is at the end (so legal) and programming my own android apps, but i have to fail on this first Note 3 phone..............
If possible, you can examine the motherboard too. Apparently, this is a way to unlock the bootloader for a verizon 900v phone.
http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Related
hello! can someone please help me with my galaxy s4 GT-i9505. I really need your help on this!
this is what happened,
a few days ago, I Got my phone unlocked from its carrier GLOBE here in Philippines.
the tech flashed it with older firmware before unlocking my phone. all went well after that.. but my phone was running an older firmware since the tech flashed it with older firmware before unlocking it.
the next day, I decided to flash it and upgrade with the firmware I9505XXUDMH8 from this website http://www.ibtimes.co.uk/articles/504394/20130907/galaxys4-gti9505-official-android422-xxudmh8-jellybean-update.htm
all went well after that. but I encountered problems on rooting and flashing with custom kernel. I've learned that the firmware I flashed from this http://www.ibtimes.co.uk/articles/504394/20130907/galaxys4-gti9505-official-android422-xxudmh8-jellybean-update.htm website includes Samsung KNOX which they say can cause rooting problems and etc.
knowing all that stuff, I decided again to revert to an earlier version of android 4.2.2 for gt-i9505 which is the I9505XXUBMG5 which I got from sammobile.com. hoping to stay clear of the KNOX rooting issues.
when I tried to flash the I9505XXUBMG5 firmware with odin 3.07, it said FAILED and now I can't basically use my phone. I'm stuck on "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried flashing back the I9505XXUDMH8 which I got from here http://www.ibtimes.co.uk/articles/504394/20130907/galaxys4-gti9505-official-android422-xxudmh8-jellybean-update.htm but it still fails!! why???
I've read somewhere that the latest firmware I9505XXUDMH8 that contains KNOX can cause issues when you would try to downgrade to an earlier firmware.
I've just read that thing after I flashed to an earler version. hohohoh. has anyone been in this situation?
please help! I hope someone could help me on this. all insights will be greatly appreciated. thank you in advance!
Go to recovery and factory reset, should fix it.
If not Just flash MH8 again in Odin and then factory reset.
Sent from my GT-I9505
Obagleyfreer said:
Go to recovery and factory reset, should fix it.
If not Just flash MH8 again in Odin and then factory reset.
Sent from my GT-I9505
Click to expand...
Click to collapse
hey bro. I can't go to recovery. whenever I try to press and hold vol up+home+power, the screen would still show up the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" message..
i'm really getting worried. (((
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this what showed up when I tried flashing back the MH8 firmware.
jarold143 said:
View attachment 2276766
this what showed up when I tried flashing back the MH8 firmware.
Click to expand...
Click to collapse
1, Make sure u have no Kies programme running in the background kill all that and try flashing the firmware using odin
2 , if that does not wrk try flashing with "pit" file along and see the result make sure to use the correct pit file or use the link Here
Also try some different latest stock firmware u have it available
One suggestion don't panic all will be fine I have been to this situation more then 6 times using different galaxy devices all were recovered
U can also use the help thread link on my sign
Edit : http://forum.xda-developers.com/showthread.php?t=2419762 one more helpful link here
I had the same issue while flashing mh1 modem. I changed to different usb port and flashed my old modem back with newer odin.
View attachment 2276845
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
Click to expand...
Click to collapse
this is what odin showed up. I used different cable and different port. daaaang! what am I gonna do. huhuhu
jarold143 said:
View attachment 2276845
this is what odin showed up. I used different cable and different port. daaaang! what am I gonna do. huhuhu
Click to expand...
Click to collapse
Repeat procedure with odin 3.04
Sent from my Galaxy Nexus using xda premium
jarold143 said:
View attachment 2276845
this is what odin showed up. I used different cable and different port. daaaang! what am I gonna do. huhuhu
Click to expand...
Click to collapse
Try using Odin 3.07
or some firmware
Best option use link below amd post there he is best at this
http://forum.xda-developers.com/showthread.php?t=2265477&highlight=stock+firmware
UPDATE! problem SOLVED
thank you for all your responses. I've figured out the problem and found the culprit.
It was the USB ports of the PC I was using to flash the phone.
FIX: I tried flashing the phone from my gf's laptop with the MH8 firmware and wallah!! odin did not show any fail and I was able to use my phone back..
after everything went fine, I tried flashing back the UBMG5 firmware just for the heck of it. then ODIN showed failed. so I flashed back again to MH8 firmware and everything went OK again..
FOLLOW up Questions:
1. can't we really go back to an older firmware version?
2. I wonder what was causing my phone to constantly disconnect from the USB port. but in my gf's laptop seems to be ok and working
(I have tried it from two PC's.. it disconnects on my pc at home and my work pc)
jarold143 said:
FOLLOW up Questions:
1. can't we really go back to an older firmware version?
2. I wonder what was causing my phone to constantly disconnect from the USB port. but in my gf's laptop seems to be ok and working
(I have tried it from two PC's.. it disconnects on my pc at home and my work pc)
Click to expand...
Click to collapse
You are stuck with MH8 firmware, worse you have KNOX and can't use all those neat little apps that require system access to run.... Even if rooted...
The new bootloader that Samsung released is REALLY going to kill Samsung support in this community. Bit stupid really as most of the latest features on their new phones started out as an idea on this site by people who wanted more out of their phones and worked out how to do it....
ultramag69 said:
You are stuck with MH8 firmware, worse you have KNOX and can't use all those neat little apps that require system access to run.... Even if rooted...
The new bootloader that Samsung released is REALLY going to kill Samsung support in this community. Bit stupid really as most of the latest features on their new phones started out as an idea on this site by people who wanted more out of their phones and worked out how to do it....
Click to expand...
Click to collapse
damn. we'll i'm still hoping some developer would find a work around about this knox issue.
Same thing happened to me with MH6 (Singapore)
So here's the thing - I have a mild vision impairment and having bold fonts throughout the entire OS helps a lot. I've always used "MyFont" to change the UI font to Akzidenz Grotesk Bold (gorgeous font, really)
So anyway the MH6 update broke MyFont - something KNOX related I suppose - it couldn't apply the font changes anymore, even though it worked perfectly fine on stock unrooted MG5 firmware
So I dug up my old XXMEA firmware, Odined my phone... then I had the worst "bricking" experience I ever had
a. Couldn't make calls (black screen)
b. No sound output from speakers whatsoever (no boot sound, no touch tones, the phone doesn't "beep" when adjusting the volume, etc)
c. Erratic connectivity to H+
d. WiFi unable to turn on
e. Very unresponsive UI
So I updated to MH6 through Kies (on another PC), wiped data, and then it refused to get past the "Samsung Galaxy S4" screen - it just hung there. I flashed broodplank's vanilla 4.3 over it, and managed to at least boot up (albeit with the same issues). THEN I noticed that the baseband was still MEA - which meant that Kies kinda failed as it upgraded ONLY the main firmware but not the modem - perhaps that's why it wouldn't boot up?
After many hours of trial and error - I managed to get my phone back in working order.
1. Flashed XXUDMH6 modem
2. Downloaded XXUDMH6 (MM1, my telco) from samsung-updates.com, Odined it
3. Success
But it's kinda disheartening that Samsung "locked down" the phone with these latest updates.. what a shame. Definitely getting a Nexus when my contract is up.. even though here in Singapore they're overpriced
Hope this helps anybody stuck in the same scenario - the gist of it is.. if you want your phone to work properly, you can't downgrade your firmware. Kinda like Apple.
If irony were made of strawberries, we'd all be drinking a lot of smoothies right now - Newscaster Ned, South Park
Thank you adrian - I had exactly the same problems after I tried to re-install an older stock rom after the Knox install.
I had no wifi, the phone dialler would show a black screen and would crash the phone, plus i no longer had any system sounds.
This was down to an incorrect baseband and firmware combination that needed to be reflashed via Odin in the order that you mention in your post.
I have a German Telekom.de SGS4 and now have the following config:
Baseband I9505XXUDMH9
Kernel 3.4.0- 1220396 [email protected] #1
Build number JDQ39.I9505XXUDMH9
SELinux status: Enforcing
Thank you!
adrian3 said:
Same thing happened to me with MH6 (Singapore)
So here's the thing - I have a mild vision impairment and having bold fonts throughout the entire OS helps a lot. I've always used "MyFont" to change the UI font to Akzidenz Grotesk Bold (gorgeous font, really)
So anyway the MH6 update broke MyFont - something KNOX related I suppose - it couldn't apply the font changes anymore, even though it worked perfectly fine on stock unrooted MG5 firmware
So I dug up my old XXMEA firmware, Odined my phone... then I had the worst "bricking" experience I ever had
a. Couldn't make calls (black screen)
b. No sound output from speakers whatsoever (no boot sound, no touch tones, the phone doesn't "beep" when adjusting the volume, etc)
c. Erratic connectivity to H+
d. WiFi unable to turn on
e. Very unresponsive UI
So I updated to MH6 through Kies (on another PC), wiped data, and then it refused to get past the "Samsung Galaxy S4" screen - it just hung there. I flashed broodplank's vanilla 4.3 over it, and managed to at least boot up (albeit with the same issues). THEN I noticed that the baseband was still MEA - which meant that Kies kinda failed as it upgraded ONLY the main firmware but not the modem - perhaps that's why it wouldn't boot up?
After many hours of trial and error - I managed to get my phone back in working order.
1. Flashed XXUDMH6 modem
2. Downloaded XXUDMH6 (MM1, my telco) from samsung-updates.com, Odined it
3. Success
But it's kinda disheartening that Samsung "locked down" the phone with these latest updates.. what a shame. Definitely getting a Nexus when my contract is up.. even though here in Singapore they're overpriced
Hope this helps anybody stuck in the same scenario - the gist of it is.. if you want your phone to work properly, you can't downgrade your firmware. Kinda like Apple.
If irony were made of strawberries, we'd all be drinking a lot of smoothies right now - Newscaster Ned, South Park
Click to expand...
Click to collapse
adrian3 said:
Same thing happened to me with MH6 (Singapore)
So here's the thing - I have a mild vision impairment and having bold fonts throughout the entire OS helps a lot. I've always used "MyFont" to change the UI font to Akzidenz Grotesk Bold (gorgeous font, really)
So anyway the MH6 update broke MyFont - something KNOX related I suppose - it couldn't apply the font changes anymore, even though it worked perfectly fine on stock unrooted MG5 firmware
So I dug up my old XXMEA firmware, Odined my phone... then I had the worst "bricking" experience I ever had
a. Couldn't make calls (black screen)
b. No sound output from speakers whatsoever (no boot sound, no touch tones, the phone doesn't "beep" when adjusting the volume, etc)
c. Erratic connectivity to H+
d. WiFi unable to turn on
e. Very unresponsive UI
So I updated to MH6 through Kies (on another PC), wiped data, and then it refused to get past the "Samsung Galaxy S4" screen - it just hung there. I flashed broodplank's vanilla 4.3 over it, and managed to at least boot up (albeit with the same issues). THEN I noticed that the baseband was still MEA - which meant that Kies kinda failed as it upgraded ONLY the main firmware but not the modem - perhaps that's why it wouldn't boot up?
After many hours of trial and error - I managed to get my phone back in working order.
1. Flashed XXUDMH6 modem
2. Downloaded XXUDMH6 (MM1, my telco) from samsung-updates.com, Odined it
3. Success
But it's kinda disheartening that Samsung "locked down" the phone with these latest updates.. what a shame. Definitely getting a Nexus when my contract is up.. even though here in Singapore they're overpriced
Hope this helps anybody stuck in the same scenario - the gist of it is.. if you want your phone to work properly, you can't downgrade your firmware. Kinda like Apple.
If irony were made of strawberries, we'd all be drinking a lot of smoothies right now - Newscaster Ned, South Park
Click to expand...
Click to collapse
can i have a step by step of you have done?I got similar problem with your phone...I upgraded to 4.4.2, it wasn't good then I succesfully downgraded to 4.2.2 but not wifi, no sound, and dialer and ui problem. Im currently running on XXUAMDD fw...I tried flashing via odin 3.04, 3.07 and 3.09 I9505XXUEMK9 and I9505XXUEMKE firmwares but it always fails.
agent2727 said:
can i have a step by step of you have done?I got similar problem with your phone...I upgraded to 4.4.2, it wasn't good then I succesfully downgraded to 4.2.2 but not wifi, no sound, and dialer and ui problem. Im currently running on XXUAMDD fw...I tried flashing via odin 3.04, 3.07 and 3.09 I9505XXUEMK9 and I9505XXUEMKE firmwares but it always fails.
Click to expand...
Click to collapse
Means u cant downgrade no more bro. Once you have updated to a newer firmware, it also means that ur bootloader has also been changed.
So when u try to downgrade, u are only downgrading the firmware. But the bootloader still stays the same which only works for the latest firmware u've flashed. This might explain why some things i ur fone doesnt work after the downgrade.
Hope this answered ur question
Sent from my SM-N9005 using XDA mobile app
Hello experts,
I have the Samsung Galaxy S5 SM-G900F with the following details:
Android version: 5.0
Baseband: unknown
Kernel: 3.4.0-4209230 [email protected] #1
Build number: LRX21T.G900FXXU1BOB7
SE for Android status: Enforcing SEPF_SM-G900F_5.0_0007
My problem, as in the title of this thread, is with the SIM not being recognized at all and the reboot that occurs 3 times/minute. This happened before, after 10/15 resets, the phone " got back to normal " and everything was fine, then, I tried to fix the data mobile connection and after the reboot it snapped and didnt work..
I mention that the screen was replace, dont know if it has anything to do with it but I saw some topics online and wanted to mention.
WHAT I DID SO FAR:
Tried with 2 versions of Odin to downgrade to kitkat 4.4.2 but I think I got the wrong firmware (got the Germany one instead of UK) because it failed everytime with the mention Complete(write) operation failed.
Ill keep trying to downgrade but Im not sure the software is the real problem here as there are many many topics on this subject I wanted to ask for your oppinion.
Thanks in advance,
BR,
Adel
Also, when trying to flash the 4.4.2 kitkat back:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANG2_G900FVFG1ANG2_G900FXXU1ANG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideeas? Anyone? Help
adelnaser said:
Hello experts,
I have the Samsung Galaxy S5 SM-G900F with the following details:
Android version: 5.0
Baseband: unknown
Kernel: 3.4.0-4209230 [email protected] #1
Build number: LRX21T.G900FXXU1BOB7
SE for Android status: Enforcing SEPF_SM-G900F_5.0_0007
My problem, as in the title of this thread, is with the SIM not being recognized at all and the reboot that occurs 3 times/minute. This happened before, after 10/15 resets, the phone " got back to normal " and everything was fine, then, I tried to fix the data mobile connection and after the reboot it snapped and didnt work..
I mention that the screen was replace, dont know if it has anything to do with it but I saw some topics online and wanted to mention.
WHAT I DID SO FAR:
Tried with 2 versions of Odin to downgrade to kitkat 4.4.2 but I think I got the wrong firmware (got the Germany one instead of UK) because it failed everytime with the mention Complete(write) operation failed.
Ill keep trying to downgrade but Im not sure the software is the real problem here as there are many many topics on this subject I wanted to ask for your oppinion.
Thanks in advance,
BR,
Adel
Click to expand...
Click to collapse
Hey pal I hope you made a EFS backup just before you started to play with your phone as the problem mitht be in the EFS,
also try to flash the correct stock firmware the right one for your country and carreer,
if that does not work try to flash a custom rom and if that does not work check if you dont have the reactivation lock ON and if it is on you will not be able to flash ANYTHING by odin
Let me know how it goes
Hey,
I didnt made any backup as I factory reseted it several times (I cleaned it before) and I dont know what that EFS backup is...
Im trying now with the correct firmware to see if it works. The reactivation lock is disabled.
Thanks for reply, Ill come back with an answer.
Guys,
Still no success... 2 different firmwares and 3 ODIN versions, still fail with the same error.
Help?
adelnaser said:
Guys,
Still no success... 2 different firmwares and 3 ODIN versions, still fail with the same error.
Help?
Click to expand...
Click to collapse
and have you tryed to flash twrp or cwm recovery than a custom rom?
Did you try getting a new SIM card from your carrier?
It's probably not a software issue, but a card one.
I had the same problem you have and the first thing I did before doing anything else was replacing my old SIM with a new one and the issue resolved itself...
Please Help Accidentally Flashed kitkat Bootloder now i cant go Back to 4.3 and i think kk bootloader cause the phone frequent reboots in every
Roms , also battery draining too fast if it booted, Hanging in all applications Totally ******up Please............ There is lot of guys with the same problem
when i flash 4.3BL its failed @ aboot.mbn odin says failed "sw rev check fail fused 3 > binary2 is there anyway to bypass the aboot.mbn to
current binary or defuse the binary please help all kind of help appreciated please i want my old ldu worked
I am samsung reseller . Backup don't worked ,sry for bad English
This post is to help anyone that upgraded to Lollipop 5.0 from KitKat 4.4.2 with any newer 2012+ devices (Not just the Note 3, but also s4 etc.) exhibiting the symptoms in the title of this post.
So i picked up a Galaxy Note 3 SM-N900W8 and got the OTA update from KitKat 4.4.2 to Lollipop 5.0 and thought "Cool!" but alas, was I to be sadly informed of a major issue when I rebooted.
It started up fine but when I hit the back button it didn't respond. Then I hit the menu button and "Search" came up instead. I freaked, I lost my cool. Then my technical mind took hold and I started digging through XDA with their search tool thinking "Maybe i'm not the only one that is having this problem" and WOAH! Did I ever find a load of trouble.
Here's what i found out:
Ebay and Aliexpress sellers of replacement screens for alot (and i mean ALOT) of samsung phones from 2012 and newer used a compatible chip from a company called Cypress who makes the touchkeys chip for samsung (and other phone makers) and that OEM part number is CY8C20065. The sellers/manufacturers of replacement screens are using the compatible Cypress chip part which is the CY8C20236A.
The upgrade to 5.0 installs new firmwares throughout the phone INCLUDING the IC that controls the capacitive keys (Menu + Back) to version 0x12, from the KitKat version 0x10. The IC CY820236A is NOT compatible with the newer 0x12 firmware and gets hosed.
Now for a Solution that you may or may not like: The only way thusfar that I have found that works is to DOWNGRADE back to Kitkat 4.4.2 as anything higher screws the IC controller up and you will have to replace your LCD+digitizer (at $180+ this is not an option, cheaper to go get a phone online used with the original screen and everything stock) This is a fully STOCK recovery to a 100% working unit. No Root, other add-ons etc.
Now, unless someone (BIG HINT HERE to devs) can figure out this issue, alot of people are stuck with a paperweight. You can try and add the softkeys onto the screen, or flash this kernel but it WILL trip your Knox counter and set you to "Custom" Binary and Status.
I take NO credit for this post at all, I just almagamated the information from this and this post.
Do you wipe factory reset after flashing your rom???
jemis1983 said:
Do you wipe factory reset after flashing your rom???
Click to expand...
Click to collapse
Yes, if you read the threads, wiping the unit before primary boot has no effect on this issue at all. once you upgrade to Lollipop, the IC is written to and is corrupted after that. Nothing can stop this process save for a non-stock update/upgrade that has the 0x12 firmware altered/downgraded and that's where the kernel flash I listed comes in to restore (but void the warranty) the keys to proper working state.
Error in Odin
repherb said:
Yes, if you read the threads, wiping the unit before primary boot has no effect on this issue at all. once you upgrade to Lollipop, the IC is written to and is corrupted after that. Nothing can stop this process save for a non-stock update/upgrade that has the 0x12 firmware altered/downgraded and that's where the kernel flash I listed comes in to restore (but void the warranty) the keys to proper working state.
Click to expand...
Click to collapse
I recently udpated from 4.4.2 to lollipop on my Note 3 SM-N900A (Build N900AUCUEOC1) and have the soft key problem.
I tried the idlekernel option but that errors out in Odin.
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it says
SYS REV CHECK FAIL : No Version
SECURE MAGICODE CHECK FAIL : boot
I am novice at this, so how can I get around this.
i found a fix no root no kernel mod
The issue has been resolved!
http://forum.xda-developers.com/galaxy-note-3/help/to-fix-softkey-note-3-t3446134
I recently discovered the hard way that S7s have version fuses. These prevent you from installing certain older firmwares. This is convenient for Sprint as it prevents you from switching your SM-G930P to another carrier.
If you look at a Samsung firmware's release ID, such as G930UUEU4BQJ5, look at the 5th place from the right, in this case a 4. That is what I'm calling the firmware version.
I am on Sprint, and that carrier incremented its firmware version to 5 starting with QJ3 (Nov. 12, 2017). See https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/ for a firmware list.
A few weeks after that, I tried changing my phone from the Sprint SM-G930P to the unlocked SM-G930U. If you check https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/, you'll see that all variants of the U were and still are on firmware version 4. Also, T-Mobile is on 4, Verizon is on 4, and AT&T is on 4. (Why is AT&T's SM-G930A not on sammobile.com?)
Anyway, I got this error during the SM-G930U firmware install: SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4.
Not appreciating what this meant at the time, I managed to get the CP (modem software) from the SM-G930U on my phone as I tried the four files one at a time. It turns out you can put some older software on the phone. However, you need to have your current firmware around so that you can put things back if they don't work. Unfortunately for me, the firmware download for SM-G930P (Sprint) QJ3 didn't become available for about a week after I did this. I couldn't use a prior Sprint firmware because all before QJ3 had a lower firmware number. While the phone worked fine with this version mismatch, I had to endure repeated Knox security warning messages.
I since put the phone back on the SM-G930P firmware (once QJ3 became available for download!), and everything's happy now. No warranty fuse issues or anything, and I'm two OTA releases newer now than QJ3.
A more detailed write-up is here: https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/
I may not be searching on the right keywords, but I can't find anyone else reporting this. As mentioned at top, it's really convenient for Sprint that it incremented its firmware version. This lock out Sprint S7 owners from switching to another carrier. I can assure that you really need to change firmware to do that: I switched to T-Mobile for one month over the summer but kept the Sprint firmware on the (unlocked!) Sprint phone. Several bands were missing until I switched to the T-Mobile firmware. For now, Sprint S7 owners cannot do that unless there is some way to increment the firmware version number, but even then, I'd guess we'd have trouble installing the other carrier's OTA updates.
All US model S7s (Snapdragon) have locked bootloaders, this is why you cannot downgrade to older firmware
*Detection* said:
All US model S7s (Snapdragon) have locked bootloaders, this is why you cannot downgrade to older firmware
Click to expand...
Click to collapse
Is that version number (5 digit from right on version string) really for the bootloader version?
novasource said:
Is that version number (5 digit from right on version strong) really for the bootloader version?
Click to expand...
Click to collapse
Not sure what the numbers / letters mean in firmware versions
But that's the reason you can't downgrade
*Detection* said:
Not sure what the numbers / letters mean in firmware versions
But that's the reason you can't downgrade
Click to expand...
Click to collapse
Still, you typically don't downgrade to switch carriers (I didn't going from VZW to T-Mobile, for example)
(I was avoiding a network lock due to shens of the previous owner of the handset -hence the move to the UnCarrier from BigRed) - I also gained VoLTE and wi-fi calling; neither of which I could have kept on BigRed for some rather odd reason).
PGHammer said:
Still, you typically don't downgrade to switch carriers (I didn't going from VZW to T-Mobile, for example)
Click to expand...
Click to collapse
You are generally correct when it comes to Android software version (occasionally, you may need to jump back a minor Android release or two if the carrier you're going to isn't as up to date on releases as the carrier you're coming from).
However, Android software is just one of four files in a firmware package. The problem is the version number embedded in the firmware package itself, which might correspond to the bootloader version. This number prevents Sprint S7 owners from going to any other firmware: at this point as it appears that Sprint is the only one whose firmware (or bootloader?) version is at 5. All others appear to be 4 or lower.
The 4 and the 5 is the binary correct? I'm assuming that because that's where Odin always has the problem when I was pointlessly trying to root my SM-G935P on QL1 firmware.
Brianmagoon said:
The 4 and the 5 is the binary correct? I'm assuming that because that's where Odin always has the problem when I was pointlessly trying to root my SM-G935P on QL1 firmware.
Click to expand...
Click to collapse
The 4 and 5 are numbers I see in the firmware version strings that may correspond to the bootloader version. Regardless, if you've installed a firmware with a 5 in that version digit, then you cannot install any firmware with a lower version. So if you are on a Sprint-branded S7 and up to date, then you cannot install any other firmware until they also have a 5 in the firmware version string.
Yeah that sucks. I was really looking forward to rooting this beast. Looks like that won't be happening any time soon
Nobody incremented their bootloader revision except Sprint.
Everyone is still on bootloader 4 (VZW/ATT/TMO)
Sprint is now on bootloader 5
Also, none of this is a downgrade, they released identical versions with different bootloader revision
Example
Latest Sprint software
G930PVPU5BQL1
Latest OEM software
G930UUES4BQL1
They are basically identical softwares
This was done intentionally to stop unbranded G930U flashing which also results in European LTE bands 3/7/20 to be enabled
Sprint does not want these items to leave the United States.
sins07 said:
...
Also, none of this is a downgrade, they released identical versions with different bootloader revision
...
This was done intentionally to stop unbranded G930U flashing which also results in European LTE bands 3/7/20 to be enabled
Sprint does not want these items to leave the United States.
Click to expand...
Click to collapse
Confirms my suspicion, if you are sure the binaries are functionally the same.
Sadly I just picked up a sprint 7 edge last night with oct 1 2017 patch ..I neglected to do my homework on this device and of course its on 5b ..does anyone know the possibility or likeliness that other carriers would feel the need to go to 5B
Sincerely,
A screwed buyer
So question.. how did you manage to get the image for the S7 930P? I tried two different 930U images and now left with a cycling device. I can't seem to download the 930P image using sammobile. I've tried 4 different sites. Some say free downloads for 2gb or less and the image size is 2.3gb. Any working link would be greatly appreciated.
Hey Guys, I have the tmobile version and went through this when the phone first came out. I am rather certain that number does correspond to the bootloader version. At the time I wanted to install the U firmware on my stock tmobile phone and couldn't because tmobile version had a higher bootloader version. At the time tmobile was the only one with the higher bootloader iirc. Eventually all the carriers, including U, caught up to tmobile and I was able to downgrade.
Hey, would you gents mind helping me out. I had a failed root attempt, and ****s been a little crazy with my 930p. Currently I get this while trying to get back to anything which will make my phone work. I understand about the SW versions, and F sprint for that. However, would any of you be so kind as to simply tell me which files I need to get this thing to not be in a constant state of boot loading either in recovery or anything else. I get this on the download screen SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4 while Odin says this:
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth
tonysak said:
Hey, would you gents mind helping me out. I had a failed root attempt, and ****s been a little crazy with my 930p. Currently I get this while trying to get back to anything which will make my phone work. I understand about the SW versions, and F sprint for that. However, would any of you be so kind as to simply tell me which files I need to get this thing to not be in a constant state of boot loading either in recovery or anything else. I get this on the download screen SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4 while Odin says this:
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth
Click to expand...
Click to collapse
Had the same issue. After much trial and error (and a few boot loops and soft bricks) I was able to get the phone back to factory with firmware G930PVPU5BQL1 from another site (not sure if I'm allowed to link, but it has the words Samsung and firmware in the address, and it's a .org). Make sure you factory reset and wipe cache afterwards in recovery (hold power, home, volume up), and I'd recommend flashing the CSC rather than HOME_CSC to avoid duplicates in the settings menu. I unchecked auto reboot in Odin to make it easier to get to recovery without having to watch the whole install like a hawk. Also, don't sweat it if you get "Installing system update" and then "No command" when you boot into recovery mode. Just wait for a few minutes and it'll take you to the recovery menu. After the factory reset and cache partition wipe, you should be able to reboot and be have a squeaky clean install. YMMV but it worked for me. Good luck.
jessemcstew said:
Had the same issue. After much trial and error (and a few boot loops and soft bricks) I was able to get the phone back to factory with firmware G930PVPU5BQL1 .
Click to expand...
Click to collapse
Wanted to say thanks. I've been struggling with this issue for a couple of weeks on and off as I play with this S7. Really frustrating to be on my like 8th firmware download and still running into issues prior to the above.
Now that I have the phone back up and running, anyone know how to move to stock non-sprint android given the issues with the sprint bootloader? My preference would be to debloat and de-gaps but from all the reading in the past week or so it doesn't sound likely.
My hope was that given the rollout of oreo now that someone would have a v5 bootloader for sm-930U (generic S7 - non carrier version)
schmism said:
My hope was that given the rollout of oreo now that someone would have a v5 bootloader for sm-930U (generic S7 - non carrier version)
Click to expand...
Click to collapse
Your hopes are likely dashed.
1. Every US carrier has updated to Oreo and none of them have updated the bootloader to v5, except for Sprint. So if you have the latest Sprint firmware, you can't switch to anything else.
2. As of this writing, the US unlocked version (SM-930U) still has not been updated to Oreo. There is no announcement when it will be released. And there is no reason to think it will be v5.
Friends, until there is an upgrade to the bootloader of the G930U Firmware, i believe it is not possible to convert the sprint device with binary 5 to G930U
At the moment, what seems to work is doing it via flashfire. There is a tutorial posted on the youtube link here
No Samsung Apps
borispavlov said:
Friends, until there is an upgrade to the bootloader of the G930U Firmware, i believe it is not possible to convert the sprint device with binary 5 to G930U
At the moment, what seems to work is doing it via flashfire. There is a tutorial posted on the youtube link here
Click to expand...
Click to collapse
Yes, but you will see on their linked site that Samsung Apps will not run on this version. Probably should wait if you care about this.