Develop Bugs

Need help recovering from failed root

I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?

Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk

dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
Click to expand...
Click to collapse
Thanks! I'll give that a shot. But a question before I do something really dumb. Where does this recovery tar file go in odin? PDA?

Yep always PDA
Sent from my SM-P900 using Tapatalk

Worked! I now have rooted KOT49H.T900UEUAND4.

Good stuff
Sent from my SM-P900 using Tapatalk

OK. Here comes the "but". It turns out that I cannot connect over SSL. Wifi works, I have an IP, I can brows non-secure websites. But I cannlt connect to anything https, nor will apps like Google Play connect.
Do we think this is related, or should i start a new thread?
UPDATE: I wiped data and now all is fine. The really interesting thing that I've noticed is that the Device Status is showing as "Official".

JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?

gbr357 said:
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
Click to expand...
Click to collapse
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.

Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?

gbr357 said:
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
Click to expand...
Click to collapse
I think I would have done that if I had known there was a B5 recovery image available. The guidance that I was given was to flash the B3 image from the P900. And that *did* work fine. Before there was a root flash for the T900, people were using the P900 root with success. Don't know that there is much difference. In the end, either way, you will end up with a B5 recovery image, as that is what Chainfire included in the T900 root file.

Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.

gbr357 said:
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
Click to expand...
Click to collapse
Which file from Chainfire did you flash? Was it CF-Auto-Root-v2wifi-v2wifixx-smt900.zip? For me, flashing that after OTAing to ND4 left me unable to boot. Maybe that got fixed in the past couple of day?

Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??

gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Well. technically I wasn't rooted either. I completely removed root with SuperSU.Is your recovery NB5?

JJMT said:
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Click to expand...
Click to collapse
That's the problem I've been writing about for a week. The new OTA update (t900ueuand4) doesn't work with auto-root and crashes exactly where yours did.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Can you give me the link for the new chainfire file that must have been re-written in the last 2 days
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Just re-downloaded the chainfire file and it's identical to the file I got 10 days ago dated May 10th. If you had success flashing it with the firmware t900ueuand4 installed at the time of rooting, then I'll give it a shot too.

JJMT said:
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Click to expand...
Click to collapse
All I had to do, was stop after 3. Didn't require a factory reset. Everything is great

The same here. Used the Note 12 recovery mod to unbrick the tablet.
Flashed the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 and it works. :good:
Now oor Samsung tablet pro 12.2 is rooted.

dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar issue except my device came up to an error regarding firmware upgrade failed, use kies to recover. I could not get this to work with kies 3. Searching the threads, I found your post. Worked beautifully. The failed attempt did trip Knox. Not sure I care.
Thanks!

T999V-Wind Mobile-TWRP problem

I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?

getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
Are you running a custom rom and/or kernel? Im wondering if this may have something to do with selinux. If not using one already, try flashing an insecure custom kernel. You might also want to try flashing CWM, just to see if it has the same issue.

DocHoliday77 said:
Are you running a custom rom and/or kernel? Im wondering if this may have something to do with selinux. If not using one already, try flashing an insecure custom kernel. You might also want to try flashing CWM, just to see if it has the same issue.
Click to expand...
Click to collapse
Thanks for the reply.
I'm not sure, I'm only running stock+root from the root66 package for the MK5 ROM for my phone from Wind in Canada. I tried installing CWM and it ran the first time, tried clearing cache to see if it had any permission/mount errors, and it froze, pulled the battery and wouldn't boot anymore. Had to reflash root66 package to get my phone to even boot. Rootchecker says I'm rooted fine, SU gives permissions to everything fine, busybox is fine. Donwload mode shows security bit disabled, so the root66 disabled knox. Not sure what to do try next.
EDIT
Installed CWM from ROM-Manager, and it worked, installed liewise ROM and it's working fine. I unno. lol.

