Hi guys, I used to be here before with an old phone and ended up loosing my acct so I made a new one
well I recently got a Samsung tab 3 T110 and I was looking forward to root ... but... after reading this thread Here I got scared to get a custom recovery on as it has this note on the top saying:
Something about the T110 makes it difficult to get the OS to boot after a custom recovery is installed. If this happens to you, DO NOT PM ME. I don't know why it happens and I don't have a T110 to troubleshoot. You will have to reflash stock firmware/recovery.
can I then root without custom recovery?
thanks alot
xx
It is possible to root an Android device without a custom recovery, sometimes it can be as simple as downloading an .apk and installing and rooting the device through that. Search Framaroot on xda.
Sent from my stock, untouched Samsung Galaxy Tab 3 7.0 on the xda-developers app
Related
Hello all, my First post so please bear with me, Been using these forums for quite a while and all answers have been allready given, so no need to post... till now.
I have a Samsung Galaxy s3 i747 running android 4.1.2 OTA update and used CF-Autoroot. No problems there,
installed Rom manager, and cwm recovery touch. no problem
When I restart in recovery mode, also everything seems fine...
When I try to backup the phone however using cwm recovery it starts backing up everything including system but the just as it starts data the phone restarts.
Tried reinstalling cwm over and over different versions.. nada same result..
went into the settings to mount the various options as suggested to another user. same problem nada...
To be completely clear, I am trying to make a backup of my stock / rooted only Galaxy s3 i747 onto it's own storage NOT SDcard.
as I also could not figure that out either.
Any help would be greatly appreciated. -Erdericks1976
Sorry about misleading Subject. This is about making my first backup successfully..
Followup.
Well seems there are/were more problems here than I thought, it has begun randomly? restarting,..
Well. not Ramdomly. Whem specific apps are run it would restart.
I did a titanium backup and it would backup alot of the apps. but them would restart the phone when it got to 1 specific app.
I think I figured out what I did wrong here.
I have a Galaxy Note 2, and I may have flashed something from it by mistake......
so I have restarted my Gs3 From scratch Re-Following all instructions.. waiting to test and see if CWM works to back it up now..
It sure was faster with the Note2 rooted Kernel though. (if that was in fact what happend)
I'll update soon as its done..
Followup 2
Yep. that musta been it. Used the correct stock (rooted) Rom
OTA updated from 4.1.1 to 4.1.2, then used CF auto root to Re-root, then reinstalled SU and CWM and Backing up now.
Just passed the Data section the phone would always restart at...
Erdericks1976 said:
Yep. that musta been it. Used the correct stock (rooted) Rom
OTA updated from 4.1.1 to 4.1.2, then used CF auto root to Re-root, then reinstalled SU and CWM and Backing up now.
Just passed the Data section the phone would always restart at...
Click to expand...
Click to collapse
good for you, yu got it solved fast and easier than expected, XDA is your place for Android and root but also every kind of OS there is
anywz am not that old in XDA i joined in April and officially started rooting and modifying my phone since May and it has been great, bricked my phone 1st time but all in all i got the S3 in case for the loss. yu'll get used to this place and ROOT/custom roms
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
after rooting and during boot, I get the "Samsung Custom" with a unlocked padlock screen...so I assume that means it is unlocked??
firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
Or are you talking about CARRIER unlocking the SIM? If so do you happen to have a reference for doing this to a Verizon Phone?
xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
i got exact same problem only i can root my device so far any solution ?
Verizon locked bootloaders. I tried this with twrp and had that issue too
Sent from my SCH-I545 using xda app-developers app
I realize this a 2-year-old post, but would you happen to still have the stock firmware (I545VRUEMK2) for this thing? I have an older Jellybean unit that I need to fix (and want to keep JB as I can root it easily).
Thanks
I have installed TWRP recovery but in the process I killed the standard OS. I was intending to put Cyanogenmod 12 on the machine after getting things backed up. Now I can't find the file.
My current build is P5210UEU0CNK1, which is a wifi-only US version.
If that is lacking, are there any recommendations for an alternate? I looked into reinstalling the original file but all the websites require membership.
bump
Officially confused
I know. I'm talking to myself again but I had to say that I am truly confused. I found Cyanogenmod 12.1 for my P5210 tablet. Installation went well. When they say the first boot takes quite a while, believe it. It took two hours to finish updating all the apps. But here's the puzzle:
This thing isn't rooted! It was before I started, or at least I thought it was. I putTWRP on it, and as suggested I installed Houdini and GApp on as well. But Titanium refused to run. Running a root check confirmed it.
I guess I have two questions in my mind. How did I install TWRP and a new OS on a tablet that wasn't rooted. Or, if it was, why isn't it now?
flashing new roms removes roots on most devices unless said rom is pre-rooted. To my knowledge rooting is only initialy needed to install TWRP or CWM. After i think you can flash new roms and such without root and so root is only needed if you want to run apps with root like es file explorer or titanium backup and such.
If you want your tablet to be rooted again download this supersu file from chainfire
https://download.chainfire.eu/696/SuperSU
And flash it in TWRP, after that you should be rooted again, it works for me on my galaxy tab 3 and kindle fire hd 7 whenever i flash a new rom and lose root
Hello, everybody. I just wanted to pass something on that more knowledgeable folks might already know, but I didn't know until now, so maybe someone else doesnt know and might benefit from something I just found out. I was under the impression that you couldn't use heimdall to install a custom recovery on a sammsung galaxy note 3 sm-n900t (tmo model) but had to use Odin instead. Well, what a PITA to borrow a windows puter for flashing and rooting when you are a ubuntu user! Yeah odin probably runs under vmware just fine and possibly wine too, but do I really want to try to make my linux laptop more windows-like? Nevertheless that is how I had been doing it until today.
last week I took my old tab 2 for a spin and decided it could use a more modern recovery and OS. I followed instructions (darn... i cant post the url! but just google for the title, "How to Install CyanogenMod on the Samsung Galaxy Tab 2 7.0 (GSM) ("p3100")") on the CyanogenMod Wiki for installing recovery using heimdall and it went off swimmingly. I already had 3 sm-n900t devices all on CM12 and just got another one for trying other ROMs. Well, that meant I had a totally expendable note 3 to experiment with, so I thought I would give heimdall a stab at it even though I was doubtful of the outcome.
I had just bought this phone on a certain popular auction site, and rushed into flashing it without doing my homework. I stuck a TWRP 4.4 recovery in it and it took just fine, but the stupid phone wouldn't boot into recovery. Okayyyyyy... looked in About Phone and noticed the android version was 4.3. The 4.4 TWRP couldnt boot with the 4.3 bootloader onboard. So I downloaded a 4.3 TWRP, flashed, and wa lah! Now it boots right up into TWRP recovery! Just to kind of check it out and make sure it was fully functional, I flashed a CM12 nightly, a GApps package, and the most recent SuperSU straight from the sd card using TWRP and it works just fine! And it all started with flashing TWRP to the Note 3 with Heimdall on Linux instead of the usual Odin on Windohs.
So fellow linux users, don't despair. Apparently heimdall v1.4.0 will work with the Note 3. At least it did for me.
I would be most interested in anybody's results, or lack of results, of attempting to install custom recovery on the Note4 or Note5, or the latest S phones., using Heimdall/Linux.
Hi there,
GrowleyMonster said:
I was under the impression that you couldn't use heimdall to install a custom recovery on a sammsung galaxy note 3 sm-n900t (tmo model) but had to use Odin instead.
...
last week I took my old tab 2 for a spin and decided it could use a more modern recovery and OS. I followed instructions (darn... i cant post the url! but just google for the title, "How to Install CyanogenMod on the Samsung Galaxy Tab 2 7.0 (GSM) ("p3100")") on the CyanogenMod Wiki for installing recovery using heimdall and it went off swimmingly.
...
And it all started with flashing TWRP to the Note 3 with Heimdall on Linux instead of the usual Odin on Windohs.
Click to expand...
Click to collapse
I know this is a long time ago, but I am exactly searching for what you did, and - unfortunately I can't find the wiki entry you mention and I did not find so far information how to put a twrp recovery on a phone using heimdall.
If you read this: how did you do it?
EDIT: I did not succeed using heimdall with the very first "download", where I used odin. Now heimdall seems to work as well. See here: https://forum.xda-developers.com/an...unlock-bootloader-using-t4136645#post83117731
Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Slerba said:
Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Click to expand...
Click to collapse
I manage to solve this all by my self.
I flashed to stock firmware using frija and odin. After flashing updated all the apps and rebooted couple of times (just to be sure that phone works). After that flashed TWRP with odin, rebooted to recovery and rooted with Magisk (followed step-by-step guide fron xda forum).
Now this works like a dream.