[Q] ATT Samsung Galaxy S2 Skyrocket will not root! - AT&T Samsung Galaxy S II Skyrocket SGH-I727

I have been trying to root my phone for about a week now and i am getting no where. I have been trying to use superoneclick and it keeps on saying failed. Installed the drivers for the phone also and still nothing. PLEASE HELP!!

xgame4u said:
I have been trying to use superoneclick and it keeps on saying failed.
Click to expand...
Click to collapse
I used this method to root my phone. I actually found this method to be a lot easier than superoneclick. As long as you follow the instructions in the first post of the thread you should be okay.
BUT, if you have permissions problems (or if you're not sure what they mean by "run the batch file"):
Right-click on cmd.exe in the start menu, select run as administrator then navigate to the folder extracted. For instance if you saved the file in your users downloads folder then navigate to: x:\users\[user name]\downloads\Skyrocket-Easy-Root and then type root.bat and press enter.
If you need help with that method, let me know. I didn't bother with superoneclick.

Try this from Copperhead! Worked beautifully!
http://forum.xda-developers.com/showthread.php?p=19223405
Don't forget to thank copperhead :thumbup:
Sent from my SGH-I727R using xda premium

Thanks!
thanks guys finally got it done!!

OneClick 4.0.4 - Can't root!
This is the first time I've rooted or flashed on my Skyrocket. I got tired of AT&T sitting on their asses with ICS and found OneClick's 4.0.4 UCLE2.
I was able to root with Odin and CWS on AT&T's stock 2.3.6 and backup my data with Titanium, and need my WiFi keys back... but I can't root again!
Odin and superuser.zip has failed after 13 attempts, SuperOneClick freezes on my Windows box (I use Ubuntu 12.04 on my Main box), and Skyrocket Easy Root fails because of permission issues. No method here works.
Am I doing something wrong, or is 4.0.4 un-rootable at the moment? I need the WiFi key for work and the only person with the password will be in Greece for two weeks!
I also can't force /system into r/w mode, with any tools (won't show up in bash, Total Commander can't mod it).

Frost58 said:
This is the first time I've rooted or flashed on my Skyrocket. I got tired of AT&T sitting on their asses with ICS and found OneClick's 4.0.4 UCLE2.
I was able to root with Odin and CWS on AT&T's stock 2.3.6 and backup my data with Titanium, and need my WiFi keys back... but I can't root again!
Odin and superuser.zip has failed after 13 attempts, SuperOneClick freezes on my Windows box (I use Ubuntu 12.04 on my Main box), and Skyrocket Easy Root fails because of permission issues. No method here works.
Am I doing something wrong, or is 4.0.4 un-rootable at the moment? I need the WiFi key for work and the only person with the password will be in Greece for two weeks!
I also can't force /system into r/w mode, with any tools (won't show up in bash, Total Commander can't mod it).
Click to expand...
Click to collapse
with superoneclick are you using zergrush?

zergRush = fail
I need to find the setting to get emailed when someone posts to a thread I'm involved in.
I tried zerg and it didn't work, but updating CWM to 5.8x and the 3.x version of superuser.zip did the trick.
I read in other threads that the screen flickers and the keys don't work with the touch interface, but I got it.
Now I just need to figure out how to do a batch restore with Titanium and get my Uverse, WiFi settings, and Opera bookmarks back.
Thanks for asking Decepticaons: So far I'm happy with 4.0.4, but was expecting individual contact SMS tones to be available... perhaps there's a ROM for that?

Related

[STICKY]NEW Showcase Newbie Guide

After bdemartino wrote his AWESOME thread for the Mesmerize it seemed only fitting that the Showcase get their very own... And since his Thread was Flawless, with his permission I'm mostly copy/pasting word for word. as I am copying most of this from elijablake . . . so thanks this thread needs some editing, and I will be working on that in the future . . . . specifically the CWM / ROM manager which will not work. I could use some assistance in rewriting that part. TY!
BEST. ADVICE. EVER. #samsung-mesmerize on irc.freenode.net
<3<3<3<3<3
Also, read the Glossary for definitions and such. I was not the sharpest tool in the shed and it took me a while to find this . . .
Disclaimers
CSOUTH IS RELEASEING 2.2 UPDATE THIS WEEK (6/26). You may just want to wait for that to be released. This thread will be updated when the release occurs as how to flash recovery that you can flash roms with etc.
Keep in mind there are many variations to each step, this is what worked for me the easiest. READ ALOT BEFORE PROCEEDING WITH ANYTHING!!
There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda - ehm and in the appropriate forum ).
Steps to get to 2.2 (EB11) on your phone:
**Please note that the links were removed by CSouth for copyright (COPY WRONG *****ES) reasons. So if you can find the files somewhere (ahem . . . ) then you can follow these steps. THIS GUIDE IS PURELY FOR EDUCATIONAL VALUE, I DO NOT ADVOCATE BREAKING COPYRIGHT LAW.
I highly recommend using Heimdall rather than Odin. Don't ask me why . . . maybe because it has a command line utility and it is cross platform. So my instructions will be for using Heimdall.
After you have the downloaded files (from wherever you might have gotten them, you bad bad person) unzip and look for the following files:
-factoryfs.rfs
-modem.bin
-recovery.bin
-zImage
1) Put your phone in download mode by powering down your device, removing the battery, connecting the USB to your computer, and holding the volume down button. It shouldn't take long. You should see a little Android with a shovel.
2) In Heimdall, if using the GUI, put all of the files in their obviously appropriate spots. Don't worry if not everything is filled, just use the files that you have. (You should be using the repartition with the .pit file, the zImage with the Kernel, the recovery, and the modem)
If using the command line utility, cd to the directory where you unzipped the files and
Code:
heimdall flash --repartition --pit atlas_v2.2.1.pit --factoryfs factoryfs.rfs --kernel zImage --modem modem.bin --recovery recovery.bin
Wait for the process to finish, your phone will reboot at the end.
3. That is all, now your phone is updated to 2.2.1. Put the battery back in and boot your new shiny toy!
DO NOT DISCONNECT USB DURING THIS PROCESS AS IT COULD BE POTENTIALLY DISASTROUS!!! DON'T EVEN TOUCH IT AS I HAVE FOUND THE USB CONNECTION TO BE A BIT FLAKY!
Also, it is ok if it takes your phone what seems like forever to boot. This happens whenever you install a new kernel, just be patient.
If you have gotten the most updated batch of files, you should have the proper recovery to begin flashing. If not, well seek help . . . You should have RED RECOVERY!
See here for more information about CWM or go on irc.
To access recovery, you can use the three finger method. (Hold down the volume up and down keys and the power button all at the same time when you're turning your phone on) Once you see the Samsung splash screen you can remove your finger from the power button, but keep holding down both volume keys.
You should then go here to check out themes and mods.
Steps For Rooting either 2.1 or 2.2.1
Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
**NOTE: most custom roms come rooted, so if you are installing a custom rom in 2.2.1, you most likely don't have to go through these steps. Just flash to the ROM you want . . . ***
The easiest way to root is through the z4root.apk. (an application that will run right on your phone)
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it. Note: If you need help at this step, no offense I would suggest getting someone with more experience to help you continue on. I'm serious here
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal
After your phone boots open z4root again and click root, this time it will run no problems and phone will reboot.
NOTE**IF YOU HAVE PROBLEMS WITH z4root: "give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Showcase. It is located here."-This Information provided by phidelt82**
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to... eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
I use Root Explorer
It's a few bucks, but there's hardly a day that goes by when I don't use it.. (Well worth the money)
THE ECLAIR SECTION IS REMOVED AS CSOUTH IS RELEASING UPDATE THIS WEEK (6/27)
Hehmmmm....
nice write-up!
Upgraded the Showcase to 2.2.1 build EE25 with Samsung Kies this morning. Also had no issue rooting with superoneclick.
cpflow said:
Upgraded the Showcase to 2.2.1 build EE25 with Samsung Kies this morning. Also had no issue rooting with superoneclick.
Click to expand...
Click to collapse
Kies has 2.3 out now =)
Kies Mini have 2.3.5 out now for generic cdma showcase.
Sent from my SCH-I500 using Tapatalk
*Edit*
It seem everyone forgot about the Samsung Showcase Galaxy S Generic CDMA.
I managed to Root it flash CWMR and flash TSM TW 4.0 ROM. but then try to go back to stock and lost 3G. So I returned it and get a new one. No more mods for me I'm done no one cares about Generic CDMA.
Can someone provide directions to install a custom rom for a Showcase running stock 2.3.4? I don't have root. I'd really appreciate any help!