getochkn said:
Thanks for the reply.
I'm not sure, I'm only running stock+root from the root66 package for the MK5 ROM for my phone from Wind in Canada. I tried installing CWM and it ran the first time, tried clearing cache to see if it had any permission/mount errors, and it froze, pulled the battery and wouldn't boot anymore. Had to reflash root66 package to get my phone to even boot. Rootchecker says I'm rooted fine, SU gives permissions to everything fine, busybox is fine. Donwload mode shows security bit disabled, so the root66 disabled knox. Not sure what to do try next.
EDIT
Installed CWM from ROM-Manager, and it worked, installed liewise ROM and it's working fine. I unno. lol.
Click to expand...
Click to collapse
Sorry that caused you so much trouble. When you are booted into recovery though, whether or not the rom is rooted makes no difference. What is important here is if the kernel is secure or insecure. I am still fairly certain selinux was causing you your problems with mounting though. If you are running any rom based on my Sprint ND8 port (such as likewise), you shouldn't have anymore problems (if I am correct about it being selinux of course). The kernel included has selinux disabled. Glad you got it working though.
Just curious, what do you mean by download mode shows security bit disabled? I think you might mean selinux? The warranty bit, which is often referred to as the knox counter cannot be disabled and is actually separate from Knox itself. Removing knox is something done only in the rom, not the kernel, and has no effect on what is shown in download mode. Also, selinux is not knox, they are two different technologies. Just fyi for future reference.

getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
how i did my wind s3 is
Unified_Android_Toolkit_v1.2.8 seemed to work for me

DocHoliday77 said:
Sorry that caused you so much trouble. When you are booted into recovery though, whether or not the rom is rooted makes no difference. What is important here is if the kernel is secure or insecure. I am still fairly certain selinux was causing you your problems with mounting though. If you are running any rom based on my Sprint ND8 port (such as likewise), you shouldn't have anymore problems (if I am correct about it being selinux of course). The kernel included has selinux disabled. Glad you got it working though.
Just curious, what do you mean by download mode shows security bit disabled? I think you might mean selinux? The warranty bit, which is often referred to as the knox counter cannot be disabled and is actually separate from Knox itself. Removing knox is something done only in the rom, not the kernel, and has no effect on what is shown in download mode. Also, selinux is not knox, they are two different technologies. Just fyi for future reference.
Click to expand...
Click to collapse
Ah. Maybe I was looking at the QualcomSecureboot or something
Either way, all is good. Not sure why TWRP gave problems or CWM did via Odin. I'm using likewise rom, which is based off your sprint so shouldn't have any more problems now anyways. Not a stranger to flashing Samsung phones, just my first newer samsung flash with this whole knox/selinus thing and all that. My old sammy S 4G was flashed hundreds of times while I worked on ROMs'. lol.

Rickyfk said:
how i did my wind s3 is
Unified_Android_Toolkit_v1.2.8 seemed to work for me
Click to expand...
Click to collapse
Be careful with that! I always advise against using it because it is very rarely updated, the op does not provide any support for it, and it has bricked several devices.

yes i forgot that in my post i always back ups of everything before i do anything.
i have also fixed bricked devices befor also but ya you have to be carful tho.
DocHoliday77 said:
Be careful with that! I always advise against using it because it is very rarely updated, the op does not provide any support for it, and it has bricked several devices.
Click to expand...
Click to collapse

i have the same problem
getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
my phone is wind T999V, rom is original JB 4.3.
i use root66 rom. i want to downgrade, i want to use twrp to copy system, but , all is no no no , sad.:crying:

welcome2you said:
my phone is wind T999V, rom is original JB 4.3.
i use root66 rom. i want to downgrade, i want to use twrp to copy system, but , all is no no no , sad.:crying:
Click to expand...
Click to collapse
Not sure what you mean there, sorry. But you cannot downgrade your firmware, but you can flash an older rom from TWRP.

DocHoliday77 said:
Not sure what you mean there, sorry. But you cannot downgrade your firmware, but you can flash an older rom from TWRP.
Click to expand...
Click to collapse
i want to use twrp,but cannot find partition, i want to downgrade to 4.1 ,then i can unlock my phone , but i have no way to finish it.

welcome2you said:
i want to use twrp,but cannot find partition, i want to downgrade to 4.1 ,then i can unlock my phone , but i have no way to finish it.
Click to expand...
Click to collapse
How are you trying to install TWRP? There are several ways to do so. Odin, recovery, Goo.Im app..... You can get the twrp files from my sig if you want to try those. No guarantee you will be able to unlock when flashing the 4.1.1 modem, let us know if it works for you.

