Related
Just rooted my Note 3 (MJE) and flashed CWM via Rom Manager and tried to boot into the recovery and get this message "System software not authorized by verizon has been found on your phone, please turn off your phone and go to the nearest store." Now the phone won't boot at all. Anyone know how to fix this without having to use Odin?
Slimfast35 said:
Just rooted my Note 3 (MJE) and flashed CWM via Rom Manager and tried to boot into the recovery and get this message "System software not authorized by verizon has been found on your phone, please turn off your phone and go to the nearest store." Now the phone won't boot at all. Anyone know how to fix this without having to use Odin?
Click to expand...
Click to collapse
The Verizon Note 3 uses secure (signed) blob verification at each step in it's boot sequence including boot images (normal OS kernel or recovery); if you attempt to flash anything which is not signed by Samsung, it results in exactly what you are experiencing. For now - no custom recoveries nor custom boot partitions.
If the phablet won't boot into *anything*, how exactly would you flash anything except by using Odin?
Disclaimer: I've never flashed used Odin. If the question you are asking is "can I put only the recovery back using Odin to avoid a full wipe?" then I suspect the answer is "possibly yes" - if you provide an Odin .tar file containing only the stuff you want to flash (e.g. the recovery image).
I note that the folks with developer versions of the VSGN3 use Odin files that do not include "aboot.mbn". That sort of suggests that Odin only wipes partitions that are slated to be flashed, not all of them. Were that not the case, you would have to always use a PIT file and always provide an image for every partition.
OTOH, Odin is a rather opaque tool, so you can't preclude it from having unexpected behaviors. Given that your device is brand-new, it would be a bummer to hard-brick it, so it might be better for you to just take your lumps and reflash the entire MJE Odin release ROM.
I *think* that folks here have said that attempting to roll back to prior full (factory) releases with Odin will result in a hard-brick. (Well, at least flashing down-rev low-level boot gearing such as aboot.mbn, sbl1.mbn, dbi, tz, etc). So if you flash anything, use MJE components (for now).
good luck. Please report your experiences, good or bad.
.
bftb0 said:
The Verizon Note 3 uses secure (signed) blob verification at each step in it's boot sequence including boot images (normal OS kernel or recovery); if you attempt to flash anything which is not signed by Samsung, it results in exactly what you are experiencing. For now - no custom recoveries nor custom boot partitions.
If the phablet won't boot into *anything*, how exactly would you flash anything except by using Odin?
Disclaimer: I've never flashed used Odin. If the question you are asking is "can I put only the recovery back using Odin to avoid a full wipe?" then I suspect the answer is "possibly yes" - if you provide an Odin .tar file containing only the stuff you want to flash (e.g. the recovery image).
I note that the folks with developer versions of the VSGN3 use Odin files that do not include "aboot.mbn". That sort of suggests that Odin only wipes partitions that are slated to be flashed, not all of them. Were that not the case, you would have to always use a PIT file and always provide an image for every partition.
OTOH, Odin is a rather opaque tool, so you can't preclude it from having unexpected behaviors. Given that your device is brand-new, it would be a bummer to hard-brick it, so it might be better for you to just take your lumps and reflash the entire MJE Odin release ROM.
I *think* that folks here have said that attempting to roll back to prior full (factory) releases with Odin will result in a hard-brick. (Well, at least flashing down-rev low-level boot gearing such as aboot.mbn, sbl1.mbn, dbi, tz, etc). So if you flash anything, use MJE components (for now).
good luck. Please report your experiences, good or bad.
.
Click to expand...
Click to collapse
I just flashed back to stock via odin. Worked fine.
Slimfast35 said:
I just flashed back to stock via odin. Worked fine.
Click to expand...
Click to collapse
Full MJE over the top of soft-bricked MJE?
bftb0 said:
Full MJE over the top of soft-bricked MJE?
Click to expand...
Click to collapse
Yeah.
Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL
The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.
Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL
Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)
No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.
Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!
Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....
Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.
Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,
Hello all...I have to first say that I HAVE been reading A LOT before I posted this question but I am somewhat confused. I have an SM-N900V with the following details :
- Rooted with Arabic Tool
- Android 5.0
- Build OF1
- Bootloader unlocked based on instructions at http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
I also have a SM-N900T for which I have been using CWM based recovery for many years and I am very happy with it. But I am not forced to change to the N900V and I have it rooted already but I am having a hard time finding the right recovery for it. I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Can someone save me a few hours, and potentially more reflashes, and tell me which is the right recvery for this unit and how to install it? I am partial to CWM but I have read that it does not work. As long as I can take backups and restore them I am happy with TWRP. I have also read that SafeStrap is the only option. So again, I just need a straight answer so I can get this done.
Your feedback will be much appreciated!
thanks!
Did you mean "now forced" instead of "not forced" in the 2nd paragraph? The use later on of antecedent references such as "it" and "this phone" make it slightly confusing which phone you are talking about.
calderonr said:
I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Click to expand...
Click to collapse
If you have unlocked the SM-N900V's bootloader, then a bootloop can be remedied by flashing with Odin only the partitions you need fixed, not the entire firmware set. This relieves you from having to re-customize a stock ROM and/or re-root. Moreover and more importantly having an unlocked bootloader means that your phone will no longer require blobs to be Sammy-signed: you can flash custom recoveries with Odin if you please. (You just need to learn how to create the *.tar.md5 files for Odin and you are in business - search for "Odin ustar md5")
So had you know that, you could have just prepared Odin flash tarballs for different recoveries and tried them out according to whim (It is also possible to flash a recovery from the rooted ROM as well, but you need to know how to escape from a perpetual failed recovery boot loop, I.e. : battery pull -> restart with VolDown+Home+Power -> Cancel)
I haven't ever put CWM on my SM-N900V, but can tell you that either the " hlte" or "hltevzw" variants of twrp should work just fine; as you are on OF1 firmware, the -4.4 versions should be used, e.g. twrp-3.0.2-0-hlte-4.4.img or twrp-3.0.2-0-hltevzw-4.4.img
PS Safestrap was the method of choice prior to bootloader unlock methods, and I believe does not work with OB6 or OF1 (possibly also NK1?).
.
calderonr said:
Hello all...I have to first say that I HAVE been reading A LOT before I posted this question but I am somewhat confused. I have an SM-N900V with the following details :
- Rooted with Arabic Tool
- Android 5.0
- Build OF1
- Bootloader unlocked based on instructions at http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
I also have a SM-N900T for which I have been using CWM based recovery for many years and I am very happy with it. But I am not forced to change to the N900V and I have it rooted already but I am having a hard time finding the right recovery for it. I tried a philz CWM based recovery and it ended u getting the unit into a recovery bootloop so I have to flash the stock firmware from scratch and start again.
Can someone save me a few hours, and potentially more reflashes, and tell me which is the right recvery for this unit and how to install it? I am partial to CWM but I have read that it does not work. As long as I can take backups and restore them I am happy with TWRP. I have also read that SafeStrap is the only option. So again, I just need a straight answer so I can get this done.
Your feedback will be much appreciated!
thanks!
Click to expand...
Click to collapse
As long as you are rooted and have the bootloader unlocked... Use Flashify to load TWRP which is an excellent recovery and does what you wish.
See this message:
http://forum.xda-developers.com/showthread.php?p=66380697
Sent from my SM-N900V using Tapatalk
I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.
If I wanted a fresh system and a re-locked bootloader, how do I do it?
negative_nidorina said:
If I wanted a fresh system and a re-locked bootloader, how do I do it?
Click to expand...
Click to collapse
imho easiest way is flashing stock ROM via Odin or Heimdall.
Done it (with Odin) several times on different devices.
Get stock ROM using samfirm_reborn
It loads firmwares directly from Samsungs servers if they are stored there.
(not for all available).
Fill in device name and region (look them up here: https://samfrew.com/)
Check "binary nature" and "decryption".
Results in one zip file to extract the files for Odin of which you should use latest.
bmwdroid said:
imho easiest way is flashing stock ROM via Odin or Heimdall.
Done it several times on different devices.
Get stock ROM using samfirm_reborn
It loads firmwares directly from Samsungs servers if they are stored there.
(not for all available).
Fill in device name and region (look them up here: https://samfrew.com/)
Check "binary nature" and "decryption".
Results in one zip file to extract the files for Odin of which you should use latest.
Click to expand...
Click to collapse
Alright! I also found you could go into download Mode when the bootloader is unlocked, long-press to access Device unlock, then press Volume Up (I think) to re-lock the bootloader.
negative_nidorina said:
Alright! I also found you could go into download Mode when the bootloader is unlocked, long-press to access Device unlock, then press Volume Up (I think) to re-lock the bootloader.
Click to expand...
Click to collapse
may be, but I don't own the device.
And as you wrote "fresh system" I thought it's safer my way than re-locking plus a factory reset which may leave traces of your data.
bmwdroid said:
may be, but I don't own the device.
And as you wrote "fresh system" I thought it's safer my way than re-locking plus a factory reset which may leave traces of your data.
Click to expand...
Click to collapse
May I ask a bit more info here? I want to do something similar: flash stock ROM via Heimdall and relock bootloader. So, I am thinking of downloading a zip from here:
https://samfrew.com/download/Galaxy__Tab__S6__Lite__-Wi-Fi-__/mn97/BTU/P610XXU2FWA5/P610OXM2FWA5/
and then try to flash it using Heimdall. Will this work? What command should I use (Linux user). I have only flashed lineage recovery through Heimdall, so I am not all that sure. Or could I just flash the whole zip through lineahe recovery and be done with it?
Also, to make sure: flashing the stock rom will automatically lock the bootloader? Do I not have to do anything else? I should at least format data, etc, right?
coxackie said:
May I ask a bit more info here? I want to do something similar: flash stock ROM via Heimdall and relock bootloader.
Click to expand...
Click to collapse
Flashing a stock ROM via Heimdall works, BUT you will flash stock recovery aa well so your thought at the end (flash with custom recovery) will not work.
coxackie said:
So, I am thinking of downloading a zip from here:
https://samfrew.com/download/Galaxy__Tab__S6__Lite__-Wi-Fi-__/mn97/BTU/P610XXU2FWA5/P610OXM2FWA5/
Click to expand...
Click to collapse
Gotta have a look at the file.
If it doesn't consist of several tar.md5 files it's no use as you have to open them to extract needed files for Heimdall (needs more than Odin).
coxackie said:
and then try to flash it using Heimdall. Will this work? What command should I use (Linux user).
Click to expand...
Click to collapse
Heimdall on Linux has a GUI frontend you just have to open via terminal.
coxackie said:
I have only flashed lineage recovery through Heimdall, so I am not all that sure. Or could I just flash the whole zip through lineahe recovery and be done with it?
Click to expand...
Click to collapse
As written above: won't work.
coxackie said:
Also, to make sure: flashing the stock rom will automatically lock the bootloader?
Click to expand...
Click to collapse
Using Odin yes. Heimdall I never used/tested for that.
coxackie said:
Do I not have to do anything else? I should at least format data, etc, right?
Click to expand...
Click to collapse
No. Flashing stock replaces all.
Try if you get Odin to run on Wine.
Makes it a lot easier imo.
bmwdroid said:
Flashing a stock ROM via Heimdall works, BUT you will flash stock recovery aa well so your thought at the end (flash with custom recovery) will not work.
Gotta have a look at the file.
If it doesn't consist of several tar.md5 files it's no use as you have to open them to extract needed files for Heimdall (needs more than Odin).
Click to expand...
Click to collapse
There are four files with names:
AP_P610XXU2FWA5_QB61306304_REV00_user_low_ship_meta_OS13.tar.md5
BL_P610XXU2FWA5_QB61306304_REV00_user_low_ship.tar.md5
CSC_OXM_P610OXM2FWA5_QB61306304_REV00_user_low_ship.tar.md5
HOME_CSC_OXM_P610OXM2FWA5_QB61306304_REV00_user_low_ship.tar.md5
Are these what they are supposed to be? And what does one do - flash all four one by one?
@coxackie So that is a multiple part stock ROM file. That's good.
In Odin only AP, BL and CSC needed to make a clean return to stock.
For Heimdall afaik you gotta extract certain files from these (tar.md5 are just archive files).
Which ones to extract? Idk.
Never did myself as I only flashed TWRP as said above.
Google will be your savier.