[Q] how to update rooted Xoom to 3.1 or 3.2

dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Simplest way i know.
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
is3od said:
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Click to expand...
Click to collapse
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer File name: SDK ADB.zip File size: 359.93 KB put them all in a folder called rootxoom or something.
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
His Xoom is 3G there is no OTA update to 3.2 for 3G.
I really would not relock and go back to stock. He's rooted and that's more than half the battle.
is3od, the method I posted is for non-US Xooms as long as they are rooted.
i'll try it
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
thank you for your help... today i'll try it and will inform you about the result.
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
first i will relock my xoon then i'll update it ..
thank you,
prowlex said:
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer put them all in a folder called rootxoom or something.
Click to expand...
Click to collapse
ok
thanks...
k66473 said:
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
Click to expand...
Click to collapse
it should be, because my Q is for 3G Xoom.
is3od said:
it should be, because my Q is for 3G Xoom.
Click to expand...
Click to collapse
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
thanks a lot
okantomi said:
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
Click to expand...
Click to collapse
I really appreciate your help .. thanks a lot ..
adb devices returns no devices
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Make sure USB Debugging is checked under Settings/Applications/Development. If it is checked, then there is something wrong with your drivers.
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Check the thread you started...people have answered there.
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
I'd like to do the same as OP, update a rooted stock 3.0.1 euro 3G to 3.2 - I've already come across the thread you link to, but there's something I don't get.
pienut (user whose post you linked to) is saying that he went from 3.0.1 to 3.2, but in step 3 he writes:
Step 3 - Install 3.2 EURO rom:
Just copied the Euro 3.2 update from this post to my SD Card and flashed it from recovery.
Just to be sure, I did a full wipe after flashing.
Click to expand...
Click to collapse
Am I missing something, or is the SD card not disabled in 3.0.1? I know it is for me, afaik it only started working with 3.1 and up. I can't wrap my mind around going from 3.0.1 -> 3.2 using the SD card method, and yet it's mentioned in quite a few more threads and posts.
Ideally, I'd like to update to the Xoom ROM 2.1 Hammerhead (http://forum.xda-developers.com/showthread.php?t=1203635), but in those instructions, too, step 2 says
Download the 2.1 rom zip file and place it on your external sdcard
Click to expand...
Click to collapse
How, if I can't access it in the first place? Should I install 3.1 first before I install Hammerhead? If so, do you know about any step-by-step I can follow?
Sorry to jump in on this thread like this... it was the closest I could find related to my problem after hours of searching and reading. Thanks.
Alright, I figured it out on my own... I took a leap of faith and installed the ClockworkMod Recovery 3.2.0.0 (R4c), booted to recovery, and in there it's possible to mount the SD card under mounts and storage > mount usb storage. It will then appear in Windows as an external drive (as usual).
Yay, learned something new today. Now on to the next battle

