Related
I'm so sorry if any of my questions are just basic. I'm so confused about rooting and installing a new rom.
I just switched to an Android phone from over 4 years of using an iPhone. I have found out that Rooting is not as easy as jailbreaking.
1. Is there a step by step guide that I can find to install Cleanrom 3.3 on my Note 2?
--- I'm confused because i thought rooting was installing a new version of a rom, but if I'm correct i have to root, then install a new rom and kernel?
2. Is there a way to back up my stock phone so that if I want to do a factory reset all i have to do is reboot to the saved stock version?
3.Is there anything that I should do before rooting and installing a new rom in case of mistakes?
THANKS FOR YOUR HELP FOR NEW ANDROID USER!
iiqwertyii said:
I'm so sorry if any of my questions are just basic. I'm so confused about rooting and installing a new rom.
I just switched to an Android phone from over 4 years of using an iPhone. I have found out that Rooting is not as easy as jailbreaking.
1. Is there a step by step guide that I can find to install Cleanrom 3.3 on my Note 2?
--- I'm confused because i thought rooting was installing a new version of a rom, but if I'm correct i have to root, then install a new rom and kernel?
2. Is there a way to back up my stock phone so that if I want to do a factory reset all i have to do is reboot to the saved stock version?
3.Is there anything that I should do before rooting and installing a new rom in case of mistakes?
THANKS FOR YOUR HELP FOR NEW ANDROID USER!
Click to expand...
Click to collapse
Jailbreaking and Rooting are not the same thing:
http://www.androidpit.com/jailbreak-android
http://android.appstorm.net/general/iphone-jailbreaking-vs-android-rooting/
Basic steps:
1. Root with Odin (using you computer and phone plugged into USB)
- Some info here and how to here (instructions and download needed on post 2):
http://forum.xda-developers.com/showthread.php?t=1980644
2. Flash a custom recovery:
- easy method: Go the Google play store and install "Goomanager" this app will install TWRP custom recovery.
3. flash you custom ROM (make sure it made for your phones model)
- Download your desired COMPATIBLE ROM
- Move ROM to your Note II
- Turn off phone and boot into recovery (holding Power+VolUp+Home, I think?)
- Click backup and backup you current ROM, just in case (this will back up your stock & rooted ROM)
- Once in recovery click install, navigate to where you placed the ROM on you device, choose you ROM and install
This is mostly from memory, so I still recommend you do some reading. Here is a good place to start:
http://forum.xda-developers.com/showthread.php?t=1987541
It's really not that hard you just have to take it step by step and make sure you follow instructions. Read, read, read.
Hope this helps you get started, and welcome to Android!
3.Is there anything that I should do before rooting and installing a new rom in case of mistakes?
THANKS FOR YOUR HELP FOR NEW ANDROID USER!
Click to expand...
Click to collapse
personally, i'm a huge advocate of a jig, which is essentially a little device that you can plug into your micro-usb of your phone that will force it into download mode.
Download mode is the mode you will need to be in to use Odin, which is the program you use to flash certain things that are not packaged to be flashed via recovery.
note that recovery and download more are not the same thing. recovery is volume up-home-power and download mode is volume down-home-power... they are two separate things.
why is a jig useful: in the rare event that you do something completely wrong like flash a rom that isn't for your phone and you can't get into recovery using the 3 button combo but the phone is showing signs of life... then insert the jig and BOOM instand download mode, you can get to stock with odin from there, re-root/install recovery and then flash your previously backed up rom and carry on merrily as if nothing happened.
it's like having a safety net.
a simple XDA search can teach you how to build one, or you can go on ebay and for like 3 bucks get one...you may not use it for a while but then one day the time will come when you're hooped and you remember you have your jig and it'll be the best 3 bucks + shipping you ever spent lol
Looked at ALL the referenced similar threads, and none applied to my device. So, with your permission, I would like to ask for information.
I bought a used, off-contract T-Mobile variant of Galaxy S3, SGH-T999. It IS SIM-unlocked, as I am using a Straight Talk-provided AT&T SIM without any problems. Also, it is rooted, as confirmed by Root Checker and running Terminal--I get the "#" prompt. SuperSU is installed and appears functional. However, neither CWM nor TWRP recovery programs are on the device.
How can I tell if my bootloader is unlocked? If it is not, what would you suggest to use to accomplish unlocking? I would like to be able to flash a custom ROM such as CyanogenMod.
Thank you for your help and patience.
Its not locked
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Many thanks to you both, Serio22 and Tonytien! I had no idea that the T999 had an unlocked bootloader; just another good reason to buy it vs. the AT&T variant.
I have read (MANY TIMES!!!) the procedure for using Odin to root the device and install a recovery program. There is one in particular on androidcentral forums (can't post the link just yet!) that uses GalaxyS3RootSprint.zip to root either the Verizon or the T-Mobile variants. The second step uses GalaxyS3RootSprint to flash CWM; then, a third step uses CWM-SuperSU-v0.87.zip to flash a super user program. Since my phone is already rooted and has a working SuperSU program, I wonder if I could use Odin just to flash CWM?
Have either of you ever used Flashify? That was mentioned in another thread on androidcentral as a way to flash with Odin or entering download mode.
I'm kind of spoiled: my last two Samsung smartphones have both had CyanogenMod already installed, with CWM, and I got used to entering recovery mode via the Restart menu.
Anyway, thanks again, and best retards to you both.
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Oh, one other question. My phone has stock T-Mobile Android 4.3, the "*MJC" software. I have read a number of cautions concerning the MJC software, and that one might not be able to flash CWM or custom ROM's to it. Might that be a problem for installing CWM?
Incidentally, Knox is installed on the phone, but NOT running.
stahlwird said:
Many thanks to you both, Serio22 and Tonytien! I had no idea that the T999 had an unlocked bootloader; just another good reason to buy it vs. the AT&T variant.
I have read (MANY TIMES!!!) the procedure for using Odin to root the device and install a recovery program. There is one in particular on androidcentral forums (can't post the link just yet!) that uses GalaxyS3RootSprint.zip to root either the Verizon or the T-Mobile variants. The second step uses GalaxyS3RootSprint to flash CWM; then, a third step uses CWM-SuperSU-v0.87.zip to flash a super user program. Since my phone is already rooted and has a working SuperSU program, I wonder if I could use Odin just to flash CWM?
Have either of you ever used Flashify? That was mentioned in another thread on androidcentral as a way to flash with Odin or entering download mode.
I'm kind of spoiled: my last two Samsung smartphones have both had CyanogenMod already installed, with CWM, and I got used to entering recovery mode via the Restart menu.
Anyway, thanks again, and best retards to you both.
Click to expand...
Click to collapse
You can flash CWM through Odin, but it'll take some repackaging (.img to .tar.md5) or you can search for one to download since CWM comes in .img form. Again, you could use ADB on a computer to install CWM in its .img form since your phone is already rooted. You could also just download TWRP or some other recovery that comes in .tar or .tar.md5 form, which will already be ready to flash in Odin. I haven't used Flashify, but some of the screenshots on the app listing show some kind of recovery install feature. I can't personally recommend it since I've never used it before.
stahlwird said:
Oh, one other question. My phone has stock T-Mobile Android 4.3, the "*MJC" software. I have read a number of cautions concerning the MJC software, and that one might not be able to flash CWM or custom ROM's to it. Might that be a problem for installing CWM?
Incidentally, Knox is installed on the phone, but NOT running.
Click to expand...
Click to collapse
The latest software version causes some weird things indirectly. I haven't noticed any issues with the latest CM12.1 nightlies, but you may run into issues when trying to flash a custom ROM in recovery. It seems the updater_script (a part of custom ROM zip files that tells the phone what to do when flashing in recovery) doesn't include the latest version in the line that determines if the ROM will work with the phone or not (a simple software version text comparison to make sure you won't brick your phone). This can be easily fixed since it's just a text file inside a custom ROM that can be easily modified. The software itself doesn't cause issues with system modification other than some interference with root (which, since you've told me your phone is already rooted, I assume you've figured it out). Keep in mind that the stock ROM could replace your custom recovery upon reboot (I think), which could be fixed by deleting the files 'install-recovery.sh' and 'recovery-from-boot.p' located in /system/etc/. If you're installing a custom ROM, you won't need to worry about that. Also, your Knox Warranty Bit will be tripped (your phone now definitely has a void warranty) but I'm sure you know since you're rooting and stuff. Sorry about the late response, let me know if you have any questions on anything I missed, I'm kind of jumping around with things that come to mind.
I have used flashify and do recommend it. Very easy to use and can select from different recoveries. MJC is not a problem as far as flashing recoveries or roms. Probably one of the only problem is as the poster above stated, but it may be fixed by now by developers
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Hope you two guys (Serio22 and tonytien) don't mind if I pick your brains a bit more. Flashing via phone download mode and Odin doesn't look too bad, but I keep reading all these posts about guys bricking their phones. I CAN'T do that--- this is my PHONE, not a PC I can play around with! Seems you have to have a version of Odin that matches your installed OS AND your particular phone variant, then the CWM version must match both of those. If anything doesn't match, it's brick city! I did finally find a site that lists the current version of Odin (3.07) for the T-Mobile SGH-T999 running the MJC version of 4.3 JellyBean, and it lists the matching version of CWM (6.0.1.2). So, using that site as a guide, I think I might get brave and try to flash CWM that way rather than use Flashify. But, thanks for your comments on it as well.
Far cry from flashing the next nightly on CM using CWM! There was usually a natural path of progression---CM 9.1 to 9.2, then to 10.0, 10.1, etc. There was never a need to jump around and risk bricking. AND, going into Recovery for CWM was a simple option in the Reboot menu, not having to hold down 3 keys and release one at just the right time. I lived thru two phones with CyanogenMod and ClockworkMod, and only went backwards once: I flashed a nightly that I didn't really like. It was a simple matter to go into CWM and restore from the previous Nandroid backup.
Anyway, thanks for your suggestions, help, encouragement, and your ears (eyes?).
tonytien said:
The T-Mobile version has an unlocked bootloader. Feel free to flash CWM or TWRP through Odin or by using ADB if you want to use that method.
Click to expand...
Click to collapse
Oh, one more thing I forgot to mention, and ask about.
When I boot my phone into download mode, the items on the screen are these:
Product name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secure Boot: Enable
Warranty Bit: 0
Bootloader RP Swrev: 1
Not sure how to interpret these, as I've not found anywhere they are defined, other than the presence of the "Warranty Bit" line indicates I'm on 4.3, JellyBean. I'm assuming the Status of Custom is because I'm rooted.
stahlwird said:
Oh, one more thing I forgot to mention, and ask about.
When I boot my phone into download mode, the items on the screen are these:
Product name: SGH-T999
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secure Boot: Enable
Warranty Bit: 0
Bootloader RP Swrev: 1
Not sure how to interpret these, as I've not found anywhere they are defined, other than the presence of the "Warranty Bit" line indicates I'm on 4.3, JellyBean. I'm assuming the Status of Custom is because I'm rooted.
Click to expand...
Click to collapse
Yes and yes. Warranty Bit was introduced in 4.3 bootloader
serio22 said:
Yes and yes. Warranty Bit was introduced in 4.3 bootloader
Click to expand...
Click to collapse
Well, successfully flashed CWM 6.0.1.2 non-touch to my phone (I think--more below). Used the Odin/TAR method, and it was painless.
When I boot into Recovery mode, the line at the top of the screen does say "ClockworkMod Recovery v6.0.1.2", but the rest of the options on that screen look just as they did before. Went to "Advanced" and chose "Show log", and I saw some lines that concern me, to wit:
Checking for extendedcommand
Skipping execution of extendedcommand. file not found...
Can't partition non-vfat: datamedia
Can't partition unsafe device: /dev/block/mmcblklpl
Can't format unknown volume: /emmc
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Then, when I run my X-plore File manager, I see NO ClockworkMod folder, either on my Internal or External SD cards. Do I really have it?
One last point: while looking around for the procedures to do this, I came across a video that showed using ROM Manager to load CWM. Even tho the Odin procedure seemed to work, I wonder...... Any opinions on that?
Thanks again for your reading this.
stahlwird said:
Well, successfully flashed CWM 6.0.1.2 non-touch to my phone (I think--more below). Used the Odin/TAR method, and it was painless.
When I boot into Recovery mode, the line at the top of the screen does say "ClockworkMod Recovery v6.0.1.2", but the rest of the options on that screen look just as they did before. Went to "Advanced" and chose "Show log", and I saw some lines that concern me, to wit:
Checking for extendedcommand
Skipping execution of extendedcommand. file not found...
Can't partition non-vfat: datamedia
Can't partition unsafe device: /dev/block/mmcblklpl
Can't format unknown volume: /emmc
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
Then, when I run my X-plore File manager, I see NO ClockworkMod folder, either on my Internal or External SD cards. Do I really have it?
One last point: while looking around for the procedures to do this, I came across a video that showed using ROM Manager to load CWM. Even tho the Odin procedure seemed to work, I wonder...... Any opinions on that?
Thanks again for your reading this.
Click to expand...
Click to collapse
Did you flash recovery and then reboot straight into recovery without it letting boot the system? If not, do so. You shouldn't need any app to boot recovery, but you can use one if you like. Just a preference
serio22 said:
Did you flash recovery and then reboot straight into recovery without it letting boot the system? If not, do so. You shouldn't need any app to boot recovery, but you can use one if you like. Just a preference
Click to expand...
Click to collapse
No. I checked the restart box in Odin, and it did restart the system normally into JB. Then, I shut down completely and did the 3-button boot into Recovery.
Got an update, however. Since I saw those entries in the log, I decided to try the ROM Manager flash of CWM. Downloaded ROM Manager from the Play Store, and started it. It said it needed to update the recovery, and I let it update to CWM v. 6.0.4.5, and everything looked good. Checked the log, and no entries for concern. BTW, it offered the "Touch" version of CWM, but I declined that, going with the old fashioned side-button version.
Got one other question, however. On my CyanogenMod phones, when I got into CWM, the backup option was for Nandroid backup. But, the version I have on this phone doesn't even mention that. Is that an add-on of some sort?
Thanks again for your help!
Best regards,
Stahlwird
stahlwird said:
No. I checked the restart box in Odin, and it did restart the system normally into JB. Then, I shut down completely and did the 3-button boot into Recovery.
Got an update, however. Since I saw those entries in the log, I decided to try the ROM Manager flash of CWM. Downloaded ROM Manager from the Play Store, and started it. It said it needed to update the recovery, and I let it update to CWM v. 6.0.4.5, and everything looked good. Checked the log, and no entries for concern. BTW, it offered the "Touch" version of CWM, but I declined that, going with the old fashioned side-button version.
Got one other question, however. On my CyanogenMod phones, when I got into CWM, the backup option was for Nandroid backup. But, the version I have on this phone doesn't even mention that. Is that an add-on of some sort?
Thanks again for your help!
Best regards,
Stahlwird
Click to expand...
Click to collapse
Not sure, I use twrp. Haven't used cwm in ages
Ok guys Ive tried every post I can find on getting TWRP on my phone. I have the latest Odin3 v3.10.6.exe, the latest TWRP, twrp-2.8.7.0-trltespr.img.tar and tried, openrecovery-twrp-2.8.5.0-trltespr.img.tar, I have followed the posts and pulled the usb, then the battery for 30 seconds. I have unchecked the auto reboot, left it checked, tried it in the AP and BL slots and I cant get a custom recovery to stick. Here is the stats on my phone, Im at my wits end with this any help or suggestions would be much grateful. Ive already bricked it with cf autoroot and reinstalled the stock rom. Im wondering if I shouldn't of let it auto activate? Does sprint have a kill mode now for TWRP?
Software Version, N910PVPU4COG5
HARDWARE VERSION N90P.O5
ANDROID VERSION 5.1.1
BASEBAND VERSION SAME AS SOFTWARE VERSION
KERNEL VERSION
3.10.40-530320
DPI!SWHE8820 #1
BUILD NUBMER
LMY47X.N910PVPU4COG5
SECURITY SOFTWARE VERSION
MDF V2.0 RELEASE 1
VPN V1.4 RELEASE 5.2
KNOX VERSION
KNOX 2.4.1
Johniex said:
...Im wondering if I shouldn't of let it auto activate?...
Click to expand...
Click to collapse
Yes, you should. Although I can't recall it specifically said, that's what I do. I use the OB7 bootloader still and the OB7 to OG5 tar flash, reboots without warning on initial boot. Using OG5 modem on OB7, the phone would ask for permission to reboot. Once that reboot is out of the way, proceed.
@tx_dbs_tx implied (not to put words in his mouth but IMO he implies as you theorize here) the same recently when he added to get a GPS lock prior to proceeding.
The other steps you mentioned should get it done. Latest Odin, default settings, wipe everything but extSdCard (backup keep sakes) and power down prior to Odin download are recommended as well. Also, remember to uncheck auto reboot for TWRP flash in Odin, pull USB and battery. Most importantly, boot into recovery to help it stick.
Sent from my SM-N910P using Tapatalk
TWRP Fails While Trying To Write
Hello to all. I am trying to install TWRP on My Sprint note 4 . I am on software version N910PVPS4DPE2 and the Baseband is the same. Android VErsion 6.0.1
I was trying to install TWRP 3.0.2-0. Odin sees the phone and tries to install, but I notice that upon the writing process it fails. I even tried to install TWRP 2.8.5.0. I think I read something that this version must be installed first before any newer versions. Now mind you I am not rooted as of yet. I want to get a backup of the original setup before I flash a new ROM.
Any and all suggestions are welcomed to help me.
Blessings and Thank You In Advance.
ulremember said:
.. I notice that upon the writing process it fails. I even tried to install TWRP 2.8.5.0. I think I read something that this version must be installed first before any newer versions. Now mind you I am not rooted as of yet. I want to get a backup of the original setup before I flash a new ROM.
Any and all suggestions are welcomed to help me.
Blessings and Thank You In Advance.
Click to expand...
Click to collapse
Don't think you have to install an older version of TWRP first but there are 2 common overlooked steps when installing TWRP:
1) Goto Settings/Security when booted and make sure Reactivation lock is unchecked. (If it's set, you can't write in Odin and your phone displays something like blocked by R/L.)
2) You've dug up an old thread, this post may conflict with the older posts above but for clarity, it's best to open Odin options tab, uncheck only the auto reboot box and flash the img.tar, loading in AP slot. After flash is verified as successful, 0 failed (wait for it), pull USB cable and battery, wait at least 30 seconds. It's important that your first boot is directly to recovery to make TWRP stick as your default recovery. Else, you revert back to stock recovery if booting into system.
Note: There is a TWRP thread in original development forum which answers this question and others. Before rooting, you may consider OTA update to the update that matches your ROM if interest. The OTA updates are incremental so it may make more sense to Odin the stock reflecting the update of interest.
When Odin flashing stock tars, use the latest Odin, verify the md5 of downloaded zip then extract the tar.md5 to Odin folder to find easily when flashing. But on your phone, backup what you like before considering wiping; don't expect the flash to wipe for you but you may lose internal memory storage. Expect that but don't wipe your extSdCard; you can move what you want to keep there along with anything you intend to flash later. After backup and wipe, power phone down and pull battery prior to flashing stock tar. That seems to help ensure your csc gets setup properly. There is a stock tar thread in general forum with the stock tar updates, tools and instructions.
Make sure you install the right recovery or your touch screen will be out of calibration. Any trouble, refer to the TWRP thread but I think I've addressed the current issues.
Thank you soooo much!!!! That worked.
God bless you!!!!
Have a great weekend!!!
Hello,
About two years ago with the help of this page I was able to ROOT and load a Cyanogenmod ROM on my former Motorola Xoom Tablet. I don't remember how I did it. I just remembered it worked.
I now have a Samsung Galaxy Tab pro 8.4 (SM-T320). Samsung said on its ROM related pages that Android 5 was coming for the SM-T320 in Q3 or Q4 of 2015. Well I am tired of waiting. So I remembered this page and here I am. I do see that a new (non-nightly build) of Lollipop will soon be available. My present Tablet has Android 4.4.2. So you can see why having Android 6 would be nice. My SM-T320 has never been rooted.
I have hunted this page and few others and I have found various threads on how to load a Cyanogenmod ROM. But, they all offer various paths and steps and are not the same. My hope is that some more experienced user can point me to a guide or video that is written like 'How to do XXX for dummies.' Thank you in advance for your help.
6 is Marshmallow not Lollipop. Everything else should be scattered around the forum (especially the CM13 thread) for you to see.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Though no official word (outside a UK Twitter Feed), was ever given. It would seem that the Qualcomm Tab Pro's:
8.4
SM-T320 (Wi-Fi)
SM-T321 (3G)
SM-T325 (LTE)
10.2
SM-T520 (Wi-Fi)
SM-T521 (3G)
SM-T525 (LTE)
Will never be updated past its stock 4.4.2 (KitKat) ROM.
Rooting these Devices is simple enough with Towelroot. But, if you go 'round messing with Custom ROMs, and are Recoveries. Your gonna tripnthe Knox Flag, meaning that you'll never be able to use, or access such Data you might have had there from that Device ever again.
That said it's a fair comp that you probably could care less. But, just note that the Knox Flag will trip if you go though with it, and that you’ll be greeted by such warnings when you cold boot then Device. To the effect of "Kernel is not SELinux enforcing".
bigfootnmd said:
I have hunted this page and few others and I have found various threads on how to load a Cyanogenmod ROM. But, they all offer various paths and steps and are not the same.
Click to expand...
Click to collapse
There are always going to be slightly different ways to skin a cat. With some differences depending on your personal preferences.
In general, you need to:
1) Root by towelroot or CF Auto-root
2) Install custom recovery. That can be TWRP or CM recovery (or even CWM, but I don't think our device is officially supported). Custom recovery can be installed by Odin, or by app (such as TWRP Manager or Flashify)
3) Put the ROM on the phone (whether you download to the device, or transfer it using a computer) either on internal storage or removable SD card
4) Boot into custom recovery, full wipe (data, Dalvik and cache) then flash the ROM
5) Reboot and drink beer, because you are now on Marshmallow
A more detailed guide is here: http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/general/qa-how-to-root-install-custom-recovery-t3087451
Personally, I rooted using CF Auto-Root by process similar to that described in the guide. But I then installed TWRP by Odin as described here (with TWRP downloads): https://twrp.me/devices/samsunggalaxytabpro8.4exynoswifi.html
Rooted and used TWRP app to load TWRP
Hello,
I successfully rooted my Samsung Galaxy Tab PRo 8.4 WIFI. I downloaded the TWP app from the Google Playstore. I downloaded the latest TWRP image. Tablet reboots and the TWRP version 3.0.0-2 loads.
However, GEE where did this APP put the recovery image? I cannot find it. I can't seem to find it on the SD card or Internal storage. Where might this app have put it? If I don't know where it is then how can I install it? YES I did look in the Download folder on the SD card. It is not there. It isn't in the download folder on the internal storage. So, Tablet on boots into recovery mode.
Any help or insight will be appreciated.
redpoint73 said:
There are always going to be slightly different ways to skin a cat. With some differences depending on your personal preferences.
In general, you need to:
1) Root by towelroot or CF Auto-root
2) Install custom recovery. That can be TWRP or CM recovery (or even CWM, but I don't think our device is officially supported). Custom recovery can be installed by Odin, or by app (such as TWRP Manager or Flashify)
3) Put the ROM on the phone (whether you download to the device, or transfer it using a computer) either on internal storage or removable SD card
4) Boot into custom recovery, full wipe (data, Dalvik and cache) then flash the ROM
5) Reboot and drink beer, because you are now on Marshmallow
A more detailed guide is here: http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/general/qa-how-to-root-install-custom-recovery-t3087451
Personally, I rooted using CF Auto-Root by process similar to that described in the guide. But I then installed TWRP by Odin as described here (with TWRP downloads): https://twrp.me/devices/samsunggalaxytabpro8.4exynoswifi.html
Click to expand...
Click to collapse
redpoint73 said:
In general, you need to:
1) Root by towelroot or CF Auto-root
2) Install custom recovery. That can be TWRP or CM recovery (or even CWM, but I don't think our device is officially supported). Custom recovery can be installed by Odin, or by app (such as TWRP Manager or Flashify)
3) Put the ROM on the phone (whether you download to the device, or transfer it using a computer) either on internal storage or removable SD card
4) Boot into custom recovery, full wipe (data, Dalvik and cache) then flash the ROM
5) Reboot and drink beer, because you are now on Marshmallow
Click to expand...
Click to collapse
1) is unnecessary - flashing TWRP with PC via Odin does not require root.
bigfootnmd said:
However, GEE where did this APP put the recovery image? I cannot find it. I can't seem to find it on the SD card or Internal storage. Where might this app have put it? If I don't know where it is then how can I install it? YES I did look in the Download folder on the SD card. It is not there. It isn't in the download folder on the internal storage. So, Tablet on boots into recovery mode.
Any help or insight will be appreciated.
Click to expand...
Click to collapse
I don't really get what you want to know, but recovery is a separate partition on the device you can't access normally. After flashing a recovery it gets written into that partition for permanent access. You won't find the recovery image anywhere on your storage.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
My quest is for Android 6 on my tablet. I downloaded one of the file twrp-3.0.0-0-mondrianwifiue because it is about 8 megs and because the later files when I tried to use ODIN I was told they were too big. The 3.0.0-0 img was loaded successfully. NOw when my tablet boots it freezes on the Samsung Galaxy Tab Pro SM-T320 screen. At the very top in RED it says KERNEL IS NOT SEANDROID ENFORCING. Second line reads Set Warranty Bit Kernel.
So, what now? Maybe if I can just figure out how to RESET it to factory I will be back where I started. Any help will be appreciated.
bigfootnmd said:
My quest is for Android 6 on my tablet. I downloaded one of the file twrp-3.0.0-0-mondrianwifiue because it is about 8 megs and because the later files when I tried to use ODIN I was told they were too big. The 3.0.0-0 img was loaded successfully. NOw when my tablet boots it freezes on the Samsung Galaxy Tab Pro SM-T320 screen. At the very top in RED it says KERNEL IS NOT SEANDROID ENFORCING. Second line reads Set Warranty Bit Kernel.
Click to expand...
Click to collapse
Try booting into recovery, and see if it boots into TWRP: hold power button until the phone reboots. Once the screen goes dark, and before the Samsung logo screen comes up, hold the vol up (you may have followed a similar process to boot into Download mode and use Odin - except vol down).
bigfootnmd said:
Maybe if I can just figure out how to RESET it to factory I will be back where I started. Any help will be appreciated.
Click to expand...
Click to collapse
"Factory reset" is a bit of a misnomer, all it does is wipe the user data partition. I don't think it will help in this case. Flashing TWRP by Odin should not have put you in a "no boot into OS" condition, and I don't know why that would have happened. But if you can get into TWRP, you can flash a ROM (put the ROM zip on the phone by adb push or copy to removable SD card) and get the phone back up and running.
Need help
Hello,
My friend rooted my samsung galaxy tab pro 10.1 SM-T520 using kingo root.
Would i be able to update to lollipop?
If yes then how?
If no then why?
Please reply as soon as possible.
Please also guide me on [email protected] by mailing me.
Thanks.
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
the0f said:
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Click to expand...
Click to collapse
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
efrant said:
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
Click to expand...
Click to collapse
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
the0f said:
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
Click to expand...
Click to collapse
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
efrant said:
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
Click to expand...
Click to collapse
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
the0f said:
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
Click to expand...
Click to collapse
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
efrant said:
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
Click to expand...
Click to collapse
Thank you again sir, I'll give that a try this evening when I get back home. The help and the hand holding is very much appreciated. I thought that I knew a fair bit about android phones and custom ROMs from my time with my old Samsung devices, and have had to do a lot of learning when it's come to the One M9. Never had a device with the S-ON feature before and have had a lot of trouble trying to find info on what I need to do. I did find that forum post you linked, but wasn't sure if that applied to my device or not. Again VERY much appreciated.
Yup, 6.0 stock is installed and working, TWRP 3.0.0-2 installed and working as well. This time took a system backup and stored it in a safe place (as I expect much the same trouble when Android N or any other major update happens). Thank you again for all of your assistance in getting my phone fixed and updated.