Related
Triange Away now supports I8190 (SIII mini)
Big thanks to Chainfire for update, and infected_ for doing the beta test so we all can be safe! Give him a thanks!!
Follow this for easy root:
EASY ROOT GUIDE​
To make things clear, as it seems to be alot of confusion about rooting, custom binary count (CBC), & custom recoveries..
Custom binary count can be seen in download mode (vol- / home / power)
It's a counter to keep track of non-Samsung signed binaries flashed with Odin.
If you need to take your device to Samsung for warranty and they notice it's not at zero, you're not under warranty anymore.
Only known way to gain root without increased CBC is to flash one of the pre-rooted firmwares that you can find here.
To be safe, make sure it says something like "This does NOT trigger the flash counter." in the thread for that firmware you are about to flash to gain your highly desired root.:cyclops:
When you got root, finally download rom manager from playstore and you can get cwm recovery with ease.
From there you can flash whatever *.zip's you want without worrying about CBC.
If you do it the other way around, start with custom recovery to be able to flash a "root.zip" you will increase CBC!!
This applies if you try to flash any custom recovery.
In other words..Everything not signed by samsung will get your CBC INCREASED WHEN FLASHED THROUGH ODIN!!
System Status back to OFFICIAL
To restore system status to official you'll need to take a few more steps.
First use triangle away to reset your counter, then tick "allow tracker to run" and "system modified workaround" in triangle away settings.
Reboot device. Supersu will be bisabled for a few minutes when tracker runs and your status will become official.
Now you can uninstall triangle away. On next reboot your systemstatus will still be official, but of course it won't work with a custom kernel or custom rom.
If everything went well you should now have your binary count at 0, and a system status that says official.
Back to Stock Recovery
Most firmwares now have recovery included in the *.tar.md5-package, which was not the case in earlier firmwares for i8190.
You can take a look inside the package to ensure it's there. If it is, you shouldn'd have to mess with restoring recovery.
Open the firmware.rar.md5 with winrar. (Not unpack, just open)
Use this "i8190_stock_recovery.tar.md5". <<---This one doesn't increase custom binary count. (Flash in Odin as PDA)
Edit: This seem to not work as it used to. I'm now adding PDA-specific recovery.tar's to this thread, with continiued updates.
Thanks to Benz0nator, here is also a CWM flashable stock recovery.(Flash with your CWM / TWRP recovery)
So...is warranty back now? NO, not really. You're still rooted so you can't just send it to service in this condition.
For unroot and get warranty back you'll have to read [GUIDE] Unroot, Flash official stock firmware on Galaxy SIII Mini GT-I8190
Whats important to know here is that stock recovery is not always a part of the official firmware package so you might need to flash stock recovery before you unroot and flash firmware.
Also, If you're on 4.1.2 firmware and flash a 4.1.1 firmware you will get problems if no wipe/factory reset is done prior to flashing, as most roms are non-wipe.
Thank you.
tys0n said:
Bah, misspelled topic!haha
To make things clear, as it seems to be alot of confusion about rooting, custom binary count (CBC), & custom recoveries..
Only known way to gain root without increased CBC atm is to flash one of the pre-rooted firmwares that you can find here.
To be safe, make sure it sais something like "This does NOT trigger the flash counter." in the thread for that firmware you are about to flash to gain your highly desired root.:cyclops:
When you got root, finally download rom manager from playstore and you can get cwm recovery with ease. From there you can flash whatever .zips you want without worrying about CBC.
If you do it the other way around, start with custom recovery to be able to flash a root.zip you will increase CBC!!
That also applies if you try to flash custom recoveries, original recoveries repacked to .tar-files.
In other words..Everything not signed by samsung will get your CBC INCREASED WHEN FLASHED THROUGH ODIN!!
Custom binary count can be seen in download mode (vol- / home / power)
It's a counter to keep track of non-Samsung signed binaries flashed with Odin.
If you need to take your device to Samsung for warranty and they notice it's not at zero, you're not under warranty anymore.
Atm there is no known way to restore CBC to zero for I8190 (SIII mini)
Also, If you're on 4.1.2 firmware and flash a 4.1.1 firmware you will get problems if no wipe/factory reset is done prior to flashing, as most roms here are non-wipe.
If you find another method for any of this, please let me know and I will update this post.
Thank you.
Click to expand...
Click to collapse
Thanks for the thread man! I was getting quite confused about this binary counter thing
Re: Impirtant Info - root,recovery,binary count.
Ohhh that was very good thanks and as for me I don't even have warranty so no problem with CBC (if ut does'nt have another disadvantage. .)
sent from the super siii mini GT-I8190 using xda premium app.
Updated with CWM flashable stock recovery. (thx to Benz0nator)
Updated: Triangle away support for i8190 (s3 mini)!!
Thanks Man....
So what are the Steps ?
Only Downloading & Use "Triangle Away" App ?
cheech01 said:
Thanks Man....
So what are the Steps ?
Only Downloading & Use "Triangle Away" App ?
Click to expand...
Click to collapse
Yes
Oh yeah!
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
That's because of my ROM.
Re: [UPDATE] Triangle Away - root,recovery,binary count.
Same here, development is getting better and better let's hope that we will get CM support.
Sent from my GT-I8190 using xda premium
bycluir boxed
Good news! thanks to all (developers and testers!) :good:
Benzonat0r said:
Oh yeah!
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
That's because of my ROM.
Click to expand...
Click to collapse
fix system status : http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346 download and odin flash
Re: [UPDATE] Triangle Away - root,recovery,binary count.
Couldn't we just Factory Reset through CWM?
Sent from my S3 Mini whilst rollin a fat one
furuko1231 said:
fix system status : http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346 download and odin flash
Click to expand...
Click to collapse
CaseyS said:
Couldn't we just Factory Reset through CWM?
Sent from my S3 Mini whilst rollin a fat one
Click to expand...
Click to collapse
Yes. These two steps are basicly the same.
It will clear /cache & /data
Re: [UPDATE] Triangle Away - root,recovery,binary count.
Alright...I can know edit my guide. with that my tutorial will be empty of faults and disadvantages maybe tomorrow I will do it
hit thanks if I helped you
sent from the wonderfull s3 mini GT-I8190 using xda app
Question
Hi!
I am a little bit confused. I flashed a pre-rooted I8190XXALJL firmware.
When I go to download mode,
on the bottom of FIRST screen is a yellow triangle with an exclamation mark.
When I press Volume Up, on the SECOND SCREEN is following text:
ODIN MODE
PRODUCT NAME: GT-I8190
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Please explain somebody, why the yellow triangle? What is the CBC count then? I'm now in official or in custom mode?
Need I run the Chainfire's Triangle Away tool or not?
ladislav.heller said:
Hi!
I am a little bit confused. I flashed a pre-rooted I8190XXALJL firmware.
When I go to download mode,
on the bottom of FIRST screen is a yellow triangle with an exclamation mark.
When I press Volume Up, on the SECOND SCREEN is following text:
ODIN MODE
PRODUCT NAME: GT-I8190
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Please explain somebody, why the yellow triangle? What is the CBC count then? I'm now in official or in custom mode?
Need I run the Chainfire's Triangle Away tool or not?
Click to expand...
Click to collapse
The yellow triangle have always been there. It's just a warning that a custom os can harm the function of the device.
official / custom can be fixed. Please read the Triangle away post by Chainfire on how to use it.
Added Stock recovery.tar.md5 to use with Odin.
furuko1231 said:
fix system status : http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346 download and odin flash
Click to expand...
Click to collapse
you mean this will enabled the official status and kies will be working? in odin flash as pda? phone?
Sv: [UPDATE] Triangle Away - root,recovery,binary count.
nazri5363 said:
you mean this will enabled the official status and kies will be working? in odin flash as pda? phone?
Click to expand...
Click to collapse
No, it will make a factory reset. Wipe all user data.
For status to official use triangle away
Sent through time and space from my s3mini.
Triangle Away worked like charm on my Galaxy S3 mini. My phone couldn't get past the samsung logo and couldn't get into stock recovery no matter what, so after hours of trying and flashing stock roms, I flashed CWM via odin and I my phone was working again. Afterwards I have purchased Triangle Away and my phone is like new again Thanks Chanfire :good:
Fool-proof-method
1. Download and run Triangle Away to bring your phone back to Samsung Official and not "Custom" so your guaranteed to be able to update....this is if you have a custom recovery already installed or have rooted the phone before...download here
2. Download the Odin file...I believe the .zip contains the .tar file For Sprint:...here
3. Read/download how to use Odin such as installing USB Drivers, proper USB cord...etc...here...
4. Install the MF9 file you downloaded.
4. Reboot phone and done...
5. Easy way to start flashing again is to use Odin again and flash this custom recovery...be sure you find the "spr" download for Sprint ".tar file" here
6. Download and flash your ROM through the recovery...no need to root or anything...just need the ROM.
Spent some time making this post...hit the thanks button on the left if I helped you in any way.
KStyles69 said:
Fool-proof-method
1. Download and run Triangle Away to bring your phone back to Samsung Official and not "Custom" so your guaranteed to be able to update....this is if you have a custom recovery already installed or have rooted the phone before...download here
2. Download the Odin file...I believe the .zip contains the .tar file For Sprint:...here
3. Read/download how to use Odin such as installing USB Drivers, proper USB cord...etc...here...
4. Special note before rebooting...Rooting, custom recovery, or Kernel will mean you loose that "Samsung Offical" so you won't be able to update.
4. Reboot phone and done...
5. Easy way to start flashing again is to use Odin again and flash this custom recovery...be sure you find the "spr" download for Sprint ".tar file" here
6. Download and flash your ROM through the recovery...no need to root or anything...just need the ROM.
Spent some time making this post...hit the thanks button on the left if I helped you in any way.
Click to expand...
Click to collapse
I don't believe all the statements you make here are true. You do not have to have Samsung official to receive an update. You only have to be on a stock recovery with no changes made to any system files or have deleted system files. The only reason to use triangle away is if you are going to send your phone to Samsung for warranty work. So to simplify your methodolgy:
Download the stock MF9 tar, install it with odin, run cf-autoroot, install custom recovery(either with odin or goomanager app), and then install any mods or roms you want.
Didn't mean to rain on your parade, but you over complicated the whole process.
I don't think we needed a thread like this.
Sent from my SPH-L720 using Tapatalk 4
Didn't MF9 break Triangle Away?
** worthless thread **
No comment..
I was trying to root my sprint s4 , however it gives an error firmware upgrade issue
cruise350 said:
I don't believe all the statements you make here are true. You do not have to have Samsung official to receive an update. You only have to be on a stock recovery with no changes made to any system files or have deleted system files. The only reason to use triangle away is if you are going to send your phone to Samsung for warranty work. So to simplify your methodolgy:
Download the stock MF9 tar, install it with odin, run cf-autoroot, install custom recovery(either with odin or goomanager app), and then install any mods or roms you want.
Didn't mean to rain on your parade, but you over complicated the whole process.
Click to expand...
Click to collapse
********************************************************************************************
I was trying to root my sprint s4 , however it gives an error firmware upgrade issue
and now my phone doesnt start up
how do i restore to factory version?
on top left of screen it says
odin mode in red
knox kernel lock 0*0
status custom
binary custom
knox warranty void 0*1
csb config 0*30
write protection enabled
emmc burst mode enabled
jaybhatia999 said:
********************************************************************************************
I was trying to root my sprint s4 , however it gives an error firmware upgrade issue
and now my phone doesnt start up
how do i restore to factory version?
on top left of screen it says
odin mode in red
knox kernel lock 0*0
status custom
binary custom
knox warranty void 0*1
csb config 0*30
write protection enabled
emmc burst mode enabled
Click to expand...
Click to collapse
Go to www.sammobile.com and download the NG2.tar. Odin it and profit.
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
wethestill said:
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
Click to expand...
Click to collapse
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
wethestill said:
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
Click to expand...
Click to collapse
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Gage_Hero said:
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Click to expand...
Click to collapse
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
wethestill said:
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
Click to expand...
Click to collapse
If your coming from 4.3 there are a number of good roms... unfortunately they are all around 1.2 to 1.4 GB so if you have a slow connection it will take a while... I run Danvh's 4.4 http://forum.xda-developers.com/showthread.php?t=2537495 , there is also this one that people seem to like but I haven't tried it.... http://forum.xda-developers.com/showthread.php?t=2375180 you will need a custom recovery.... both of these suggest twrp.... I flashed with 2.6... 2.7 is out now and I don't know how it reacts but you will need a custom revovery to flash the zip file....
I guess the issue is you have to restore to stock via odin but you don't know what version bootloader you have? Guess you'll have to use samsung tool which will probably install knox?
Can you install custom recovery via odin?
Try with the new 4.4 files
sent from my mobile device
Knox is already tripped. I'd go into recovery, do a factory restore again and then plug it into the computer and do a restore with Kies.
Sent from my SGH-I337M using Tapatalk
Hi, guys!
There is on guy on 4pda that has bootloader with the following in Download mode:
Code:
Odin mode
Product Name: SM-N910H
Current Binary: Samsung official
System Status: Custom
Reactivation Lock (KK): OFF
Secure Download: enabled
Knox warranty void: 0
AP SWAEV: 0 (test devise)
I believe that this is test device, and accordingly to Note 3 story it can give a possibility to reset Knox Warranty counter. Could some one of gurus please advice how we can backup and share his bootloader?
Thanks a lot in adnance!
This may help to backup sboot and param. And maybe other can restore with it. But we must be calm. And wait for advanced help.
Wanam tool
https://play.google.com/store/apps/details?id=ma.wanam.partitions
kadiremrah said:
This may help to backup sboot and param. And maybe other can restore with it. But we must be calm. And wait for advanced help.
Wanam tool
https://play.google.com/store/apps/details?id=ma.wanam.partitions
Click to expand...
Click to collapse
The only problem - it requires root. And I don't know yet if that guy has a root. Flashing root with Odin may change warranty bit. Any other idea?
Re flashing stock ROM will replace original bootloader.
I strongly NOT in favor of making backup of bootloader and restore using anything other than Odin. In world of flashing if anything is RISKY it's only and one bootloader. Also I don't believe any method of restoring bootloader other than Odin will work anymore on newer device. Either it will make no effect OR IT CAN BRICK device.
Also If anyone have boot loader with re engineering which reset knox warranty - I do not recommend to try UNLESS you must required to do it.
Say for example your device have something wrong and you needs to send to service station - still you can flash that bootloader if required isn't? Only condition when you cant flash bootloader is
-Faulty USB pin - Who cares for warranty ? It does cost couple of $ why we should take risk for complete device?
-Hard bricked with unable to boot to download mode - How samsung service station can find your Knox status in this condition?
So Flash such bootloader only you really need it when required with own risk.
Thank you very much for advice.
But on Note 3 there was procedure to restore Knox warranty bit exactly by flashing test bootloader with Odin. I just want not to loose possibility to have a solution... Of course, I will think twice before flashing that BL, but at lease we will have some data to explore! Isn't it?
Obviously it's marvelous thing to have possibility to reset knox but only thing I suggest is to use as only real needy case not for fun /experiment.
Sent from my SM-N910G using xda premium
So - any idea on how to copy bootloader?
I furtunately found this gide:
http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
I hope it will help!
Zer0r said:
So - any idea on how to copy bootloader?
Click to expand...
Click to collapse
But why you need to copy bootloader? You can get it from stock ROM file too. simply unzip stock ROM tar.md5 and you will have it.
BTW exynos version requires only one file for bootloader sboot.bin
dr.ketan said:
But why you need to copy bootloader? You can get it from stock ROM file too. simply unzip stock ROM tar.md5 and you will have it.
BTW exynos version requires only one file for bootloader sboot.bin
Click to expand...
Click to collapse
I need to copy bootloader from Developer Edition phone. That bootloader is unlocked. I have access to one of such phones, that is why all thiss mess
Oh ok got it now.
Sent from my SM-N910G using xda premium
So - here is bootloader with param partition. If anybody wants to explore them - you are welcome!
This bootloader is from Test Devirce. It doesn't locked, so any unoficcial actions wit device doesn't affect on Knox Warranty Void bit, it is checked.
Who is going to test it? :laugh:
Is it possible to reset N910C device? Testers waiting for you??
megatooth said:
Who is going to test it? :laugh:
Click to expand...
Click to collapse
Other file should be used for testing, not that. That file can not be flashed via Odin as a bootloader.
I will not post it, because it is a bit risky. And there some backup preparation should be done before flashing. But anyone who wants to be a volonteer - welcome in PM, please.
Well, unfortunately it does nothing. I tested and flashed it on my own device - bootloader has changed, but not to (test device) status, and the Warranty bit was not resetted to 0... But we tried!
I want to thank a man who helped me a lot - @A.S._id.
On Note 3 prosedure was.
* Flash sboot an param
* Reboot download mode again
* Flash stock rom of your region from odin
* Factory reset on stock recovery
* Boot system
* Again download mode
* Re flash stock rom
* Factory reset and boot
This was working on note 3.
Zer0r said:
Well, unfortunately it does nothing. I tested and flashed it on my own device - bootloader has changed, but not to (test device) status, and the Warranty bit was not resetted to 0... But we tried!
I want to thank a man who helped me a lot - @A.S._id.
Click to expand...
Click to collapse
Any news? Sorry for spamming. @Zer0r Did you tried to reflash stock ROM and as well reset factory as the same procedures with Note 3? Post some images from successfull changing Bootloader please. I'm curious to that bootloader too. Mine is 910C.
tuannghia1985 said:
Any news? Sorry for spamming. @Zer0r Did you tried to reflash stock ROM and as well reset factory as the same procedures with Note 3? Post some images from successfull changing Bootloader please. I'm curious to that bootloader too. Mine is 910C.
Click to expand...
Click to collapse
No news, bootloader from test device, which, as we thought clearing warranty bit, didn't clearing...
Here is bootloaders for flashing via odin, one from test device, and different from realise device, you can to try flash them and make sure...
https://yadi.sk/d/IUpILBpjh2JKW
p.s.
as it turned out - the test device has ceased to be a test, after he flashed stock firmware
http://cs3-3.4pda.to/6337019/%C1%E5...d4b8c000000007ac5697c47447c2fe32cb87a6142b1cb
Any update?
Recently decided to try the Bootloader unlock.
Thought everything had gone well, it seemed OK.
Flashed TWRP, and now it won't boot.
I'm stuck at the phone telling me to take it to a Verizon store to fix it.
That being said, I can get into download mode and I get the following :
ODEN MODE
PRODUCT NAME : SM-N900V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOW WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SMREV: S1, T1, R1, A2, P1
WRITE PROTECTION: Enable
UDC START
SYS REV CHECK FAIL : No Version
SECURE MAGICCODE CHECK FAIL : recovery
From all that, it seems that my recovery is not any good (probably from flashing twrp, duh).
I haven't been able to find a NC2 or NC4 flashable recovery anywhere.
Help?
Or am I barking up the wrong tree and do I need something else?
darkhawkff said:
Recently decided to try the Bootloader unlock.
Thought everything had gone well, it seemed OK.
Flashed TWRP, and now it won't boot.
I'm stuck at the phone telling me to take it to a Verizon store to fix it.
Click to expand...
Click to collapse
That "Verizon" message means that you did NOT unlock the bootloader succesfully.
You would normally see [size=+1]MODE: Developer[/size] in the Odin/Download mode screen if you had successfully unlocked.
As a matter of fact, that condition should always be checked for before trying to flash any recovery.
darkhawkff said:
AP SMREV: S1, T1, R1, A2, P1
Click to expand...
Click to collapse
[size=+1]Whoa! HOLD THE PHONE![/size] (Somebody with an older bootloader - MJE or NC2 at the latest)
If you reflash with Odin, USE EITHER MJE or NC4 at most - nothing later than that!
darkhawkff said:
SYS REV CHECK FAIL : No Version
SECURE MAGICCODE CHECK FAIL : recovery
Click to expand...
Click to collapse
I've never seen those messages before, but it's probably because you flashed something either into the boot partition or the recovery partition and your bootloader is not yet unlocked.
darkhawkff said:
From all that, it seems that my recovery is not any good (probably from flashing twrp, duh).
I haven't been able to find a NC2 or NC4 flashable recovery anywhere.
Help?
Click to expand...
Click to collapse
I will help you out. Please stand by. DO NOT FLASH NJ6 NK1 OB6 or OF1.
darkhawkff said:
Or am I barking up the wrong tree and do I need something else?
Click to expand...
Click to collapse
Stand by for more. posting now (quickly) so you don't do something rash.
bftb0 said:
That "Verizon" message means that you did NOT unlock the bootloader succesfully.
You would normally see [size=+1]MODE: Developer[/size] in the Odin/Download mode screen if you had successfully unlocked.
As a matter of fact, that condition should always be checked for before trying to flash any recovery.
[size=+1]Whoa! HOLD THE PHONE![/size] (Somebody with an older bootloader - MJE or NC2 at the latest)
If you reflash with Odin, USE EITHER MJE or NC4 at most - nothing later than that!
I've never seen those messages before, but it's probably because you flashed something either into the boot partition or the recovery partition and your bootloader is not yet unlocked.
I will help you out. Please stand by. DO NOT FLASH NJ6 NK1 OB6 or OF1.
Stand by for more. posting now (quickly) so you don't do something rash.
Click to expand...
Click to collapse
Thanks for the insight. No worries, I was downloading NC4 ATM, but I would prefer NC2 I think, for now. I got no problems waiting...it isn't my 'main' phone anymore. I got a note 5, but I prefer my note 3 for most usage. It's just....nicer....
I appreciate the help greatly though! Finding older files (like NC2) is damn near impossible. If I was at home, it's probably sitting on my file server somewhere, but I don't have access at the moment. Still at work.
I will also note, I did verify prior to trying to bootloader, to ensure the CID started with 0x15, and it does. Checked like 5 times, just to be sure.
And I figured it would.....since I bought this the day it was released. Anyway.....
Thanks!
OK. First things first. Let's examine the state your phone is currently in before you flash anything.
My educated guesses are that (a) your bootloader is NOT unlocked, and possibly (b) the phone is "stuck" always trying to boot into the recovery - which gives you the Verizon screen, or (c) something worse - for example if you flashed the custom recovery into the wrong partition.
The not-unlocked condition means that whatever is trying to be booted (either the recovery partition or the boot partition) has something non-Samsung in it. Either one would give you the Verizon message about unauthorized software.
When the phone boots from a cold startup, it looks at something in NVRAM called the "BCB" - the Boot Communication Block. If it is "empty" it will do the normal thing - try to boot the phone normally, starting with the "boot" partition. But, the BCB can contain other instructions, such as "boot to recovery", or "boot to Odin mode". And experience seems to indicate that the conditions under which the BCB is cleared (i.e., goes back to the default) is a little bit buggy or quirky - so that the phone can get "stuck" always trying to boot either the recovery or Odin/Download mode.
The "three-finger salute" of Vol-Down + Home + Power - which you normally use to start up Odin - seems to clear the BCB when you choose the "Cancel" option (Vol-Down) from that initial splash screen, and it usually will attempt to boot the normal ("boot") partition if you select "Cancel" ( = Vol-Down ).
So FIRST: Pull your battery. Re-insert. Vol-Down+Home+Power until you get that "do you want to install custom software?" screen. Press Vol-Down to cancel.
===> Does your ROM boot correctly?
If so, then you can attempt to unlock again without any flashing. I suppose you are still rooted if your phone still boots.
===> If your ROM still boots, please report it's exact firmware version. It makes a big difference whether it is a M-series or an N-series. (Note: I am asking about the bootloader firmware, not the ROM version).
If your ROM does not boot, then you are going to have to use Odin in one way or another.
I can help you out with that and point you at the correct custom recovery, depending on which bootloader firmware you want to end up with. (Especially if you have a copy of the NC2 firmware at home (it's the only one I don't have).) DON'T FLASH NJ6 OR ABOVE IN ODIN - yet. (Towelroot V3 is trivially easy on anything from MI9 through NC4, and rooting appears to be a pain in the rear beyond that)
let me know what you find.
darkhawkff said:
I will also note, I did verify prior to trying to bootloader, to ensure the CID started with 0x15, and it does. Checked like 5 times, just to be sure.
And I figured it would.....since I bought this the day it was released.
Click to expand...
Click to collapse
That certainly is a mandatory prerequisite to success. But it doesn't mean that something won't go wrong during the unlock process. To be sure, just boot into Odin mode after you think everything has succeeded and look for that "MODE: Developer" message on the Odin screen to verify that the unlock process succeeded.
There are a couple different versions of the unlocker binary in that Unlock thread, and most of the variations have to do with how the program went about reading the CID value out of the volatile filesystem /sys during initial sanity checks. As that location seemed to change from firmware release to release, there was some dependency between the unlock binary version and the OS release level of the rooted ROM it was used on. So a "safety check" in the code was what was making it non-portable; the actual CID change and binary patching of the "aboot" partition was the same in every version.
I might have used @donc113's original variant (post #218) when I was on MJE. If you are rooting with M* or N* ROM firmware, that version should work.
The other thing that happened was that (I think?) someone released an app that was really just a wrapper around the binary file. That had the unfortunate side effect of hiding the status and error messages the unlock binary produces if someone happened to use it on the wrong OS version. It's possible that someone that is rooted could slip a different version of the "unlock" binary underneath that app (in it's appropriate /data/data/* location), but that's asking a lot from people who gravitate towards using "one click" apps.
You didn't mention whether you were using the app or just the command line. If it was the latter I think that careful inspection of the unlock binary's output would have indicated success or failure.
Anyway, some TWRP custom recovery links:
TWRP for hltevzw
If you have a M* series bootloader use the -4.3.img recoveries, otherwise use -4.4 for N*, O*, or P* firmware
(The AryaMod ROM uses the Aroma installer, which apparently needs the twrp-2.8.7.0-hltevzw version, not the twrp-3.0.2-0-hltevzw. So... grab both of them)
PS I recently "upgraded" my bootloader from MJE to NC4. I did this because the M* series bootloader is incompatible with later kernels (due to technical issues about how the "DTB" (Device Tree Blob) attached to the kernel is parsed and initialized by the bootloader). I probably would have gone with NC2 instead of NC4, but all the links for the NC2 leak firmware were dead. At least NC4 is easy to root with Towelroot v3, and so far I've been able to boot and run not only lolipop roms (e.g. CM13) but a marshmallow rom (AryaMod) without major troubles. So I have an Odin-back-to-stock method for device recovery that is easily rootable (in contrast to NJ6, NK1, or PL1 which have no root method, or OB6/OF1 which have crufty/difficult rooting methods (& perhaps dodgy too)).
.
Any chance of just using Odin and flashing a stock recovery image? Rather than killing the entire os too?
I can't find just a recovery image though.
darkhawkff said:
Any chance of just using Odin and flashing a stock recovery image? Rather than killing the entire os too?
Click to expand...
Click to collapse
That works when the bootloader is unlocked (even with unsigned recoveries such as TWRP). Not sure about the locked case.
Code:
tar -H ustar -c -f my_recovery_only_Odin_bundle.tar recovery.img
md5sum my_recovery_only_Odin_bundle.tar >> my_recovery_only_Odin_bundle.tar
mv my_recovery_only_Odin_bundle.tar my_recovery_only_Odin_bundle.tar.md5
Note that the above technique for preparation of Odin flashables isn't restricted to adding just a single file. For instance, someone that had a bootlooping stock ROM in need of repair could probably create a tar.md5 bundle that only contained "boot.img" and "system.ext4.img"* Note that when Odin does the MD5 checking, it wants the filename to be unchanged (other than the .md5 extension). So don't change the name of the .tar.md5 file to something else or the MD5 check in Odin will fail.
darkhawkff said:
I can't find just a recovery image though.
Click to expand...
Click to collapse
It's inside the stock Odin tar.md5 bundle. Just extract it.
Is it even important at the moment? So long as your phone boots normally, what's in the recovery partition simply doesn't matter
Did you try the Vol-Down+Home+Power startup (followed by Cancel == Vol-down) that I suggested above? What happens?
.
* There is one place where partial firmware flashes would be extremely ill-advised: if you were flashing a bootloader (dear lord why?) ALL five pieces (aboot.mbn, sbl1.mbn, rpm.mbn, tz.mbn, sdi.mbn) need to be flashed as a group all in one go
Yup. Just tried that finally (was busy at work).
Fixed. I'm unlocked bootloader.
Yup, I'm still on NC2 (not that it's a surprise).
Still haven't been able to find the files at home. I thought I might have them saved somewhere, but apparently not. Still have 1 or 2 places to look, but I'm going to guess that I don't have it anywhere.
darkhawkff said:
Yup. Just tried that finally (was busy at work).
Fixed. I'm unlocked bootloader.
Yup, I'm still on NC2 (not that it's a surprise).
Still haven't been able to find the files at home. I thought I might have them saved somewhere, but apparently not. Still have 1 or 2 places to look, but I'm going to guess that I don't have it anywhere.
Click to expand...
Click to collapse
hope I helped.
Make a backup of your current ROM in TWRP and get it off the phone into a safe place. Then you will feel free to experiment with different ROMs as time allows. I would also suggest it is really a good idea to save that "debrick" image on the SD card in case a utter disaster happens (probably you will never use it though).
(before reformatting the SD card to get it back to usefulness)
Code:
dd if=/dev/block/mmcblk1 bs=4096 count=65536 of=/data/local/debrick.img
(or, too-late... get a debrick image with the modded "aboot" partition unlocked bootloader)
Code:
dd if=/dev/block/mmcblk0 bs=4096 count=65536 of=/sdcard/debrick.img
I'll archive the NC2 if you can find it (send me a PM) even though I can't use it any longer as I recently flashed NC4 bootloader. I have all the other firmware releases, just not that one.
The NC2 (leak) engineering bootloader appeared at a time when the kernel DTB blobs were changing structure; hopefully it is able to boot all later kernels. Please drop a note somewhere in these forums if you discover problems booting newer kernels - whether custom or stock. As I mentioned, if NC2 won't work, NC4 seems decent enough so far and it preserves a full-stock Odin recovery/rescue to a ROM version which is easily rooted with Towelroot v3
As to modems, I've done a few pairings of my flashable-stock ROMs with different modem releases (see the flashable stock thread for downloads) and - strangely - the NC4 modem won't work at all with NJ6 or NK1 (no service) kernels/ROMs, but it will work with later kernels/ROMs e.g. OB6-PL1. Just mentioning it because the NC2 modem might behave in a similar strange fashion since it is of the same vintage. I haven't had any troubles flashing modems up-version or down-version.
.
Well, all great!
I got Aryamod installed and going well.
NC2 bootloader yet too! TWRP obviously installed and OK, with 2.8.7 I believe. Installing apps now.
It really makes a difference with this phone too. I'm quite surprised by it to be honest.
All I know, is I might actually switch back to using my note 3 instead of my note 5 as my daily driver again.
Thank you again for the help. I really appreciate it.
darkhawkff said:
Well, all great!
I got Aryamod installed and going well.
NC2 bootloader yet too! TWRP obviously installed and OK, with 2.8.7 I believe. Installing apps now.
It really makes a difference with this phone too. I'm quite surprised by it to be honest.
All I know, is I might actually switch back to using my note 3 instead of my note 5 as my daily driver again.
Thank you again for the help. I really appreciate it.
Click to expand...
Click to collapse
Good deal.
AryaMod is a pretty nice ROM. Marshmallow FTW!
(I'm glad I bought a device with 3GB of RAM.)
Could you please message me at [email protected] I tried to root my sm-n900v note 3 on 5.0 and it's soft bricked. I can't get Odin to flash..keeps failing. I need to talk to someone just bought it week ago man.