I had tried TWRP through Odin flashable and also Goo Manager. I tried 2.7.0 and 2.7.1, both Tmo and Can version, and none could mount anything . CWM through Rom Manager works great though.
I know, from my experience working on ROM's and getting the first Heimdall flashable package to upgrade the Galaxy S 4G from Wind, that the Wind models of phones are slightly different than the Tmo versions. It took me a dev a while to find the right files, lots of soft bricking ,etc, to figure out the minute difference to allow Heimdall to flash a package, and even then, Heimdall could never flash a modem to the 4G-Wind Variant. I even tried working with the Heimdall dev to find out why, and never could. Modems would flash from CWM or TWRP, but not from the PC, even though Tmo firmwares and ROM's worked, so maybe the Wind phone is slightly different in partition layout that CWM can adapt for, but TWRP can't. Maybe I'll contact the TWRP team and see if I can help them figure out why, although now I'm working a lot more than I was and don't have a lot of time to flash my phone 100 times and brick it and flash again like in the older days.

getochkn said:
I had tried TWRP through Odin flashable and also Goo Manager. I tried 2.7.0 and 2.7.1, both Tmo and Can version, and none could mount anything . CWM through Rom Manager works great though.
I know, from my experience working on ROM's and getting the first Heimdall flashable package to upgrade the Galaxy S 4G from Wind, that the Wind models of phones are slightly different than the Tmo versions. It took me a dev a while to find the right files, lots of soft bricking ,etc, to figure out the minute difference to allow Heimdall to flash a package, and even then, Heimdall could never flash a modem to the 4G-Wind Variant. I even tried working with the Heimdall dev to find out why, and never could. Modems would flash from CWM or TWRP, but not from the PC, even though Tmo firmwares and ROM's worked, so maybe the Wind phone is slightly different in partition layout that CWM can adapt for, but TWRP can't. Maybe I'll contact the TWRP team and see if I can help them figure out why, although now I'm working a lot more than I was and don't have a lot of time to flash my phone 100 times and brick it and flash again like in the older days.
Click to expand...
Click to collapse
As far as partition layout goes, all of the T999 and I747 variants are the same. I believe the Sprint and Verizon ones are as well, but am not 100% confident in that. You said you tried the d2can and d2tmo versions, but what about d2lte? Everyone should be just using d2lte now as ALL the S3 models have been consolidated into that one. Where did you download it from btw? You can get it from the link in my sig. I know for sure it works. (I think I still need to add 2.7.0.1 though. But 2.7.0.0 is there.)

DocHoliday77 said:
As far as partition layout goes, all of the T999 and I747 variants are the same. I believe the Sprint and Verizon ones are as well, but am not 100% confident in that. You said you tried the d2can and d2tmo versions, but what about d2lte? Everyone should be just using d2lte now as ALL the S3 models have been consolidated into that one. Where did you download it from btw? You can get it from the link in my sig. I know for sure it works. (I think I still need to add 2.7.0.1 though. But 2.7.0.0 is there.)
Click to expand...
Click to collapse
I looked in your sig but don't see a D2LTE TWRP, only the 2.7.0 TMO one, which I downloaded from the official TWRP site, as well as 2.7.1 and neither worked. I also tried installing from Goo Manager. Maybe I'll try yours since it is a CWM flashable zip as opposed to an odin tarball and I have CWM working

getochkn said:
I looked in your sig but don't see a D2LTE TWRP, only the 2.7.0 TMO one, which I downloaded from the official TWRP site, as well as 2.7.1 and neither worked. I also tried installing from Goo Manager. Maybe I'll try yours since it is a CWM flashable zip as opposed to an odin tarball and I have CWM working
Click to expand...
Click to collapse
Ill have to double check that later. Been a while since I've flashed recovery. I know I am using the one in my repo though, so it should work fine whether its d2tmo or d2lte

[Q] TWRP replaced with stock recovery[t805]