Odin stuck at "recovery.img" on Tab 2 10.1

Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
SlickAl41 said:
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
Click to expand...
Click to collapse
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Ryanscool said:
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
Click to expand...
Click to collapse
Heimdall did it. Thanks for pointing me that direction. :highfive:
SlickAl41 said:
Heimdall did it. Thanks for pointing me that direction. :highfive:
Click to expand...
Click to collapse
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
SlickAl41 said:
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
Click to expand...
Click to collapse
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Ryan79 said:
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Click to expand...
Click to collapse
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
SlickAl41 said:
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
Click to expand...
Click to collapse
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
SlickAl41 said:
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
Click to expand...
Click to collapse
Hey Alan, sorry... been away from the forums for a couple days. But it looks like you got it figured out you are correct on the Heimdall command, the only thing different that I did is that I already had root explorer purchased... so after the SuperUser install I just ran it to move the install_recover.sh to my SD card
Glad to hear you got it working!
I am trying to Flash the Stock ROM on my Galaxy Y PRO after it is gone into a bootloop (by itself), i am using ODIN , but it got stuck on Flashin the recovery img
i tried all The USB ports of my computer and only 1 worked. Please i need help and a sure answer thx
MultipleMonomials said:
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Click to expand...
Click to collapse
How to use Heimdall when I have bl, ap, etc

