[HELP]System software not authorized by Verizon.

[HELP]System software not authorized by Verizon. - Verizon Samsung Galaxy S III

I installed Rom Manager on my phone to install TWRP to flash a new rom
My Device is SAMSUNG GALAXY S3 VERIZON
After the installation of TWRP, I restarted my device
then the annoying message appeared
I look for some solution in Google but no luck
I tried going in to Download Mode but the key combination is not working
and when i press the key combination, It is only Black Screen and vibrating every second.
Is my device Hard-Bricked? How to bring it back to working again?
Please I need your HELP!! THANKS!!

What version of Android was the phone on?
Somewhere about 4.4.2 the bootloader got locked.
Go read the threads for SuperLiteROM and the special recovery for the locked bootloader.

Did you ever find a solution to this?
Sent from my SCH-I535 using XDA-Developers Legacy app

It's soft bricked, just need to run Odin and load a stock ROM back on. You probably have 4.4.2.

I already fixed it and using it now as i type....
THANK YOU ALL GUYS FOR THE EFFORT YOU'VE MADE....
i fix it by using a so called USB JIG and after it booted perfectly, i found out the problem was with the vol. flex

I've now been at this for 4 hours, with no luck. :C
I'm having the same error issue as OP.
I'll try to share as many details as I actually remember/have, because I'm not sure what's needed. I broke the phone trying to root it to make it an mp3 player and to remove bloatware. Being an idiot, I must have deleted something the phone needed. I'm an absolute a beginner at any and all things android rooting and flashing.
I have no idea, after so many hours have gone, by what exactly I uninstalled with Kingo. I've just been trying to reset the phone to the factory OS. I already tried a factory reset to no avail.
Apps I've installed throughout my attempts to fix this include: SuperUser, Official TWRP App, ROM Manager, BootDroid, Kingo ROOT, and Samsung Odin Download Helper.
The only thing I can do to start the phone up past the "Verizon software warning" screen is hold volume down, home, and power to bypass it to the booting screen.
The phone info
Samsung Galaxy s3
Model #: SCH-1535
Android Version 4.4.2
Baseband version: unknown
Kernal version: 3.4.0 [email protected] #1
Build number: kot49h.1535VRUDNE1
SE Android status: Enforcing SEPF-SCH-1535_4.4.2_0016
Hardware: 1535.10
64gb SD Card
ERRORS:
This one comes up twice on startup. "Unfortunately, the process com.android.phone has stopped."
If I use BootDroid to launch Bootloader, I get a green droid with this in the corner
ODIN MODE
PRODUCT NAME: SCH-1535
SYSTEM STATUS: Custom
QUAL.COMM SECUREBOT: ENABLE
BOOTLOADER AP SWAEV: 2
If I press volume down, home, and power it gives warning about installing a custom ROM and I can choose volume up to load the custom one, or press volume down to boot normally.
If I press up now, I get a screen saying this in the corner instead:
ODIN MODE
PRODUCT NAME: SCH-1535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUAL.COMM SECUREBOT: ENABLE
BOOTLOADER AP SWAEV: 2
And under a green droid it says "Downloading..." Do not turn off target!! But nothing happens, it just stays on this screen.
If I select Recovery mode in ROM Manager, it gives me the "System software not authorized by Verizon" screen.
Currently I have a file named I535VRBMF1_I535VZWBMF1_VZW.zip on the SD card, but it doesn't show up anywhere in the phone, only when I open the folder on my PC. When I choose "install ROM from sd card" in ROM Manager, the files aren't there. After the first try, I also added the files unzipped also, but they are also not visible.
I've tried Fix Permissions in ROM Manager. All of the apps listed above have root access. Then it says to reboot my phone, but nothing appears to have changed.
I don't remember everything I've tried, but I at least know tried How to Use ROM Manager to Flash Custom ROMs after Rooting via Kingo Root, for sure, but I couldn't get past
"Download the ROM you want and copy it to your phone's SD card.
Before you find the custom ROMs you should use your phone model to find your wanted Android version on Google. You should be aware that each ROM will be based on a specific Android version." because the files on the SD card won't show up on the phone.
Thanks in advance!

Yard-Paragon said:
I'm having the same error issue as OP. I'll try to share as many details as I actually remember/have, because I'm not sure what's needed........
Click to expand...
Click to collapse
Oh My.... This is a real mess... LMAO!
I will do my best to help you out but, I can't guarantee anything. I'm going to try to address this the best way I can since your post is really all over the place.
Let me just clarify 2 things:
1) Your device is currently on the NE1 firmware and you will not be able to flash the MF1 or any other firmware besides the NE1.
2) You had mentioned that you wanted to install a Custom Firmware on your device and unfortunately, you will not be able to Unlock your Bootloader since your on the NE1 Firmware and your Bootloader is locked up.
Your only option is to either:
A) Debloat, that requires careful consideration to figure out what can be removed and what can't. You'll be surprised at what odd apps the Firmware actually has a dependency on and can crash your device (as you've already experienced).
B) Install what's called the TW Based Firmware. This is the Stock Firmware that is specially customized with the appropriate debloated apps and a few other customizations that varies on the developers.
3) Finally... There's the "Kingo" that you used and, I'll get to the point, that's garbage. very few Succeed with this and is rarely used nowadays. We'll hopefully get back to rooting.
What it looks like is the possibility of your device being on the verge of being Hard Bricked...
You need to flash the NE1 Firmware and might need to use the PIT file (PIT = Partition Information Table) but, we'll start without the pit file first.
Go to the following thread and obtain the "I535VRUDNE1_I535VZWDNE1_I535VRUDNE1_VZW" Firmware for your device.
https://forum.xda-developers.com/showthread.php?t=3744627
Be sure to read the top portion of the OP (OP = The First Post) regarding what you need to have and know within the instructions for Flashing the Stock Firmware.
Please let me know where/how you're doing...
FYI... The TW Based Firmware are those that are either labeled with "TW" and/or "Debloated" on the Threads Title.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

I fixed this a long time ago. I used a USB JIG because I found out the volume keys are not working. After using the JIG, I flashed the stock rom for Verizon S3 Android 4.4.2. Then it works. But I'm not using the device anymore. If anyone who still experience this problem, try USB JIG.

Related

[Q] Where to start the root process?

I have a GT-N8013 Galaxy Note 10.1 Wireless 16G. It has been updated to Jelly Bean and has been updated to JB through the Keis OTA and has also just recently received one or two other updates, for what reason I am not sure.
I just recently rooted my Droid Razr Maxx and so far, I am happy that I did that. Now I want to go ahead and root my Note 10.1, however I am thoroughly confused as to where to start. Through all of my Google searches and message board searches, I keep coming across what seems to be older instructions for updating to JB, which I already have, or rooting based upon apps that were in existence as far back as say August, 2012.
Well now it is the end of March, and I do not know if I should be pursuing this using Odin (which version and where is the best place from which to download it) or is there an alternative or better approach using CM 10, etc. As I typed the question, the last similar threads that popped up were from November 30, 2012 and prior.
I wanted to avoid having to ask what to many of you seems to be such a basic question, but there just doesn't seem to be anything that I see out there that has a recommended method, post OTA JB.
Any advise will be greatly appreciated.

bookbean said:
I have a GT-N8013 Galaxy Note 10.1 Wireless 16G. It has been updated to Jelly Bean and has been updated to JB through the Keis OTA and has also just recently received one or two other updates, for what reason I am not sure.
I just recently rooted my Droid Razr Maxx and so far, I am happy that I did that. Now I want to go ahead and root my Note 10.1, however I am thoroughly confused as to where to start. Through all of my Google searches and message board searches, I keep coming across what seems to be older instructions for updating to JB, which I already have, or rooting based upon apps that were in existence as far back as say August, 2012.
Well now it is the end of March, and I do not know if I should be pursuing this using Odin (which version and where is the best place from which to download it) or is there an alternative or better approach using CM 10, etc. As I typed the question, the last similar threads that popped up were from November 30, 2012 and prior.
I wanted to avoid having to ask what to many of you seems to be such a basic question, but there just doesn't seem to be anything that I see out there that has a recommended method, post OTA JB.
Any advise will be greatly appreciated.
Click to expand...
Click to collapse
Some of the rooting methods have been defeated by Samsung with the last 2 updates.
Zedomax has a root method that does work will the most current firmware updates and his version of CWM that is installed with his root method seems to be more compatible with a few of the custom ROM's out there.
You should visit these links, they are very informative.
http://forum.xda-developers.com/showthread.php?t=1831152
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Root Video Link
http://www.youtube.com/watch?feature=player_embedded&v=nIYiXzcW7xs
Un-Root directions
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/