I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for
Android 4.4 KitKat: Google Making Root Without Unlocked Bootloader Difficult?
Click to expand...
Click to collapse
(sry can't link)

JoeRifle said:
I have flashed twrp recovery over odin. I can only get into stock recovery though. Usual fix would be to remove battery b4 rebooting, but I can not make out the battery on this device - seems integrated / hidden.
I am running 4.4.2 KitKat. Trying to root it to debloat.
Any ideas? Maybe remove some startup scripts or Idk...
EDIT: I got word that it seems to be either some hash verification in the new android 4.4.x kernel or even a locked bootloader on top. Is that correct? And, if so, what would be a good course of action now?
More info can be found imo when googling for (sry can't link)
Click to expand...
Click to collapse
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?

The question would be why you didn't use the recommended way of using Flashify to flash twrp?

Eddie Hicks said:
I don't know of any tablet that has user removable battery. I'm sure you have to be rooted before you can install a custom recovery. Are you using the rooting method in the development topic?
Click to expand...
Click to collapse
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
kenkiller said:
The question would be why you didn't use the recommended way of using Flashify to flash twrp?
Click to expand...
Click to collapse
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?

JoeRifle said:
Yes. Would have posted there too had it been allowed. It is the method described in the t800 thread, where it says you should flash twrp via odin and then install SuperUser zip in TWRP.
I thought that this was the way to do it. I have not read anything in that thread about flashify.
If flashify works with Android 4.4.2 I will dig into that. Does it?
Click to expand...
Click to collapse
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.

kenkiller said:
You did not follow the instructions in the first post, but the latter ones posted by bodivas? Then you should consider trying those in the first post - they work for T805 as well.
The ones in the first post work. Flashify I found it in the CF-Root for T700 thread, it works fine on T805 as well, as long as you get the correct img file from the TWRP site.
Click to expand...
Click to collapse
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:

JoeRifle said:
yes bodivas is his name. it seemed to be the better method. but since it did not "accept" the image, although odin said success, I dug deeper and found out that there is supposed to be a hash check in 4.4.2 which keeps me from keeping the flashed image
Will flashify solve that problem and make TWRP "resident"? I would rather not flash the CF Auto since it is for a t800 not t805, but maybe i am overcautious:angel:
Click to expand...
Click to collapse
You don't get by in XDA by being cautious in everything. There's enough reports to tell otherwise.
Yes, using Flashify to flash TWRP replaces stock recovery. TOTALLY.

Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.

JoeRifle said:
Requires root though right? So is not possible for me I fear Only way would then be CF Auto for t800...as we found out. TU anyhow.
Click to expand...
Click to collapse
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.

kenkiller said:
Of course it requires root. Not possible because you don't dare to flash the T800 files? Hehe.....you're gonna have a hard time here.
Click to expand...
Click to collapse
I just need to get the hang of these appy lil spy thingy thing things...god knows what g**gle has in store for you. out of curiosity, so you are saying there is no hash check in the bootloader keeping me/us from doing our evil deeds? how about the article up there I quoted, and what the heck happened when i odined TWRP?
just asking...will flash the CF. so lets cross thumbs and make tha knox trip count

Hi Guys. As following the instructions to flash openrecovery-twrp-2.8.0.1-chagallwifi.tar using Odin3 v3.09, my T805 reboots into recovery, the TWRP boot screen is blurred, and after the Menu appears, my device locks up and there is no way to reboot it. Force reboot by holding down the Power button doesn't work. I've been trying for nearly an hour and nothing works. The Task Menu and Return buttons are lit, but the screen is blank. Any suggestions on how to get my T805 to reboot normally?
Thanks.
UPDATE:
I found that 2.8.0.1 appears out of alignment on the screen, and I had to poke around until I found where the Reboot button was located. By chance I got it to go into Bootloader and the system rebooted. Once online I installed Flashify and installed TWRP 2.7.1.1 and SUCCESS!! Now my T805 is working normally. WHEW!!

[Solved] Need help with installing Cyanogenmod (Without a PC if possible)

Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.

Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app

jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!

KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.

dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.

KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.

dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.

KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.

Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app

Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?

KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"

As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband

Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.

KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.

Here is the info mrrocketdog

Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.

audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse

KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?

Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop

can't get a rom to load, probably a newbie think on my part.

Now that i'm in the correct thread.......
this phone is just for messing with so backup isn't needed. Unlocked, son did factory reset only twrp was left on it. D/L Magma rom, went into twrp clicked on zip, nadda. D/L different rom (forget the name) still no dice. D/L Odin, installed stock rom, phone works no issues etc, but twrp was gone. Re-loaded twrp with Odin, but still couldn't get either of the previous 2 roms to load. Searches have yielded inconsistent results. Some say you can load a rom over the stock with Odin, others say you can't. Tried to find a rom I could load via Odin that would work on the sm-n900t but the stock rom is all that comes up in my searches. Not really sure where to go from here, if someone can point me in the right direction it would be appreciated. I'm pretty sure I d/l the correct twrp for my phone as I actively looked to make sure I was getting the one for my phone, and it said it was......

Are you using a version from here: https://dl.twrp.me/hltetmo/ ?

audit13 said:
Are you using a version from here: https://dl.twrp.me/hltetmo/ ?
Click to expand...
Click to collapse
the file I used is twrp-3.2.3-0-hlte.img.tar

kevin24018 said:
this phone is just for messing with so backup isn't needed.
Click to expand...
Click to collapse
Trust me, backup is always needed.
kevin24018 said:
Unlocked, son did factory reset only twrp was left on it. D/L Magma rom, went into twrp clicked on zip, nadda. D/L different rom (forget the name) still no dice.
Click to expand...
Click to collapse
you might be installing wrong version of rom. (i'll tell you why i assumed this)
kevin24018 said:
D/L Odin, installed stock rom, phone works no issues etc, but twrp was gone. Re-loaded twrp with Odin, but still couldn't get either of the previous 2 roms to load. .
Click to expand...
Click to collapse
when you install stock rom through odin. it removes everything. everything means your device is as new as you bought it. so when you installed stock rom, it always removes twrp and installs stock recovery. same goes with any custom rom you previously installed.
kevin24018 said:
Searches have yielded inconsistent results. Some say you can load a rom over the stock with Odin, others say you can't.
Click to expand...
Click to collapse
yes you can load a rom over the stock but not with odin. with twrp instead.
kevin24018 said:
Tried to find a rom I could load via Odin that would work on the sm-n900t but the stock rom is all that comes up in my searches. Not really sure where to go from here, if someone can point me in the right direction it would be appreciated.
Click to expand...
Click to collapse
normally people use odin to install stock roms or twrp or for root. nobody installs custom rom through odin. i don't want you to go deep into this right now so i'm just suggesting you the easiest way.
i assume currently you have stock lollipop rom rooted with twrp. all you need to do is to go to here ans choose your rom. read and follow instruction to the point. i'm sure you'll get things done .
kevin24018 said:
I'm pretty sure I d/l the correct twrp for my phone as I actively looked to make sure I was getting the one for my phone, and it said it was......
Click to expand...
Click to collapse
now sadly. the twrp version you mentioned above is for n9005 international version while you're having n900t (t mobile version) so you'll need correct twrp the says "tmo" or something like this.
above i said you might be installing wrong version of rom because you're not using correct twrp and pretty sure about it. thats why i assumed you may also have d/l wrong version of rom.
long story short : you need everything regarding tmobile (tmo) not any other. just in case please check if you really have n900t or not by taking out battery.

Sharjeel.Khan said:
Trust me, backup is always needed.
you might be installing wrong version of rom. (i'll tell you why i assumed this)
when you install stock rom through odin. it removes everything. everything means your device is as new as you bought it. so when you installed stock rom, it always removes twrp and installs stock recovery. same goes with any custom rom you previously installed.
yes you can load a rom over the stock but not with odin. with twrp instead.
normally people use odin to install stock roms or twrp or for root. nobody installs custom rom through odin. i don't want you to go deep into this right now so i'm just suggesting you the easiest way.
i assume currently you have stock lollipop rom rooted with twrp. all you need to do is to go to here ans choose your rom. read and follow instruction to the point. i'm sure you'll get things done .
now sadly. the twrp version you mentioned above is for n9005 international version while you're having n900t (t mobile version) so you'll need correct twrp the says "tmo" or something like this.
above i said you might be installing wrong version of rom because you're not using correct twrp and pretty sure about it. thats why i assumed you may also have d/l wrong version of rom.
long story short : you need everything regarding tmobile (tmo) not any other. just in case please check if you really have n900t or not by taking out battery.
Click to expand...
Click to collapse
after installing the correct twrp, I was able to install Lineage, thanks for the help. I have a better idea of what I'm doing, I'll continue to play around with it.