I need help flashing my phone back to regular old Verizon stock/factory 4.4 NC5 default. I tried downgrading my phone back to 4.3 by flashing my phone and did so incorrectly causing it to no longer accept or make calls. Now I'm just trying to revert everything back to normal. I tried flashing the MK2, MDK, ME7 and a few other older stock roms but Odin kept failing at aboot.mbn. If I read things correctly, this is due to the fact that I cant flash older ROM's after upgrading but I'm not 100% sure if that's whats causing it.
Right now I just want to find a regular stock Verizon Galaxy S4 NC5 4.4 ROM to flash in Odin and revert things back to normal. Please help.
Phone Details
SCH-I545
Android Version: 4.3
Baseband Version: I545VRUEMK2
kernel Version: 3.4.0
Build Number: JSS15J.I545VRUEMK2
SE for Android Status: Enforcing SEPF_SCH-I545_4.3_0012
I hope this info helps. Please help.
You are right the challenges you had were due to the fact that you tried to downgrade when you can't. Another thing you want to know is that 4.3 Firmware does not get signal if you flashed older modem/radio.
If you want just the Stock Firmware without Rooting or anything, then try this thread. Otherwise you might be able to go through KIES and pull emergency Firmware option. (Don't remember what its precisely called.).
You might also be interested in this thread where Deodexed firmware is posted without Knox.
Perseus71 said:
You are right the challenges you had were due to the fact that you tried to downgrade when you can't. Another thing you want to know is that 4.3 Firmware does not get signal if you flashed older modem/radio.
If you want just the Stock Firmware without Rooting or anything, then try this thread. Otherwise you might be able to go through KIES and pull emergency Firmware option. (Don't remember what its precisely called.).
You might also be interested in this thread where Deodexed firmware is posted without Knox.
Click to expand...
Click to collapse
This is awesome information Perseus!! Thank you very much! You've confirmed my beliefs and pointed me in the right direction.
I don't know what Deodexed or Knox is but I'll look at that thread and read up on it. Thanks!
Related
I see, that we have nothing normal here, just Q&A with persons, so I decided to do guide if you have soft bricked phone or you want go from JB to GB or other questions.
Question: I somehow bricked my phone
Answer: If you can boot your phone and see bootloop (Samsung and device name), everything is fine. You just need to go to download mode (hold volume down + home button + power about 4-5 seconds), download Odin 3.07 and Russian FirmWare. Flash Russian FirmWare (just CODE_GT-I8160_I8160XXLK6... file) with Odin PDA and your device is alive again.
Question: I have JB, but I want GB back.
Answer: Easy. Download Russian FirmWare, flash with Odin 3.07. Find your wanted GB FirmWare version in SamMobile.com and flash it with Odin 3.07 again. You have GB once again.
Question: I have GB and I want JB. Which version to install?
Answer: It seems ME7 is best version, but you can still try MF1 or any other.
If you have any other questions, please ask and I will help in this thread.
If you want to go from JB back to GB on P version ?
Shadowcareful said:
If you want to go from JB back to GB on P version ?
Click to expand...
Click to collapse
Sorry, I don't have P version and I can't test and tell that. I have regular I8160.
To put it simply, no matter what happen (I mean bootloop, caused by anything), the only solution is to flash that Russian Firmware and Flash the Firmware of your choice (either GB or JB), right?
Many, many thanks for this. After bircking my Ace 2 and trying all kinds of ways of reflashing the stock ROM this is the only thing that worked. So, you've saved my phone - and me some expense.
Now, however, I have a new issue. The Russian version won't update, so I would like to revert to a UK stock ROM with JB 4.2.2. Given my recent epxerience thohgh, I am wary of trying to flash anything again. Any advice on a "safe" way to do this?
StevePC said:
Many, many thanks for this. After bircking my Ace 2 and trying all kinds of ways of reflashing the stock ROM this is the only thing that worked. So, you've saved my phone - and me some expense.
Now, however, I have a new issue. The Russian version won't update, so I would like to revert to a UK stock ROM with JB 4.2.2. Given my recent epxerience thohgh, I am wary of trying to flash anything again. Any advice on a "safe" way to do this?
Click to expand...
Click to collapse
we have cm10.1 and so on, but no stock 4.2.2, were you trying this?http://forum.xda-developers.com/showthread.php?t=2363309
Typo
Sorry I meant JB 4.1.2 which is the last official version for the Ace 2.
Hey guys!
Each phone company has its own policies and ways to void users' warranties when installing custom firmwares/roms on their phones.
Unfortunately, I didn't give myself enough time to read about Samsung's crap being very busy lately.
You're pretty lucky if you bought a phone with a 4.2.2 firmware (I9500 in my case). You do have a binary counter as much as I can recall, but it's not as big of a deal as KNOX (and warranty bit, you can find that in your download mode) which was introduced in the OTA (i.e 4.3 firmware).
I strongly recommend not to update your phone to 4.3, and I will list the reasons why; but I want to give some tips beforehand.
Make a full nandroid backup if you're planning to change roms. It is very important to have your factory firmware with you; you will need it at some point. Keep it in a safe place.
Backup your EFS folder and keep it in a safe place too. Your EFS has your IMEI, MAC address, serial number and many other important things. There are many ways to backup your EFS folder.
Do NOT use a custom recovery to back it up for you.
Open Dialer, write *#1234# and take a screenshot of (or write down) the version numbers of AP, CP and CSC (which correspond with PDA, PHONE (MODEM) and CSC respectively).
Keep at least 2-3 GB free in your internal storage before flashing any rom.
Some ROMs like MIUI are flashed through ODIN. What happens is that CWM is installed by flashing the .tar file supplied by MIUI and CWM in-turn flashes the ROM. Do not use that method. Flash the zip file from your custom recovery instead. Don't forget to wipe cache/data before flashing the rom.
Click to expand...
Click to collapse
You are lucky if you have 4.2.2. Why? Read on.As mentioned earlier, Samsung introduced a new KNOX security system to which our knowledge is limited so far. The flash counter has been replaced with that annoying KNOX. We don't know where the Boolean flag is store yet (some people claim it is an eFuse); but the truth is still unknown (to my limited knowledge anyway ).
The new update to 4.3 added a line in the Odin Mode, which is "Warranty bit: 0x[0|1]".
* A bit of 0x0 means that KNOX is still active.
* A bit of 0x1 means that KNOX is inactive.
The Warranty bit gets triggered (0x1) when you flash a custom recovery, custom ROM or root. [Some even say that it happens even if you flash a stock firmware through ODIN (someone please confirm that).]
More information about the KNOX behavior can be found here.
Enough about KNOX, now what is your advantage?
Being on a 4.2.2 firmware does trigger your binary counter when flashing custom ROMs. For I9505 users, it is easy to reset using Triangle Away. For us I9500 users, we don't really have one yet (maybe never), but we can still flash official firmwares or custom ROMs, and Samsung probably will not even bother looking at the counter. Worst cases, you could upgrade to 4.3 which will eliminate the flash counter but will get you in a bigger hole, the KNOX monster.
No matter what you go through, do not update to the official 4.3. Use a custom ROM instead. Most (if not all) of the 4.3 custom ROMs have KNOX security disabled. So you will have a 4.3 ROM without the KNOX (Warranty bit) hassle.
In-case you need an official firmware, find yours on Sammobile or Samsung-Updates and choose the 4.2.2 one.
Click to expand...
Click to collapse
Errors with IMEI, serial number, etc. ("Emergency calls only" error).You may face times when you flash different ROMs that either a bad flash corrupted your EFS or simply something in your modem got messed up. Check your system status after each flash (Settings -> About -> Status).
An IMEI that is either 0 or starts with 0049, signifies an error and will leave your phone in a state where you can make "Emergency calls only".
In-case of an IMEI with 0049, I would suggest flashing your modem again. Remember the first nandroid backup you did? Go to your recovery (PhilZ touch or CWM) -> Custom Backup and Restore and choose modem. This should fix your issue.
If the solution above does not do it for you, restore the EFS you had backed up before.
Q: I did not have any backup of my factory firmware. What should I do now?
A: Try to find your Factory CP (modem). A collection of modems could be found here. Otherwise, you can find some informative things in here which will tell you more details about your country specific firmware.
Click to expand...
Click to collapse
I will keep on adding more things but for the time being, I hope this was informative and helped you in anyway.
Please let me know if I said anything wrong or missed any important details.
Thank you!
Best regards,
Claude
Reserved.
Reserved 2.
Reserved
Some useful information thanks
I wish this post existed before which would basically prevent me from buying S4. I was told about this issue however I was naive and decided to buy S4 from the store thinking that all the new devices have 4.2.2 and the old bootloader. To my surprise when I took the new device from the box and loaded to download mode it already had the bootloader with the KNOX.
anubius said:
I wish this post existed before which would basically prevent me from buying S4.
Click to expand...
Click to collapse
Yeah, luckily I'm still on 4.2.2 with custom rom (foxhound) because I was really happy with it and therefore I didn't read the S4 at all but today I decided to upgrade to Kitkat and discovered this new Knox crap.
Is it possible for me to format the phone, put it on 4.2.2 stock and then root and flash custom rom again? Because my internal sd is full of old folders and files from previous roms.
PedroFlaxh said:
Yeah, luckily I'm still on 4.2.2 with custom rom (foxhound) because I was really happy with it and therefore I didn't read the S4 at all but today I decided to upgrade to Kitkat and discovered this new Knox crap.
Is it possible for me to format the phone, put it on 4.2.2 stock and then root and flash custom rom again? Because my internal sd is full of old folders and files from previous roms.
Click to expand...
Click to collapse
Even if you manage to install an 4.2.2 rom Knox will still be 0x1. But users from European Union like you are not affected by Knox 0x1. Rooting your device does not lead to warranty void.
PedroFlaxh said:
Yeah, luckily I'm still on 4.2.2 with custom rom (foxhound) because I was really happy with it and therefore I didn't read the S4 at all but today I decided to upgrade to Kitkat and discovered this new Knox crap.
Is it possible for me to format the phone, put it on 4.2.2 stock and then root and flash custom rom again? Because my internal sd is full of old folders and files from previous roms.
Click to expand...
Click to collapse
From what I've read it is impossible to downgrade to older version since new bootloader prevents it. Your only option is to join the dark side by installing CWM and install custom roms but you will have 0x1. However as mentioned in the previous post the warranty should still work since you are in EU, however you never know with Samsung. Time will tell.
Hello and happy new year all.
Dear Moderators....
This is a question AS WELL AS a information thread. My plan is to gather the information from posters then combine it all into a neat bundle and have it here for our readers to help. Not sure if that is ik. Please let me know.
Dear Members....
Could someone please confirm 100% that after flashing NL8 Boot and Modem that it is infact possible to revert back to 4.4 at will. Please only confirm if you have done this yourself. If you succeeded or failed please let us know either way and also please include your model number and wether you just restored a previous backup or flat out reflashed the 4.4 boot and modem to revert. Also please include links to the modems and boot you flashed upto or back to if youbare able to. If there was any other crucial information please include as well so we can have a very informative thread for knowledge here.I feel this information is very crucial to people and i think it would be helpful.
I wanted to create a thread to keep updated with success and failures as well as the method that seems to work best and fail worst.
Reserved for details
Reserved for detail oand or links
Flashed 5.0 along with the bootloader, went back to 4.4.2 without any issues.
Me too, flashed everything: bootloader, modem, etc... went back to 4.4.2 without any problems (N9005XXUGNI4)
Did you all flashed your old pit file when you reverted back to 4.4.2 or just flashed the rom? Thanks
How do you flash back 4.4.2 ? Using stock firmware and ODIN ?
gvpula said:
Did you all flashed your old pit file when you reverted back to 4.4.2 or just flashed the rom? Thanks
Click to expand...
Click to collapse
No, i did not make a backup PIT file. Flashed PIT for Lolipop, did not use any PIT for reverting to Kitkat.
Updated lollipop with BL, PIT then go back to 4.4.2 (GNG1) with no problems.
Thanks everybody...did you see if knox is still 0x0 ?
Odin flash back to GNG1 (DBT) did not work at first (size fail). So I flashed with PIT file which was ok. Knox still 0x0.
mattdiehl83 said:
Hello and happy new year all.
Dear Moderators....
This is a question AS WELL AS a information thread. My plan is to gather the information from posters then combine it all into a neat bundle and have it here for our readers to help. Not sure if that is ik. Please let me know.
Dear Members....
Could someone please confirm 100% that after flashing NL8 Boot and Modem that it is infact possible to revert back to 4.4 at will. Please only confirm if you have done this yourself. If you succeeded or failed please let us know either way and also please include your model number and wether you just restored a previous backup or flat out reflashed the 4.4 boot and modem to revert. Also please include links to the modems and boot you flashed upto or back to if youbare able to. If there was any other crucial information please include as well so we can have a very informative thread for knowledge here.I feel this information is very crucial to people and i think it would be helpful.
I wanted to create a thread to keep updated with success and failures as well as the method that seems to work best and fail worst.
Click to expand...
Click to collapse
Flashed only boot and modem, flashed several Lollipop ROMs, got back to a KitKat backup I had withTWRP 2.8.3.0 restoring everything but the EFS and the modem.
No issues so far, though the phone needed a couple of minutes to get mobile data properly, after that - no issues turning it on and off in matter of seconds.
BigBoi said:
Odin flash back to GNG1 (DBT) did not work at first (size fail). So I flashed with PIT file which was ok. Knox still 0x0.
Click to expand...
Click to collapse
which pit file you used? the one which you used to flash lollipop or KK one
If possible please include the files you used when you tell of your process. If you could provide you model number as well it would provide very useful. Thank you.
can i get some help on reverting back to 4.4.2 please.
ive flashed all the files for 5.0 and not backed up my pit file.
ive tried flashing 4.4.2 firmware ( no signal, null imei, lots of fc's
ive tried flashing 4.4.2 firmwae with kitkat pit, result( same as above )
UPDATE, ive managed to downgrade to 4.4.2,
i downloaded another firmware from sam ( btu ) flashed in odin and it worked perfect, no fc's or anything.
Did you flash also bootloader or Just The firmware ?
Sent from my SM-N9005 using XDA Free mobile app
just the firmware file, make sure you do a wipe data before you flash tho
Someone can provide me a post with all the bootloaders? I only flashed a 4.4 modem and i have a signal problem
do you have an imei? or is it null?
Hello all,
Have rooted my SM-S906L (5.0.2), which is the SM-G920V for Straight Talk.
TWRP recovery is installed and all is well there.
Trying to install the stock VZW Rom 6.0.1 with the file name: "G920VVRU4CPC2_G920VVZW4CPC2_G920VVRU4CPC2_HOME.tar.md5"
Odin finds the com and device gets added, and the rom takes forever loading into the AP field, then its ready to go.
Hit Start and it fails on sboot.bin...
Could someone possibly point me into the right direction, what I could have or been doing to get this error.
My goal is to get Marshmallow on this S6. My stock firmware is backed up using TWRP.
Thanks!
Update:
..
please let me know if you find any solution
S609l vs g920v
Here here...
Been hoping someone would confirm that the G920V is, or not the same hardware as the S906L.
Would be inclined to experiment more if that was indeed the case.
Regardless, installing TWRP through Odin was straight forward, then rooting with SuperSU, again not an issue.
Quite surprised that there is not a custom rom out there yet?
In the meantime, will keep researching
Still no joy on custom rom for s906l?
Sent from my SM-S906L using Tapatalk
Negative
Nothing yet, still hoping that someone will have figured it out and share. I did have the stock G920V rom boot looping at the Samsung logo but since this is my main phone at the moment, I flashed the stock rom back... I am sure the SM-G920 varient is the SAME unit, just would be a drag to hard brick my only phone.
OTA Update Recived
Last night my SM-S906L did indeed receive an OTA update 275mb, and have harvested to ZIP from the cache/fota folder to my GoogleDrive if anyone needs it.
So before I apply said update, who do I see what OS version it is before it is applied?
My phone is rooted and using TWRP which means once this is applied I am back to loading TWRP and SU.
anyone else get this on theirs, thoughts??
I updated it. Still on 5.0.2. Build number now ends with pk4. When I googled the build number there were s7 nougat roms that ended in that. I was really hoping tracfone was gonna give us a real update.
Edit... just tried flashing the s906l twrp in odin and it wouldn't take. Odin said success but it still boots to stock recovery with the power volume up and home press AND I can't go back to the oe3 firmware or whatever the one that's post around is. Now I'm even screweder
Sent from my SM-S906L using Tapatalk
Anyone ever figure anything out with the pk4 firmware with regards to rooting?
Sent from my SM-S906L using Tapatalk
Good day everyone, just got my note pro WiFi version? Already rooted and has custom kernel civz, tablet feels slow so I'm planning on changing rom maybe lineageOS but I'm concerned about the procedure because I'm not sure where I'm standing with every change done to this device, any help is appreciated I just don't want to brick this device trying to flash a new rom.
Currently it's running stock rom 5.0.2, 3.4.39 civz kernel and knox 2.3, if someone could provide a step by step on what should I do or check in this device to be on the safe road id really appreciate it. Btw I don't even know what recovery I have or how do I access it.
Bump
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
xxjahasotoxx said:
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
Click to expand...
Click to collapse
someone told me that I just need to install twrp as it is and start flashing roms, dont know if this the best way to do it what do you think?
It could work just keep in mind that you don't know exactly what the previous owner did to it so if they installed a custom kernel you'll be stuck with that, could be a good thing could be a bad thing
You could always give it a shot and if it gives you problems go back to stock then TWRP then start rom-ing