Did not succeed with root
kkretch said:
Some of the rooting methods have been defeated by Samsung with the last 2 updates.
Zedomax has a root method that does work will the most current firmware updates and his version of CWM that is installed with his root method seems to be more compatible with a few of the custom ROM's out there.
You should visit these links, they are very informative.
http://forum.xda-developers.com/showthread.php?t=1831152
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Root Video Link
http://www.youtube.com/watch?feature=player_embedded&v=nIYiXzcW7xs
Un-Root directions
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/
Click to expand...
Click to collapse
I carefully watched the video. After the CWM-SuperSU-v0.94.zip file was transferred onto my external drive, I ran odin3 v1.85exe and got to the green pass screen. After the reboot, I held down the power and volume up buttons until I saw the screen go off. When the logo came up, I let go of the power button and I kept holding onto the power up button, but I did not get to the ClockworkMod Recovery screen. Instead, I was brought to the Android Recovery Screen. I tried clicking on the file on the external SD from that screen, but all that I got were failures.
What other options are there?
Thank you, btw, for trying to assist me.

bookbean said:
I carefully watched the video. After the CWM-SuperSU-v0.94.zip file was transferred onto my external drive, I ran odin3 v1.85exe and got to the green pass screen. After the reboot, I held down the power and volume up buttons until I saw the screen go off. When the logo came up, I let go of the power button and I kept holding onto the power up button, but I did not get to the ClockworkMod Recovery screen. Instead, I was brought to the Android Recovery Screen. I tried clicking on the file on the external SD from that screen, but all that I got were failures.
What other options are there?
Thank you, btw, for trying to assist me.
Click to expand...
Click to collapse
You did something wrong....... Did you do power and vol down at the same time first 1:40 of video after that run odin again.
It maybe better to download video in1080p to your computer so you can watch easier.

Resolved with an alternative process
kkretch said:
You did something wrong....... Did you do power and vol down at the same time first 1:40 of video after that run odin again.
It maybe better to download video in1080p to your computer so you can watch easier.
Click to expand...
Click to collapse
I used Odin, but found another root method called CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.zip. That worked like a charm. I then installed Root Checker to ensure that it worked, which it did.
So now I need to know what applications I need to install next as a follow-up.

I don't believe Auto root installs CWM. You may need to get Mobile ODIN, there's a free version on XDA or a paid version in the play store... I prefer to get the licenced version as there's more things you can do.
After installing this, you can then put the CWM file on your sd card or internal memory and flash it or just flash a custom rom...
Flashing a custom rom should put a custom recovery on too...
You might want to download and run an app called triangleaway to reset your flash counter too...

Moving right along
ultramag69 said:
I don't believe Auto root installs CWM. You may need to get Mobile ODIN, there's a free version on XDA or a paid version in the play store... I prefer to get the licenced version as there's more things you can do.
After installing this, you can then put the CWM file on your sd card or internal memory and flash it or just flash a custom rom...
Flashing a custom rom should put a custom recovery on too...
You might want to download and run an app called triangleaway to reset your flash counter too...
Click to expand...
Click to collapse
Thank you all for helping this root noobie. So I am running CWM Recovery v6.0.0.1.1 right now and doing a full backup to my external card. Seems like it should be done pretty soon. The blue widget in Andy's belly doesn't seem to move too much, if at all, however I do see that the progress bar is moving along and the file names keep changing below "backup up data...".
On top of Andy's head are three little guys with the words "High on Android" across his head. Oops, now I'm getting messages about skipping backup of apps and the fact that No sd-ext found. I don't understand that as there is most certainly an ext SD card.
Assuming that this completes OK, I will next proceed for CM10 and Triangleaway, unless there are other recommendations. Now back to the main Backup and Restore screen. Sorry for the blow by blow, but this is all new to me. Would my Titanium license provide the same benefits?

Here are a few good must haves for me.
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&feature=search_result#?t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS50cmlhbmdsZWF3YXkiXQ..
Carbon - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
AirDroid (better than Kies for wireless file transfer)
https://play.google.com/store/apps/details?id=com.sand.airdroid
MyScript Calculator
https://play.google.com/store/apps/details?id=com.visionobjects.calculator
.

Triangle Away
kkretch said:
Here are a few good must haves for me.
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&feature=search_result#?t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS50cmlhbmdsZWF3YXkiXQ..
Carbon - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
AirDroid (better than Kies for wireless file transfer)
https://play.google.com/store/apps/details?id=com.sand.airdroid
MyScript Calculator
https://play.google.com/store/apps/details?id=com.visionobjects.calculator
.
Click to expand...
Click to collapse
I went ahead and downloaded Triangle Away. When I start in download mode, I receive the warning along with the big yellow triangle. After pressing volume up to continue, it goes into Odin Mode (in Red) and shows that the Custom Binary Download: Yes (5 counts), followed by Current Binary: Custom and then System Status: Custom. To get out of that screen, I have just held down the power button to turn off the device.
When I start up the Triangle Away app, the current status (under Flash Counter) says that Status cannot be determined, need to reboot into a special bootmode - tap "Reset flash counter".
In the Overview section on Play Store, it shows this warning:
On a number of devices, TriangleAway can work, but your firmware may not be supported directly. In that case, the app will tell you it needs to reboot into a special boot mode, which will be happen if you select "Reset flash counter". The device will reboot into a special mode which will allow you to review the current status and reset the binary and flash counter values (or abort and do nothing). On some devices this will actually trigger the counter to 1 if its 0 - so if you're "just checking", do that in download mode!
!!! THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE !!! ( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you *really* mean it! )
Note#1: using Triangle Away may unmount your SD card. Reboot or manually remount it from Android settings.
Note#2: on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!
I am not clear on how to interpret the warning, other than it makes me a bit nervous about bricking the device. I did a quick search of USB JIG for the SGN10 and I didn't see anything come up in the first few Google pages. One placed discussed making your own JIG which involves soldering. Not my thing!
So my question is has any other GT-N8013 user performed the step of selecting the reboot into the special mode, and if so, what happens after that? More importantly, did anyone experience having their SGN10/GT-N8013 bricked from this step?
Again, sorry if this is basic to most, but it is new to me, and we all have to start somewhere.
Thanks,
'Bean

bookbean said:
I went ahead and downloaded Triangle Away. When I start in download mode, I receive the warning along with the big yellow triangle. After pressing volume up to continue, it goes into Odin Mode (in Red) and shows that the Custom Binary Download: Yes (5 counts), followed by Current Binary: Custom and then System Status: Custom. To get out of that screen, I have just held down the power button to turn off the device.
When I start up the Triangle Away app, the current status (under Flash Counter) says that Status cannot be determined, need to reboot into a special bootmode - tap "Reset flash counter".
In the Overview section on Play Store, it shows this warning:
On a number of devices, TriangleAway can work, but your firmware may not be supported directly. In that case, the app will tell you it needs to reboot into a special boot mode, which will be happen if you select "Reset flash counter". The device will reboot into a special mode which will allow you to review the current status and reset the binary and flash counter values (or abort and do nothing). On some devices this will actually trigger the counter to 1 if its 0 - so if you're "just checking", do that in download mode!
!!! THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE !!! ( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you *really* mean it! )
Note#1: using Triangle Away may unmount your SD card. Reboot or manually remount it from Android settings.
Note#2: on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!
I am not clear on how to interpret the warning, other than it makes me a bit nervous about bricking the device. I did a quick search of USB JIG for the SGN10 and I didn't see anything come up in the first few Google pages. One placed discussed making your own JIG which involves soldering. Not my thing!
So my question is has any other GT-N8013 user performed the step of selecting the reboot into the special mode, and if so, what happens after that? More importantly, did anyone experience having their SGN10/GT-N8013 bricked from this step?
Again, sorry if this is basic to most, but it is new to me, and we all have to start somewhere.
Thanks,
'Bean
Click to expand...
Click to collapse
I think there's no USB jig to Note 10.1. I have used TriangleAway for my I9100 few times and N8010 (same that your device but european) once and both worked fine, no bricks. After you boot in "special mode", you'll be shown your counter, and it will confirm are you sure, you can cancel it there if you want and it does nothing to your device. Just check that your download mode's counters match TriangleAway's counters.

