Database Info

upgrading to custom ROM/going back to STOCK ROM/

After several hours on the internet I finally found the solution to upgrading to a custom rom/and how to install the stock firmware even after my device was bricked. I downloaded all the necessary tar.md5 files, and unlocked/rooted my phone. The only custom rom I have not been able to successfully use is cyanogenmod. Although I'm sure I just need to find the most current version that has the bugs worked out. I have a verizon Galaxy S III, but I have straight talk service. I have successfully installed Carbon, and Liquid Jellybean. Liquid jelly bean has a ton of options, and my camera actually worked. With carbon it did not. Although I did save a backup of my phone to my SD card I was not able to retrieve my apps. and contacts on the new operating systems. I'm sure with further exploration I can find a custom rom, and have everything I need. I have only been doing this for two days now. While my device was bricked I spent countless hours searching the internet, and there was only one detail that kept me from being successful sooner. I read in someones post that keis air doesnt work well with ODIN. not true in my case I have version 3.07. I found a downloadable version of keis and put it on my computer. I went to tools and selected upgrade firmware/initilization. This enabled me to install the stock firmware/and unbrick my device, but not after following all the wrong ways to fix it.I made sure to look for my model, carrier, and device. I still have no idea how people had so many different variables that supposedly worked for them. download ODIN 3.07, all the neccessary files, Kies air ,and you will be successful. the link to root/install custom recovery is on androidable. Since I am a new user to this site I am not able to post outside links. how convenient.

Root on PD2 6.0.1 Sprint S6 Edge/TWRP 3.0.2-1.

Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!

Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.

Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?

baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.

Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.

baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.

Would these root methods trip knox?

chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes

Thanks.

Working for g920v 6.0.1?

freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man

How to upgrade & root Note 10.1 N8013, running stock 4.1.2?

Hello all! OK, I have a Samsung Galaxy Note 10.1 (GT-N8013) that I'm still using and love, still running stock everything (Android 4.1.2, Build JZO54K.N8013UEUCMA3). Ideally, I'd like to upgrade to 4.4.2 and root it.
I checked the "Software Update" link on the device (in Settings), and sure enough, it says that I have I have an update downloaded...I'm thinking that it's an update to 4.4.2 that was pushed out to this device some time ago, but I'm not sure...I'm worried that it's some sort of "Samsung-software-only" update or something similarly useless that I may like less than what I have. So I have several questions:
1) Has anyone else experienced this before who can say what this update most likely is? If it's not 4.4.2, what is it?
2) I want to root this device, but from the different forums I've been reading, it appears that it's easier to root 4.1.2; rooting 4.4.2 seems to have met with mixed success, and that makes me nervous. But if I root, I won't be able to do the software update (and I don't want to deal with the custom 4.4.2 roms out there unless I have to, as the process seems very involved).
Does anyone have some insight or advice? Am I wrong about the difficulty involved in rooting stock 4.4.2? Thanks in advance for all your input!

4.1.2 is the last release for N8013 .
Custom Roms have 4.4.2 .
Question is why do you want to root ?

JJEgan said:
4.1.2 is the last release for N8013 .
Custom Roms have 4.4.2 .
Question is why do you want to root ?
Click to expand...
Click to collapse
Hello JJegan...thanks for responding to me!
I successfully rooted my phone (a Samsung Galaxy S4) some time ago, and I love it...rooting gives me more finely-grained control over my device, particularly since a lot of apps ask for (in my opinion) rather intrusive permissions (e.g., why should a word-processing app want to know my location?). I have an app on my phone that monitors permissions requested and gives me the option to allow or deny access; I feel better having that and I just wanted to add that to my tablet.
If you're saying that 4.1.2 is the last release (that's what my tablet came with), then what is this software update the tablet is referring to? Also: I have noticed a few custom ROMs available for the 8013, but a lot of them are quite involved and require some unsettling jerry-rigging (e.g., after installation you must disable the phone portion of the ROM because it is added in by default, then you must install a Wi-Fi fix afterward that some users have reported does not always work, etc.)...so I'm worried about that option. But even if I find a custom 4.4.2 ROM that works great, would I be able to root after installing it?
Thanks!

But even if I find a custom 4.4.2 ROM that works great, would I be able to root after installing it?
YES via SuperSu

JJEgan said:
But even if I find a custom 4.4.2 ROM that works great, would I be able to root after installing it?
YES via SuperSu
Click to expand...
Click to collapse
I have SuperSU on my rooted phone: correct me if I'm wrong, but SuperSU only allows you to manage superuser access for your apps, right? I don't think that app itself can give you root. I'm thinking I'll have to use the second of two methods mentioned in this post, but there have been conflicting reports of whether this works on an N8013 running 4.4.2.
Oh, and for anyone else who might be researching this thread with similar questions in the future: I managed to reach someone in Samsung customer support (wow!): If you have the stock Android 4.1.2 on your Galaxy Note 10.1 GT-N8013, the software update that the machine may say is available to you is an update to 4.2.2 and that is "the most recent update" (read: last one) provided for this model. You'll have to find a custom ROM to get it to 4.4.2...very disappointed in that!

Long time since i actually rooted . As i understand the supersu zip flashed through TWRP recovery will root your phone .
https://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
4.1.2 is the last listed release from Samsung .for N8013 .
N8010 is up to 4.4.2 as stock rom .

D801 TWRP Issue - Bottom portion of touch screen doesn't respond

tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!

S5 root help

I bought the S5 when it first came out and subsequently used towelroot, as soon as it was available. It's been great for customization and extended functionality through the years. Now, however, i have slowly been experiencing more and more issues with this current setup...i.e. some functions have stopped working and many apps no longer work with the kitkat andoid version. Anyway, I am looking for a way to upgrade to marshmallow, or even lollipop, to be able to use apps...and hopefully some ui functionality returns with a reset during the process.
Warning: I have never used odin or flashed roms or anything to that level but i am willing to learn with some good direction.
Current setup:
SM-G900V, Android 4.4.2, Kernal 3.4.0, Build KOT49H.G900VVRU1ANCG, eMMC 15****
If it matters, I also use SuperSU, Xposed.
Not sure what other info would be helpful to assist me, but feel free to ask.

Also lately it can get stuck in a boot loop when rebooting. I'm afraid one day i will be unable to get it to boot up. additionally, it was hit or miss on reboots previously, but now i am unable to get the phone to recognize the SD card. Maybe i should unroot and hard reset, then reroot. Any suggestions regarding that approach? I vaguely remember something about having to undo all the changes made before unrooting.
Edit: All works fine currently, but hit or miss on reboots.