Cannot Root After Many Attempts

My Acer Iconia Tab A100 was updated to 4.0.3 ICS a while back and due to a webbed digitizer I had avoided use (did not want to cut myself on the screen)
After a while of letting the loose glass fall out I can now use it without worry. My problem is no matter what method I have tried rooting this tablet... It is either me who is doing something wrong, I am missing a step before everything else, OR I am just misunderstanding the steps.
I have tried the fastboot/recovery method by nullzero (abd.exe and other programs are not found in internal/external)
i have tried just running the ICS a100 root method (abd.exe and other programs are not found in internal/external)
I have tried watching youtube videos doing exactly as they did... but to no avail and I have no idea what I am doing wrong or if its all just because my tablet is already updated to 4.0.3? or what but its quite frustrating.
I am by no means educated in android so I honestly have no idea what I am doing other than following the steps I watch online so....
That being said. Any and all help is appreciated greatly
Acer Iconia Tab A100
android version 4.0.3
kernel 2.6.39.4+
build number av041 a100 1.049.00 pa cus1
img version av041 a100 rv22rc02 pa cus1
Still looking for assistance
NicholasHarris said:
Still looking for assistance
Click to expand...
Click to collapse
i have always used this method:
http://thedroidnation.com/acer/iconia-tab-a100/root-acer-iconia-tab-a100-android-40-ics-rom.html
i dont know what it is called, so i am not sure if you mentioned it
i have rooted 3 or 4 times with it, and i am also on 4.0.3
it tells you how to set up your tablet before you attempt to root and how to root (follow the directions)
where it tells you to run "runit-win.bat" try right-clicking it and choose "run as administrator" not sure if is matters but it wouldn't hurt to try it
close to the final step, it tells you to install superuser and titanium backup, get them from the android market for free
fred99u said:
i have always used this method:
i dont know what it is called, so i am not sure if you mentioned it
i have rooted 3 or 4 times with it, and i am also on 4.0.3
it tells you how to set up your tablet before you attempt to root and how to root (follow the directions)
where it tells you to run "runit-win.bat" try right-clicking it and choose "run as administrator" not sure if is matters but it wouldn't hurt to try it
close to the final step, it tells you to install superuser and titanium backup, get them from the android market for free
Click to expand...
Click to collapse
Tried this method before I am sure
Ran without admin
Waiting for device
daemon not started startting it now
daemon started successfully
20 minutes go by no changes
ran win bat with admin
abd abd abd abd not recognized an internal or external
says none of the stuff has been installed and i get no pop ups on my tablet
Mkdir access denied
i am having problems rooting my a100 runing ics 4.0.3.. i have tried every method and nothing seems to work. when i try ZeroNulls root i get Mkdir /data/local/tools access denied. Anyone else having this problem?

[Q] Sidekick 4G Woes

