[Q] Another method to root UCLB3 gingerbread update - Samsung Infuse 4G

After many many days and countless hours ive found a easier way to root UCLB3 2.3.6 gingerbread ATT official update. i have tried this on two different phones with success (HOWEVER TRY AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE. IM JUST SIMPLY STATING WHAT HAS WORKED FOR ME ON TWO DIFFERENT PHONES ONE BEING MY WIFES AND THE OTHER MY SONS.) Ok this is what i learned. The Captivate Glide and the Infuse are near identical in build properties, boot sequences and partitions. they were close enough for me to try this and it worked. OK follow the steps just as listed... I did this on a windows 7 pc so i am not sure about any others.
1. Download and save CWM recovery tar to your pc.
2. Download the Superuser-3.0.7-efghi-signed.zip from below and copy it to your phone via the usb cable. (you will need it in a few moments)
3. Make sure the proper drivers for your phone is installed on your pc. if not visit samsung mobile website download page for your device and download and install them.
4. Download and install Odin 1.85 if you do not already have it.
Ok thats all you need so now lets proceed with what you need to do. again follow these steps exactly or dont cry to me if it dont work.
1. make sure usb debbugging is checked on your phone.
2. turn phone off.
3. right click the odin file you downloaded earlier and click run as administrator.
4. put phone in download mode by pressing both volume up and down and power button while pluuging the phone via the usb in the computer.
5. once in download odin should recognize your phone if you took the time to make sure you had the right drivers for your phone. when odin recognizes your phone you will see a yellow com in the first window.
6. make sure repartition is NOT checked.
7. click the pda button and navigate to where you saved the cwm.tar file on your pc and select it.
8. then click go.
9. when done you will see the yellow box turn blue and say pass. if not you will see a red box that says fail. in that case go back and folow every step but do not unplug your phone from the pc until you see a blue pass. when flashing you will see it say recovery image dont panic this is normal.
10. after you get a blue pass and have successfully installed clockwork recovery reboot the phone into recovery mode by holding both volume up and down and press power untill you see the att logo then release the power button only.
11. once in recovery mode you will see install update from sd card. arrow down to that and press the power to select it. navigate to where you saved the superuser zip file at on your phone and select it. you may have to do this 3 or 4 times but keep doing it it will eventually root the phone and push superuser. one phone it took 3 tries and the other 4 tries.
12. when it installs succesfully reboot phone and make sure superuser is installed.
13. go to google market and down load two apps. one busybox install it, the other rom manager. install busybox first then rom manager.
14. open rom manager then click fix permissions. do not skip this. if you do dont wine to me about any apps that dont work any more or any force closes you may get.
and thats it. enjoy. as i said this worked for me twice with no problems but those are the exact steps i did and it worked for me....

hummmm?

http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
http://forum.xda-developers.com/showthread.php?t=1613523

Some more on the subject. Several ways to cook a stew.:
http://forum.xda-developers.com/showthread.php?p=24935969
Sent from my HTC_Flyer_P512_NA using Tapatalk 2

Related

Method for 100% factory restore, unrooted.

