Related
ALL:
It has been a long time since I posted to this thread. Back then, the Samsung Exhilarate had just come out, and there was no way to root it. Thanks to several other members, most notably j3r3goss and shabbypenguin, I was able to get root on this phone. As of now, this post is very old. The instructions here, are not needed for you to root your Samsung Exhilarate anymore. You are free to read through them, but you should pay attention to the last page (currently page 3). There, j3r3goss posted a link to the the TWRP or CWM recovery files, that you can now use to get root, without following the step-by-step instructions I posted below. I'm leaving the thread up, but for all intents and purposes, consider it closed.
Here's the link to the section you need in order to root your phone:
http://forum.xda-developers.com/show...php?p=32520094
It has been fun, and I've been using my Exhilarate for nearly two years. Because I've been extremely busy, I haven't had time to keep up with the latest changes - but others have. I hope that you found these instructions useful.
In any case, take care and ROOT ON!
Everything past this point is old and no longer applicable
==========================================
IMPORTANT NOTE: If you have UPDATED your phone to ICS, and want to root it, these instructions will work. You will not need to do the last part where you need to update the firmware keys!
Do you plan to update your phone from Gingerbread (Android 2.3) to Ice Cream Sandwich (Android 4.0). Do that first! Otherwise, you'll just have to root again (not that that's a problem, but why???)
I) How to update to ICS:
1) Download Samsung Kies from here: http://www.samsung.com/us/kies/ if you haven't already, and install it, and then run it
2) Put your phone into ODIN (Download mode - see section II below).
3) When Kies detects you phone (your computer will need to install drivers, and then Kies will say it's connecting to your phone, and it will take about 3-4 minutes and finally connect to it), it should let you know that there is an update. Just follow the instructions on Kies and be patient. The phone will update, and once it reboots into normal mode, you'll know it's updated by going to "Settings" and if they are grouped into different sections, then you have ICS. Otherwise, you probably still have GB.
II) How to enter ODIN Mode:
For the Exhilarate I've found it's best to use this sequence:
1) Power phone down
2) Plug the USB cable into your computer (do not plug the phone into the USB cable yet).
3) While pushing and holding both the vol up and vol down buttons, plug the phone into the computer. As soon as you see "SAMSUNG" flash and then dissappear, release the buttons.
4) Phone should boot into ODIN mode.
III) How to Root
What you need:
1) Samsung Galaxy Exhilarate phone (unrooted)
2) microSD Card (any size of 1GB or larger will work)
3) USB cable to connect your phone to your computer
4) Files below
First, download all the files...
1) Download the latest version of ODIN here: ODIN.
2) Download the drivers here: Samsung Galaxy Drivers and run the setup program after unzipping.
3) Download the tar file here: www.Shabbypenguin.com/OUDstuff/Blaze4G/Clockworkmod-Blaze-4G.tar Don't mess with it, just download it somewhere where you can find it later
4) Download SuperUser here: SuperUser Save it somewhere where you can find it later.
Second, conduct the root:
1) Put your phone into Odin (Download mode - see Section II above).
2) With phone in ODIN mode, run Odin.1.85.exe (it's in the folder where you unzipped ODIN too).
3) Odin will launch on your computer. It should show, in the first box under ID:COM, a port in yellow. Mine was Port 5. This means you have successfully connected to your phone.
4) Click the button in ODIN labeled "PDA", and then browse to the .tar file you downloaded above and then select "Open". The file will show up next to the PDA button.
5) Make sure that "Re-Partition" is NOT checked!;
6) Click "Start" and wait till your phone reboots. It should reboot into normal mode. If it doesn't, just power down and reboot into normal mode.
7) Copy the SuperUser.zip file you downloaded above to your phones microSD card.
8) Reboot the phone into recovery mode: While pushing and holding both the vol up and vol down buttons, push the power button. As soon as you see "SAMSUNG" flash, release the buttons. You shouldn't need to have the phone connected to the computer this time. The phone will boot into CWM recovery.
9) using either: the "menu" button to move down and the "home" button to move your selection up; or alternately the volume down button to move down, and the volume up button to move up: highlight "install zip from sdcard". Use the "search" button or power button to select/enter.
10) highlight "choose zip from sdcard" and press the "seach" button to select it.
11) browse to the directory which you copied SuperUser to and select it.
12) scroll down to "Yes - Install Superuser" and select it.
13) Once done, reboot your phone into normal operating mode.
14) If rooting Gingerbread, see Section IV below.
15) If rooting either Gingerbread or ICS, see section V below.
16) If having issues with Root, see section VI below.
IV) Rooting Gingerbread?:
Last: Finish up (Steps 1-4 are ONLY needed if you are still using GingerBread and not Ice Cream Sandwich):
NOTE: Your buttons (the four at the bottom) WILL NOT work at this point. You need to do the following:
======
1) Push your phone dialer as if you were going to make a call.
2) Dial *#*#2663#*#*.
3) You will see the attached thumbnail below on your phone (stolen from j3r3goss).
4) press the bottom button that says "Touch key FW update". Wait. Once it's finished, your bottom row of buttons will work again!
Note: If you are on GB, and not ICS, every time you boot into recovery and then back into operational mode, you will need to do the four steps in this section above!
======
V) Using either GB or ICS:
You do need to do these last steps (I believe):
5) ADDENDUM/UPDATE: At this point, there is one last thing you need to do!: You must go to "Settings/Applications/Development" and Enable USB Debugging! If you don't do this, you will NOT be able to get root access! Also, if for any reason you turn off USB Debugging, make sure you turn it back on! If you lose root access, check this FIRST! If you still can't get root access, boot into recovery mode and wipe the Dalvik Cache, the regular Cache, and "Fix Permissions". Then double check to make sure USB Debugging is ENABLED!
6) You're done! Your phone is now rooted and you can do whatever you want! :highfive:
VI) TROUBLESHOOTING:
If you run into problems
1) Check to make sure that SuperUser is installed on your phone. Check the apps section first, and then, use RootExplorer and check the System/bin folder. If you see SuperUser is in the system/bin folder, then you are very close to being rooted.
If it is not installed:
a) make sure that you copied the superuser.zip file to the EXTERNAL sdcard.
i) Boot the phone up normally
ii) plug the phone into your computer, pull the notification bar down, select USB connection, and tap the "Connect USB storage" button.
iii) Using Winbloze explorer, copy the SuperUser.zip to the external sdCard (on my computer, it is drive F:, and the Internal is drive G.
iv) disconnect once the copy is finished and use any file explorer on your phone to check the contents of the external sdCard (look in the "sdcard/external_sd" folder)
v) if it's not there, then you are doing something wrong. If it is there, shut down the phone, and boot into CWM recovery.
vi) Use CWM recovery to install the superuser.zip file on your phone.
vii) reboot into normal mode
viii) check to make sure that you have enabled USB Debugging
viii) check again to see if SuperUser is now in your apps, and in the system/bin folder.
ix) Run SuperUser 1x, and then close it out.
x) Run ANY app that requires Root Permissions. You should get a request from SuperUser to "Allow" or "Deny" the app root access. Make sure you allow root access. If you make a mistake, you'll need to launch superuser again and completely remove the app from the denied list.
2) Make sure USB Debugging is enabled.
3) if you still can't get root, boot into CWM Recovery, and try clearing the cache and the Dalvik cache, and resetting permissions, then reboot and check everything again. You may need to do this last step several times.
Beyond that, I don't know what else might be causing you to not gain root access, so keep trying.
If anyone has any questions, feel free to PM me.
V/R
BlackWolf
Thanks for the write-up Black-wolf.
I wasn't aware that the touch key fw needed to be updated each time after booting recovery,hopefully that is something that will be fixed when Shabbypenguin gets his hands on the stock recovery.
Personally I find the easiest, works every time method to get into Download mode is to have the usb cable plugged into the pc, then while holding the volume up/down buttons, plug the cable into the phone, continue holding vol up/down buttons until download mode boots.
Sent from my Liberty using xda premium
j3r3goss said:
Thanks for the write-up Black-wolf.
I wasn't aware that the touch key fw needed to be updated each time after booting recovery
Click to expand...
Click to collapse
Yeah, I figured that out when I went to boot recovery to check something, and then came out of it and the keys weren't working again... :/ At least there's a work around. I suspect, that this is something that an automated app could handle if Shabby or someone else doesn't come up with a permanent fix.
V/R
BlackWolf
Can someone update the links??.....
Fixed
JUSMEJOSE said:
Can someone update the links??.....
Click to expand...
Click to collapse
Links are all working now. There was only one broken one that I'm aware of. Let me know if there are others.
BlackWolf
Any update on getting the stock recovery? I blew through rooting my Exhilarate before I noticed the request for help or I would have offered.
The root seems to be working OK for me. JuiceDefender is working great with it to throttle the CPU clock speeds and has really improved my battery life. Also worked OK in blocking all the bloatware apps with the Gemini App Manager. So I don't really have a reason to unroot and go back to stock firmware, but it would be nice to have the option available should I ever hit a problem.
Thanks for all you guys hard work!
DK
I just needed this tutorial!, Good job.
Thanks!
Dream_Killer said:
Any update on getting the stock recovery? I blew through rooting my Exhilarate before I noticed the request for help or I would have offered.
The root seems to be working OK for me. JuiceDefender is working great with it to throttle the CPU clock speeds and has really improved my battery life. Also worked OK in blocking all the bloatware apps with the Gemini App Manager. So I don't really have a reason to unroot and go back to stock firmware, but it would be nice to have the option available should I ever hit a problem.
Thanks for all you guys hard work!
DK
Click to expand...
Click to collapse
domobile said:
I just needed this tutorial!, Good job.
Thanks!
Click to expand...
Click to collapse
Dream_Killer: No, we have not gotten a stock recovery. I've had several inquiries into it, but so far as I know, Shabby has not been able to help out in this regard. I am willing to try myself, but I'll need an un-rooted (and it must never have been rooted) phone.
domobile: Glad it worked for you.
V/R
BlackWolf
Black-wolf said:
Dream_Killer: No, we have not gotten a stock recovery. I've had several inquiries into it, but so far as I know, Shabby has not been able to help out in this regard. I am willing to try myself, but I'll need an un-rooted (and it must never have been rooted) phone.
domobile: Glad it worked for you.
V/R
BlackWolf
Click to expand...
Click to collapse
To get into stock recovery you...
1. open a command terminal on your computer.
2. type cd (where ever you have your ADB located on your computer) for example my is located in desktop/platform-tools so the command would be "cd desktop/platform-tools"
3. type "adb"
4. type "adb reboot recovery"
Presto you are in stock recovery.
ChefAnt said:
To get into stock recovery you...
1. open a command terminal on your computer.
2. type cd (where ever you have your ADB located on your computer) for example my is located in desktop/platform-tools so the command would be "cd desktop/platform-tools"
3. type "adb"
4. type "adb reboot recovery"
Presto you are in stock recovery.
Click to expand...
Click to collapse
We know how to boot into the stock recovery. What we need is to pull the stock recovery image off of the phone so that we can restore the phone to stock.
Btw.. pressing both volume keys while turning on the phone will get you there also.
I rooted the exhilarate. Loaded the t mobile blaze cm7 rom. And all works like a charm. The only thing is you can't make a call. You can,you just can't hear. I called my other phone and it went through. The speaker doesn't work. Mms and all works. Just not the speaker...... why? This wud. Be a awsome rom for this phone.. think we can find a fix?
harley1rocker said:
I rooted the exhilarate. Loaded the t mobile blaze cm7 rom. And all works like a charm. The only thing is you can't make a call. You can,you just can't hear. I called my other phone and it went through. The speaker doesn't work. Mms and all works. Just not the speaker...... why? This wud. Be a awsome rom for this phone.. think we can find a fix?
Click to expand...
Click to collapse
I'm not exactly sure but it might be just as simple as replacing the audio libs on the blaze rom with the ones from the exhilarate. I'm not sure which files though.
I'm curious if by coming together (blaze and exhilarate users) if there would be enough interest to get official cm support. if the only major diff is audio they could basically support 2 devices for the price of one.
Sent from my SAMSUNG-SGH-I577 using xda premium
If i knew/or had the kno how,shoot id do it. Is there a program u need to change the libs?. This is a pretty sweet device.
i think you just need root explorer, and copy the new ones over the old ones. I'll look to see if i can find out which files need swapped. Should be able to make a zip to flash through CWM recovery.
Sent from my SAMSUNG-SGH-I577 using xda premium
Man,im good at alotta things,buildin houses,workin on diesels,and flashin roms to my s3 and note,what i cant figure out is building roms. Im sure gettin this speaker workin has somthin 2 do with dismantling blaze cm7 rom and find the fix.
Another words,im good,but not that good. If som1 held my hand thru it,i cud do it. Or just show me
NFC for Exhilarate!
All: rodracruz found a thread for enabling NFC on AT&T phones. Apparently, the Samsung Exhilarate does have NFC - but why the hell AT&T has it disabled, I have not idea... In any case, check out this thread and follow the instructions to enable it on your phone: http://forum.xda-developers.com/showthread.php?t=1545751
There are even links as to some of the things you can do with NFC.
V/R
BlackWolf
Black-wolf said:
All: rodracruz found a thread for enabling NFC on AT&T phones. Apparently, the Samsung Exhilarate does have NFC - but why the hell AT&T has it disabled, I have not idea... In any case, check out this thread and follow the instructions to enable it on your phone: http://forum.xda-developers.com/showthread.php?t=1545751
There are even links as to some of the things you can do with NFC.
V/R
BlackWolf
Click to expand...
Click to collapse
Sweet, I was wondering, especially since this phone was released after the skyrocket.
Wolfman
Worked beautifully. You the man!
Thx
j3r3goss said:
I'm not exactly sure but it might be just as simple as replacing the audio libs on the blaze rom with the ones from the exhilarate. I'm not sure which files though.
I'm curious if by coming together (blaze and exhilarate users) if there would be enough interest to get official cm support. if the only major diff is audio they could basically support 2 devices for the price of one.
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
I'm pretty sure it wouldn't have anything to do with the audio lib files. More so most likely a kernel, modem, or APN problem.
Edit: not to mention the build.prop is completely written for the blaze. I'm working on some things. I'll let you guys know tonight. I wish there was source for this damn phone.
ChefAnt: There is a stock file from Samsung... read my post (about 2/3 of the way down):
http://forum.xda-developers.com/showthread.php?t=1828426
ChefAnt said:
I'm pretty sure it wouldn't have anything to do with the audio lib files. More so most likely a kernel, modem, or APN problem.
Edit: not to mention the build.prop is completely written for the blaze. I'm working on some things. I'll let you guys know tonight. I wish there was source for this damn phone.
Click to expand...
Click to collapse
THIS METHOD:
- ONLY WORKED FOR ICS (Android 4.0.x)
- IT WILL NOT WORK FOR THE SGS3 RUNNING JELLY BEAN (Android 4.1.x)
But I hate it when threads say that ^ or worse...
they don't get updated and you read it and/or try it for NOTHING!
So here you go...
CLICK HERE FOR AN AWESOME JELLY BEAN THREAD
Step by step guide to Root your phone, Unlock the bootloader, and then install ClockWorkMod Recovery. Also some unnecessary mods at the bottom if you're interested. I know there is another really well written guide for rooting the SGS3 and other mods but I wanted to post this and hope to get it sticky'd for the beginners
************************************************************
DISCLAIMER:
I am not responsible for any damage that happens to your device. I've made this guide as simple as possible and include less risky methods to achieve root and simple modifications. If you follow a link from this guide I am not responsible for the content on that page, read it in full yourself.
************************************************************
Confirmed working with newest VZW update/patch:
I535VRALG1
I535VRALG7
I535VRALF2
I535VRLHE -- Thanks DHamilton44!
GETTING ROOTED:
Navigate to https://www.dropbox.com/sh/1aksh2bikfsne43/wmpWRj7Und
Download:
- Verizon_Wireless... (USB Drivers for SGS3)
- Root Debug FS.7z... (7zip (freeware) file used to one-click root)
Credit to Noxous Ninjas as he created this program. It's the best I've found to easily root my S3 without feeling the need to baby sit the phone during rooting.
Thanks Droidstyle for reminding me about the credits Noxous Ninjas deserves!
Install (Computer):
- USB drivers
- Unzip Root Debug tool to a folder of your choice
Enable USB Debugging and Unknown Sources (Phone):
- Settings -> Developer Options -> Tick USB debugging
- Settings -> Security -> Tick Unknown source
Plug in phone to computer using OEM USB cable:
- Allow the drivers to complete (the little balloon pop-up in the right hand corner will say "Device ready/installed" -something to that effect)
MUST BE RAN AS ADMINISTRATOR
Navigate to your extracted Root Debug FS folder (Computer):
- Double-click "RootDebugfs"
- Choose option 1 (press 1 and then enter)
- Read the disclaimer, IF YOU AGREE, press y, then enter
- USB drivers reminder appears, press any key to continue
- Unknown Sources/USB Debugging reminder appears, press any key to continue
- Yet another informational message appears (READ THIS ONE), then press any key to continue
- Root process starts -> WAIT UNTIL IT COMPLETES | DO NOT UNPLUG YOUR DEVICE
- Once complete you will need to open the Superuser app and click through the initial dialog to actually start the program/allow it to run in the background. -- Thanks Whyzor!
ON YOUR PHONE: Navigate to https://www.dropbox.com/sh/1aksh2bikfsne43/wmpWRj7Und
Download the following from the APKs folder:
- ez_unlock.apk (Also found on Google Play store, free)
- rom_manager.apk (Also found on Google Play store, free)
- Normally when downloading them right to your phone it will immediately prompt you to install them, choose install in both instances
- Open your app drawer and open EZ-Unlock
- Accept/Grant the app SuperUser permissions, select Unlock, you should hear "That was easy" and the word "Unlocked" should show in green at the top of the screen
BEFORE CONTINUING: it is recommended that you are connected to a stable WiFi network to ensure a successful flash!
- Open your app drawer again and open ROM Manager
- Select "Flash ClockworkMod Recovery"
- Find and select "Samsung Galaxy S3 (Verizon)"
- You'll see the blue bar at the top indicating progress, when it nears the end you'll need to Accept/Grant the app SuperUser permissions
- You may receive a message that Touch recovery is available, install if you'd like (I have read some posts a week or two ago about Touch recovery not always working flawlessly though, just FYI)
***AT THIS POINT ROOTING, BOOTLOADER UNLOCKING, AND CWM RECOVERY ARE COMPLETED/INSTALLED***
RECOMMENDED! BUT OPTIONAL: MAKING A NANDROID BACKUP
- I would recommend having your preferred apps and home screens set up prior to making a recovery
- From the ROM Manager application select "Reboot into Recovery"
- FYI: Recovery mode can be entered manually as well, turn the phone off.
- While off, press AND HOLD Vol. Up, Home, Power
- Once you see the "Samsung" boot screen you can release (There will also be some blue text in the top left hand corner, this indicates recovery mode is booting)
- Recovery mode navigation: Vol. Up/Down moves the selection, Power selects it
- Select "backup and restore"
- Select "backup to external sdcard"
- Wait for it to finish (Usually takes about 5 minutes)
- Select back to get to the main menu
CONGRATS!
- If all that worked your phone is now rooted and (hopefully) a backup has been made after rooting. This way if you start tinkering and break something you can (hopefully) restore back to this recovery.
REMOVE PERSISTANT/ONGOING WIFI NOTIFICATION AND POPUP (REQUIRES ROOT)
ON PHONE: Navigate to Google Play https://play.google.com/store/apps/details?id=com.speedsoftware.sqleditor
- Download: SQLite (Yes it's a paid app, support our Devs!)
- Open the app, Accept/Grant the app Superuser permissions
- Select Settings Storage
- Select settings.db
- Select system
- Long-press "wifi_offload_network_notify"
- Select "Edit Record"
- Change the value field to "0" (zero)
- Select Save
- Press back key
- Select "Secure"
- Long-press "wifi_networks_available_notification_on"
- Select "Edit Record"
- Change the value field to "0" (zero)
- Select Save
- Reboot your phone
UI MODS (Not necessary but are definitely improvements in the UI)
- Notification bar toggles mod: http://forum.xda-developers.com/showthread.php?t=1775235
- More (personalized versions): http://forum.xda-developers.com/showpost.php?p=28829000&postcount=67
--Above files are flashed using recovery
HOW TO: FLASH A .ZIP USING RECOVERY (REQUIRES ROOT & UNLOCKED BOOTLOADER)
**ONLY FLASH A ZIP UPDATE THAT IS COMPATIBLE WITH YOUR MODEL AND OS**
- Know where you downloaded the file to (Preferrably external SD card)
- Reboot into recovery
- Choose "install zip from sdcard"
- Choose "install zip from (external) sdcard" -or wherever you saved it
- Choose the desired file you want to flash
- Scroll up (it's quicker) to select "Yes - ..."
- The file(s) will flash (progress at bottom), once it's done you can flash another or go back to the main menu and reboot!
Great write up. This should be sticked instead of the tutorials that are already there.
I'm having trouble getting rid of the persistent wifi notification, i have successfully achieve root, and flashed cwm. I go to edit record and the value is already a "0". any idea whats up here? i flashed one of those ui customizations you linked too if that matters.
That Baker Guy said:
I'm having trouble getting rid of the persistent wifi notification, i have successfully achieve root, and flashed cwm. I go to edit record and the value is already a "0". any idea whats up here? i flashed one of those ui customizations you linked too if that matters.
Click to expand...
Click to collapse
One of the toggle customizations shouldn't bother it. There are 2 records to edit though, did you make both 0?
Relayed from the moon to xda via my handheld beam machine!
Nice job on the guide!
eMpTy43 said:
One of the toggle customizations shouldn't bother it. There are 2 records to edit though, did you make both 0?
Relayed from the moon to xda via my handheld beam machine!
Click to expand...
Click to collapse
wow, im dumb, i only saw the first record that needed editing, thanks for pointing that out
That Baker Guy said:
wow, im dumb, i only saw the first record that needed editing, thanks for pointing that out
Click to expand...
Click to collapse
No prob! Glad you got it going!
Relayed from the moon to xda via my handheld beam machine!
Been wanting to root my phone but have been too busy to do the research. I might take the plunge now, thanks to your guide. Sounds pretty straightforward.
Sent from my Xoom using xda premium
nattygirl said:
Been wanting to root my phone but have been too busy to do the research. I might take the plunge now, thanks to your guide. Sounds pretty straightforward.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Go for it! If you have any questions just reply on the thread. I've got my notifications on.
Relayed from the moon to xda via my handheld beam machine!
Thanks Man!!! You made it easy breezy.
Surprised this hasn't been stickied yet!
Sent from my Cocaine White S3.
lol im the guy who hates to read more of the visual guy, found a youtube video on how to root the phone after rooting what else should i do in order to gain complete access
eMpTy43 said:
Go for it! If you have any questions just reply on the thread. I've got my notifications on.
Relayed from the moon to xda via my handheld beam machine!
Click to expand...
Click to collapse
Just rooted!!!! Couldn't be any easier!!! Now time to start flashing!!!
---------- Post added at 08:52 AM ---------- Previous post was at 08:08 AM ----------
HELP!!!!
Followed this to a "T". Everything went smoothly and appeared successful until I flashed a rom. I flashed Jellybean CM10 for VZW. Now all I get is a screen that says "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.".
I tried booting into recovery manually so I could do restore my backup, but i can't even get back into it. It just keeps taking me to this screen.
Followed the guide to return to stock using odin and repeated all of these steps.... i'm back in business now.... phew!!!!
This is Noxous Ninjas root Tool! its pretty obvious when it says "Noxious Ninja" at the top of the program. Download both versions and compare them.
http://forum.xda-developers.com/showthread.php?t=1792342
This guide is the best I've read yet!
I've been casually reading these forums for over two years and still haven't decided to lose my rooting virginity, probably because every guide always seems so damn confusing. This looks nice and simple.
3 questions:
1- If I'm not going to be putting on a custom ROM yet, do I need to continue and install CWM right away? Can I just wait and do it when I finally take the next step? (I really just want to root to get rid of some bloat for right now. I know I'll last a day though where I start wanting to use mods and tweaks though, will I need to install CWM for that?)
2- Can I just ODIN back to stock instead of bothering with a Nandroid backup? I keep nothing on my phone that I feel is of importance for backing up. Everythings in the cloud.
3- When I go to flash my first ROM, does it need to be on the internal SD or on the external SD card (I have a jillion laying around, but they are only 2GB a piece)?
Thanks!
droidstyle said:
This is Noxous Ninjas root Tool! its pretty obvious when it says "Noxious Ninja" at the top of the program. Download both versions and compare them.
http://forum.xda-developers.com/showthread.php?t=1792342
Click to expand...
Click to collapse
I'll put credits in my OP. Didn't mean to imply that was my work at all! That was just the most straight forward and one-click program I'd found to root the S3.
bbeelzebub said:
This guide is the best I've read yet!
I've been casually reading these forums for over two years and still haven't decided to lose my rooting virginity, probably because every guide always seems so damn confusing. This looks nice and simple.
Thank you
Click to expand...
Click to collapse
bbeelzebub said:
1- If I'm not going to be putting on a custom ROM yet, do I need to continue and install CWM right away? Can I just wait and do it when I finally take the next step? (I really just want to root to get rid of some bloat for right now. I know I'll last a day though where I start wanting to use mods and tweaks though, will I need to install CWM for that?)
Click to expand...
Click to collapse
Even if you don't flash a custom ROM or custom .zip update a backup is nice to have in case you make one little tweak that breaks something. Eliminates the hassle of having to flash back to stock and start from scratch again.
bbeelzebub said:
2- Can I just ODIN back to stock instead of bothering with a Nandroid backup? I keep nothing on my phone that I feel is of importance for backing up. Everythings in the cloud.
Click to expand...
Click to collapse
You sure can. Keep in mind ODIN flashing does have a higher risk than a Nandroid backup. You simply cannot perma-brick your phone if there is no cable plugged into it.
bbeelzebub said:
3- When I go to flash my first ROM, does it need to be on the internal SD or on the external SD card (I have a jillion laying around, but they are only 2GB a piece)?
Click to expand...
Click to collapse
Having either a full ROM or a .zip update ROM flash on the external SD is the best scenario. Part of a nice clean install is to make sure a factory reset was done (which wipes the internal SD). If your ROM is on the internal SD... well you know the rest lol
Thanks! Just want to make sure folks are properly credited for thier work...and again nice guide!
i have been stuck on the odin downloading screen and command prompt is still looking for device to be detected. i waited till it installed the driver now what ?
prztruspaz said:
i have been stuck on the odin downloading screen and command prompt is still looking for device to be detected. i waited till it installed the driver now what ?
Click to expand...
Click to collapse
This guide doesn't use download mode. Reset your phone and start from the top.
Relayed from the moon to xda via my handheld beam machine!
Hi,
Background:
I am a retired software engineer. I worked on the windows platform and focused on the Visual Basic family of code though I was familiar with many languages from assembly to C. I am very familiar with the programming jargon but find myself at a loss when reading to posts here, so bear with me if I don’t have a complete grasp on the terminology.
My Story:
I have an AT&T Samsung Infuse with android v2.3.6 and have been very happy with it. This is my first smartphone and didn’t pay much attention to how it worked until now. I bought an irrigation controller that has an app for the phone. After installing the controller, I found out the app only runs on v3.0 or newer (mine is v2.3.6). So, here I am trying to upgrade my phone to a newer version so the app will work (trying not to buy a new phone for this). My first goal was to back up everything, so I spent a number of days reading threads here trying to understand what I needed to do. I discovered that v3.0 is a tablet only OS (not completely sure about this). I researched the different version and thought that v4.3 or v4.4 would be the final goal. This lead me to finding a path that required going through v4.0 to get there (please correct me if I have drawn the wrong conclusion on this). I could not find a way to back up the OS without stumbling on the instructions to either root the phone and/or wipe the data and cache to install something.
What I have done so far:
1). I paid to have my phone rooted. The apps I installed would not back up the entire OS and my recovery did not have an option to do that.
2).I followed [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g instructions. I was able to back up the entire rom from the red recovery.
3).Next I followed the [Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012) instructions. I was now up in the v4.0.4 OS but did not have any of my applications or any of my old data.
4). I redid step 2 and restored the backup I made and was back on v2.3.6 again.
5). I installed fx w/root, Easy Back, then step 3 and got some of what I wanted but no apps. So step 4 again. I did this again with My Backup Root (MBR). I had a backup of my apps this time but they would not install in v4.0.4. So I did step 4 once more.
And yes I have been bitten by a boot loop. I did something wrong after I got it to 4.0.4 once. Not sure what it was.
Questions:
1). Is (was) there a way to back up the OS(ROM) from my vanilla v2.3.6 so I had a true representation of my original phone? Seems like a bit of a catch 22.
2). When I was on v4.0.4, I could not find settings/application to change both my USB settings and Playstore options. This caused the restore to fail because it was not from the playstore. I was able to use fx to find the backup file, select an apk file and try to restore it that way. It told me it was not a playstore app, but gave me a link to settings/Application so I could change it. Then I restored the app successfully. Then I went back to MBR and tried to restore the data for that app, it failed. Now that the Playstore option was turned off, I tried to restore from MBR. This went successfully but the restore of the Data failed because the app was not installed. I am thinking that there is a difference in the folder structure that is causing this (maybe to do with MTD). I was not able to turn on the Setting/Application/Playstore option. Where did the Settings/Application option go in v4.0.4?
3) Is there a way to backup up applications from v2.3.6 and restore them to v4.0.4 (or any 4.0 + version)? I could do it one at a time from the MBR backup but not the applications data.
4). I noticed that in v4.0.4 there was a screen after the first Samsung one that said Galaxy S. Can this be changed?
5). After the Galaxy S screen (again in v4.0.4) came a screen with a stickman and real intense flashing. Can this be changed?
6). How can I find the most stable ROM to use? is there a list of available ROMs all the way to v4.4?
I am sure I will have more questions, Thanks
Shoraht said:
Hi,
Background:
I am a retired software engineer. I worked on the windows platform and focused on the Visual Basic family of code though I was familiar with many languages from assembly to C. I am very familiar with the programming jargon but find myself at a loss when reading to posts here, so bear with me if I don’t have a complete grasp on the terminology.
My Story:
I have an AT&T Samsung Infuse with android v2.3.6 and have been very happy with it. This is my first smartphone and didn’t pay much attention to how it worked until now. I bought an irrigation controller that has an app for the phone. After installing the controller, I found out the app only runs on v3.0 or newer (mine is v2.3.6). So, here I am trying to upgrade my phone to a newer version so the app will work (trying not to buy a new phone for this). My first goal was to back up everything, so I spent a number of days reading threads here trying to understand what I needed to do. I discovered that v3.0 is a tablet only OS (not completely sure about this). I researched the different version and thought that v4.3 or v4.4 would be the final goal. This lead me to finding a path that required going through v4.0 to get there (please correct me if I have drawn the wrong conclusion on this). I could not find a way to back up the OS without stumbling on the instructions to either root the phone and/or wipe the data and cache to install something.
What I have done so far:
1). I paid to have my phone rooted. The apps I installed would not back up the entire OS and my recovery did not have an option to do that.
2).I followed [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g instructions. I was able to back up the entire rom from the red recovery.
3).Next I followed the [Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G (07/28/2012) instructions. I was now up in the v4.0.4 OS but did not have any of my applications or any of my old data.
4). I redid step 2 and restored the backup I made and was back on v2.3.6 again.
5). I installed fx w/root, Easy Back, then step 3 and got some of what I wanted but no apps. So step 4 again. I did this again with My Backup Root (MBR). I had a backup of my apps this time but they would not install in v4.0.4. So I did step 4 once more.
And yes I have been bitten by a boot loop. I did something wrong after I got it to 4.0.4 once. Not sure what it was.
Questions:
1). Is (was) there a way to back up the OS(ROM) from my vanilla v2.3.6 so I had a true representation of my original phone? Seems like a bit of a catch 22.
2). When I was on v4.0.4, I could not find settings/application to change both my USB settings and Playstore options. This caused the restore to fail because it was not from the playstore. I was able to use fx to find the backup file, select an apk file and try to restore it that way. It told me it was not a playstore app, but gave me a link to settings/Application so I could change it. Then I restored the app successfully. Then I went back to MBR and tried to restore the data for that app, it failed. Now that the Playstore option was turned off, I tried to restore from MBR. This went successfully but the restore of the Data failed because the app was not installed. I am thinking that there is a difference in the folder structure that is causing this (maybe to do with MTD). I was not able to turn on the Setting/Application/Playstore option. Where did the Settings/Application option go in v4.0.4?
3) Is there a way to backup up applications from v2.3.6 and restore them to v4.0.4 (or any 4.0 + version)? I could do it one at a time from the MBR backup but not the applications data.
4). I noticed that in v4.0.4 there was a screen after the first Samsung one that said Galaxy S. Can this be changed?
5). After the Galaxy S screen (again in v4.0.4) came a screen with a stickman and real intense flashing. Can this be changed?
6). How can I find the most stable ROM to use? is there a list of available ROMs all the way to v4.4?
I am sure I will have more questions, Thanks
Click to expand...
Click to collapse
1. when updating unless you have a google account synced for contacts and apps....it all disappears when you jump from gb to ics to jb to kk
2.the only apps that will back up to the google account will be ones downloaded from the playstore..minus the data
3. that galaxy s screen will stay all the way to 4.4.3 kk
4.you can always change the bootanimation in custom roms (the stickman screen)
5.CarbonRom so far most stable 4.4.3 kk rom https://carbonrom.org/downloads/?device=infuse4g&type=nightly flash with these gapps http://forum.xda-developers.com/showthread.php?t=2397942
6. after a certain point you cant flash a GB backup on KK cwm cause it will cause brick so if you want to go back to stock use heimdall or odin to do so
7.most of the apps on a gb roms wont run on ics or higher same with ics apps and jb apps
6th_Hokage said:
5.CarbonRom so far most stable 4.4.3 kk rom https://carbonrom.org/downloads/?device=infuse4g&type=nightly flash with these gapps http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
Thanks for the reply
Can I go directly to 4.4.3 from 2.3.6 or do I need to step through 4.0.x like the others? I can't seem to find any specific instructions for them.
There are only nighty's at that link, no releases. How do I know what version they are (4.4.2/4.4.3)? I think it is the one dated 4/19/14.
Thanks again.
Shoraht said:
Thanks for the reply
Can I go directly to 4.4.3 from 2.3.6 or do I need to step through 4.0.x like the others? I can't seem to find any specific instructions for them.
There are only nighty's at that link, no releases. How do I know what version they are (4.4.2/4.4.3)? I think it is the one dated 4/19/14.
Thanks again.
Click to expand...
Click to collapse
go to the channel log https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/pub if you look at it itll tell you updating to 4.4.3 no nightlys or something like that but right now all the latest nightlys are 4.4.3......sorry not linking you to that before and they may be nightlys but they are stable im running the latest one at the moment
---------- Post added at 01:57 PM ---------- Previous post was at 01:39 PM ----------
and som infuse phones have been able to jump to kk from stock with red cwm with lagfix turned off.....http://forum.xda-developers.com/showthread.php?t=2773833 look here for som more info
6th_Hokage said:
go to the channel log https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/pub if you look at it itll tell you updating to 4.4.3 no nightlys or something like that but right now all the latest nightlys are 4.4.3......sorry not linking you to that before and they may be nightlys but they are stable im running the latest one at the moment
---------- Post added at 01:57 PM ---------- Previous post was at 01:39 PM ----------
and som infuse phones have been able to jump to kk from stock with red cwm with lagfix turned off.....http://forum.xda-developers.com/showthread.php?t=2773833 look here for som more info
Click to expand...
Click to collapse
Thanks,
I missed your update
Shoraht said:
Thanks,
I missed your update
Click to expand...
Click to collapse
have you been able to update?
6th_Hokage said:
have you been able to update?
Click to expand...
Click to collapse
I will try tomorrow. I will post the results
Thanks.
6th_Hokage said:
and som infuse phones have been able to jump to kk from stock with red cwm with lagfix turned off.....http://forum.xda-developers.com/showthread.php?t=2773833 look here for som more info
Click to expand...
Click to collapse
Got RiseFox to try my method and it work out for him also and probably work for others too.. Skip ICS and JB
scmfxt said:
Got RiseFox to try my method and it work out for him also and probably work for others too.. Skip ICS and JB
Click to expand...
Click to collapse
i went back to stock to see if your method would work and it did even jumping to 4.4.4 kk
scmfxt said:
Got RiseFox to try my method and it work out for him also and probably work for others too.. Skip ICS and JB
Click to expand...
Click to collapse
OK, I am about to try this but have a couple questions. In other instructions, the clear cache (step 6a,b and c) is done before the flash, yours is after. What is the difference between the two methods? In step 3 you say "DISABLE vodoo lagfix and /system lagfix". I have CWM v2.5.1.3. I can see the option for vodoo lagfix but not /system lagfix. What is /system lagfix and where can I find this option?
[UPDATE] I found /system lagfix. it shows after selecting the voodoo lagfix option.
I am also making the assumption that because I got CWM v2.5.1.3 through [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g instructions, that I can skip step 1 thru 2c and start at step 3
OK,
Everything went well. Even better than I hoped. I can't remember what setting I changed to make this happen, but all the apps in playstore have been restored to the phone, even the free ones. I used Titanium to backup all my apps and then used it to restore the data for some apps like color notes. There is a setting that tells it to use the new locations instead of the original locations. I am a happy camper.
It will take a while for all this to finish, but this is what I was expecting.
I still can't find the equivalent option for Settings/Application from v2.3.6. Like, let me chose what USB mode when I plug it in? Most of the time I just use it to charge the phone. And where can I change the permission to restrict installing only apps from playstore?
Thanks your input.
Shoraht said:
I still can't find the equivalent option for Settings/Application from v2.3.6. Like, let me chose what USB mode when I plug it in? Most of the time I just use it to charge the phone. And where can I change the permission to restrict installing only apps from playstore?
Thanks your input.
Click to expand...
Click to collapse
Glad you got most everything working. The option you are looking for is under Settings > Security > Device Administration (heading), and it should be called Unknown Sources. Hope this helps.
Ok,
Now I am having a new issue. I can't seem to get any of the apps that move apps to the external sd to work. The option to move is missing in the storage section. I am running out of space in the 2gb partition. AppMgr III and App to SD can show me a list of apps that can be moved, but when selected, there is no Move button present. Am I using the wrong app for 4.4.3?
It would be nice if that 2gb partition could be made bigger.
Thanks for any advice.
Shoraht said:
OK, I am about to try this but have a couple questions. In other instructions, the clear cache (step 6a,b and c) is done before the flash, yours is after. What is the difference between the two methods? In step 3 you say "DISABLE vodoo lagfix and /system lagfix". I have CWM v2.5.1.3. I can see the option for vodoo lagfix but not /system lagfix. What is /system lagfix and where can I find this option?
Click to expand...
Click to collapse
It doesn't hurt to clear them and safer for new rom to boot up w/o residual data from previous version. Flashing from odin would wipe all data from your phone.. not your Internal SD card. Reason I did it after is because of the installing of sgs kernel flasher to flash Synthesis GB Kernel. If you didn't install anything then just wipe cache partition and dalvik cache are good enough.
[UPDATE] I found /system lagfix. it shows after selecting the voodoo lagfix option.
I am also making the assumption that because I got CWM v2.5.1.3 through [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root and CWM recovery option - Infuse 4g instructions, that I can skip step 1 thru 2c and start at step 3
Click to expand...
Click to collapse
Yes skip them if you already reached that part. The rest is simple enough to do once lagfix is disabled.
joel.maxuel said:
Glad you got most everything working. The option you are looking for is under Settings > Security > Device Administration (heading), and it should be called Unknown Sources. Hope this helps.
Click to expand...
Click to collapse
Thanks,
That solves the Application install option. I still need to find the USB connect option so I can select at connect.
OK, New problem,
Everything was working just fine. Then I unplugged the USB cable and went for a ride. No Mobile Data (no Internet). I checked all the settings That I know about (They moved them all of course) and it looks like everything is set right (though I am not an expert). Can anyone help me with this?
Thanks again
Shoraht said:
OK, New problem,
Everything was working just fine. Then I unplugged the USB cable and went for a ride. No Mobile Data (no Internet). I checked all the settings That I know about (They moved them all of course) and it looks like everything is set right (though I am not an expert). Can anyone help me with this?
Thanks again
Click to expand...
Click to collapse
Well, I found out that the APN was changed, not sure how. It is a good think my wife has the same phone that I can check or I would be going back to my stock image to find this.
Thanks,
So there is a bargain chinese 4G phone called the 'InFocus M512'.
The problem with it is that it comes without Google Apps and also is not rooted (sometimes is). Also it does not have CWM Recovery.
So this quick tutorial shows you how to root, install CWM Recovery and install google apps on the M512.
I'm not responsible for any damage
Rooting:
Method 1
1.Go to settings>>Security>>Check Unknown Sources tap OK.
2.Download this file.
3.Install
4.Run and tap 'get root' or somthing like that.
5.Delete KingRoot and some chinese app, but DO NOT DELETE KingUser!
6.Done!
Method 2
Flash CWM Recovery using the 2nd method from this post. If you have rooted usign the first method use method 1 from that post.
Download UPDATE-SuperSU-x.xx.zip (i used 2.46)
Reboot into CWM.
Select Install zip>choose zip from /sdcard>select UPDATE-SuperSU-x.xx.zip, press power button
Reboot now
GApps
1.Download this zip file
2.Reboot into CWM.
3.Select Install zip>choose zip from /sdcard>select the file, press power button
4.Reboot now.
How to delete KingUser (only if you have SuperSU and it is working)
Download ES File explorer, enable root explorer, go to /system/app and delete KingUser.
So this is how to get root, cwm and gapps on the m512.
First Method no good for me
I put the kingroot file in the adb tools folder and used the install command. It wasn't clear from the above whether the phone needed to be in recovery or some other mode so I tried a few times, in recovery mode and again just connected as an mtp device in the normal way. Either way the result was the same, it said "Invalid APK File: KingRoot.......".
I will have a go at the CWM thing next.
I am still on the 103A ROM that the phone came to me with - I have been trying, on and off, without success to update and then root it , for months.
When trying to flash an update ROM it tells me that the update package has unexpected contents and the there is an error in the update file and then says "Status 7". You can read all about my lack of success on this forum under the threads M512 started by Galaxy Why.
I'm trying, I really am....
Let me start by saying thanks for making the effort to post what you know and so to help people like me, however.
I tried to follow the method 2 (as I don't have root) from your other post (the one linked to above with the words "the 2nd method from this post" but got stuck.
Your instructions in normal my comments in italics.
Method 2: (No root)
1.Connect your phone via USB to your PC. OK
2.Enable MTP. OK
3.Enable USB Debugging. Settings>Developer Options> tick USB Debugging. OK
4.On your computer, 2 drives will appear: One of them is a CD-Rom which contains all drivers. OK
5.Click on that CD-Rom and it will install all drivers. It doesn't, or it may do, but what it definately does is asks me to put a disc in the drive and tries to do some kind of dir_all in windows explorer - I would post a screenshot here but this page only allows URL's- and I'm not sure how to go about that.. but I think I've managed to upload a screenshot....
After waiting for 5 minutes or so to see if something would happen as the green progress bar ground to a halt but the busy circle continued I hit the cancel button on the "please insert a disc dialogue" and then ploughed on anyway ....
6.Plug phone in again. Now this had me confused, I assume you mean unplug AND THEN plug the phone in again.
7.Download the .ZIP file and extract it somewhere. Which/what zip file do you mean exactly?? I couldn't get past this.
8.Click on _install_cwm_6.0.5.1.cmd
9.Your phone will ask you something, just tick "always allow from this computer" and hit OK.
10.Your phone will reboot into DL Mode, then it will reboot again.
11.Recovery is installed.
It's late and I'm tiring so sorry if missed something obvious. Any advice?
androo235 said:
Let me start by saying thanks for making the effort to post what you know and so to help people like me, however.
I tried to follow the method 2 (as I don't have root) from your other post (the one linked to above with the words "the 2nd method from this post" but got stuck.
Click to expand...
Click to collapse
Looks like you don't have a adb driver
And... why do you want to root your phone? Installing CWM is not root required.
M512 comes with a unlocked bootloader, just boot into bootloader and you can flash anything you like.
I made a customized stock rom based on version 2280, bloatwares removed and Google Play framework included. (You can download the apps back from Play Store, if you needs those)
Now the phone has 2.09GB free spaces :victory:
If you were interested on it, I can upload it and give you a link.
PochiMak said:
Looks like you don't have a adb driver
And... why do you want to root your phone? Installing CWM is not root required.
M512 comes with a unlocked bootloader, just boot into bootloader and you can flash anything you like.
I made a customized stock rom based on version 2280, bloatwares removed and Google Play framework included. (You can download the apps back from Play Store, if you needs those)
Now the phone has 2.09GB free spaces :victory:
If you were interested on it, I can upload it and give you a link.
Click to expand...
Click to collapse
I am interested in the custom rom you made for this phone. There's so little info on this model.
Lorien_Silmaril said:
I am interested in the custom rom you made for this phone. There's so little info on this model.
Click to expand...
Click to collapse
https://copy.com/3IfoZUCTCna1wa3U
The calendar is not working, you can install Google calendar from Play Store.
PochiMak said:
https://copy.com/3IfoZUCTCna1wa3U
The calendar is not working, you can install Google calendar from Play Store.
Click to expand...
Click to collapse
How do I install this?
GalaxyWhy said:
How do I install this?
Click to expand...
Click to collapse
Flash this ROM by a "3rd party recovery" = CWM
I just wonder how many of you are still using this device?
PochiMak said:
I just wonder how many of you are still using this device?
Click to expand...
Click to collapse
Just me, I think.
Can you give another link to your ROM, please, the one you put days ago doesn't works.
Thank you.
it's works for me. thx~
OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
I was going to write some very insulting message, but i don't want to fill this thread with stupid nonsense, as it is completely obvious that you have no clue what you are talking about... Just a few areas where i'v helped...
http://forum.xda-developers.com/showpost.php?p=38886073
http://forum.xda-developers.com/showpost.php?p=26608802
http://forum.xda-developers.com/showthread.php?p=34381433#post34381433
Yes that is my phone in post 3, as i was the first outside of the team to have a rooted LG optimus G, thanks to TeamCodefire, shellnut2, JCase, AutoPrime, thecubed, and many more that contributed to the lg root evolution. If you have any questions about my integrity, you can ask any of them...
I cleaned the offensive posts and the user was infracted. At the OP, thanks for managing this appropriately and not escalating it to a flame war.
Back on topic please.
These steps are NOT needed... Once you complete step 10 and reboot SuperSU is installed and accessible...
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
This is only a temporary solution for root... Why?
And, the Kingroot and Super Sume method works sometimes to get root without tripping KNOX! This info I also posted in another thread...
This recovery/root method will work for mostly ALL Samsung and Nexus devices that have a working recovery... Thanks to Chainfire for his hard work!
K94U said:
These steps are NOT needed... Once you complete step 10 and reboot SuperSU is installed and accessible...
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
This is only a temporary solution for root... Why?
And, the Kingroot and Super Sume method works sometimes to get root without tripping KNOX! This info I also posted in another thread...
This recovery/root method will work for mostly ALL Samsung and Nexus devices that have a working recovery... Thanks to Chainfire for his hard work!
Click to expand...
Click to collapse
Temporary solution is in the meaning of not fully rooted... This method is systemless, and if you want to make full init.d edits, i would not recommend using a systemless root option, as its kinda like a sudo root, for those that use linux, they will understand what i'm talking about. Yes you can allow root access to apps the request it, but as for full system modifications like the sound mixer, and init.d edits, i don't think i would go there, also not really sure if this will work with debloating, I'm not exactly sure about on samsung how it acts when you remove "system" apps (more so apps installed by default by samsung), I do know that one of the quickest ways to brick a lg is to remove system apps, and if you don't have an unlocked bootloader, as well as custom kernel, during boot, you get a kernel panic if system apps are removed, and in some cases has rendered the device unusable, (nothing an insurance claim couldn't fix tho... lol). Oh, and for the final steps, i actually did have to do them, I had no superuser app in my apps drawer, I attempted downloading from the playstore, and it was the wrong version SuperSU, and kept telling me i needed to update my binary. Then did steps 11-13, and all was nice in the world again, and no more nag about updating binaries, as well as it is the correct apk for the su binary that is flashed in step 10.
fiddy619 said:
Temporary solution is in the meaning of not fully rooted... This method is systemless, and if you want to make full init.d edits, i would not recommend using a systemless root option, as its kinda like a sudo root, for those that use linux, they will understand what i'm talking about. Yes you can allow root access to apps the request it, but as for full system modifications like the sound mixer, and init.d edits, i don't think i would go there, also not really sure if this will work with debloating, I'm not exactly sure about on samsung how it acts when you remove "system" apps (more so apps installed by default by samsung), I do know that one of the quickest ways to brick a lg is to remove system apps, and if you don't have an unlocked bootloader, as well as custom kernel, during boot, you get a kernel panic if system apps are removed, and in some cases has rendered the device unusable, (nothing an insurance claim couldn't fix tho... lol). Oh, and for the final steps, i actually did have to do them, I had no superuser app in my apps drawer, I attempted downloading from the playstore, and it was the wrong version SuperSU, and kept telling me i needed to update my binary. Then did steps 11-13, and all was nice in the world again, and no more nag about updating binaries, as well as it is the correct apk for the su binary that is flashed in step 10.
Click to expand...
Click to collapse
Im currently on 4.2.2 with rooted philz recovery.
How can i get to 5.x? If i use OTA I imagine id loose root.
this trick works ...my tab 4 never looked this better
HELP!!!
Having an issue with my sm-237p . Download mode is not allowing me to flash anything via odin. I am trying to root my tab. Recoveries nor firmware wil flash. it starts but never ,akes progress. please help
A samson sm-T237P is sheeped to Nigeria,the problem is that you cannot make call with it because it is not connected with the network here.
Is there an updated way to do this root? I can't get the files I need to root like this
fiddy619 said:
OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
Click to expand...
Click to collapse
Mjme34 said:
Is there an updated way to do this root? I can't get the files I need to root like this
Click to expand...
Click to collapse
Here's the magic: mega(dot)nz/#F!ZkARSbRI!SV3kQ6jmsi9eGwHoRKPfew
(sry first post.. they have rules against posting web links directly.. replace (dot) with . and you should have your recovery file)
had to do a bit of digging myself. The other files should be easy to find via Google.
fiddy619 said:
OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
Click to expand...
Click to collapse
Can you fix the link to the recovery says 404 not found
g7755725 said:
Can you fix the link to the recovery says 404 not found
Click to expand...
Click to collapse
Just Read the posts before yours, the link is right there.
There's a reason posts are added and not just replaced with new ones. This is only a 2 paged thread, not hard at all to read it all.
g7755725 said:
Can you fix the link to the recovery says 404 not found
Click to expand...
Click to collapse
Updated, but like bodyshop said... look up. No offense tho...
Thanks for this, however I can't get wifi to turn on. I saw mention in another thread about deleting wpa_supplicant.conf and using ODIN to upgrade to PF1 (could only find PH4 but it fails), but neither worked. Does anyone know of a fix?
thank you 403sc softbank
thank you for solution 403sc softbank
i find tools 7 hour
thank you again