After Special Mode
niko0o said:
I think there's no USB jig to Note 10.1. I have used TriangleAway for my I9100 few times and N8010 (same that your device but european) once and both worked fine, no bricks. After you boot in "special mode", you'll be shown your counter, and it will confirm are you sure, you can cancel it there if you want and it does nothing to your device. Just check that your download mode's counters match TriangleAway's counters.
Click to expand...
Click to collapse
Thanks for giving me the courage to give it a shot, which I have now done. The counter in the special mode matched what Odin was showing, so I went ahead with it.
Now when I start up holding down the volume down button along with the power button, I am still getting the Triangle. However this time, below the Odin Mode (written in red), it shows Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
I take it that because there is still root on the device, that the System Status will continue to show "Custom" and I will continue to have the triangle? I thought that the idea was to get everything to "look" official stock. Please let me know if I am missing anything else.
Thanks,
'Bean

I Got All Things Official By Flashing A Stock Rom Through Mobile ODIN Onto The Note At This Point BUT You Will Need To Factory Reset. You Will Also Go Back To Stock Recovery. If You Want All These Things To Display Official Status.
I Haven't Got It Back To Not Show Official While Running A Custom Rom As Current Binary Changes To Custom When You Install Cwm Or System Status Does.
Theres Also A Status In Settings> About> Status That Will Also Say Custom Too. Shouldnt Be A Problem Unless You Try To Use The Allshare Cast Hub...

ultramag69 said:
I Got All Things Official By Flashing A Stock Rom Through Mobile ODIN Onto The Note At This Point BUT You Will Need To Factory Reset. You Will Also Go Back To Stock Recovery. If You Want All These Things To Display Official Status.
I Haven't Got It Back To Not Show Official While Running A Custom Rom As Current Binary Changes To Custom When You Install Cwm Or System Status Does.
Theres Also A Status In Settings> About> Status That Will Also Say Custom Too. Shouldnt Be A Problem Unless You Try To Use The Allshare Cast Hub...
Click to expand...
Click to collapse
My understanding is that Allshare is useful only if you have other Samsung devices. So first, please advise if my understanding on that is correct. Assuming that this is the case, then I suppose that I do not need to immediately concern myself with getting all three settings to be "official", as I am in no immediate need (hopefully) to go back to full factory settings with official software since I do not own any other Samsung Android device. I am only beginning the root journey. I guess that it is good to have the bread crumbs to find my way back home at first, but I also want to be adventurous and try out some of these really interesting things which root is supposed to lead me to.
Is it fair to say then, that the counter thing shouldn't be a concern for now?

bookbean said:
My understanding is that Allshare is useful only if you have other Samsung devices. So first, please advise if my understanding on that is correct. Assuming that this is the case, then I suppose that I do not need to immediately concern myself with getting all three settings to be "official", as I am in no immediate need (hopefully) to go back to full factory settings with official software since I do not own any other Samsung Android device. I am only beginning the root journey. I guess that it is good to have the bread crumbs to find my way back home at first, but I also want to be adventurous and try out some of these really interesting things which root is supposed to lead me to.
Is it fair to say then, that the counter thing shouldn't be a concern for now?
Click to expand...
Click to collapse
To zero that last you need to flash stock firmware with Odin, but thats not necessary except if you need to return your Note to warranty or something.

bookbean said:
My understanding is that Allshare is useful only if you have other Samsung devices.
Click to expand...
Click to collapse
I own an allsharecast hub and I use it at school to lecture.I project the tablet screen to an hdmi LED TV which is not a Samsung brand.So no;you have a misunderstanding at this.And since I have a GT-N8005 device and triangle away doesn't support this device I can't use the 'reset flash counter' method:crying:

Allshare
ordeniz said:
I own an allsharecast hub and I use it at school to lecture.I project the tablet screen to an hdmi LED TV which is not a Samsung brand.So no;you have a misunderstanding at this.And since I have a GT-N8005 device and triangle away doesn't support this device I can't use the 'reset flash counter' method:crying:
Click to expand...
Click to collapse
Thank you for clarifying the allsharecast hub use and I am sorry that you cannot change your flash counter. Is it possible for the author of the program to modify it for your device? Perhaps you can contact them about it.

bookbean said:
Thank you for clarifying the allsharecast hub use and I am sorry that you cannot change your flash counter. Is it possible for the author of the program to modify it for your device? Perhaps you can contact them about it.
Click to expand...
Click to collapse
Thanks.I posted a comment on google play store,and I will contact them soon.

How to root your samsung galaxy s3 (easily)