This is for those of you that may need warranty work, exchanges whatever. It may or may not be an issue but im sure many of you have noticed that clockwork will pop up whenever the phone is powered off with a usb connection present. Which in most cases would be an immediate red flag for those of you needing work done. This will completely restore your phone and remove the clockwork recovery flash.
Update: I no long have an Aria to try this with but if you guys are running into issues try this as well.
winsettr said:
I'd like to suggest that you update the first post to include a link with the last 2.1 RUU, seeing as the 2.2 RUU breaks the ability of future rooting (for now). I have uploaded what I believe is the updated RUU 09142010 to MegaUpload, linked below. Just thought this might help
http://www.megaupload.com/?d=XXYBORR6
Click to expand...
Click to collapse
1.) Download ATT Original Shipped ROM file from here:
http://www.htc.com/us/support/aria-att/downloads/
2.) Disconnect USB connection to phone.
3.) Power down phone
4.) Boot into Fastboot Menu (hold trackpad on start)
5.) Insert USB
6.) confirm that the phone shows "FASTBOOT USB"
7.) Run downloaded exe file
8.) Process will take a few min at the end you should have a 100% restored and unrooted phone.
It may seem self explanatory now but I was running into issues getting the HTC tool to communicate with the phone and it would fail whenever trying to send the phone into the bootloader. Thought I would just save you guys the headache.
thanks for your solution. was thinking about unrooting my phone and exchanging my aria for a samsung captative...
thanks man. doubt i'll do this, but i might need this just incase ATT and HTC actually come through with a stable update to froyo 2.2 within the next couple months.
I think it will be safe to assume that said 2.2 ROM will begin floating around in a rooted form not before too long, and will be flashable via recovery.
this is great info to have. great work.
???
has anyone actually tried this? because my pc dosent recognize phone when i try
bred904= said:
has anyone actually tried this? because my pc dosent recognize phone when i try
Click to expand...
Click to collapse
install Android SDK USB drivers first
??
i think i did... i installed something from google called android-sdk. and when i connect my phone in bootloader i can see fastboot change to fastboot usb and my pc says driver successfully installed. but when i run the .exe file it never sees my phone. also htc sync wont connect and neither will droid explorer. thanks
i agree with bred, can't seem to restore the original rom. it doesn't recognize it during the process
I have tried this method on 2 computers and the exe can NEVER find my phone.
I have installed the SDK USB drivers, my computer sees the Android 1.0 device and sees it as the HTC booloader. And I see FASTBOOT and FASTBOOT USB when unplugged/plugged.
----UPDATE 2010-07-23----
After further research I was able to determine that even with the device NOT in FASTBOOT mode, that adb couldn't see it, so I thought it might be a driver issue.
I've gotten my computer to recognize the device when it's booted normally. But when put the device in FASTBOOT or the BOOTLOADER, adb can't recognize it and I can't get the recover exe to recognize the device, regardless of mode.
I have the latest clockwork recovery installed and I would like to get everything back to factory to exchange for a captivate.
theres no way to do a nandroid backup or anything like that? curious because i was going to take mine back tomorrow to exchange for the captivate as well. i bought mine from radioshack so i might try my luck and just return it rooted . i did the trade in program with them with my iphone and it was jailbroken and they still accepted it. i dont think i would try that with at&t though... worse comes to worse just return it and say it was like that when you got it! maybe an at&t employee messed around with it before you bought it. they cant prove it was you.
Can anyone confirm this works? Just in case. This might be something I will need to do quick fast and in a hurry in the morning. And I'm hoping that if it comes down to this I won't have any issues.
Sent from my HTC Liberty using XDA App
I have been thoroughly unsuccessful in getting this method to work.
I have tried it on 3 different computers and I can never get the HTC OriginalShipRom.exe to find my phone.
I have tried following the instructions to the letter, I have also tried plugging in while booting the phone into various menus (HBOOT, FASTBOOT, and regular booting), which was advice given to me in the IRC room.
I'm plugging the phone in right after I click "Next" on the "Plug your phone into the usb port" right as it shows the "Verifying data on your PDA" window. I have tried with the phone in HBOOT, FASTBOOT, and while booting the phone, none of these seem to work.
I've also tried it with just plugging the phone in and running the exe. Nothing seems to work. People in the IRC channel are claiming successful factory restores, but I can't seem to get it to work.
So can someone please update the first post with more thorough instructions? Because those instructions don't seem to work.
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
OutsiderWV said:
The following instructions came directly from the HTC webiste for restoring the original state of the phone.
1. Download and save the HTC Aria™ Original Software to your PC.
2. Power your device off.
3. Connect your device to your PC via the data USB cable.
4. On the device, press and hold the Volume Down and Power Button until you get the bootloader screen (a white screen with 3 Androids on the bottom).
5. Press the Power Button once to enter FastBoot mode.
6. Locate the HTC Aria™ Original Software that you downloaded and double-click on the file to launch the RUU Wizard.
7. Follow all of the RUU Wizard instructions shown on your PC.
8. Once the update is complete, click Finish in the RUU Wizard and the device will reboot.
9. Once the device reboots it will run through the Customization Process; this must be allowed to complete.
10. Once the Customization process is complete, the device is then ready for use.
I hope this helps. I haven't tried it yet, but would like to know if this works in case I need to do this as well.
Click to expand...
Click to collapse
My problem is with step 3. The second I plug my powered down Aria into the computer via USB, it powers on and goes directly into Clockwork.
If I boot the device into FASTBOOT, then plug it in, and then run the exe, it says it can't locate the device.
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
farquep said:
If you had flashed the unrevoked clock work you will not be able to plug your phone into the computer while its turned off. Your best bet is to boot into fastboot then plug in your phone. And try to do this under linux since there is no need for drivers.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hi farquep, can you give me instruction on how to use linux what's the command line?? thanx
If you do it under linux, just download the file and run it like any other program in any other operating system. Although you will have to let the file run as an executable under permissions. I don't know if you need to install WINE which will emulate windows programs. There should be no need for terminal scripts.
Sent from my HTC Liberty using XDA App
Doesnt recognize my device at all. If I'm returning to insurance company, should I even bother taking off clockwork? I already have the replacement.
EDIT:
Update:
Just worked for me. I had to install aria_shipped_rooted_signed.zip first then HTCAriaOriginalShipROM.exe recognized the phone.
SysAdmNj wrote:
> I had to install aria_shipped_rooted_signed.zip first
perhaps that can be added to the original instructions.
the archive can be downloaded from here

