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.
Related
Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) !
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices (Galaxy S1, Galaxy Tab 7", Galaxy S2, Galaxy Note, Galaxy Nexus, Galaxy S3, and many more) and has clocked over 13 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Why isn't this just called CF-Root
The traditional CF-Root's included a custom recovery (CWM, TWRP, etc) and were meant for devices that had a single kernel/recovery combination. CF-Auto-Root doesn't include a custom recovery and is meant for devices that have kernel and recovery separate (so you can manually install any custom recovery you wish). The Auto part comes from the fact that a large part of the process is automated (though it constantly needs adjusting)
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
ODIN Installation (detailed)
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download
SGH-I337M: CF-Auto-Root-jfltecan-jfltevl-sghi337m.zip
Other models
International Samsung Exynos GT-I9500: http://forum.xda-developers.com/showthread.php?t=2292615
International Qualcomm Snapdragon GT-I9505: http://forum.xda-developers.com/showthread.php?t=2219803
Sprint: http://forum.xda-developers.com/showthread.php?t=2291827
T-Mobile: http://forum.xda-developers.com/showthread.php?t=2294005
AT&T: Bootloader locked, do not use CF-Auto-Root on it
VZW: Bootloader locked, do not use CF-Auto-Root on it
History
2013.05.24: SuperSU v1.30
Worked wonderfully!
Sent from my SGH-I337M using xda app-developers app
Awesome work, any possibility of an ATT USA version? Just got my 32Gb Black Mist delivered today by UPS!
Exellent.
Perfect like always!!! UR the best
very nice thaks a lot i had my s4 almost 3 weeks i was wiating your post finly i got it today . love it so easy root it thanks again.
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .
one question, is this really easier than just installing samsung drivers, checking debug and pressing run.bat on motochopper??? if anybody thinks thats hard, maybe they need a motorola razr. I dont want to offend you chain because i love your work, but i dont understand why you invested time into this
---------- Post added at 02:08 AM ---------- Previous post was at 02:07 AM ----------
wasimahmad said:
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .
Click to expand...
Click to collapse
Check this thread:
http://forum.xda-developers.com/showthread.php?p=41845225#post41845225
highaltitude said:
Awesome work, any possibility of an ATT USA version? Just got my 32Gb Black Mist delivered today by UPS!
Click to expand...
Click to collapse
ATT version has a locked bootloader, and you already need root to apply a hack to flash and run custom firmwares on it. As such, CFAR wouldn't be much use on it. It may be so at a later stage (amongst other things that would probably require a different bootloader unlock method than is used now) that you need an old ATT firmware to be even to unlock, then need something like CFAR to root a newer firmware, but for now that seems unlikely. And even if that were the case, it would still be confusing and people would try to use CFAR on their locked device which could result in brickage (worst case).
wasimahmad said:
very nice thaks a lot i had my s4 almost 3 weeks i was wiating your post finly i got it today . love it so easy root it thanks again.
just i need to ask wen rooted s4 in stats says now custom not official if i flash Triangle Away it will come agian official in stats or not? thanks adv- .
Click to expand...
Click to collapse
Triangle Away can work to reset "flash counter" and "binary status" (though the current version sometimes the modification doesn't stick - update coming). As I've explained a hundred times probably but nobody listens and everybody keeps repeating the wrong information: the custom system status is scanned by the Samsung firmware and set in the bootloader. One of two truly reliable way to keep that status set to official is to unroot and flash a stock firmware. There are some other workarounds (like some of the advanced options in Triangle Away) that will keep that value official *most* of the time, but nothing 100% foolproof longterm - no matter what others tell you. The other reliable way is to first have that value reset to official using a forementioned method, than flash a modified system that has all the detection stuff patched out and/or removed.
polish_pat said:
one question, is this really easier than just installing samsung drivers, checking debug and pressing run.bat on motochopper??? if anybody thinks thats hard, maybe they need a motorola razr. I dont want to offend you chain because i love your work, but i dont understand why you invested time into this
Click to expand...
Click to collapse
Exploit vs firmware root. Think about it for a while.
Was definitely hoping and waiting that you release this, awesome work as always!!!
Thank you for CF Auto Root! Any chance there will be support for the SGH-I337M in Mobile Odin?
Sent from my SGH-I337M using xda app-developers app
hi
MR Chainfire bundle of thanks for reply your triangle away works flawlessly brought my phone s4 from custom to official and zero binary. i selected both options: auto reset at boot and allowed tracker to run. Then i restarted the phone and it says counter zero and status official
thanks for all the help and your hard work.
---------- Post added at 05:15 AM ---------- Previous post was at 04:57 AM ----------
is that mobile odin pro dos sport s4 yet or not thanks adv. ?
Finally! Rooting Right Away, the only method I trust in and from the best developer out there. Thanks man!
:thumbup:
Sent from my SGH-I337M using xda premium
When you say Canadian models, does that include the Wind variants too.. or is that a different? Would I have to use the T-Mobile version for the Wind variant?
Any chance to support triangle away? I tried the one linked in OP and it didn't work
I see that you said it doesn't stick, is that the same as it just never working? It worked great on my S3 but on my S4 it just reboots and does nothing
10cheesecakes said:
When you say Canadian models, does that include the Wind variants too.. or is that a different? Would I have to use the T-Mobile version for the Wind variant?
Click to expand...
Click to collapse
Yes that includes Wind, all Canadian variants. Do not use the t-mobile one.
just curious you did not mention the i337m bootloader is locked. Therefore after we flash this through odin are we able to flash custom roms. Just curious. thanks
casualt said:
just curious you did not mention the i337m bootloader is locked. Therefore after we flash this through odin are we able to flash custom roms. Just curious. thanks
Click to expand...
Click to collapse
Yes. I would make a nandroid first off course.
Sent from my SGH-I317M using Tapatalk 2
I think canadian models don't have bootlock
Sent from my SGH-I337M using xda premium
Now just mobile Odin and we're on top of the hill....
JKAY DELUXE [I9300 JB 4.1.2]
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!
Need a link to the files you mentioned.
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin
I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!
sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...
Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.
Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:
Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:
Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you
Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?
VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.
Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk
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.
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
I did as you said, but I'm still on 4.1.2:crying:
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.
Hi guys,
Not started a thread on XDA for years but I really am stumped.
I have claimed my girlfriends s6 (SM-G920F) after she upgraded and intended to root it and maybe try a few Oreo ROMs etc. After investigation I saw that (I think this is right) I don't need to OEM unlock this version of the device and rooting via Odin is the best way to do it. BTW if I do need to OEM unlock then that might be the solution to my issue, so if some one could clarify that'd be great.
So a week ago I downloaded Odin and also my old favourite CF-AutoRoot after putting in the device details. The package was generated, I unzipped and put it in a folder in my desktop
After putting the device in download mode I run Odin as administrator and plug it in. The device is recognised and I get the blue box to show this.
I then click the AP box and select the image file and click start, everything runs as expected to this point and I get PASS displayed in the info bar. On the phone the progress bar looks like it has not completed and I can see a small portion still to run. On the first try I left phone like this waiting for it reboot for over an hour. I was expecting 5he device to reboot and get the android with the red exclamation point. At this point I restarted manually and saw during the boot process an error message saying Recovery not SE Enforcing in red.
I have read a few posts saying this can be caused by the wrong image being used, so I downloaded the Auto root package again and made sure that it was all correct, but the same thing occurred.
I have been looking and reading for the last week to find a solution, but I'm still in the same position. Can anyone help or point me in the right direction?
If you need any more info let me know.
Thanks in advance
Jon
im in exacltly the same boat pal. was running nanorom on my rooted s6, but had no vr capability and just got some galaxy gear goggles. tried to reflash arter97 kernal and lost my whole setup. ive been in and out of hard brick for last 24hrs and am back now to where you are, i can access download and recoveries via three button combo, but any packages i flash with odin just fail out right.
ive been here before though and usually get out once i find the right stock rom and csc's for my version. iof i find anything ill come back and share it with you pal.
Cheers mate, it's really frustrating. I'll keep looking too and post back if I have any success.
Hi guys, this thread hasn't been responded to so I thought I'd just replied to it to give it a little bump up. I'd much appreciate it if anybody could help me out here.
Thanks again,
Jon
copernicus666 said:
Hi guys, this thread hasn't been responded to so I thought I'd just replied to it to give it a little bump up. I'd much appreciate it if anybody could help me out here.
Thanks again,
Jon
Click to expand...
Click to collapse
Just try bro to reflash full stock rom again by odin and after flash it , reflash cf-autoroot again
also , can you provide more information about your android version and your csc stock rom ?
what a f**k about!!!!
Right then Jon,
sorry for my delay but not the greatest at reponding to things at the best of times, but with my own s6 in a right old state, and a 7y.o and 4 month old in the house, my pc time is limited.
anyways, im guessing you're a bit like me, and you've had your fair share of flashing roms and roots since the days of old! (Galaxy thru and thru for me s 1,3,4,6, plus tabs and watches).
this s6 gt-920f is a completely different kettle of fish mate. where you're at at the minute, if your still stuck in bootloop with no recovery, your gonna want to find twrp recovery, as you know mate, google will be your guide. you flash this just like a rom or the old cwm, download a zip, bang it in ap/pda in odin and let it flash. KEY NOTE IS MAKE SURE ODIN HAS ~"AUTO-REBOOT"~ UNTICKED, UNCHECKED, NO MARK IN THE BOX. THIS IS KEY TO THE RESTORATION PROCESS GOING FORWARD. Once odin shows that the file has flashed and passed, get ready to perform a three button power reset, Home button, Vol DOWN and Power for 8 seconds. when your pc makes the badong sound and the screen goes off, IMMEDIATELY SWITCH TO Vol UP, Home and Power, thus straight into recovery mode, AND WAIT.
You should see the blue and silver TWRP splash screen and then the recovery options. Firstly, wipe and format everything, dalvik, caches and perform a factory reset. twrp should ask you to type yes to confirm, do it, there's nothing there yet any ways. if you get any issues about cant mount data or some jazz, DONT PANIC, use twrp to reformat the partition to ext4, your pc should ping to show reconnection to the phone.
Now whilst still in twrp, nav to the reset options and reboot into download mode. if all has go well, the scren should have the regular greenish odin screen but without all the samsung odin mode in at the top. odin should show the phone as a connected device, you should be able to access your memory card from your pc to transfer rom zips etc and get the phone back up the way you are used to.
if on the other hand you want to get back to vanila stock style android, with the expense of a tonload of bloatware and crapps, you're gonna wanna take a goggle at stuff like "G920F Repair Firmware X.X UK YYY) , Where X.X is 5.1, 6.1, 7.1, depending on the original android version your brick was on, and YYY is your carrier or network operator, off the top of my head they are VOD, TMO, O2U, H3G.
AGAIN A KEY POINT IF YOUR GOING THIS ROUTE, THESE FILES ARE MADE FOR INDIVIDUAL MODELS OF S6 (THERES ABOUT 12 MODEL NUMBERS -YOURS IS AND ALWAYS WILL BE SM-G920F - SO DO NOT EVER STRAY FROM THAT NUMBER!!!! ) THAT MEANS YOU NEED TO BE FINDING FILES LIKE "G920XXU5EXUE 4 files repair firmwares", THESE ARE YOUR SAVIOUR. GET THE ONE THAT MATCHES YOUR PHONE AND CARRIER OR ONE THAT IS AS NEAR AS DAMMIT, AND AGAIN PLEASE MAKE SURE FOR THE LOVE OF YOUR PHONE THAT YOU ONLY GET FILES MARKED G920, ANYTHING ELSE WILL RESULT IN VERY SERIOUS ERRORS.
YOUR ALSO GOING TO NEED SOMETHING CALLED A PIT FILE, EASY TO FIND, LOOK FOR " S6 ZEROFLTE HIDDEN IMG FILE" IN GOOGLE.
USE OUR OLD BUDDY ODIN TO FLASH THE FOUR FILES YOU GOT FROM THE REPAIR FIRMWARE ZIP, WHICH ARE USUALLY LABEL AP, BL, CP AND CSC.. NOW TAP THE PIT TAB IN ODIN (IGNORE THE WARNING) AND NAVIGATE TO THE HIDDEN.IMG FILE YOU GOT AND BANG IT HERE. ON THE OPTIONS TAB YOU WANT TO TICK AUTO REBOOT, REPARTITION, and NAND ERASE ALL. i know, i know, you probably never use it out of some shear panic but right now its kosher.
start the flash and take a break. like a big break. the process is gonna wipe the phone in totalilty, rewrite every bit of code and software and reload like new after about forty minutes.
now, if it doesnt, there are a few things we can look at but am gonna leave it here and hope you can make some use of the ramblings of a lost man. my 6 is currently in an inverted touch bug where if i touch one side of the screen, the opposite side responds so its a proper nightmare, typing anything means that a becomes l, s becomes k etc. thisis down to me drunk flashing the wrong roms for and s6 edge, g925f, hence all my warnings earlier. anyways, i need a reefer and a scran after all this, God, allah, buddah i hope it helps someone.
shiko2007 said:
Just try bro to reflash full stock rom again by odin and after flash it , reflash cf-autoroot again
also , can you provide more information about your android version and your csc stock rom ?
Click to expand...
Click to collapse
Hi, thanks for replying.
I'm on the original stock, I've not flashed any thing just yet. To be honest, I'm not sure it'd work.
The android version is 7.0 and the build is NRD90M.G920FXXS5EQH6
Be glad if you have any advise.
Thanks
copernicus666 said:
Hi, thanks for replying.
I'm on the original stock, I've not flashed any thing just yet. To be honest, I'm not sure it'd work.
The android version is 7.0 and the build is NRD90M.G920FXXS5EQH6
Be glad if you have any advise.
Thanks
Click to expand...
Click to collapse
if your not root yet just download latest your carrier/country firmware
from sammobile
and flash it by odin
but you are probably trip knox so you must root
so the steps you should do :
1-download your carrier/country firmware from sammobile
2-flash it by odin
3-flash cf-auto root to pass bootloop
or
download twrp recovery of g920f and flash it by odin to replace stock recovery then after flash it ,wipe delvik cash then flash su binary
DagsyMc said:
Right then Jon,
sorry for my delay but not the greatest at reponding to things at the best of times, but with my own s6 in a right old state, and a 7y.o and 4 month old in the house, my pc time is limited.
anyways, im guessing you're a bit like me, and you've had your fair share of flashing roms and roots since the days of old! (Galaxy thru and thru for me s 1,3,4,6, plus tabs and watches).
this s6 gt-920f is a completely different kettle of fish mate. where you're at at the minute, if your still stuck in bootloop with no recovery, your gonna want to find twrp recovery, as you know mate, google will be your guide. you flash this just like a rom or the old cwm, download a zip, bang it in ap/pda in odin and let it flash. KEY NOTE IS MAKE SURE ODIN HAS ~"AUTO-REBOOT"~ UNTICKED, UNCHECKED, NO MARK IN THE BOX. THIS IS KEY TO THE RESTORATION PROCESS GOING FORWARD. Once odin shows that the file has flashed and passed, get ready to perform a three button power reset, Home button, Vol DOWN and Power for 8 seconds. when your pc makes the badong sound and the screen goes off, IMMEDIATELY SWITCH TO Vol UP, Home and Power, thus straight into recovery mode, AND WAIT.
You should see the blue and silver TWRP splash screen and then the recovery options. Firstly, wipe and format everything, dalvik, caches and perform a factory reset. twrp should ask you to type yes to confirm, do it, there's nothing there yet any ways. if you get any issues about cant mount data or some jazz, DONT PANIC, use twrp to reformat the partition to ext4, your pc should ping to show reconnection to the phone.
Now whilst still in twrp, nav to the reset options and reboot into download mode. if all has go well, the scren should have the regular greenish odin screen but without all the samsung odin mode in at the top. odin should show the phone as a connected device, you should be able to access your memory card from your pc to transfer rom zips etc and get the phone back up the way you are used to.
if on the other hand you want to get back to vanila stock style android, with the expense of a tonload of bloatware and crapps, you're gonna wanna take a goggle at stuff like "G920F Repair Firmware X.X UK YYY) , Where X.X is 5.1, 6.1, 7.1, depending on the original android version your brick was on, and YYY is your carrier or network operator, off the top of my head they are VOD, TMO, O2U, H3G.
AGAIN A KEY POINT IF YOUR GOING THIS ROUTE, THESE FILES ARE MADE FOR INDIVIDUAL MODELS OF S6 (THERES ABOUT 12 MODEL NUMBERS -YOURS IS AND ALWAYS WILL BE SM-G920F - SO DO NOT EVER STRAY FROM THAT NUMBER!!!! ) THAT MEANS YOU NEED TO BE FINDING FILES LIKE "G920XXU5EXUE 4 files repair firmwares", THESE ARE YOUR SAVIOUR. GET THE ONE THAT MATCHES YOUR PHONE AND CARRIER OR ONE THAT IS AS NEAR AS DAMMIT, AND AGAIN PLEASE MAKE SURE FOR THE LOVE OF YOUR PHONE THAT YOU ONLY GET FILES MARKED G920, ANYTHING ELSE WILL RESULT IN VERY SERIOUS ERRORS.
YOUR ALSO GOING TO NEED SOMETHING CALLED A PIT FILE, EASY TO FIND, LOOK FOR " S6 ZEROFLTE HIDDEN IMG FILE" IN GOOGLE.
USE OUR OLD BUDDY ODIN TO FLASH THE FOUR FILES YOU GOT FROM THE REPAIR FIRMWARE ZIP, WHICH ARE USUALLY LABEL AP, BL, CP AND CSC.. NOW TAP THE PIT TAB IN ODIN (IGNORE THE WARNING) AND NAVIGATE TO THE HIDDEN.IMG FILE YOU GOT AND BANG IT HERE. ON THE OPTIONS TAB YOU WANT TO TICK AUTO REBOOT, REPARTITION, and NAND ERASE ALL. i know, i know, you probably never use it out of some shear panic but right now its kosher.
start the flash and take a break. like a big break. the process is gonna wipe the phone in totalilty, rewrite every bit of code and software and reload like new after about forty minutes.
now, if it doesnt, there are a few things we can look at but am gonna leave it here and hope you can make some use of the ramblings of a lost man. my 6 is currently in an inverted touch bug where if i touch one side of the screen, the opposite side responds so its a proper nightmare, typing anything means that a becomes l, s becomes k etc. thisis down to me drunk flashing the wrong roms for and s6 edge, g925f, hence all my warnings earlier. anyways, i need a reefer and a scran after all this, God, allah, buddah i hope it helps someone.
Click to expand...
Click to collapse
Legendary post! Cheers mate you just made my morning. I knew the XDA guys would pull through.
I'm on my way to work, but I'll give it a crack later.
Cheers bud - Kudos