**** UPDATED 7-24-13 *****
Please read the tutorial now as I have added a new section on how to unlock the bootloader for your Verizon Samsung Galaxy S3. If you are not using a verizon SGS3
specifically model SCH-i535 then you do not have to worry about unlocking your bootloader as it comes unlocked by default. If you are using a verizon samsung galaxy s3 model sch-i535 and you do not fully unlock your bootloader you could run into problems when using certain root apps such as "mobile odin pro" or you could run into big problems when trying to flash custom roms such as cyanogenmod roms.
In this update I am adding one final step at the end of the root process to fully unlock the boot loader for the verizon samsung galaxy s3. There will be two ways to unlock the bootloader. One way will be to flash a final bootchain file with Odin, and the other will be to use an app to unlock the bootloader. Depending on what version of android you are using and your phones baseband version you will either need to use odin or you could use the application for any android version such as 4.1.1 or 4.1.2 and you can use the application for any baseband version your phone might be. I will leave the choice up to you, but I will show how to do it both ways.
Samsung users, don't forget if you plan on flashing a custom rom that with Samsung phones you could get the ugly yellow triangle warning. To get rid of this yellow triangle you can either go to google play store and get "yellow triangle away" app or go to this forum on this great xda developers site: http://forum.xda-developers.com/showthread.php?t=1494114
**NOTE** for those of you who would like to see a video of how to root your phone using these exact steps you can go to here: http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
A member on this thread gave me that link and it is a video by phone rebel and show you how to root your verizon SGS3 using the same steps i have outlined in this tutorial. Thank you so much for providing that link to my attention, I am sure it will help many users here!
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
*****UPDATED STEP*****
IMPORTANT NOTE: i want to point that this step is completely optional. You do not have to unlock your bootloader but i would recommend it. If you just want to use a stock rom and have your phone rooted then you can ignore this last step. But...if you want to flash custom rom's or do any kind of serious customize your phone, then you will need to have your phones bootloader unlocked. Plus with the application I am going to show you further down this tutorial, it is so easy to unlock your bootloader, you might as well go for it.
Step 10. Okay now from the link that I gave you above: http://forum.xda-developers.com/showthread.php?t=2046439 you are going to need to download another bootchain file to fully unlock your verizon samsung galaxy s3 model sch-i535 phone.Go into your phone and under settings go into "about phone' and look at the section "baseband version". Now depending on what version of android you are using will determine your baseband version. On my Verizon SGS3 running 4.1.2 my baseband version is I535VRBMB1 the important part is -> "VRBMB1" now go to site i provided in this step and download the bootchain for your specific phone.
Since my phones baseband version is "VRBMB1" i will download that bootchain file obviously. VRBMB1 is for android 4.1.2
The other boothchain files are "VRBLK3" for android 4.1.1 and "VRBMD3" for android 4.1.2
Now take that bootchain file that you downloaded and load up Odin again. Connect your phone to your computer (MAKE SURE YOUR PHONE IS IN DOWNLOAD MODE -> VOL DOWN + HOME + POWER) and wait for Odin show a connection. Odin will show a blue light on newer Odin versions and a yellow light on older Odin versions.
When the connection is made hit the "bootloader" button and select the proper bootchain file for your specific phone. Before you hit start make sure that only "Auto Reboot" is selected on the left hand side.
Now go ahead and hit start and if all goes well your phones bootloader should be unlocked. You can tell that your phones bootloader is unlocked two ways.
One, when your phone reboots the Samsung Logo in white bold/block writing will disappear within 1-2 seconds. It will go by very fast.
Two, the custom lock icon that showed up after you ran the CF-AUTOROOT exploit will now disappear, if for any reason if you still see this logo then your phones bootloader is still locked and you can either try to flash the bootchain file again or use the application I am about to tell you about.
For my phone flashing this bootchain file worked fine, but for my brother's phone he has a verizon samsung galaxy s3 model sch-i535 this did not work and I had to use an application to unlock his bootloader.
****UPDATE UNLOCKING THE BOOTLOADER WITH EZ-UNLOCK*****
Okay so my brother who has a verizon samsung galaxy s3 model sch-i535 asked me to root his phone just the other day. I rooted his phone following all the same steps I have written above with no problems. His phone rooted perfectly, however his bootloader would not unlock. I believe that his bootloader would not unlock because he had an updated version. While his android version was the same as mine 4.1.2 he had a different baseband version.
His baseband version was "I535VRBMF1" the important part -> "VRBMF1"
Now i have been told that you can use the bootchain file VRBMB1 to unlock the bootloader for verizon SGS3 running android 4.1.2 baseband version "VRBMF1" but when i tried it, the bootloader staid locked. So i had to use an application to unlock his bootloader.
The application i used was "EZ-Unlock" which you can get here: http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Now this application is SO EASY to use it is amazing. Just download the file, the author recommend version 1.2 as the most stable and that is version i used. To download this file make sure you have the option "Unknown Sources" check in your Settings -> Security menu.
Okay to unlock your bootloader with EZ-Unlock follow these easy steps:
Step 10A. Download EZ-Unlock version 1.2 from the link above.
Step 10B. Install the application and open it.
Step 10C. Once open click on the giant "Unlock" button. If all goes well you will hear "That was easy" from the application.
Once you have hit the unlock button on EZ-Unlock reboot your phone to see if the Samsung in bold/block white letters disappears within 1-2 seconds, and make sure the custom lock icon has disappeared.
Now the application EZ-Unlock is designed specifically for verizon samsung galaxy s3 phones, it does not matter what baseband version you use or android version you use. So this is a very appealing and easy way to unlock your bootloader. If you don't feel like flashing a bootchain file with Odin or if you are not sure what bootchain file you should use then using this application. NOTE: you do need root access to run this application.
And that is it! Your phones bootloader should be unlocked either with Odin or EZ-Unlock the choice is all up to you!
***LAST THOUGHT ON INSTALLING CUSTOM RECOVERY***
This rooting method does not install and kind of custom recovery manager on to your phone. If you want to install a custom recovery manager such as "ClockworkMod Recovery" you can do that very easily once your phone is rooted. Once your phone is rooted go to the google play store and download "Rom Manager". Once Rom Manager is installed open it up and give it root access with SuperSU. Once that is done go into the option to flash a recovery manager and follow the steps and the application Rom Manager will take care of that for you!.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow

Thanks might have to do this on my wife's phone
Sent from my SCH-I535 using xda premium

kgirlx said:
Thanks might have to do this on my wife's phone
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I think that the easiest way to root any Samsung Devices - Samsung Toolkit

I'm not having any luck with this. I've followed the instructions step by step and when I flash a custom ROM, I get the dreaded yellow triangle of death apon rebooting. There were some other files mentioned in the links. Do I need to unzip those at some point?

sorry i have been away
Okay i am so sorry for the late response I have been away and very busy. This tutorial is how to root your samsung galaxy s3 (verizon) model sch-i535 because you need to unlock the bootloader for that specific model.
Now you mentioned that when you try to flash a custom rom you get a yellow triangle of death....
Have you unlocked the bootloader?
Is your phone already rooted? Are you trying to flash a custom rom or are you still trying to root your phone?
I hope you have already resolved your issue but if you haven't I would be more than happy to try and help you out.

How is it any easier then the other guides for jelly bean? Here you added the cf-auto root which is one extra step . Also with auto root there is a possibility of bricking the phone since it supports a lot of devices and as you are well aware that a lot of people new to flashing tend to flash the wrong files even if you give them a step by step guide. While this guide is helpful and does work it isn't as idiot proof as the other guide you linked on your post.

This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!

benbrown said:
This does not work on my phone. When I try this, the phone boots normally. I have tried this several times and I get the same results. I can however hold the vol up button+the home button+the power button and get to stock recovery mode. I had an older S3 that this did work on but not my new one. I have read several threads here for rooting the S3 i535 with Jelly Bean 4.1.2 and this is supposedly the method but it will not work on my phone. What am I doing wrong? What am I missing? Please advise!
Click to expand...
Click to collapse
This guide is different in that it uses cf-auto root so I highly doubt you even tried this method.

I finally did get it. All rooted now.
Sent from my SCH-I535 using Tapatalk 2

The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done
Sent from my MIUI powered S3 thanks to StrumerJohn

maybe i should have been more clear...
faehsemc said:
The easiest way to root is odin'ing Mr. Robinson's root injected tar and the unlock the bootloader. Done
Sent from my MIUI powered S3 thanks to StrumerJohn
Click to expand...
Click to collapse
Hey everyone,
Well i guess everyone has their own favorite way of rooting their phone/device. I did not mean for this small tutorial to be the *absolute easiest* way to root a verizon samsung galaxy s3 model i535 i just thought that I could do people a favor by elaborating a bit more on certain steps to make the rooting process a bit easier.
On certain tutorials i found I didn't seem them clearly state that the VRLAC BOOTCHAIN file needed to go in the boot loader section of ODIN to unlock the phone's bootloader.
On other tutorials that show you how to use CF-AUTOROOT I didn't see any that told you that you needed to install SUPERSU from the google play store manually in order to fully utilize your phones rooted status.
Yes there are other ways too root a SGS3, the Samsung Toolkit is a good option, or using a custom root such as Cyanogenmod is another great option as well...
All of those options you will have to research for yourself and ultimately decide for yourself.
However, if you want to keep your phone's stock ROM and you just want to root your Verizon SGS3 model SCH-I535 then I like using ODIN + CF-AUTOROOT exploit.
All i wanted to do was assist and do my part on this great forum which has helped me so much in the past...
I hope it helped someone...
Thanks for everyone who replied and shared your thoughts on other rooting options.
-DroidShadow

droidshadow said:
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Click to expand...
Click to collapse
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .
The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.
Anything you can help me with? I''m going crazy here.
Thanks

Rooting and installation on S3 GTI9300
I rooted my S3 2 days back (i think so), now i want to install a custom rom (mostly xperia Z) and I am new to this world, so can you plz help me??
I followed your instructions there was no such msg as Andriod is Updating, and how should i do install the rom??
I wish to install from this http://forum.xda-developers.com/showthread.php?t=2174644

