Related
I have a note 2 arriving this afternoon and I would like to unlock the bootloader and flash stock samsung experience. My understanding is that I download and run CASUAL (link in general forum) from linux using oracle java 7 and the system will be prepared for flashing (have bootloader unlocked, radio firmware updated and twrp installed).
-
I then download cleanrom (either cleanrom ace 4.2.5 or cleanrom vzw-se) put the binary on a microsd card; double check md5 hash. I then reboot the note 2 and hold volume up; home and power at same time while it boots and there will be an option to select a rom to boot?
-
Four questions:
1) Am I correct in the instructions (and will the radio be automagically updated by casual or is that a different process) ?
2) Which is 'better' or what is the difference between cleanrom ace 4.2.5 and cleanrom vzw-se ? Which is more likely to see updates as samsung make changes ?
3) When future radio updates occur how are they applied; do I rerun CASUAL?
4) Can the device be permanently bricked or can I always get into bootloader to load somethjing off sd card (I though the original hack - pre CASUAL - suggested that if you did not flash the radio first you could permantly brick the device which I did not understand is why you could not start over and then flash the radio?)
--
This will be my first time flashing an andriod device. My current (and first smart) phone is a verizon razr which is locked.
jake21 said:
I have a note 2 arriving this afternoon and I would like to unlock the bootloader and flash stock samsung experience. My understanding is that I download and run CASUAL (link in general forum) from linux using oracle java 7 and the system will be prepared for flashing (have bootloader unlocked, radio firmware updated and twrp installed).
-
I then download cleanrom (either cleanrom ace 4.2.5 or cleanrom vzw-se) put the binary on a microsd card; double check md5 hash. I then reboot the note 2 and hold volume up; home and power at same time while it boots and there will be an option to select a rom to boot?
-
Four questions:
1) Am I correct in the instructions (and will the radio be automagically updated by casual or is that a different process) ?
2) Which is 'better' or what is the difference between cleanrom ace 4.2.5 and cleanrom vzw-se ? Which is more likely to see updates as samsung make changes ?
3) When future radio updates occur how are they applied; do I rerun CASUAL?
4) Can the device be permanently bricked or can I always get into bootloader to load somethjing off sd card (I though the original hack - pre CASUAL - suggested that if you did not flash the radio first you could permantly brick the device which I did not understand is why you could not start over and then flash the radio?)
--
This will be my first time flashing an andriod device. My current (and first smart) phone is a verizon razr which is locked.
Click to expand...
Click to collapse
You can download any rom, and it doesn't matter if it is on the SD card or not. I just always make sure I have a nandroid on my sd and on my computer at all times.
I'm unsure how to answer 1.), because i'm unsure what you are asking exactly.
2.) neither is better than the other. if you use VZW apps, use the VZW cleanrom. If you don't and want the purest version possible, use cleanrom ace. I personally use cleanrom ace.
3.) do you mean OTA? they are international roms so you don't get asked for the VZW updates
4.) i think you can brick the device, but it is really hard and almost impossible to do as long as you are reading the instructions for hte mod/rom/etc... you are using. Most of the time you can use a nandroid to get back to a saved state.
With (1) I was asking if i listed the right sequence or if I missed some critical detail. If I use cleanrom ace (I'm leaning towards either cleanrom ace or jellybean) is there a way for me to install myverizion (which is the only verizon ap I used; polaris is also nice but both version include polaris).
kimdoocheol said:
You can download any rom, and it doesn't matter if it is on the SD card or not. I just always make sure I have a nandroid on my sd and on my computer at all times.
I'm unsure how to answer 1.), because i'm unsure what you are asking exactly.
2.) neither is better than the other. if you use VZW apps, use the VZW cleanrom. If you don't and want the purest version possible, use cleanrom ace. I personally use cleanrom ace.
3.) do you mean OTA? they are international roms so you don't get asked for the VZW updates
4.) i think you can brick the device, but it is really hard and almost impossible to do as long as you are reading the instructions for hte mod/rom/etc... you are using. Most of the time you can use a nandroid to get back to a saved state.
Click to expand...
Click to collapse
jake21 said:
With (1) I was asking if i listed the right sequence or if I missed some critical detail. If I use cleanrom ace (I'm leaning towards either cleanrom ace or jellybean) is there a way for me to install myverizion (which is the only verizon ap I used; polaris is also nice but both version include polaris).
Click to expand...
Click to collapse
I think you're missing a lot of steps. Also to get to recovery power off. Then do the button combo to power it on. Here is a great guide on how to flash a ROM. You are going to want section 2. Also if you want my Verizon you're gong to want the Verizon version of clean or beans or Eclipse. Then just download my Verizon from the play store
http://forum.xda-developers.com/showthread.php?p=34891181
Sent from the dark on a Note 2
Ok thanks. There is some side confusion on my part (perhaps with system layering) that I think contributes:
I understand what a bootloader is but I'm unsure what twrp is (is it a boot loader or does it act as a kernel that the bootloader runs and in itself allows for execing another kernel (the actual user layer). I also don't quite understand where the radio fits in this picture. I.e, how do you tell the system to flash the radio eprom indepdently of the kernel. My basic understanding of the system layer is:
rom -> exec bootloader from nvram -> bootloader has a configured option to exec the kernel -> kernel runs everything else
radio is in a different nvram that the chip knows how to read when radio is triggered by the kernel
(I used nvram above but I really don't know what sort of r/w chip they use these day; i.e, eeprom or something else)
-
My understanding is that if the flashing of hte bootloader fails then the phone is truely bricked and will require the nvram/eeprom be pulled and falshed exeternally as the rom bootloader has no method to recover.
-
Is this correct ?
kintwofan said:
I think you're missing a lot of steps. Also to get to recovery power off. Then do the button combo to power it on. Here is a great guide on how to flash a ROM. You are going to want section 2. Also if you want my Verizon you're gong to want the Verizon version of clean or beans or Eclipse. Then just download my Verizon from the play store
http://forum.xda-developers.com/showthread.php?p=34891181
Sent from the dark on a Note 2
Click to expand...
Click to collapse
jake21 said:
Ok thanks. There is some side confusion on my part (perhaps with system layering) that I think contributes:
I understand what a bootloader is but I'm unsure what twrp is (is it a boot loader or does it act as a kernel that the bootloader runs and in itself allows for execing another kernel (the actual user layer). I also don't quite understand where the radio fits in this picture. I.e, how do you tell the system to flash the radio eprom indepdently of the kernel. My basic understanding of the system layer is:
rom -> exec bootloader from nvram -> bootloader has a configured option to exec the kernel -> kernel runs everything else
radio is in a different nvram that the chip knows how to read when radio is triggered by the kernel
(I used nvram above but I really don't know what sort of r/w chip they use these day; i.e, eeprom or something else)
-
My understanding is that if the flashing of hte bootloader fails then the phone is truely bricked and will require the nvram/eeprom be pulled and falshed exeternally as the rom bootloader has no method to recover.
-
Is this correct ?
Click to expand...
Click to collapse
I think you are way over thinking this. So, TWRP is just your recovery. It replaces the stock Android recovery. To change your radio you would boot into TWRP and flash it like anything else.
As for the system layer break down. It's not really important for flashing except that kernels are included with whatever ROM you flash so unless you want to run a different one there's no need to worry about it. Also, radios are never included in a ROM flash so no need to worry about it.
To the if you can brick your phone. If course you can, but as stated is hard to do. Check the md5 before using Odin and don't unplug in the middle of a Odin flash. You can still recover most the time anyways, but why risk it.
Sent from the dark on a Note 2
Hey all. I had Hypderdrive installed. I updated it to 21 but had a force close issue. I wiped to reinstall in safestrap and realized that I didn't have the ROM on the device anymore. Whoops. All of a sudden I had no OS and couldn't connect to the phone via USB to put the ROM onto it.
After trying some stuff I got a bit more stuck. I can only reboot into 3 places: 1) Download mode (with volume down) 2) stuck at samsung unlocked icon (no buttons pressed) and 3) default recovery mode (with volume up). I tried with Kies to just install the latest firmware, figuring I'd be happy with lollipop and just go ahead and get a new phone in the near future. That firmware upgrade process fails right when the status bar shows up on the screen. Now rebooting the phone says Software Update Failed.
What are my options via Kies, Odin, or something else to either get back to rooted Hyperdrive or just get the latest firmware up and running? Thanks!
ODIN v3.10
https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
This is the SCH-I545 lollipop image:
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api
And once you go forward..There is NO ROOT or ROMMING!!!
If you want to stay NK1 and ROOT:
https://docs.google.com/file/d/0B4RU_ZH5QUASdHE1b2Q2NXpVX0U/edit?usp=docslist_api
In ODIN, WITH EITHER file select these checkboxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS CLEAR
Thanks a ton. Haven't gotten it to work yet. I followed your directions and Odin fails with "SW REV. CHECK FAIL : fused : 7, Binary : 6". My guess is that is a mismatch of the bootloader versions? I believe I was on NC5 before, so I tried flashing the No Wipe file from here: http://forum.xda-developers.com/showthread.php?t=2735172 and had no luck.
Any idea what version I should be trying to get it to work? Thanks for the help so far!
No. That means you are on lollipop Bootloader already! You have to flash lollipop
KaosMaster said:
No. That means you are on lollipop Bootloader already! You have to flash lollipop
Click to expand...
Click to collapse
Yup. Learned that while I was thinking about it. Such is life, right? Currently trying to just get OC1 installed via Odin but it keeps failing late in the process with XmitData_Write. If anyone has an idea beyond changing cables and ports (which I'm doing now) then I'm all ears.
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
volantis said:
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
Click to expand...
Click to collapse
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
KaosMaster said:
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
Click to expand...
Click to collapse
Thanks. I finally got it working. I'm not sure exactly what did it. I kept trying various combinations of flashing at CSC or AP and in Download mode and Software Upgrade Failed. I believe the one that actually took was the Sammobile stock OC1 file flashed as AP, but I'm not 100% and not sure that really is what made the difference. I did have all the options checked when it finally took.
After the Odin flash passed it did just boot to a black screen with the LED on solid blue. I went to recovery and did a factory reset and the phone booted up. Maybe that'll help someone else.
Don't have root anymore, but Lollipop seems like a very nice update coming from KK.
Thanks! - but still in trouble.
Spoke too soon!! Yours was the only one that actually loaded with Odin. After that phone will not reboot, just comes on for 2 seconds and then turns off. Any ideas would be greatly appreciated.
I have tried the following firmware versions, except for yours, they all get fused: 7 , binary : 6:
I545_VZW_I545VRUDMI1_I545VZWDMI1_Original
I545_VZW_I545VRUEMJ7_I545VZWEMJ7_Original
VZW-I545VRUFNC5-20140429111807
VZW-I545VRUFNG6-20141021092718
plus several others
--------------
Thanks, bricked my Verizon S4 and tried 5 different firmware files, including the ones from the Samsung site. Yours is the only one that worked.
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
volantis said:
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
Click to expand...
Click to collapse
Sorry, thought I updated the post. I tried again and the second time around it worked all the way through with the file on this thread.
This tutorial gets your MetroPCS Grand Prime (model SM-G530T1) root, a deodexed and bloatware-free TouchWiz, 'fairly stock' ROM, and Xposed Framework. This method will likely work on the T-Mobile variant because much of this is actually intended for that variant... but no guarantees. If you do, indeed, attempt this with a non-MetroPCS variant, please let me know your model number and if it works or not so i can add it to the compatibility/incompatibility list.
Known compatible variants:
SM-G530T1 - MetroPCS
This tutorial comes with no guarantees or warranties. I am not responsible if you brick your device or for any damage caused by following this tutorial. You can most likely recover any problems you find along the way by simply flashing back to Stock with Odin, but I can't guarantee that you will be able to. This is true of basically everything on XDA, so no surprises here.
I estimate the entire process taking less than a half hour, assuming that everything goes as expected, and that you don't need to flash back to stock first.
There is one caveat... the TrapKernel method fully roots the device, but it trips Knox. If you don't want to trip Knox, don't use this method. As an alternative, if all you want is some minor root functionality, KingRoot will give you SOME root functionality, but not enough to install Xposed, or to do many things that a true root gives you. KingRoot can be found here: SITE / DOWNLOAD
At any time, even if you brick your device, you can probably always flash back to Stock. Here is the Stock MetroPCS SM-G530TI 5.1.1 ROM: THREAD / DOWNLOAD
Alright... without further adieu, here are the files you will need:
Odin SITE / DOWNLOAD
ShinySide's TrapKernel for SM-G530T THREAD / DOWNLOAD
DUHAsianSKILLZ's deodexed and bloatware-free ROM for SM-G530T: THREAD / DOWNLOAD
Chainfire's FlashFire SITE / DOWNLOAD
Xposed Installer THREAD / DOWNLOAD
TWRP 2.8.7.0 (for lollipop) THREAD / DOWNLOAD
Custom Xposed Framework for Samsung Lollipop THREAD / DOWNLOAD
Got all the files you need? Here are the steps:
1. On your phone, boot to Download Mode by booting your device while holding down the Down Volume and Home Button, then hitting Volume Up. Connect it to your PC. If your PC doesn't recognize the phone, you need to install drivers. There are lots of threads out there with tutorials on how to do that. This tutorial assumes you already have the drivers.
2. On your PC, open Odin, Click the "AP" button, Select the file: TrapKernel_G530T_AOF8_Root.tar.md5. Flash it. Let the phone boot normally. If it doesn't load after a few minutes, pull the battery and reboot. If it continues to get stuck on boot, it probably failed. Flash back to Stock and try again.
3. On your phone, once it fully boots up, download Chainfire's SuperSU from the Play Store. You'll need it in order to authorize the root app in the next step.
4. On your phone, download FlashFire from the Play Store at the link above, or if you have the APK, install it. Open FlashFire and authorize SU permissions. Hit the + button, then Wipe. Check System data, 3rd party apps, Dalvik cache, Cache partition, and Cache partition format, then click the Checkmark on the top-right to confirm. Now hit the + button again, then Flash Zip or OTA. Select GwizRomSMG530T-V1.1.zip, then click the Checkmark on the top-right. Now click Flash. The screen will go off during this step... DON'T WORRY. It will take about 10 minutes total to boot for the 'first time'. This ROM basically removes Knox, retains root, and frees up a lot of resources that Samsung was using for useless bloatware. Even if you stopped at this step, your phone will be MUCH better off than with a purely Stock ROM on it. I noticed a HUGE performance improvement after installing this ROM.
5. On your phone, install XposedInstaller_3.0_alpha4.apk.
6. On your phone, open FlashFire. Tap the + button, then Flash Zip or OTA. Find TWRP_2870_Samsung_SM_G530H.zip and flash it. This one takes a little while to load, so be patient. I would say, if you're at the 10 minute mark after tapping Flash, it probably failed so pull the battery and reboot. If it continues to happen, you'll likely need to flash Stock and start over completely.
7. The phone will boot back to your home screen. Once it does, restart it and go into Recovery Mode by booting the phone while holding the Volume Up and Home buttons.
8. Once in Recovery, tap Install. Find and choose the file xposed-v86.0-sdk22-arm-custom-build-by-wanam.zip and swipe the slider at the bottom to Install Xposed.
9. Once it finishes flashing and boots back up, you're good to go. Full Root. Bloatware-Free. Really fast. With Xposed.
10. One last thing, I would install an app like NoBloat or something to disable or delete the app com.tmobile.pr.adapt. It doesn't like that you rooted your device and will start acting up. The reason a T-Mobile app is there is because the bloat-free ROM you installed in step 4 above is based on a T-Mobile Stock ROM, not MetroPCS. You don't need it. It will ask for root permissions all the time, use cell data, and deplete your battery. Just disable it if you are not comfortable fully deleting it. I would also look into disabling/deleting some of the other apps like some of the Samsung stuff, but you'll have to research what is safe to remove. I know the com.tmobile.pr.adapt app is pointless and a data/battery hog.
Well then thanks for putting this together. Now everything is in one spot. Well done.
Sent from my SM-G530T using Tapatalk
after flashing "TrapKernel_G530T_AOF8_Root.tar.md5" Phone reboots fine, but wifi doesn't works anymore, I repaired it with SmartSwitch, reloading the firmware back to Stock.
bullracing said:
after flashing "TrapKernel_G530T_AOF8_Root.tar.md5" Phone reboots fine, but wifi doesn't works anymore, I repaired it with SmartSwitch, reloading the firmware back to Stock.
Click to expand...
Click to collapse
How did you end up doing that? I couldn't figure out how
you mean, how to restore to stock?
Download Smatch by Samsung, the use theere option "MORE" and go to "EMERGENCY SOFTWARE RECOVERY AND INTIALATION" there Switch will ask you phone the phone model and the SN number to get the original or Stock firmware to it
No... went to root my Samsung Galaxy Prime to remove bloatware
Help
GwizRomSMG530T-V1.1.zip will not install, there are 2 options to check on the flash screen, should I leave those blank or check them?
Disclaimer:
I am not responsible for anything that happens to your device after following this guide. Also, I'm not entirely sure if this works 100% for OF1, although I can guarantee that this guide works for OB6 because I just successfully rooted, unlocked the bootloader, and flashed a custom recovery onto my Galaxy Note 3 running the OB6 update.
This guide was compiled for the sole purpose of convenience for other users here on XDA Forums. My reason for making this guide was to make it as easy as possible for Verizon Galaxy Note 3 owners to root, unlock the bootloader, and flash a custom recovery without jumping from thread to thread, searching for answers.
ONLY FOLLOW THIS GUIDE IF YOU KNOW WHAT IT MEANS TO BE ROOTED, HAVE AN UNLOCKED BOOTLOADER, AND WHAT A CUSTOM RECOVERY IS USED FOR
If you are the proud owner of a Verizon Galaxy Note 3 (SM-N900V) and would like to root, unlock the bootloader, and/or flash a custom recovery onto it, you've come to the right place. Included in this guide are methods of doing these exact things, which also happen to be generally easy to perform.
Before you begin, you'll need a few things:
a Verizon Galaxy Note 3 (running OB6 or OF1, obviously)
a computer of some sort (running Windows)
a micro SD card (make sure there isn't anything on it, because it WILL be erased)
Odin 3.09 *
TWRP 3.02-1 *
ArabicTool *
eMMC Brick Bug Checker app
unlock_n3 (for unlocking the bootloader, attached) *
* place these files in a location that you know the path of. e.x. C:\ or C:\Users\...\Desktop
Once you are 100% sure that you have all of these things, continue to the rest of the guide.
Root
Open ArabicTool
Make sure your phone is connected to your computer
In ArabicTool, click on the "Version" field and select your firmware version (OB6/OF1)
Click on "Read phone info" and wait for the information above to show your phone's status
Check the logs on the bottom right to make sure that everything is correct, then click on "Root" below the "Phone info" box (if there is an error about not being on 5.0, close the app, set the compatibility mode to W7, and run as admin)
Once your phone restarts, continue to the next part of the guide
Unlocking the Bootloader
Just follow this tutorial. The consequences of messing this part up can lead to bricking your phone, although the process itself is fairly simple. Just remember that you need to unzip samsung_unlock_n3.zip and rename the file in there to unlock_n3. Follow the instructions from there.
Flashing TWRP
Honestly, this part was the easiest for me.
Unzip and open Odin 3.09
Reboot your phone into download mode (with it plugged into the computer, obviously)
In Odin, click "AP" and find the flashable TWRP tar that you downloaded earlier
Start the flashing process by clicking "Start" in the bottom right hand corner
If, after this process, your phone reboots and shows an error about the recovery partition in the top left hand corner (in blue), then goes into a bootloop:
Download the stock recovery.tar from the attached files at the bottom of this post
Open Odin again
Click "AP", find the file you just downloaded, and start the flashing again
Follow the instructions to unlock your bootloader again, but only do the second set of code. The first set is irrelevant to us at this point.
Flash TWRP onto your phone again. This time, it should work if it didn't already.
To make sure, boot your phone into recovery mode. If TWRP boots up, success (obviously )!
If you have any issues whatsoever that I haven't covered in this guide, please either PM me or reply to this thread. Also, if I have made any mistakes in outlining the instructions in this guide, do the same.
Credit to:
@androidyemen and others for finding the root method,
@ryanbg for finding the bootloader unlock method,
@beaups for finding the eMMC backdoor,
and Team Win for creating TWRP
Source posts:
[Official] Note 3 Verizon Bootloader Unlock by ryanbg
OB6 & OF1 N900V Note 3 Verizon Oneclick SuperSU Rooted Successfully
If in any case you would like to donate to me for this post (which in no way am I asking you to), here is my PayPal email:
[email protected]
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Sent from my SM-N900V using XDA-Developers mobile app
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Click to expand...
Click to collapse
I'm not entirely sure if it will work on JasmineROM 6.1 specifically, but it won't hurt your device to try. Unless your CID doesn't start with 15 for some reason. If it does, the worst that can happen is the unlock file won't work.
I'll have to edit that part when I get home. I'm only going to be gone for about 20 minutes or so.
Sent from my LG-H634 using XDA Labs
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Click to expand...
Click to collapse
It really only needs root, although the spot it looks for the eMMC CID value changed from kernel release to kernel release, so there were some minor release dependencies.
[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.
The version which seems to be most compatible with M*, N*, and O* kernels is the build posted (along with source code) in post #218 of the bootloader unlock thread.
( The newly-rebuilt version in the OP of that thread is still incompatible with 4.3 and 4.4 (M*, N*) releases. )
Man up and use your browser if the XDA app is broken.
.
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes it will, I did it already months ago when all this first came out.
Sent from my SM-N900V using Tapatalk
@jamesalynch
I know you are trying to help and everything, but you've kind of screwed the pooch in a couple of different ways. First, the binary that you attached doesn't work on any 4.3.x (M*) or 4.4.x (N*) series ROMs, and I'm not sure it ever worked even on OB1 and OF1.
Second, you should not be re-attaching files that are available in other people's posts. Just provide a link to the original post; if there is an ambiguity as to what download is desired, then describe it in your post.
Third, you should not be taking other people's downloads, unpacking them, and then renaming the included files to match filenames used elsewhere - that is only going to increase people's confusion.
Fourth, in that OP (@ryanbg 's post) he mentions re-building the code and NOT USING the version that you provided as an attachment. Unfortunately, he was in a hurry when he rebuilt the code, and even the new version he built still does not work on 4.3.x and 4.4.x ROMs.
[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.
The version that will work for everyone is in @donc113's post #218 in that thread.
Code:
$ find . -type f \( \! -name '*.zip' -a \! -name '*.c' \) -exec md5sum {} \;
[b][color=green]ea856efcb7de0ca8ff428522dbdc0267 ./donc113-post218/unlock[/color][/b] [b]<<<==== Use this for NK1 and prior.[/b]
0bcb409af65e311ce4b67faf7ed3f0af ./ryanbg0804/unlock_n3 [b]<<<==== Use this for OB6 and OF1.[/b]
cba959357ed1d0207dbde56bb6b6a1b7 ./ryanbgORIG/samsung_unlock_n3
cba959357ed1d0207dbde56bb6b6a1b7 ./JAL/unlock_n3 [b]<<<==== Your version with name change from 'samsung_unlock_n3'.[/b]
Thanks to everyone who posted. I will be going back to the post mentioned in the comments.
Sent from my SM-N900V using XDA-Developers mobile app
This is kinda confusing, to be honest.
Once bootloader is unlocked you could just download FlashFire and download and flash TWRP from there rather than using Odin.
The root tool you linked didn't work for me, even on Windows 7, granted others said it worked for them. If they are on Windows 10, there is a different tool to use.
stock recovery?
I need the stock recovery file, that you said would be attached. My phone is not booting with the Recovery warning..
Tremo419 said:
I need the stock recovery file, that you said would be attached. My phone is not booting with the Recovery warning..
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/45906/N900VVRUEOB6_N900VVZWEOB6_VZW/
Open that file and extract the recovery image. Compress it in a TAR. Flash.
Sent from my LG-H634 using XDA Labs
I have the sm-900v on 5.0 and I rooted and unlocked bootloader and twrp and flash a rom but didn't go through so I Odin stock rom back to begin fresh and now it won't root...as soon as I do the root process and it restarts my phone into stock recovery...so I clean cache and reboot and goes right back to stock recovery...can anyone help
Sent from my SM-N900V using XDA-Developers mobile app
ozz200127 said:
I have the sm-900v on 5.0 and I rooted and unlocked bootloader and twrp and flash a rom but didn't go through so I Odin stock rom back to begin fresh and now it won't root...as soon as I do the root process and it restarts my phone into stock recovery...so I clean cache and reboot and goes right back to stock recovery...can anyone help
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Firstly, if you have an unlocked bootloader, you never have to flash STOCK again.
So - after you have gotten this problem fixed - learn how to avoid using Odin with STOCK firmware bundles.
Odin can flash a custom recovery when the bootloader is unlocked. That will save you trouble in the future. You need to learn how to build Odin ".tar.md5" files. In a nutshell, for doing what I just mentioned, you take a TWRP .img file, rename it to "recovery.img", put it in a "ustar" format tar file, and then compute the md5 signature of that and append it to the end of the file. Search for "Odin md5 ustar" in these forums.
For your current problem, I can't tell exactly what you are saying. If you are saying "I am stuck in a vicious cycle of nothing but recovery reboots (the stock recovery)", then
- pull the battery and wait ten seconds
- put the battery back in
- start in download mode with Vol_Down+Home+Power. When you get the pop-up screen, select cancel.
- if it still boots into the stock recovery, the do a full wipe (yes the whole phone, data+cache) and try booting. If the same trouble persists, go back and do the Odin STOCK flash again. (You can't flash a custom recovery with a locked bootloader).
If it still doesn't work, make sure your next problem report includes far more details than the one above, for instance:
- what version of firmware was on your phone before this mess started
- what version of firmware you were trying to flash with Odin
- what version of Odin you were using
- the name of the Odin file and it's MD5 signature.
that's a start.
VZW Note 3+Root+Jasmine Rom+Partial Firmware
CID starts with 15 (verified with EMMC)
Android Ver: 5.0
N900VVRUEOF1
Ive ran the unlock countless times I gets nothing no unlock of the bootloader at all
Omegastorm said:
VZW Note 3+Root+Jasmine Rom+Partial Firmware
CID starts with 15 (verified with EMMC)
Android Ver: 5.0
N900VVRUEOF1
Ive ran the unlock countless times I gets nothing no unlock of the bootloader at all
Click to expand...
Click to collapse
It produces error messages when it encounters a problem and exits without completing it's job.
Is there some reason why you believe we should be able to intuit what those countless error messages were? (It would be simpler if you just cut-n-paste that output into your post.)
You might also want to state which version of the tool you used - there are at least 3 in the original thread.
im thinking about getting a verizon note 3.. does this work for all variants to get root, twrp and custom roms?
thanks
Jaws4God said:
im thinking about getting a verizon note 3.. does this work for all variants to get root, twrp and custom roms?
thanks
Click to expand...
Click to collapse
No
You can root all variants but can not unlock all variants, thus can't use TWRP or use custom ROMS or kernel.
Must be model SM-N900V, must have a specific Samsung eMMC (cid must start with 15) and the external SD card slot must work along with the USB port.
Sent from my SM-N900V using Tapatalk
bftb0 said:
It produces error messages when it encounters a problem and exits without completing it's job.
Is there some reason why you believe we should be able to intuit what those countless error messages were? (It would be simpler if you just cut-n-paste that output into your post.)
You might also want to state which version of the tool you used - there are at least 3 in the original thread.
Click to expand...
Click to collapse
Oh wow didn't know there was three I'm gonna go back and check that out again thanks
This is awesome man, great thanks to you. I'm new on n3 verizon, i like unleashing the power of my phone, =D
THANK YOU!
Nice post! I hadn't looked at XDA/ note 3 development in awhile. Awesome to see an exploit found! BAM!
Has anyone made a STOCK deodex/? CM is cool, but I like the S-pen. I have the n900V.
Thanks again
1Xfan said:
Nice post! I hadn't looked at XDA/ note 3 development in awhile. Awesome to see an exploit found! BAM!
Has anyone made a STOCK deodex/? CM is cool, but I like the S-pen. I have the n900V.
Thanks again
Click to expand...
Click to collapse
There are some Stock out there:
[LP] [5.0] [RE/DE] [Xposed] [MultiSystem] JasmineROM v6.1
mostly stock N900VVRUEOF1[debloated/deodexed/wifi fixed]
So, I cobbled together a (custom-recovery) flashable NC4 stock ROM.
I'm interested to find out whether it is possible to boot it successfully from later bootloader firmware - e.g. NK1, OB6, or OF1
(I'm still on NC4 bl and not planning on upgrading near term. It boots on NC4 bl but that's pretty obvious lol)
[size=+2]Q: Why would this be useful?
A: to provide a means for upgrading bootloader firmware without starting from scratch.[/size]
For instance, there are folks on OB6 firmware that would like to use a custom ROM that will only work on OF1 firmware. They can certainly start from scratch (backup and unload the entire device); an alternative would be to:
- Make a backup of an existing rooted ROM (that more than likely has a custom or modified boot image so is not bootable when the bootloader gets re-locked) using the currently-installed custom recovery (which will also be non-bootable under re-lock).
- Restore a (debloated) pure stock ROM w/ Samsung kernel. Root it with Towelroot (does not touch boot image)
- Flash replacement bootloader only in Odin. Locked bootloader = no custom recovery... but with a rooted stock ROM already in place with an unmodified stock kernel it can be immediately unlocked.
NC4 is easily rooted with Towelroot-v3 "on device". No need for PC drivers, online rooting tools with a separate PC, etc (e.g. as with Yemen rooting methods on OB6, OF1)
This approach in principle saves the need to backup everything up in the /sdcard - but you have to know in advance that the NC4 stock kernel and ROM can successfully be booted with later bootloaders.
So anyway, that's what I'm asking for help testing with - folks that are: (a) unlocked and (b) on NK1, OB6 or OF1 bootloader willing to try flashing a debloated NC4 Stock ROM using their existing custom recovery, and see if it boots, roots, and if root survives a single boot cycle.
Contact me via this thread or PM; I'll provide the flashable NC4 and the Towelroot .apk
.
my n900v came with 5.0 Of1 but i rooted, unlocked BL. installed twrp and flashfired NC4 tar minus recovery
runs smooth.I hate lollipop.lol
only bug is wifi password resets everytime i reboot
im curious as to why i have trouble running certain nc2/nc4 roms..some want to bootloop/freeze
baja,biggins,and objective rom
kernel issue maybe? or BL version
btw. i am rooted via towelroot v3
hotrod85z said:
my n900v came with 5.0 Of1 but i rooted, unlocked BL. installed twrp and flashfired NC4 tar minus recovery
runs smooth.I hate lollipop.lol
Click to expand...
Click to collapse
Thank you for posting that, very useful/helpful information to know.
Does Flashfire understand the Samsung "sparse" image format of the system.img.ext4 file inside the Stock (Odin) .md5 tarfile blob? Or maybe somebody else packaged up a "flashable .zip" of NC4?
hotrod85z said:
only bug is wifi password resets everytime i reboot
Click to expand...
Click to collapse
in /system/build.prop, set ro.securestorage.support=false and reboot. You might also want to set ro.config.tima=0 as well.
I suspect that mixing and matching Samsung kernels with bootloader versions breaks something in the TrustZone, and so secure containers and other sort-of-obscure security functions no longer work as the TZ smells something fishy. I am using a rooted PL1 rom on NC4 bl and it would spontaneously reboot (infrequently) until I made the above changes - it's been rock stable for about 4 days now. Why this works I can't really say - it's a "generation skipping" bootloader and stock rom combination - N* bootloader and P* ROM *
hotrod85z said:
im curious as to why i have trouble running certain nc2/nc4 roms..some want to bootloop/freeze
baja,biggins,and objective rom
kernel issue maybe? or BL version
btw. i am rooted via towelroot v3
Click to expand...
Click to collapse
all of the above or none of the above LOL
There are definitely some mysteries here, and I don't claim to fully understand the interdependence of the TZ (== bootloader firmware), the TIMA and RTKP stuff in the kernel, and the cross-communication between kernel and TZ via the qseecom service daemon (which is in the ROM in /system/bin) much less how the APIs of all these interfaces might have changed between major releases.
You could check those two build.prop settings in those ROMs for starters though. I suspect that if the TZ smells something fishy (e.g. a kernel TIMA to TZ info mismatch), a variety of secure credential services in the TZ stop working. It is possible that "ro.securestorage.support" is a toggle that attempts to use TZ services when it is set to "true", and so anything in the ROM which builds on it breaks because the TZ is refusing to play on an otherwise "stock" ROM variant.
FWIW I got the AryaMod (S7Edge MM port) + phantom kernel running on NC4 bl + OF1 modem for a full 24 hours after I disabled the qseecom service daemon. It ran long enough that I had customized the whole thing as a daily driver with all my apps, verified that all sensors & radios worked, made test calls, etc. Rebooted it and the kernel started getting reset by a "Modem Reset". Even weirder was that despite the use of the OF1 "modem" firmware, the kernel was reporting a bunch of RIL "unknown ioctl's". Strikes me as odd that the whole thing could run that long with so many different things happening, and then the "modem" is unhappy - even though other folks are using the ROM with OF1 bl + OF1 radio/modem firmware. (As if the "modem" isn't really the source of the problem, even though that's what initiates the device reset).
.
i initially tried flashing NC4 full tar via ODIN. but even bl unlocked. i got FAIL. flashfire worked!
very curious as to whether a custom n900v kernel would boot my 4.4.2 custom roms..its either that or the BL isnt compatible with non-touchwiz roms....
most of the kernel/modem/firmware links on here are 404 error dead links.. would be nice to see an up to date sticky. ill flash anything as long as i dont end up in JTAG mode with a brick.lol
ive played with verizon s5 atnt s2,galaxy capitivate,atrix 4g and many other phones
the s2 is still by far the fastest Smoothest phone on cm7..the newer the phones..the newer the OS..the bigger the resourse hogs"ram" im a minimalist...
even after flashing NC4 official full tar..im still showing OF1 baseband under settings
@hotrod85z
FWIW I posted a bunch of recovery-flashable stock ROMs here.
There is also a link in that thread to a complete set of (Odin flashable) modems for NC4, NJ6, NK1, OB6, OF1, and PL1 if that is of interest to you.
Maybe I wasn't paying attention, but I could swear that on at least one occasion or two when I performed an Odin modem flash, it didn't "stick", despite no complaints on the handset screen or in Odin - the next boot showed the (prior) baseband version, not what I flashed. Its a bit of a mystery to me; but for now I've resolved to make sure that after the Odin session is complete, I wait 30 seconds or so, then remove the USB cable, and then pull the battery rather than try to restart the device by holding buttons down. It is possible that those events occurred when I soft-restarted the phone, but I'm not sure. For now I'm just trying to always flash and restart with exactly the same method to avoid different behaviors from creeping in.
PS I have no idea if those ROM flashables are compatible with Flashfire. They might be, but I've never tested it, and as they are not pre-rooted I'm not going to suggest it for fear that somebody with a rooted but locked (bootloader) phone will try using flashfire and then end up with a phone that needs a full Odin re-install. Appearances are that each version of the bootloader restricts the Samsung signing verification to only the matching kernel version - you can't even boot a Signed samsung kernel on a locked phone if it is a different version than the bootloader's version.
Hello all I have a emmc exploit note 3 I'm using here and I wanted to flash different radios for the us carrier note 3's and I first tried to use flash fire to try to update the modem, but even that didn't stick, cause I don't readily have a pc available, I wasn't ballsy enough to flash a different carrier modem, since I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode and I didn't want a brick, so overall my question is, do I need a unlocked bootloader to flash different modems and do I need odin tovdo it or will some sort of mobile odin or something do it? Thanks mates and happy flashing.
Dlind said:
Hello all I have a emmc exploit note 3 I'm using here and I wanted to flash different radios for the us carrier note 3's and I first tried to use flash fire to try to update the modem, but even that didn't stick, cause I don't readily have a pc available, I wasn't ballsy enough to flash a different carrier modem, since I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode and I didn't want a brick, so overall my question is, do I need a unlocked bootloader to flash different modems and do I need odin tovdo it or will some sort of mobile odin or something do it? Thanks mates and happy flashing.
Click to expand...
Click to collapse
Well, your question is way off topic for this thread.
But since nobody is in here anyways, I guess I'll answer the parts that I am able to.
The modems that I posted over in that other thread were meant to be flashed in Odin using a PC. You can use either the AP slot or CP slot. Note that the very first post says - in big bold blue letters "Odin-flashable Modems".
Not flashfire. It never said anything about flashfire.
Is there such a thing as MobileOdin? If there is, I know nothing about it and certainly have never tested anything with it. So I don't know and am not going to speculate.
You said something confusing here:
Dlind said:
I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode
Click to expand...
Click to collapse
If it says "MODE: Developer" you have an unlocked bootloader. Which is exactly the same thing as a Developer Edition phone.
If you were to use a PC with Odin and you flashed a FULL Stock firmware flash, yes it would overwrite the unlocked bootloader and indeed re-lock the phone. If you were able to re-root that (stock) ROM, you could perform the unlocking procedure again to unlock it.
On the other hand, those Odin-flashable modem packages do not contain the bootloader firmware, so if you were to use Odin on a PC to flash just those modem images, your bootloader would not get re-locked - the unlocked bootloader is still there, untouched.
When the carriers issue an OTA update, many times (perhaps most of the time) they contain a modem update (NON-HLOS.bin and modem.bin). So it is obvious that they are able to be flashed **somehow** right on the phone, without using Odin from the PC or an "Odin app" at all.
BUT that happens using a combination of the STOCK recovery and the bootloader itself during the reboot following the actions taken by the STOCK recovery. (My guess is that the recovery simply "stages" it into place, and sets some flags so that the bootloader knows that it is supposed to evaluate the crypto signatures of the file blobs that the recovery put into place and it is actually the bootloader that does the flashing. That's really not a whole lot different than what happens when you transfer files from Odin to the phone - the "Odin/Download" mode is just one of the personalities of the bootloader. (Odin is actually a rather dumb program - it's the bootloader on the phone that gets to decide whether a flash happens. It does that by carefully examining the file blob that gets transferred, e.g. crypto signature checks)
My guess is that you would be able to flash STOCK modem packages from Odin (using a PC) independent of whether the bootloader is locked or unlocked. But as I said: "guess".
I don't have a second phone to test with, so I would have to flash completely back to stock and lock my bootloader to be able to test that hypothesis. That's a big jobs because of all the crap I have to backup and restore to my phone.
Frankly, if you don't have access to a PC, and you really need your device to keep working, I would advise you to stop screwing around with it, simply because you don't have good tools available to fix it if a disaster occurs.
PS. I've never once noticed anything different between various radio firmwares on ANY device I've ever owned.
bftb0 said:
Well, your question is way off topic for this thread.
But since nobody is in here anyways, I guess I'll answer the parts that I am able to.
The modems that I posted over in that other thread were meant to be flashed in Odin using a PC. You can use either the AP slot or CP slot. Note that the very first post says - in big bold blue letters "Odin-flashable Modems".
Not flashfire. It never said anything about flashfire.
Is there such a thing as MobileOdin? If there is, I know nothing about it and certainly have never tested anything with it. So I don't know and am not going to speculate.
You said something confusing here:
If it says "MODE: Developer" you have an unlocked bootloader. Which is exactly the same thing as a Developer Edition phone.
If you were to use a PC with Odin and you flashed a FULL Stock firmware flash, yes it would overwrite the unlocked bootloader and indeed re-lock the phone. If you were able to re-root that (stock) ROM, you could perform the unlocking procedure again to unlock it.
On the other hand, those Odin-flashable modem packages do not contain the bootloader firmware, so if you were to use Odin on a PC to flash just those modem images, your bootloader would not get re-locked - the unlocked bootloader is still there, untouched.
When the carriers issue an OTA update, many times (perhaps most of the time) they contain a modem update (NON-HLOS.bin and modem.bin). So it is obvious that they are able to be flashed **somehow** right on the phone, without using Odin from the PC or an "Odin app" at all.
BUT that happens using a combination of the STOCK recovery and the bootloader itself during the reboot following the actions taken by the STOCK recovery. (My guess is that the recovery simply "stages" it into place, and sets some flags so that the bootloader knows that it is supposed to evaluate the crypto signatures of the file blobs that the recovery put into place and it is actually the bootloader that does the flashing. That's really not a whole lot different than what happens when you transfer files from Odin to the phone - the "Odin/Download" mode is just one of the personalities of the bootloader. (Odin is actually a rather dumb program - it's the bootloader on the phone that gets to decide whether a flash happens. It does that by carefully examining the file blob that gets transferred, e.g. crypto signature checks)
My guess is that you would be able to flash STOCK modem packages from Odin (using a PC) independent of whether the bootloader is locked or unlocked. But as I said: "guess".
I don't have a second phone to test with, so I would have to flash completely back to stock and lock my bootloader to be able to test that hypothesis. That's a big jobs because of all the crap I have to backup and restore to my phone.
Frankly, if you don't have access to a PC, and you really need your device to keep working, I would advise you to stop screwing around with it, simply because you don't have good tools available to fix it if a disaster occurs.
PS. I've never once noticed anything different between various radio firmwares on ANY device I've ever owned.
Click to expand...
Click to collapse
Thanks SOOOOOO MUCH for your input I kinda had a feeling that the idea was risky at first and I don't know a whole lot about odin and I wish Samsung could have created something much easier to use, but thanks for answering the wayyyyy off topic question, I'm gonna smash that thanks button, I'm also going to take the advise on not cross flashing different modems, its just to risky. You answered all my questions so thanks, Also I want to say thank you for your continued work on this phone is by normal terms "old" now but in reality its still an amazing phone with the right custom software, and happy flashing!