I am currently on the MK1 build. In the P600 CF-Auto root thread, as I understand two files needed, One is for the root which is autorootp600mj4.tar.md5 and the other is for recovery which is the stock mj4 recovery, Okay all that being said. Now the question. Can I flash autoroot600mj4.tar.md5 for root, but instead of using the stock mj4 recovery, can I flash the stock mk1 recovery that was post in the P600 CF-Auto root thread. (Refer to Post #144)
Thanks,
Jeff
it could make sens. who got an answer for us please?
yopmania said:
it could make sens. who got an answer for us please?
Click to expand...
Click to collapse
Amen!!
landj1 said:
I am currently on the MK1 build. In the P600 CF-Auto root thread, as I understand two files needed, One is for the root which is autorootp600mj4.tar.md5 and the other is for recovery which is the stock mj4 recovery, Okay all that being said. Now the question. Can I flash autoroot600mj4.tar.md5 for root, but instead of using the stock mj4 recovery, can I flash the stock mk1 recovery that was post in the P600 CF-Auto root thread. (Refer to Post #144)
Thanks,
Jeff
Click to expand...
Click to collapse
yes you can
Thanks
lsherif said:
yes you can
Click to expand...
Click to collapse
Thanks for the info!!!
J
One other question please, If rooting is so great, why are there so many post requesting help because their device is not booting, in a bootloop or some other problems.. I really would like to root., but am not sure that some of these problems others have would happen to me. Convince me I should root. Not concern about Knox, (that horse has been beaten in the head enough) or the warranty.
One other question please, If rooting is so great, why are there so many post requesting help because their device is not booting, in a bootloop or some other problems.. I really would like to root., but am not sure that some of these problems others have would happen to me. Convince me I should root. Not concern about Knox, (that horse has been beaten in the head enough) or the warranty.
landj1 said:
One other question please, If rooting is so great, why are there so many post requesting help because their device is not booting, in a bootloop or some other problems.. I really would like to root., but am not sure that some of these problems others have would happen to me. Convince me I should root. Not concern about Knox, (that horse has been beaten in the head enough) or the warranty.
Click to expand...
Click to collapse
Rooting has nothing to do with boot looping issues you are referring to, these were TWRP problems .
Related
Hey guys,
I was wondering if someone could help me a little. I just bought this tablet (2014 version) and it has MK1.
I am trying to read information on how to root it but can't figure it out. I tried to flash autoroot with odin but it errored. I didn't find mk1 autoroot anywhere so i used autorootp600.mj4.tar.md5. Is there autoroot for MK1 and i can use? Also i guess i will need to have custom recovery file for my stock OS, where do i get that?
Thank you in advance for all the help.
Edit: I finally located autoroot for mk1 and it worked. But i do have a question: why do we need to flash it with Stock Recovery after? btw i am using this tutorial : http://theunlockr.com/2013/12/17/root-samsung-galaxy-note-10-1-2014-edition/
What version do you have?
P600 (wifi only)
P601 (3g)
P605 (lte)
?
They have different chipsets and different root methods.
[e] I see you have found the correct version if you want to get OTA updates you need to flash stock recovery so your device status is not custom. But it basically doesn't matter since you can always flash updates through odin. You may choose a custom recovery that offers you a lot of cool features instead.
stamina11 said:
Hey guys,
I was wondering if someone could help me a little. I just bought this tablet (2014 version) and it has MK1.
I am trying to read information on how to root it but can't figure it out. I tried to flash autoroot with odin but it errored. I didn't find mk1 autoroot anywhere so i used autorootp600.mj4.tar.md5. Is there autoroot for MK1 and i can use? Also i guess i will need to have custom recovery file for my stock OS, where do i get that?
Thank you in advance for all the help.
Edit: I finally located autoroot for mk1 and it worked. But i do have a question: why do we need to flash it with Stock Recovery after? btw i am using this tutorial : http://theunlockr.com/2013/12/17/root-samsung-galaxy-note-10-1-2014-edition/
Click to expand...
Click to collapse
I believe...... so you can still get OTA updates and some functions like All Share Cast may not work if you don't.
The thing is, even if you have stock recovery but modify your system in other ways like uninstall alot of bloatware or use busybox your status will be custom anyway so I recommend a custom recovery for the safety of using backups etc.
Thank you guys for responding so quickly.
It's starting to make sense.
My device is Wifi only so SM-P600 (mk1). I rooted it but haven't flashed with stock recovery. Would you guys recommend i do a custom recovery or keep it stock? Where do i get stock recovery from? i can't seem to find it.
clouds5 said:
The thing is, even if you have stock recovery but modify your system in other ways like uninstall alot of bloatware or use busybox your status will be custom anyway so I recommend a custom recovery for the safety of using backups etc.
Click to expand...
Click to collapse
Yea i definitely plan on de-bloating it. So where do you get custom recovery?
http://forum.xda-developers.com/showthread.php?t=2515656
Check this thread
clouds5 said:
http://forum.xda-developers.com/showthread.php?t=2515656
Check this thread
Click to expand...
Click to collapse
Ok, that makes sense i went though it. So i see that there is ClockMod and TWRP and GooManager, do they do pretty much the same thing?
So as far as Roms go, i see that in Development section there are few ROMs available but some say they are for MJ9 or ML1, i cannot use those on my MK1 right? Do ROMs from note 10.1 (2013) work on this device? Is there a list of ROMs that would work on my device.
Sorry, guys i know these are newb questions but i just could never figure out some of this stuff.
stamina11 said:
Ok, that makes sense i went though it. So i see that there is ClockMod and TWRP and GooManager, do they do pretty much the same thing?
Click to expand...
Click to collapse
I got the same question here. Any help?
legender said:
I got the same question here. Any help?
Click to expand...
Click to collapse
Goomanager is an app use it to flash twrp recovery.
TWRP and clockmod (CWM) they are 2 different tools but have the exact same functions, just a user choice. Sometimes custom rom preferred one over the other. I like TWRP a bit better (easier).
is there a way to check if it is rooted or not?
legender said:
is there a way to check if it is rooted or not?
Click to expand...
Click to collapse
Download rootchecker in the play store
Sent from my Nexus 5 using Tapatalk
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
Click to expand...
Click to collapse
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Click to expand...
Click to collapse
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
buhohitr said:
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
Click to expand...
Click to collapse
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
deV14nt said:
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
Click to expand...
Click to collapse
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
wha2do said:
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
Click to expand...
Click to collapse
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
wha2do said:
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
Click to expand...
Click to collapse
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
22sl22 said:
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks - that was the post had been reading through - appears after the kitkat OTA, latest posts mentioned problems with SU when running the original CF-AUTO Root method (flashing autorootp600mj4.tar.md5). Wondering if flashing the "newer" CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5
would be best. At this point feel confident either way!
deV14nt said:
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
Click to expand...
Click to collapse
Yep, will be downloading TWRP v2.6.3.3 and flash it and SuperSU after rooting. After rooting, will be curious to see where I sit with superuser (sorry, reading the latest posts kind of muddy whether a SU app is already installed or not, lol)...
Thanks everyone for all the great input & help!!
Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
pandabamboo said:
Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
Click to expand...
Click to collapse
I have all of these questions!
There's so much information in these forums, and it's very confusing.
I simply can't find a guide for how to get from Kit-kat on the Note 8 to rooted and with civato's ROM (would love some increased pen accuracy).
Any help would really be appreciated!
pandabamboo said:
Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
Click to expand...
Click to collapse
I don't have a 5120 but everything I have read confirms that CF Autoroot works without issue on that device. Just make sure after boot up you install SuperSU, update binary, and set it to apply upon system boot. If it doesn't work the first time keep trying. As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
You will want to install a custom recovery to flash roms (PhilZ or TWRP). However, changing the recovery, bootloader, etc. will prevent you from taking OTA updates. This is not such a bad thing because you never know if a new OTA will destroy root and lock the device. It is better to let the devs modify it first and then flash it safely. Usually only takes a day or so for devs to do this.
As for changing the bootloader, it depends on the rom you flash. Some will be fine running from older bootloader and some require the KK bootloader. Just check the first post of the rom and it should give you the requirements.
---------- Post added at 09:07 AM ---------- Previous post was at 08:53 AM ----------
jwdink said:
I have all of these questions!
There's so much information in these forums, and it's very confusing.
I simply can't find a guide for how to get from Kit-kat on the Note 8 to rooted and with civato's ROM (would love some increased pen accuracy).
Any help would really be appreciated!
Click to expand...
Click to collapse
You can use CF Autoroot to obtain root and then install custom recovery via Odin as well. Then you can flash whatever rom you want.
7014
As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
Click to expand...
Click to collapse
Thanks CCallahan. Do you know of any method that will not trip Knox?
You can use CF Autoroot to obtain root and then install custom recovery via Odin as well. Then you can flash whatever rom you want.
Click to expand...
Click to collapse
I just wasn't sure on the details of these steps, and wasn't sure where to find more detail. I think I've figured it out now.
First I'd follow these steps: http://www.theandroidsoul.com/samsu...n5100-wifi-philz-touch-advanced-cwm-recovery/
Then, I'd use philz to install the custom kernel (edit: and ROM). I haven't been able to find any step-by-step instructions, however. But these seem close enough: https://www.youtube.com/watch?v=aDOY3Oi1VX8
Does this all sound correct?
jwdink said:
Thanks CCallahan. Do you know of any method that will not trip Knox?
I just wasn't sure on the details of these steps, and wasn't sure where to find more detail. I think I've figured it out now.
First I'd follow these steps: http://www.theandroidsoul.com/samsu...n5100-wifi-philz-touch-advanced-cwm-recovery/
Then, I'd use philz to install the custom kernel. I haven't been able to find any step-by-step instructions, however. But these seem close enough: https://www.youtube.com/watch?v=aDOY3Oi1VX8
Does this all sound correct?
Click to expand...
Click to collapse
I do not know of any root method compatible with the N8 that will not trip Knox. Towelroot is not compatible otherwise it would be an obvious choice.
Yes...looks like that walkthrough will work fine for installing PhilZ.
Why are you installing a custom kernel? Are you sticking with the stock rom or flashing a custom one? A lot of roms already come with the kernel packaged.
CCallahan said:
I do not know of any root method compatible with the N8 that will not trip Knox. Towelroot is not compatible otherwise it would be an obvious choice.
Yes...looks like that walkthrough will work fine for installing PhilZ.
Why are you installing a custom kernel? Are you sticking with the stock rom or flashing a custom one? A lot of roms already come with the kernel packaged.
Click to expand...
Click to collapse
I'm installing a custom ROM & Kernel because the accuracy of the pen is not very good on my device, and I primarily brought it for note taking. My understanding is that civato's ROM/kernel will fix this (hopefully!).
But I didn't mean to imply that I'm only installing a custom kernel but keeping the stock ROM. I was planning on doing both, as described in civato's kernel+ROM release thread.
jwdink said:
I'm installing a custom ROM & Kernel because the accuracy of the pen is not very good on my device, and I primarily brought it for note taking. My understanding is that civato's ROM/kernel will fix this (hopefully!).
But I didn't mean to imply that I'm only installing a custom kernel but keeping the stock ROM. I was planning on doing both, as described in civato's kernel+ROM release thread.
Click to expand...
Click to collapse
Ah ok....after you get PhilZ on there just flash civato's rom and you will be good to go.
1928
CCallahan said:
I don't have a 5120 but everything I have read confirms that CF Autoroot works without issue on that device. Just make sure after boot up you install SuperSU, update binary, and set it to apply upon system boot. If it doesn't work the first time keep trying. As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
Click to expand...
Click to collapse
Hi CCallahan,
Would you please confirm whether the method described in the link you mentioned to root Galaxy note 8.0 GT-N5120 running android 4.4.2 would work on note 8.0 i467m (LTE canadian version) running on 4.4.2?
beniboy86 said:
Hi CCallahan,
Would you please confirm whether the method described in the link you mentioned to root Galaxy note 8.0 GT-N5120 running android 4.4.2 would work on note 8.0 i467m (LTE canadian version) running on 4.4.2?
Click to expand...
Click to collapse
The procedure is the same but you want to go and download the CF AutoRoot for your device here: http://autoroot.chainfire.eu/
Your device is on the list so is compatible. There are also some basic instructions listed for how to root.
CCallahan said:
The procedure is the same but you want to go and download the CF AutoRoot for your device here:
Your device is on the list so is compatible. There are also some basic instructions listed for how to root.
Click to expand...
Click to collapse
Thanks for your response. I have only one corcern left. In the link you posted, on top of the table of CF-Auto-root, it mentions that if the bootloader is locked this might brick the device! How can I make sure that my bootloader is unlocked prior to start rooting.
Previuosly, I had my note 8 rooted with CF auto root via odine when it was on jelly bean 4.1.2. Does this mean that it is safe to root it again with new CF auto root for 4.4.2?
It's just a warning pal I rooted fine from 4.4.2 with chainfire autorotate it's just a precaution before proceeding as with any flashing procedure it contains a risk of bricking
Sent from my GT-I9505
beniboy86 said:
Thanks for your response. I have only one corcern left. In the link you posted, on top of the table of CF-Auto-root, it mentions that if the bootloader is locked this might brick the device! How can I make sure that my bootloader is unlocked prior to start rooting.
Previuosly, I had my note 8 rooted with CF auto root via odine when it was on jelly bean 4.1.2. Does this mean that it is safe to root it again with new CF auto root for 4.4.2?
Click to expand...
Click to collapse
How did you update to 4.4.2? Rom flash or OTA? Did you manually update the bootloader?
As far as I know Samsung doesn't usually lock bootloaders unless it is carrier dictated. It is usually common on HTC and Moto devices.
Better to be safe than sorry though.
Sent from my SM-G900P using Tapatalk
CCallahan said:
How did you update to 4.4.2? Rom flash or OTA? Did you manually update the bootloader?
As far as I know Samsung doesn't usually lock bootloaders unless it is carrier dictated. It is usually common on HTC and Moto devices.
Better to be safe than sorry though.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I updated to 4.4.2 via Kies with samsung's released firmware. I havent done any other flashing apart from this. So, I suppose rooting must be fine, right?
beniboy86 said:
I updated to 4.4.2 via Kies with samsung's released firmware. I havent done any other flashing apart from this. So, I suppose rooting must be fine, right?
Click to expand...
Click to collapse
Sorry but I can't/won't confirm whether or not that particular model is safe to root after 4.4.2 upgrade. Maybe someone with more knowledge on that version can chime in. I wouldn't think it would be an issue but don't want to steer you wrong. The bootloader could be locked.
Sent from my GT-N5110 using Tapatalk
CCallahan said:
Sorry but I can't/won't confirm whether or not that particular model is safe to root after 4.4.2 upgrade. Maybe someone with more knowledge on that version can chime in. I wouldn't think it would be an issue but don't want to steer you wrong. The bootloader could be locked.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
thanks, I will dig in more on this and will post here if I find something useful.
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!!
I'm somewhat certain I already know the answer to this but I just need confirmation.
With a locked bootloader, flashing anything other than stock will be unsuccessful, right? I've just rooted my t807a and am looking to get xposed running. I just don't want to brick this thing now that I've FINALLY got it rooted.
So what's the bad? What happens if I try to flash a custom recovery? Will it flash and then not work? Will it fail to flash? Will I be bricked/caught in a bootloop?
Right off the bat, let me make one thing abundantly clear: I do not care if I trip Knox. I assume the warranty is voided as soon as I take a new device out of the box so I really don't care if Samsung or AT&T finds out that I've been misbehaving.
In case it matters:
Model: SAMSUNG-SM-T807A
Android version: 5.0.2
Baseband version: T807AUCU1BOD4
Kernel version: 3.4.39-4727547
Build number: LRX22G.T807AUCU1BOD4
Device Status: Custom
Okay I'm no genius, but maybe do a search on using the app flashify to flash custom recovery (twrp) ......obviously the right file for your device.
I've used thus before on other devices and it work well but do your research . Flash at own risk.
Sent from my SM-T800 using Tapatalk
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
ashyx said:
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
Click to expand...
Click to collapse
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
thorvindr said:
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
Click to expand...
Click to collapse
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
ashyx said:
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
Click to expand...
Click to collapse
Having trouble finding documentation on this device's partitions, which are (it seems) not quite the same as most Android devices. To make sure I can recover from (for example) a bad ROM flash, what should I backup? Is flashfire the thing to use for making such a backup?
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
ashyx said:
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
If I can boot to recovery, won't I be able to access the flashfire backup on my microsd card? As long as I don't try to flash a custom recovery, shouldn't I always be able to work from that backup? Or does a flashfire backup need the flashfire app to be useable?
thorvindr said:
Or does a flashfire backup need the flashfire app to be useable?
Click to expand...
Click to collapse
You just answered your own question.
ashyx said:
You just answered your own question.
Click to expand...
Click to collapse
No, I didn't. I assume you're telling me the answer to my first question is no?
ashyx said:
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
thorvindr said:
No, I didn't. I assume you're telling me the answer to my first question is no?
Click to expand...
Click to collapse
I quoted your last question. The answer is you need flashfire.
---------- Post added at 07:24 PM ---------- Previous post was at 07:06 PM ----------
thorvindr said:
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
Click to expand...
Click to collapse
Tbh I don't use kies/smart switch much, but you will find information on it on the net.