droidshadow said:
Hello everyone,
Well this is one of my first tutorials for this forum on how to root your Verizon Samsung Galaxy S3.
I just recently got my Verizon Samsung Galaxy S3 and all of the tutorials I found were quite complicated and not very detailed so I thought that
I would write this tutorial and maybe it might help others out there....
Since the Galaxy S4 is getting ready to come out, the price has dropped considerably for the S3 and i believe more and more people will be getting this phone and wanting to root it.
Oh, and if you want an alternative guide you can use this very excellent tutorial from another post on this amazing forum:
http://forum.xda-developers.com/showthread.php?t=2046439
Here is the specs for the phone I am using and the step by step process I used to root it.
Verizon Samsung Galaxy SIII model I535 running Android 4.1.2
Okay step 1 you are going to need some files...
First thing you are going to need is the Samsung Drivers so you can connect your phone to your computer and your computer can recognize it.
All of the files you are going to need I am just going to reference the link from the other tutorial that I posted above, no sense in redoing work
that has already been done especially if it has been done well!
1. You can get the samsung driver files here: http://forum.xda-developers.com/showthread.php?t=2046439
click on the link that says samsung drivers
2. You are going to need Odin you can get it from the same link, click on the Odin Link
3. You are going to need the VRALEC BOOTCHAIN you can get it from the link I posted in step 1 make sure you get this file it is very
important.
Since I am using a Verizon Samsung Galaxy S3 the bootloader comes by default locked so we need this file to unlock the bootloader
so we can root the phone. If we were using any other phone besides Verizon we would not have to worry about this but since I have
Verizon I have to do this. IMPORTANT: if you are not using a VERIZON PHONE DO NOT download this file or use it in the step
process you do not need it.
4. Next you are going to need the exploit so that you can root your phone and you can grab that from a different website, here is the address:
http://autoroot.chainfire.eu/
This is the CF-AUTOROOT file and this is what roots your phone. If you have the same phone as me scroll down to the SCH-I535 link and
download that file.
Okay now that we have all of that downloaded lets get things moving...
First thing we are going to need to do is install the Samsung USB drivers, so do that.
After the drivers are installed plug in your phone and make sure that it connects to your computer correctly, after it connects disconnect
your phone from your computer.
Next thing we are going to need to do is extract the ODIN zip file and install the Odin executable.
Now we need to get to the critical stuff...
Step 1. Make sure that [USB Debugging] is enabled in your phone, if it is not go to Settings -> Developer Options and enable it.
Step 2. Put your phone in DOWNLOAD Mode. You do that by pressing Volume Down + Home + Power button and hold it down till you see
a warning screen. When you see the warning screen hit Volume Up to allow Download mode.
Step 3. Now that your phone is in Download Mode you are going to connect your phone to your computer with ODIN RUNNING if
everything connects correctly you will see ODIN highlight yellow (older versions of ODIN) or highlight blue (newer ODIN versions)
Step 4. Now this is where previous tutorials kind of messed up in my opinion (just my opinion). Now that your phone is in download mode
you need to only have the "auto boot" option selected in ODIN and click on the bootloader button and select the VRALEC file
you downloaded earlier. Every tutorial i read said to use this file with the PDA button/option but you need to use it with the bootloader
button/option in ODIN. Now that you have the VRALEC file selected under bootloader in ODIN select START. This will reboot your
phone and if everything goes correctly your phone's bootloader will be unlocked.
After reboot make sure to disconnect your phone from your computer.
Step 5. After your phone reboots from step 4 turn off your phone and then boot it back into DOWNLOAD mode. Vol Down + Home + Power
Step 6. Now that your phone is in Download Mode again (Reconnect your phone to your computer) and make sure ODIN is still running
Step 7. With your phone connected go to the PDA option/button and when you select it choose the CF-AUTOROOT file you downloaded earlier
Step 8. With your PDA option selected hit start. When this happens your phone will reboot and your will see a CUSTOM lock icon on your
screen don't worry it is okay. Now you will see some new text on your phone and if everything is working you will see things like
"Android is UPDATING"
Your phone is now rooted! but you are not done...
This is where all of the other tutorials I found also fell short...
Your phone is rooted but it will not work correctly without SuperSU
Step 9. Go to the Google Play Store and Download SuperSU. When the download is complete run SuperSU and now your phone is fully
rooted. You can test it by downloading Android Terminal and running the terminal and typing "su" or by downloading a root required
app Titanium Backup.
Congrats on rooting your phone! I hope this tutorial has helped you and I want to thank all of the system administrators of this forum and all of
the great guys and gals that contribute to this place. You guys/gals are what makes the open source community great!
I thank you all...
Hope it helped!
-droidshadow
Click to expand...
Click to collapse
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL

hello everyone
bgenchel said:
I ran ODIN with the bootchain, and that worked, but when i tried running it with PDA set to CF-autoroot file, I get SECURE CHECK FAIL
Click to expand...
Click to collapse
bgenchel: what kind of phone do you have? Are you 100% sure that you downloaded the correct CF-autoroot file for your specific phone model?

mlev1987 said:
Followed all instructions, and the phone never rebooted. Not its not turning on. Tried vol up+home+power, vol down+home+power, battery pull, holding down power for 2 minutes. . .
The only thing I can think of is that I possibly unplugged the phone before the reboot after Step 4, just as soon as the phone shut down and before the actual reboot.
Anything you can help me with? I''m going crazy here.
Thanks
Click to expand...
Click to collapse
Did you run the Odin with the VRLAC bootchain file then you unplugged your phone before a full restart could take place? This is a very sensitive issue because that bootchain file unlocks your bootloader on your verizon phone. Your bootloader is everything to your phone. It controls how your phone starts and your phone can not work correctly if your bootloader became compromised in any way. I really hope you figured it out, and if you didn't maybe you could call your insurance company (if you have one) and get a new phone. If you are worried about rooting your phone again you could look on craigslist, there are always people/professionals willing to do it for very reasonable prices $10-$20. Again i really hope you figured this out and if you give me some more details maybe we can figure this out together.

Phone Rebel Method
This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.
At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.

UPDATE
ohemetophobia said:
This is the same method that Phone Rebel has on his YouTube channel for rooting d2vzw. This tutorial is missing one step that Phone Rebel covers, after running CF Auto Root, he flashes the corresponding bootchain file that goes with whatever firmware your phone is running. When I rooted, I was running VRBMB1, so I flashed that boot chain following the other two odin flashes. http://www.youtube.com/watch?v=K4b9hcWHrW8&feature=share&list=FL8Y3FM4mtznp0GQbwkkwaSg
What I've learned is that CF Auto Root does not unlock the bootloader and trying to flash a custom ROM with result in the dreaded triangle message every time. I was given this method: http://droidviews.com/2013/root-and...erizon-galaxy-s3-sch-i535-android-4-1-14-1-2/
to try instead. In this method you flash the VRALEC, then CWM recovery, then you can flash SuperSU with an unlocked bootloader via CWM, then flash the final bootchain file depending on the firmware you're running. Method 3 contains the casual root tool, but I've seen mixed reviews for that one.
At the suggestion of someone on the Google+ community for the SGS3, I"m gonna attempt to root VRBMF1 (JB 4.1.2 w/multiwindow) via method 1 and then flash the VRBMB1 bootchain for the previous version and see what happens.
Click to expand...
Click to collapse
You can use method 1 outlined in the droidviews link i posted yesterday to root the phone and when you get to the point where you're flashing the second bootchain you can flash VRBMB1 instead of needing VRBMF1 and it will work just fine! I also believe this method will truly unlock the bootloader for flashing custom roms, to avoid the yellow triangle of frustration, but I have no oversight on this as it was not my plan to do so.

VRBMF1??
I must admit that I am new to rooting.
I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............
For VRBLK3 (Jelly Bean 4.1.1) Link
MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A
For VRBMB1 (Jelly Bean 4.1.2) Link
MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1
For VRBMD3 (Jelly Bean 4.1.2) Link
MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF
I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.

BKSinAZ said:
I must admit that I am new to rooting.
I just bought a new S3 i535 with 4.1.2 and would like to root it. In the link provided there are files to download. One of these files are the bootchain... When I look in my settings, I see VRBMF1 and in the link provided I see.............
For VRBLK3 (Jelly Bean 4.1.1) Link
MD5: E3A1CB07DE214ED8081ED9D42C9BAF4A
For VRBMB1 (Jelly Bean 4.1.2) Link
MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1
For VRBMD3 (Jelly Bean 4.1.2) Link
MD5: 9CB65EAE8784807349EC3D4FF3A0AAEF
I am confused on what to do. I would imagine that this instructional post was created before I got my phone (07/13/2013) and thus is the reason why it might be missing from the instructions. Please advise me.
Click to expand...
Click to collapse
Yes, the instructional post was created prior to you getting an S3. So, if you got into Settings> About Phone and look at your baseband version you'll probably see I535VRBMF1 and you'll probably see it again in another field just below it. This indicates that you're running the VRBMF1 firmware. That is JB 4.1.2 with multi-window. When using the root process in the droidviews article it outlines flashing VRALEC, then CWM touch, then using CWM to flash the supersu file, then flashing either VRBLK3, VRBMB1, or VRBMD3. Since none of those bootchain files match your firmware and there is no VRBMF1 bootchain on the forums, I flashed VRBMB1 since it was the the bootchain from the previous firmware. It worked. I successfully achieved root with no problems. Hope this helps.