CognitionV2.2Beta6 (noob guide)

**Please note that following these steps will completely erase your phone**
**Back up any important information before starting(contacts, photos, etc)**
**This guide is for Windows users**
Flashing Cog 2.2 Beta6 (From 2.1 Eclair or 2.2 Frozen Yogurt)
Things to download before you start:
Odin 1 click stock - http://www.thevod.org/misc/captivate/I897UCJF6-final-OCD-REV0.rar
one click root - http://forum.xda-developers.com/showthread.php?t=739304
cognition beta 6 - http://www.ponack.net/designgears/index.html
On your phone - go to Settings, Security, restore factory data.
Reboot your phone.
Enable USB debugging.
Start Odin (you downloaded earlier).
Plug your phone into your computer via USB.
Odin should recognize your phone at this point.
Click "Master Clear".
Once finished, close Odin. Your phone should be rebooting.
Once phone has rebooted, make sure usb debugging is still enabled.
Remove usb plug from phone and then power down the phone.
Remove battery, remove sim, (remove external SDCard).
Insert battery.
Open Odin.
Hold vol up and vol down.
While holding vol buttons, insert USB.
The phone should show a triangle with android digging (or sweeping?)
odin should recognize the phone at this point
Click "Start".
You should see a progress bar on your device display, and within Odin.
The phone will reboot when finished.
Close Odin.
Go back to your phone an re-enable usb debugging.
Run "One-Click Root"
Click "one click root"
Your phone will boot into recovery mode.
Use the volume buttons to highlight "reinstall packages".
Hit the power button to select.
Your phone will apply the update then reboot itself.
Go into app drawer and verify that "superuser permission" icon is visible.
Close one click root.
Power off your phone.
Re-insert your sim card.
Power phone on.
Allow your phone time to read the internal SD card.
Connect your phone to your computer via USB.
From your phone - select mount usb.
using windows, copy Cognitionv2.2beta6.zip onto your SD card.
Sign into Market.
Find ROM Manager, download, and install it.
On your phone, open ROM Manager.
Click "Flash clockwork mod recovery"
Select "Galaxy S Captivate".
Observe the green progress bar at the top of your phone's display.
When complete, clockwork will ask for superuser permissions - allow it.
Choose install rom from SD Card.
Navigate to your SD card and select the cognition zip.
Click OK.
Click OK.
Your phone will either install and reboot automatically, or it may hang at the recovery screen waiting for your input. If this happens, select reinstall packages.
From within this menu select install rom from .zip.
Navigate to the cognition rom and select it.
Confirm that you actually want to do this.
Your phone will reboot to menu again.
Select "reboot system" and sit back.
Your phone should boot into the Android OS.
Almost done...
Go here, https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_LG.gif:NonHosted and buy DesignGears some beverages
It seems that this is already well documented in the Cognition wiki, no?
http://cognition.theidiotshideout.net/mw/index.php?title=Main_Page
You may also catch some flack as this has nothing to do with actual android development.
Cog 2.2 Beta 6 should be rooted already when you flash it, unless something changed. I dont see the need to use one click root.
z28james said:
It seems that this is already well documented in the Cognition wiki, no?
http://cognition.theidiotshideout.net/mw/index.php?title=Main_Page
You may also catch some flack as this has nothing to do with actual android development.
Click to expand...
Click to collapse
+1
Plus this list may be a bit confusing to a real noob.
Jimmy thanks for this, simple but very precise. The wiki seems to be written for somebody that already knows all the details. It's also not very clear as to whether or not you can go straight from eclair to cog2.2, you cleared it up for me so now I don't have to start a "sorry about the noobness" thread/post. I'm running cog 2.1.5 so I have done it before, even used odin once. Thanks again
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
+1
Sent from my SAMSUNG-SGH-I897 using XDA App
kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
That's an answer that belongs in some sort of guide for noobs haha
I appreciate the detailed instructions. A few details to be added. Odin is Windows only, and one click root does not copy the zip file successfully for me (on a Mac). I had to view the package contents of the program and drag the file over and rename it myself, then used the program to reboot into recovery (3 button didn't work for me either).
kakwvu said:
Or you could just use his pre-made Odin flash and skip all of those steps.
Delete.
Click to expand...
Click to collapse
And this is +3.
Sent from my SAMSUNG-SGH-I897 using XDA App
For everyone that gripes about battery life after a flash, try this first after every new ROM:
http://forum.xda-developers.com/showthread.php?t=765656
joeybear23 said:
For everyone that gripes about battery life after a flash, try this first after every new ROM:
http://forum.xda-developers.com/showthread.php?t=765656
Click to expand...
Click to collapse
If you gonna take this there, I'd suggest this one instead.
http://forum.xda-developers.com/showthread.php?t=806211
So does this mean I cant go from stock eclair to froyo with only Rom Manager and no use of ODIN (my phone never recognizes ODIN )
Actually, I think this is a good idea, might keep some of the junk out of the regular Cog thread, that thing is Frickin HUGE...
ozy944 said:
So does this mean I cant go from stock eclair to froyo with only Rom Manager and no use of ODIN (my phone never recognizes ODIN )
Click to expand...
Click to collapse
yes you go from stock eclair to froyo with only Rom Manage...
i did it on sunday night and today i see new cog 6 beta released!!!!
copy cog file to your sd card; install rom manager and continue from there, it will fail the first time (mostly) start phone again and reinstall package..done.
There's also one more thing the op didn't mention. If this is targeted at noobs, it really should be mentioned that if you follow these instructions, you are essentially wiping your entire phone clean (by the odin one click stock). If your that paranoid, go for it.
To me though, I just use titanium backup first, and back everything up. Then after upgrading to cog from eclair (directly without reverting to stock) you can restore your THIRD PARTY apps plus their data. (avoid restoring core apps as thats a bad idea) Not to mention no need to back up and restore any of the media you might have on the internal sd card. (not sure if odin one click stock touches that stuff or not)
I've had no problems in any of my ROM upgrades, and I've moved from 2.1 to cog 2.2 beta 2, then again today to cog 2.2 beta 6. All of that without a restore to stock. You really should only restore to stock if you are having problems AFTER upgrading. Why do extra work and wipe the whole thing clean if it's not necessary? Just adds steps, and possible frustration from people not expecting a wiped phone.
thank u man! rly!
Please verify that you are able to get into download mode using only button combinations before you start any flashing process.
Sent from my SAMSUNG-SGH-I897 using XDA App
orlandoxpolice said:
Cog 2.2 Beta 6 should be rooted already when you flash it, unless something changed. I dont see the need to use one click root.
Click to expand...
Click to collapse
You have to root to be able to flash it in the first place.
Do you mean that Odin won't recognize your phone? WHat happens when you try?

[Q] Screwed up phone. Was bricked, now can't mount anything.

Let's see, where shall I begin?
Got my phone back from my girlfriend since she bought the Nexus 4. Battery was extremely swollen and because of that, the phone basically didn't work. Constantly restarting, couldn't use data, etc... Bought a new battery and decided that I would get a nice fresh ROM installed to get this thing running nice again. It has been on Valhalla for about a year now, and I tried to jump straight to the ICS milestone ROM that I saw in Development. Unfortunately, I didn't know of the new CWM that I was supposed to have, which results in a nice little brick. Frozen at the Boot screen. I was able to get it back into download mode with the volume buttons+cable method and luckily Odin recognized it. I installed a really old KD1 Rom that I had which appears to be all the way back to Froyo.
Now that you are up to speed, the phone boots up fine and seems to be working, but nothing in CWM works at all. Everything fails to mount, which means I can't flash any zips to get off this ROM. To top that off, Odin stopped recognizing it in download mode after I installed that other ROM.
It's been too long since I have been on this phone, and within a couple hours of messing with it again, I can see that I have obviously fallen behind on the development. Any suggestions as to what I should do next? My goal is the get it up to the newest ROMs and see how well it runs. I have the Basic with a twist kernel and ICS milestone ROM ready to go, but no way to flash them.
Thank you to anyone who took the time to read this.
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
th3controller said:
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
Click to expand...
Click to collapse
I didn't even realize it was a Froyo rom, to be honest. I would go and search for a Gingerbread Rom, but the "All roms/rooting/FAQS....." sticky in the development section has been updated in such a long time. I decided to take my chances on that one instead of looking through tons of threads. Froyo was the only one I had for Odin at the moment unfortunately, and Odin was all that I could use.
Thank you so much for the help! This phone should be up and running again in no time!
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
th3controller said:
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
Click to expand...
Click to collapse
Just the Samsung Drivers? I'll try to find them all.
Well, looks like the guide isn't going to work very well for me. I got all the way up to installing drivers with zadig. Heimdall opened automatically like I installed it before ( I may have, it has been forever), but zadig never did. I had to trick it into opening. Once it did open, my phone never shows up in the list of devices as a Samsung device. It only shows up as "Unknown device" and there are no drivers for it to install.
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
TwitchyEye said:
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
Click to expand...
Click to collapse
Finally got around to working on my phone again. Unfortunately, I am unable to follow the guide how I was supposed to. Fortunately, on the other hand, it appears that I successfully got it to flash gingerbread.
Here were my steps to get it work if you want a laugh. My computer didn't like the procedure that the guide had.
1. Update Java, download file, place file into C drive, etc... Everything up to this point worked fine.
2. Open command prompt and execute command. (This is where it all went crazy)
3. Command says false. (instead of opening Zadig, my computer immediately opened Heimdall. So how do I install drivers?)
4. Went to Heimdall help menu and selected install, which froze heimdall completely. Upon Heimdall crashing, Zadig opens.
5. Open Zadig. All drivers are uninstalled, but my device can't be found in the list. (Right after here is where to told me to reboot.)
6. Reboot. Windows keeps automatically installing drivers and I can't do anything about it, so I just uninstall them and try again.
7. Same process. Command prompt, heimdall opens early, crash heimdall, open Zadig, SUCCESSFULLY install drivers.
8. Command prompt again, because that is my only way of getting heimdall open
9. Heimdall finds device, try to flash, but it fails.
10. Unplug phone, and plug in again. Heimdall finds it again.
11. Try to flash again, and success.
It was kind of a nightmare getting it to work, but it looks like it will fix it finally. Thanks for the help everyone!
Double-flashing with Heimdall seems fairly standard. When that happens, sometimes you don't actually have to unplug the phone again, just repeat the same flash-command and it should work the second time. If that doesn't work, reboot the phone, it should go to panic-download mode where it doesn't boot to launcher anymore, just shows the yellow exclamation mark screen, and there the flash should work.
Both my SGS4G and my wife's have done this since we first got them. Sometimes.

ROOT SM-T210R SIMPLE and Easy, 8gb, White

Okay so I've been at it for days and i mean like months.... when I first bought my 8 gb white Samsung galaxy tab 3 Kernel 3.4.5, android 4.1.2, model JZ054K.T210RUEAMK1 and all i have been running into is problems, like jittery display issues, or flickering display, I tried every method but none has worked but i finally found one and got it all working and running, First of all i would like to thank gr8nole for this method, and all who have helped him. So first let me explain the most easiest explanation for dummies like me, or noobs
Just and example video for visual learners http://www.youtube.com/watch?v=XolmtyvS3Yk&feature=youtu.be, but you want to click on the files i suggested on the bottom lol not what he has on his screen xD
Must Have: KIES, make sure you have fully updated rom from samsung themself which can be found on kies when you plug it in and update firmware, which your android should be on 4.1.2 and version because that's what i have
1. First lets Get all the files we need, First go download SM-T210.CWM.6.0.4.5.recovery.tar.zip at his xda post http://forum.xda-developers.com/showthread.php?t=2433853, after you have download that you will a friend name odin, which can be found here http://forum.xda-developers.com/showthread.php?t=2189539 (With odin you only want to use v3.07) and nothing else , Last but not least you want this file from gr8ole android-armeabi-universal-root-signed.zip and save that to your sd card or ext while click on usb debugging or w.e you wanna store in on tablet
so you should have odin 3.07
T210.CWM.6.0.4.5.recovery.tar.zip
android-armeabi-universal-root-signed.zip
2. Use the same method as g8nole and minor adjustments
Instructions:
1. Download ODIN on your computer (just do a google search to find it...version 3.07 will work fine). http://forum.xda-developers.com/show....php?t=2189539
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program using admin rights which means right click run as admin. I recommend un-checking Auto Reboot. DO NOT CHECK RE-PARTITION LEAVE UNCHECKED YOU BEEN WARNED (which it already should be). See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them) which can be found here http://www.samsung.com/us/kies/.
7. Select "PDA" then choose the T210.CWM.6.0.4.5.recovery.tar.zip.
8. Hit "START"
9. Wait for device to restart. Which means wait til odin says OKAY in the white box and the Picture ask you to reset, When the download icon under download updates is full bar, and odin says reset!, just unplug it. then restart by holding the power button down, with vol up, and home, once the samsung picture shows, only hold the up vol button, recovery mode should now be on. Select install zip, and locate the android-armeabi-universal-root-signed.zip)navigate with the up down volume button and power button to select) file, whichever you placed in sd, or exsd,
10. When all is done reboot device, then it will update your android once you turn it on, Now the anoying part, It will be rooted but what google play won't connect?, easy fix , first lets just update all the binaries since its already rooted in supersu app,
Google Store Fix, now first you have to delete your some things, your apps wont dissapear or nothing as long as you dont uinstall them, go to settings<application manager<all<google play store<clear data/cache w.e<force stop<uninstall updates<it will then ask you it will be factory installed<yes, next step, delete your gmail account if you haven't done so, now go to your time settings (Date and Time) and change it to recent date whichever today is , then open play store and it will ask you to sign in again, blah blah google needs sign up and it should be up and running
ALL DONE, remember this is for people who have run into flicker display problems, which is caused by kernal issue with our model, but with stock rom itself we can universally root it through odin with just that simple method which took me like 3 mins lol to do
Grats guys! you have root and cwm now who doesn't want that enjoy and thanks to developers hard work! and my ambition!
this worked for my SM-T210 also. Thanks heaps for this how-to!
Ok my device is already rooted but I would like to install CWM Recovery on it. So I can make a backup. Or does anyone have the stock kernel for it
Sent from my SM-T210 using xda app-developers app
Odin 3.07
Link was busted so I posted a new one for lazy people.
http://www.android.gs/download-odin-3-07/
or something like this??
http://forum.xda-developers.com/attachment.php?attachmentid=1168421&d=1341114315
drolgnir said:
Link was busted so I posted a new one for lazy people.
http://www.android.gs/download-odin-3-07/
or something like this??
http://forum.xda-developers.com/attachment.php?attachmentid=1168421&d=1341114315
Click to expand...
Click to collapse
But you can also use Odin 3.09.
I'm portant is that you flash always the newest CWM / TWRP or PhilzTouch Version about the new updater scripts.
cspiresucks said:
Ok my device is already rooted but I would like to install CWM Recovery on it. So I can make a backup. Or does anyone have the stock kernel for it
Sent from my SM-T210 using xda app-developers app
Click to expand...
Click to collapse
Your best option is to get CWM sknce it will be your original backup instead of a Rom created from another device.
SM-T2105?
Hello,
I came here beacause of a shorcut link given by @gr8nole and another member (I forgot sorry).
But my English must be to bad, i read and re-read, still don't find the answer...
I have the G Tab 3 kids model, SM-T2105.
@bierma32 says: "Important is that you flash always the newest CWM / TWRP or PhilzTouch Version"
Could you tell me wich one is the best, CMW or TWRP, plz? (the last I can find for T210 is CMW-6.0.4.9 and/or TWRP-2.8.2.0)
More important, do you know where I can find the zip of a rooted stock rom, including that 'kids' stuff? (SM-T2105). Or will I not loose the stock rom? Is there no wipe? Sorry, I don't understand.
I want to root, because of lack of space, and the rest.. but I don't want to loose that..
And the most important, "last but not least", I could not find the zip " android-armeabi-universal-root-signed.zip", so can you help me please, putting a mirror or so? Or could it work only with flashing a SuperSU zip? Not so easy, right?
As you maybe can read, I am a newbie in Android rooting. Or is there another way to do?
Thanks for reply.