Argh! Pulling my hair out over this one. I've been flashing custom ROMs and rooting my phones for years now, since my old HTC G1. Even had KitKat running on my HTC Desire 4G!
... but this Sidekick is proving another matter. I've been through forum after forum, all saying the same things on how to root/flash this thing, but I haven't managed to get anything to work! So, here's step-by-step of what I just did and the result I get every single time, no matter the initial method:
1: Fired up ODIN3.
2: Wiped the user data and cache from the stock recovery (Android System Recovery (3e)).
3: Connect USB cable, reboot phone into download mode (using the battery-pull method).
4: Successfully flash to stock ROM, reboot.
5: Sign in with Google, enable WiFi.
6: Run SuperOneClick, reboot.
7: Grab ES File Explorer from the Market, after it updates.
8: Attempt to replace "recovery" in /system/bin with custom
... and here's where things break. Doesn't matter what version of SuperOneClick I use (and I've tried from 1.9.1 through 2.2.3), nor does it matter what exploit I select. What happens? Well... aside from everything on-screen claiming to be okay, and everything claiming it's working, once the rooting is "successful", I reboot like it says, see that SuperUser is in the applications, it shows me an su binary version...
... but anything that tries to run super-user (ES File Explorer included) that gets added to the super-user list simply does not work. I can't over-write the recovery, can't delete or muddle with anything that requires elevated privileges, and the ROM Manager for sure won't work because I can't get CWR installed.
I love my phones with keyboards. I really do. I'd love to keep this thing, but the stock firmware is driving me up a wall (especially that stupid media scanner). So if anyone has any ideas to throw at me, care to offer some? Haven't a clue at this point what I'm doing wrong.
Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around
demkantor said:
Hey buddy!
I feel your pain, this is one of the last nicely built hardware keyboard phones, first time rooting it is a bit strange
See post #27 (or so) here
http://forum.xda-developers.com/showthread.php?t=2221030
I ran through the manual steps there and have links for needed files
If you get stuck let me know, I'll be around
Click to expand...
Click to collapse
Awesome! I'll give this a go once I'm all done with today's activities and see if it works.
Well, apparently I have root access for the moment, but it is denying my replacing of /system/bin/recovery - in adb shell, it states "Filesystem is read-only", so I re-mounted /system -rw and no dice. Going to attempt to try again in a moment, after a reboot.
Okay, so since there's a problem with all of this, I'm going to try that second ROM (KD2 I think it was) - but as I recall, it was on a very slow server. Plus I have a load of things to do tomorrow, so it probably won't be until tomorrow evening sometime when I'll be able to flash it. Once I've used Odin to re-flash, I'll get back to you.
Well, I had to dissect "t839-Sidekick4G-UVKG2-One-Click.jar" and remove the xml file from within it, but I acquired the necessary package to upgrade to KG2 from KD1 through Odin3. Took a while to figure out just how to deal with it, and I was successful in flashing... and I even replaced the recovery file after rooting it again!
... however, now it just sits there at the "T Mobile Sidekick 4G" start-up screen when I attempt to boot into recovery, so now I'm preparing to re-flash it again to recover the stock recovery. So... still more on this, later.
EDIT: Also, I named the tar file "KG2OdinHeimdall.tar", since I basically ripped it right off the "HeimdallPackage.tar" file from the Heimdall one-click thing. Turns out, it apparently works just fine if you remove the .xml file from the original tar.
Finally!
I ended up having to use my own method to get the KG2 update installed because the one-click program kept crashing on me when selecting "Show all devices", and I opted to use AntTek Explorer (all you have to do is go into the program's options and it'll attempt to acquire admin privileges, if the device is rooted) to copy the recovery file to /system/bin - but your post worked for everything else, once I got past not being able to copy the recovery file.
I opted for the CM6 package and it's quite fast! Thank you loads, demkantor!
Nice! I'm glad all worked out well for you!
If you get a chance try out the one gingerbread ROM, its cool to see it running but there are still driver issues so keyboard is borked, really makes it pointless to have on this phone...
But there are a few nice froyo ROMs ready to be played with, someday development will hopefully pick up again
Until then, happy flashing!

Categories

Resources