[Q] P905V recovery brick

Hey Guys,
When I try to boot in Odin mode the tablet just boots with RECOVERY BOOTING....then hangs...
Samsung
Galaxy Note Pro
Unlocked Pic
Custom
Android
I was rooted then i wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working. I really dont want to take it to verizon. I have revived but the three button salute doesnt let me get into download mode. Please help Its insuranced but will they cover it since it has Custom on it?
Edit: Screen is not faint and the device is working.

So reading some other threads where people encountered this problem. Two main solutions
1. bad recovery flash, it needs to be flashed again.
2. Can you still plug in the tablet and charge it? If you can do that the other recommended solution was burning the battery out until dead, basically forcing a full on restart of everything, then plugging in the device letting it recharge then trying to boot into download mode again. They say pull the battery, but since you can't do that you need to burn it down to 0. As long as you can charge your tablet you aren't lost. If you can get into download mode after trying that flash stock firmware from odin. Then start the process from step 1, clean start.
Either way, I wouldn't panic yet. Well don't panic at all. Panicking just makes mistakes and you aren't anywhere near the hopeless stage where you have to bring it back to verizon yet. I'm sure other people here will have other ideas as well and some people may have had the same problem. Just breathe. Burning the battery will give you some relaxing time lol. Pretty confident it can be fixed.
biggiesmalls657 said:
Hey Guys,
When I try to boot in Odin mode the tablet just boots with RECOVERY BOOTING....then hangs...
Samsung
Galaxy Note Pro
Unlocked Pic
Custom
Android
I was rooted then i wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working. I really dont want to take it to verizon. I have revived but the three button salute doesnt let me get into download mode. Please help Its insuranced but will they cover it since it has Custom on it?
Click to expand...
Click to collapse

Gatsrom said:
So reading some other threads where people encountered this problem. Two main solutions
1. bad recovery flash, it needs to be flashed again.
2. Can you still plug in the tablet and charge it? If you can do that the other recommended solution was burning the battery out until dead, basically forcing a full on restart of everything, then plugging in the device letting it recharge then trying to boot into download mode again. They say pull the battery, but since you can't do that you need to burn it down to 0. As long as you can charge your tablet you aren't lost. If you can get into download mode after trying that flash stock firmware from odin. Then start the process from step 1, clean start.
Either way, I wouldn't panic yet. Well don't panic at all. Panicking just makes mistakes and you aren't anywhere near the hopeless stage where you have to bring it back to verizon yet. I'm sure other people here will have other ideas as well and some people may have had the same problem. Just breathe. Burning the battery will give you some relaxing time lol. Pretty confident it can be fixed.
Click to expand...
Click to collapse
Thats why ^^^^^^^ i love this great community because people help each other and positive feedback rather than negativity. I have modified dozens of device over the years and this device is my first big fail as of now but I will let it die. What gets me is Verizon and ATT know that locking their device makes people mad and yet they continue to do whats best for business. I someday would love to reach dev status. How would I flash the recovery without download mode?

Debrick IMG
I also have the Stock Rom decompiled and am trying to make a Debrick IMG to get the tablet to boot from SDext to get to download mode then im out of the woods but i need to find out what imgs to use. I have Win32 Disk Imager ready and this is how I saved my S3 verizon last year. I don't have download mode yet or ADB (i think) so im running out of ideas. There are a lot of awesomesauce devs out there (including you) that do amazing things for our devices. Mattlgroff saved my RAZR Maxx and Trident made the ally a great phone for its time. It might not seem sometimes especially how people act by bickering but we really do appreciate the hard work of development across the board of devices. End Story