HELP NEEDED. stuck in bootloop after editing build.prop file. (gt-s7562)

This is my first ever use of any forum. So plz sry if i am posting this thread in the wrong place/discussion!!
I had a samsung galaxy s duos(gt-s7562). i rooted it about 2-3 years back. a few days back i tried to edit my build.prop file using es file explorer. It did work but after my work was done i made the mistake of copy-pasting the backed up file.(i had made a general copy-type backup of the file.) When i tried to reboot my phone it got stuck at the samsung screen.(maybe a bootloop.)
I can go to the recovery mode by pressing volume, home and power button. But it is the android system recovery. No cwm.
How can i get it back to life??!!
I have another s duos phone which i am currently using to write this thread. I thought of rooting this phone and then using its nandroid backup to restore my first phone. But as told, there is no custom recovery on that. And usb debugging is also off.
Can i use odin to install cwm recovery on my phone withou usb dedebugging. And is there any other easier method to recover my soft bricked phone.
Please help.
shubham aadeez said:
This is my first ever use of any forum. So plz sry if i am posting this thread in the wrong place/discussion!!
I had a samsung galaxy s duos(gt-s7562). i rooted it about 2-3 years back. a few days back i tried to edit my build.prop file using es file explorer. It did work but after my work was done i made the mistake of copy-pasting the backed up file.(i had made a general copy-type backup of the file.) When i tried to reboot my phone it got stuck at the samsung screen.(maybe a bootloop.)
I can go to the recovery mode by pressing volume, home and power button. But it is the android system recovery. No cwm.
How can i get it back to life??!!
I have another s duos phone which i am currently using to write this thread. I thought of rooting this phone and then using its nandroid backup to restore my first phone. But as told, there is no custom recovery on that. And usb debugging is also off.
Can i use odin to install cwm recovery on my phone withou usb dedebugging. And is there any other easier method to recover my soft bricked phone.
Please help.
Click to expand...
Click to collapse
Follow the steps i tell u and u might get ur phone back
Requirements
1.Windows PC
2.Samsung USB Drivers
3.Odin for Windows
4. Samsung GT s 7526 Stock Rom
See if u can find STOCK ROM for ur country, if not then just download a closer one or just any
LETS GET STARTED
1. Install Samsung USB Drivers on PC smoothly
2. Extract Odin anywhere u wish
3. Boot phone to DOWNLOAD MODE {Hold Volume Up+Home+Power}
4. When warning screen pops up press Volume Up to continue
5. Open Odin on PC and connect Phone to PC via a DATA CABLE
6. U will see a message "ADDED"
7. Select AP or PDA, whichever is there and browse the STOCK ROM
8. Check the "Auto Restart'' and "F. Reset Time"
9.....................CLICK START............................
And after a while u will see a Green PASS/RESET message and ur phone will reboot
THATS ALL, U GOT UR PHONE BACK.......................

Categories

Resources