just boots with RECOVERY BOOTING....then hangs...
--- wanted to flash stock and it went downhill from there. It flashed last night but wifi wasnt working.
Click to expand...
Click to collapse
the first one sounds so, that the recovery Image was/is the wrong one. This matched also the 2nd one : Stock, but Wifi is not working. If you flash e.g. on P905 the H3 Imagage and after that the C3 kernel, Wifi doesn't work in this status also anymore. I'll believe, you've flashed a wrong image.
To change anything / or the repair the Tab, you must have the possibility to have an access to the Tablet.
What does you've try?
Fastboot / Recovery-Menu? [This one failed -if I've understood you right]
Download-Menu?
Up to which point does your Tab start's up ? Doers you've any access?

biggiesmalls657 said:
I also have the Stock Rom decompiled and am trying to make a Debrick IMG to get the tablet to boot from SDext to get to download mode then im out of the woods but i need to find out what imgs to use. I have Win32 Disk Imager ready and this is how I saved my S3 verizon last year. I don't have download mode yet or ADB (i think) so im running out of ideas. There are a lot of awesomesauce devs out there (including you) that do amazing things for our devices. Mattlgroff saved my RAZR Maxx and Trident made the ally a great phone for its time. It might not seem sometimes especially how people act by bickering but we really do appreciate the hard work of development across the board of devices. End Story
Click to expand...
Click to collapse
Hmmm we definitely need someone with a 905 to post the partition info if you're going to try to build a debrick.img. Have you used search to see if anyone maybe already has? I only have the 900 and I was pretty sure they were different. Just glancing at this program I'm guessing you'd need boot.img since it's going to basically provide a bootloader as the phone hops from internal to external looking for a way to boot. I've never used it though so I don't want to tell you the wrong thing :x

Gatsrom said:
Hmmm we definitely need someone with a 905 to post the partition info if you're going to try to build a debrick.img. Have you used search to see if anyone maybe already has? I only have the 900 and I was pretty sure they were different. Just glancing at this program I'm guessing you'd need boot.img since it's going to basically provide a bootloader as the phone hops from internal to external looking for a way to boot. I've never used it though so I don't want to tell you the wrong thing :x
Click to expand...
Click to collapse
Now the software wont flash and there seems to be a hardware issue (my screen flickers) and it didnt last night.
Update: This device is fixed except for wifi wont initialize but this can help other users. Please lock this thread and hope it helps other people in unbricking! I love XDA and its community!

Update: This device is fixed except for wifi wont initialize but this can help other users
Click to expand...
Click to collapse
What does you'Ve done? Maybe other users have teh same issue and there are happy, if they can found a way to reanimate the Tab?

Mad07 said:
What does you'Ve done? Maybe other users have teh same issue and there are happy, if they can found a way to reanimate the Tab?
Click to expand...
Click to collapse
The Tablet has to be completely dead and then you can charge it to odin cause of the recovery booting ...... but draining the battery clears RAM and then i can get into download mode. Its still better than a 750 dollar paperweight just need to fix wifi. Its almost set up this way and takes longer to fix the device if you are kind of in a hurry. I was rooted but unfortunately have no safestrap so i could not back up my image It was in a bricked state and was corrected by troubleshooting android related problems and flashing in Odin. The only question besides the wifi problem is even though i flashed Stock firmware, my device shows up as Custom????? Any Ideas its not tripped i know that much.

biggiesmalls657 said:
The Tablet has to be completely dead and then you can charge it to odin cause of the recovery booting ...... but draining the battery clears RAM and then i can get into download mode. Its still better than a 750 dollar paperweight just need to fix wifi. Its almost set up this way and takes longer to fix the device if you are kind of in a hurry. I was rooted but unfortunately have no safestrap so i could not back up my image It was in a bricked state and was corrected by troubleshooting android related problems and flashing in Odin. The only question besides the wifi problem is even though i flashed Stock firmware, my device shows up as Custom????? Any Ideas its not tripped i know that much.
Click to expand...
Click to collapse
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.

Gatsrom said:
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.
Click to expand...
Click to collapse
Wifi and bluetooth and system status is custom and updating bricks and puts me back to letting it die.

Wifi and bluetooth and system status is custom and updating bricks
Click to expand...
Click to collapse
Where you can see, that Wifi and BT is custom ?
System status is also Custom on my tab ( TWRP was flashed )
At which point the update bricks? Near at the end > hiddenfile ext4 wrong ?
Which this error ( I've select the GBT - file, but the Tab was buyed in Austria > so I need the ATO ) I've triggered KNOX After download the correct FW-File, odin could flash successfully.
If you change temporary the Kernel for root, Wifi is no working , too...
updating bricks
Click to expand...
Click to collapse
If odin failed during flashing, press one time Reset in odin, dis-/ connect the USB cable from the TAB and you can continue with odin. During next flash, you received a lot of red text lines, that the progressbar indicator is not correct, but this one you can ignore. Urgent is, that odin said : PASSED at the end.
In you case, I would make direct after successfull flash -> boot into the EM Menu and initiate a factory reset

Mad07 said:
Where you can see, that Wifi and BT is custom ?
System status is also Custom on my tab ( TWRP was flashed )
At which point the update bricks? Near at the end > hiddenfile ext4 wrong ?
Which this error ( I've select the GBT - file, but the Tab was buyed in Austria > so I need the ATO ) I've triggered KNOX After download the correct FW-File, odin could flash successfully.
If you change temporary the Kernel for root, Wifi is no working , too...
If odin failed during flashing, press one time Reset in odin, dis-/ connect the USB cable from the TAB and you can continue with odin. During next flash, you received a lot of red text lines, that the progressbar indicator is not correct, but this one you can ignore. Urgent is, that odin said : PASSED at the end.
In you case, I would make direct after successfull flash -> boot into the EM Menu and initiate a factory reset
Click to expand...
Click to collapse
I had NB1 installed and it was working then i used Repair Assistant and it has recovery booting and the boot logo with Custom android. They wont cover it for insurance, i might as well just damage and pay the deductible. I have tried everything and it results in a brick.

From where is this image ND repair assistant ? The bootlogo is changed via root very easy. For that nobody needs a total ROM flash. It's only 1 zipfile.... Hopefully the repair assistant does not has make a recreate partitions....
let go out from the best case Which stock rom does you try to flash? The latest one?
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 1810991
Build date: Mon, 10 Nov 2014 07:03:29 +0000
Product Code: VZW
PDA: P905VVRUANK1
CSC: P905VVZWANK1
MODEM: P905VVRUANK1
I didn't still know at which area Odin failed to flash

Mad07 said:
From where is this image ND repair assistant ? The bootlogo is changed via root very easy. For that nobody needs a total ROM flash. It's only 1 zipfile.... Hopefully the repair assistant does not has make a recreate partitions....
let go out from the best case Which stock rom does you try to flash? The latest one?
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 1810991
Build date: Mon, 10 Nov 2014 07:03:29 +0000
Product Code: VZW
PDA: P905VVRUANK1
CSC: P905VVZWANK1
MODEM: P905VVRUANK1
I didn't still know at which area Odin failed to flash
Click to expand...
Click to collapse
Yes the latest build is what I flashed. I wonder if the kernel changed but right now NB1 makes it usable with no WiFi or bluetooth.

Which Rom does you mean exactly with NB1 ?
the only one, which I've found - which contains NB1 at the end is:
Model: SM-P905V
Model name: GALAXY NotePRO 12.2 LTE
Country: USA (Verizon)
Version: Android 4.4.2
Changelist: 617169
Build date: Thu, 06 Feb 2014 12:19:18 +0000
Product Code: VZW
PDA: P905VVRUANB1
CSC: P905VVZWANB1
MODEM: P905VVRUANB1
Click to expand...
Click to collapse
Why you don't try to flash the K1 Rom? [See above].
If I think about my Galaxy S3 LTE : I have the old Bootloader ( without Knox ) on the device -> if I flash the new System / Kernel without the new Bootloader, I'll have also a problem with a nonworking Wifi ...

Gatsrom said:
So the battery trick did reset it? Score! lol. I've actually had two friends have to do something similar with other android devices. So you flashed stock onto it (thank god) and now the only problem remaining is no wifi? I know we had a thread about no wifi for our specific device in the forums. Search for that. It seemed like people were able to fix it in that thread.
Click to expand...
Click to collapse
The software is flashed and notice the system sleeps and screen wont turn back on until i three finger salute. Boot Logo has no unlocked symbol but About phone displays Custom. Also Wifi/Bluetooth issue which I could not find. If i can fix the wifi and bluetooth i wont send into verizon. They should cover it, Odin mode displays 0x0.
Edit: Odin mode still displays SYSTEM STATUS: Custom even though I flashed the NB1 build. Wifi/Bluetooth still do not work. I have wiped data/ cache and rebooted the device. Towelroot didnt work previously but I will try with this build.

ok, first of all, go into the settings, developer and enable USB system debugging. Shut down the Tab, Hold The home key, volume down and Power. After that, the tab starts into the download mode, press volume + to continue. The screen changed. Connect the Tab with you running Odin ( check the task manager, that nothing from Kids is still running in the background. Select as PDA the K1 Firmware which was in the zip. Ending is tar.md5.
Check is Only Autogreboot and the F fuse(?) >>default settings are selected. Press Start and wait... In Odin you can following which Parton is now flashed. Hopefully Odin stopped with Passed and the Tab rebooted. If you've the wrong region rom, Odin failed at the hidden file ext4.

Mad07 said:
ok, first of all, go into the settings, developer and enable USB system debugging. Shut down the Tab, Hold The home key, volume down and Power. After that, the tab starts into the download mode, press volume + to continue. The screen changed. Connect the Tab with you running Odin ( check the task manager, that nothing from Kids is still running in the background. Select as PDA the K1 Firmware which was in the zip. Ending is tar.md5.
Check is Only Autogreboot and the F fuse(?) >>default settings are selected. Press Start and wait... In Odin you can following which Parton is now flashed. Hopefully Odin stopped with Passed and the Tab rebooted. If you've the wrong region rom, Odin failed at the hidden file ext4.
Click to expand...
Click to collapse
I have flashed it that way several times. The software flashing isn't the problem, its WiFi and Bluetooth jam and wiping data cache do not fix it. I have re downloaded the software and its a no go.

biggiesmalls657 said:
I have flashed it that way several times. The software flashing isn't the problem, its WiFi and Bluetooth jam and wiping data cache do not fix it. I have re downloaded the software and its a no go.
Click to expand...
Click to collapse
If Knox still triggered? Ill believe so. K1 is now the current FW?
Try after install TWRP , wipe normal and go into the adv. wipe settings to format / System and / Data / Cache etc..
Reflash K1 again.
How does it looks like Jam of Wifi / BT ? does you received a FC? only Interruption ?

Looking for ROMs for LG VS890/FX3

Hi, folks,
After many, many attempts, I finally was able to root my Verizon LG Enact/VS890/FX3, using NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, which I got from this forum about a week ago... for which I heartily thank Zero Sparks. Finally able to uninstall a lot of the crapware I didn't want, and to install several root-only apps which I did want.
The thing I'm having trouble with now, is finding custom ROMs for the phone. It's running KitKat, so it's not ancient, and if I can't use anything but the stock ROM, so be it. But I'm dying to try flashing Lollipop or even Marshmallow. It has to be a very specific ROM for that phone, because of the slide-out QWERTY keyboard... the wrong firmware wouldn't function properly. And there are a lot of bogus sites out there which want you to "complete a survey" or "sign up for one of these offers", but they never give you the download, it's just an endless circle of phishing sites... with lots of malware for my system, I'm sure. I'd much rather trust you folks on here, if you have anything.

I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.

UsualNoise said:
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
Click to expand...
Click to collapse
In my research, I could have sworn I came across a site that had the original "stock" LG software for download, but I can't find it now. The closest I come is this LG link that will give you the firmware -- and the VS890 is on their list: http://www.mylgphones.com/latest-lg-phones-firmware-update-model-version-date
I don't know if that might restore your stock recovery, at least. But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.

Mr2nSmith said:
But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Click to expand...
Click to collapse
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).

UsualNoise said:
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
Click to expand...
Click to collapse
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.

Mr2nSmith said:
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Click to expand...
Click to collapse
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.

UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
Good for you! See, you don't give up, and you get a happy ending.

It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .

Androide3 said:
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Click to expand...
Click to collapse
Wish I could help you, but I never could do that on mine... had to use a sideload tool to do it from my PC. BUT -- I have two suggestions for you. First, download and install the KingRoot tool, to root the phone... it's called NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, and I think there is a link earlier in this thread which you can use to find and download it. You'll have to install it manually, then run it. (Don't bother with the "Purify" portion, you don't need that for now.) Your phone will now be rooted, by the only method that ever worked for me. Next, go to the Play Store, and download an app called "Quick Reboot", from Phong IT. This is a root-only app (hence the need to root, first) which includes a "Recovery" option. Try that out, and see what happens.

[HELP THREAD] Ask any questions [NOOB FRIENDLY]

Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing

Going back versions?
Ok, I'm pretty good on flashing ROMs and using TWRP. But I was thinking of trying a 5.1.1 Rom, I am rooted running just the stock Rom 6.01 currently. I have a SM-N900W8, so I assume I'll likely have to get the modem too depending on what ROM I choose.
My only concern is going backward, I don't know what kernel I might need to flash? Should be able to keep the answer simplistic in explanation, I just need the warnings and a basic checklist of what to do when going backward. And if I can complete this using just TWRP or whether I need to flash something with Odin or whether Flashfire might work.
Thanks in advance. Sorry I'm not a guy who has time to learn code. I try to donate if I'm going to use someone's work though. Just nice to have my phone run fast and smooth and be able to tinker...

Jetmerritt said:
Ok, I'm pretty good on flashing ROMs and using TWRP. But I was thinking of trying a 5.1.1 Rom, I am rooted running just the stock Rom 6.01 currently. I have a SM-N900W8, so I assume I'll likely have to get the modem too depending on what ROM I choose.
My only concern is going backward, I don't know what kernel I might need to flash? Should be able to keep the answer simplistic in explanation, I just need the warnings and a basic checklist of what to do when going backward. And if I can complete this using just TWRP or whether I need to flash something with Odin or whether Flashfire might work.
Thanks in advance. Sorry I'm not a guy who has time to learn code. I try to donate if I'm going to use someone's work though. Just nice to have my phone run fast and smooth and be able to tinker...
Click to expand...
Click to collapse
Hi
What do you mean by 'going backward'? Do you wanna downgrade your device from Marshmallow to Lollipop? If yes, refer to this thread.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing

Ok, if going back to a earlier version of Android, then flash the factory full ROM of that version through Odin, then flash custom ROM of same version. Got it, thanks. Sounds like the easiest way.

Jetmerritt said:
Ok, if going back to a earlier version of Android, then flash the factory full ROM of that version through Odin, then flash custom ROM of same version. Got it, thanks. Sounds like the easiest way.
Click to expand...
Click to collapse
Yeah. Welcome!
Regards,
PoseidonKing

Stuck N915G
Am using a N915G , it was rooted with CW recovery , since yesterday it would go in restart loop , so i went into recovery and did a reset , still the loop would not go , so i took into a service center they tries kies and it would intall lollipop but half way through it will show " erasing " and then go back to boot loop , now at this point when i re checked the phone there is no CW recovery , so i tried Odin with Marshmallow to flash the system , it shows PASS but during installation " System updating .. erasing " then goes back to reboot so i flashed new set of Pit files , but still the phone stays in boot loop , vibrates then goes off to loop , what am i doing wrong

Won't power on after normal power off.
Hi,
i mean; when i turn of the phone with normal shutdown menu, device power off normally.
But when i attempt to turn on device again, it won't turn on. nothing happens when i press or hold the power button.
only the way to turn on again, "plug a charge cable or usb cable"
after it detects the charge, and shows charging. after then i can turn on the device normal.
but, not possible to turn on without plug the cable once.
so; what can be my device's problem. (there is no another problem) except fast battery drain.
my opinion; humidity damage? or something like that.?
can any oxidation causes this problem?
please reply for help.
thanks.

Bump
Sent from my Motorola XT1080 using XDA Labs

Hello, I rooted my Samsung Galaxy Note Edge (N915T) Tmobile way back in 2014, I have since then forgot how to root again. I know that my phone is still rooted because I have SU.
My phone specs right now:
Bootloader: N915TUVU1ANJL
OS Version: KitKat 4.4.4
CPU: ARMv7-A (armeabi-v7a)
Kernel version: 3.10.0-2990579
I saw a post here in XDA about new Custom ROM (7.1.2 AOKP Nougat) and I would like to install custom ROM, and reading the instructions it states that it requires Bootloader 6.0.1 and Modem. I have no idea how to install bootloader and modem up to 6.0.1 on my phone. Kindly please guide me how to identify my current bootloader and how to upgrade up to 6.0.1. Thanks!

Hello,
I am using Odin v3.12.7 and I tried to select (twrp-3.0.2-0-tbltetmo.img) from Odin, but is not selectable because it does not have (.md5) or (.tar), where can I find a TWRP in those file formats?

What custom rom can i flush with my note edge sc-01g docomo japan,

Corrupt microsdcard and otg devices
Hi,
This is about my note edge N915G and what will follow has strangely happened with every kind of rom for the device stock rooted, aokp, customized stock, and slimroms.
What happens is
scard shows as corrupted after busybox/magisk7viper mods I mean the card is fine when I install busy box and magical and viper then in stall viper drivers and it is still good but when I reboot to activate the viper mods my card shows as corruption. I another thing that happens is when the card shows as corrupt, I I can try another card and still shows corrupt and strangely even the devices I connect through otg all show as corrupt. Ii think it is busy box which is needed for viper that does it, but am not sure.
Another guess is that maybe some embedded file on the phone has been deleted or corrupted and that is causing me the trouble. I have installed the Enhanced rom this evening and had set it up with closed root and magical. I it was all fine. I then I installed busy box using smart install and after that opened viper fx 2.5 and viper xhi=fi and each prompted to install drivers and they installed successfully and advised a reboot. It is after reboot that I opened my music player and found no songs which was be aise it is showing my card as corrupt. I strangely even if I reverse the process and uninstall viper drivers then viper apps and finally busybox it still does not change the status of the card. It is either that I install the rom again dirty or restore a system backup that was made while there were no add ons.
I would really appreciate if anyone can help figure this out as I do have the workaround of restoring system but it is tedious as I have to install all apps etc.
I would like to reiterate that this is not the kind of issue associated with Samsung phones in general where they are said to kill microsdcards. This is not the case and the card works flawlessly in a different phone which I did to check. My laptop too has no issues with same card it is a Samsung evo 64 gb card I'm using. Maybe they key is that even other as cards whether I put them in the card slot or in a card reader for otg it shows any card I use as corrupt and even my otg drives show up as corrupt. I think it is something I have never seen happening yet.
Thanks for reading this and for your suggestions and advice. I will look forward to your thoughts and inputs, knowledge and experience.
Regards
Centaur31

anybody install android 7 on note edge ?
please describe the method
i have been tried a lot to root the device but fail with error
in my phone in the developer setting there is no OEM unlock option
in all guide mentioned to this option
my phone model is: N915F
if possible please help me

At&t Samsung Note Edge N915A 6.0.1
Hi I'm a noob. Last phone I "jailbroke" was a IPhone 3gs. Could you link me in the right direction to root my Samsung note edge from At&t 6.0.1 a list of procedures would be great, also a list of downloads. Anything & Everything I need on my phone or my Laptop to complete the process. All input would be appreciated. I just paid a large chunk of $ to Samsung to have my screen replaced and I am the original owner of my device which I paid a lot of money for in 2014, so I would hate to brick my device. Thanks

Hello
I have Samsung Galaxy Note edge n915F and i want to to flash n915g stock rom in it
is it possible. .?
Or if possible any problem will occur. .?
Thanx in advance

Database Info

welcome