Heya. Trying to install CMW and it just isn't happening. First I tried the Rom Manager method, which failed. On reboot, I'd get the default menu, and if I try to use reinstall, it aborts installation. Upon reading more threads, everyone says to stay away from RM and just do it manually. So I go over to the CMW thread, and follow the instructions completely. And I just can't overwrite the "recovery" file no matter what I try.
First I tried the file manager in Super Manager, since I already had it and it was mentioned in another tutorial. It didn't give me any errors, but apparently it failed. File date didn't change and still can't boot CWM. Next, I tried Android Commander, via CMW thread's recommendation. It too, is unable to overwrite it. The programs console readout says it failed to copy the file, then the program spits out a memory access violation. I tried running AC as administrator and without. I tried click n drag or using the buttons to initiate the push. I tried enabling writing on the recovery file. No dice.
Yes, my phone is rooted. I even rooted it again just to make sure via SuperOneClick. AC says it has root access too. Sidekick 4g with everything stock. Android Commander was ran on a Win7 Ultimate 64 bit machine.
What should I try next?
Edit: In the meantime, downloading http://forum.xda-developers.com/showthread.php?t=1593065 , gonna see if it helps.
Edit2: Nvm, figured it out. Had to use Super Manager and turn on Root mode, and had to reboot several times to get Root mode to turn on *facepalm*. Running GenericGinger now and all is well.
tr0ubl3mak3r said:
Heya. Trying to install CMW and it just isn't happening. First I tried the Rom Manager method, which failed. On reboot, I'd get the default menu, and if I try to use reinstall, it aborts installation. Upon reading more threads, everyone says to stay away from RM and just do it manually. So I go over to the CMW thread, and follow the instructions completely. And I just can't overwrite the "recovery" file no matter what I try.
First I tried the file manager in Super Manager, since I already had it and it was mentioned in another tutorial. It didn't give me any errors, but apparently it failed. File date didn't change and still can't boot CWM. Next, I tried Android Commander, via CMW thread's recommendation. It too, is unable to overwrite it. The programs console readout says it failed to copy the file, then the program spits out a memory access violation. I tried running AC as administrator and without. I tried click n drag or using the buttons to initiate the push. I tried enabling writing on the recovery file. No dice.
Yes, my phone is rooted. I even rooted it again just to make sure via SuperOneClick. AC says it has root access too. Sidekick 4g with everything stock. Android Commander was ran on a Win7 Ultimate 64 bit machine.
What should I try next?
Edit: In the meantime, downloading http://forum.xda-developers.com/showthread.php?t=1593065 , gonna see if it helps.
Edit2: Nvm, figured it out. Had to use Super Manager and turn on Root mode, and had to reboot several times to get Root mode to turn on *facepalm*. Running GenericGinger now and all is well.
Click to expand...
Click to collapse
Supermanager? Anyways, glad to see you are enjoying GG 3.7.
JiN1337 said:
Supermanager? Anyways, glad to see you are enjoying GG 3.7.
Click to expand...
Click to collapse
Yep. Super Manager has a whole bunch of useful tools, including a file manager with root access. And it's free.
And GG 3.7 is awesome.
Related
I have a My Touch 4G currently running 2.3.4 that I want to downgrade to 2.2.1 so I can root it. I am unable to get it to take the PD15IMG.zip to take once I hit the bootloader. It says its extracting fine, but the phone never reboots and if I manual reboot it, it boots up on 2.3.4.
I was using the following instructions.. cyanomod instructions and I did everything fine but get stuck with step 8.
Here is a copy of my ABD session:
Open to any suggestions.. I did some searches but no luck.
I tried to paste the URLs for the pastebin and the instructions I used but was blocked because of the stupid spam rules for newbies.. so PM me and ill send them to you.
Also as you can see I have been a member for over a year now, I just do a lot of lurker so I don't post much. I usually can find my answer searching without asking but I am stumped on this one.
This exact same thing happened to me.
The problem was that ADB wasn't pushing the entire PD15IMG file to the SD card. Every time I tried it it was missing exactly 53 bytes. (You can check this by looking at the file size of the PD15IMG on your hard drive and see if it file size matched EXACTLY on your SD card down to the single byte.)
I fixed it my using the file manager on my computer to just drag and drop the PD15IMG file onto the SD card. For some reason that transferred the entire file without problem.
I ran through the steps again and viola, 2.2.1 upon reboot.
You might also have a corrupted PD15IMG file. You can fix that by re-downloading the file, preferably from a different source just in case.
why u need downgrade 2.2.1 ?
@skipjacks - ill try that, on the 2nd attempt at it yesterday I manually copied of the file over after I downloaded it from another source, yet it still would not upgrade. I will give it a 3rd shot and report back.
@Ridofu - I am tried of having the HTC offical software crashing on me. I would like to root and then install CM7.1
Same thing..
I downloaded PD15IMG.zip manually over the HTC E:\ drive I have mounted.. did all the commands again, went to bootloader, it says it installs but then never reboots or does anything...
the image say loading, and I see a blue bar on the right top corner... then it switches to checking with a yellow/orange bar in the right top corner..
then it just goes back to the main screen and doesn't do anything..
all i see is fastboot, recover, factory reset, simlock, image crc
Id love to run the adb shell md4sum /sdcard/PD15IMG.zip but everytime I run it it comes back with md5sum: not found
Any ideas?
How I rooted my MT4G
Try this guide:
http://androidrootking.blogspot.com/2011/10/how-to-root-your-mytouch-4g-original_12.html
This is a step-by-step guide to root your MT4G. It has a link to another guide that will help you downgrade your phone.
You must downgrade FIRST, in order to root, because the root tool (gfree) DOES NOT WORK with Android 2.3, it only works with 2.1.
If you really like GingerBread, and want to keep root, go here AFTER you're rooted:
http://forum.xda-developers.com/showthread.php?t=1264704
—E!
Do you have MicroSD card reader in/for your PC?
Try to use it instead of copying the file through the phone.
@Ericm301 that is the exact method I have followed and it does not work. I have done the Push method, I have done the copy via USB cable to the E:\ drive that is mounted and neither allow me go to bootloader and load the file.
@Jack_R1 I will try getting a Micro usb adapter and copying the file over as well.
I tried taking the SD card and copying the file manually, I also tried to use the file from a 3rd source. It will not downgrade. I can post a video if you want to see it fail.
Just wanted to give a update. I did the manual downgrade 2 or 3 more times and I finally gave up on it.. then I switched to Fastboot Downgrade method and it worked perfectly the 1st time..
man what a frustration!
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
So I rooted my phone for the first time via Odin. And it worked -- after that, I tried to install a custom ROM (slim bean) -- I ended up uploading the non zipped version on my SD card. And I went through all the steps to install up until "format/system" to realize that I didn't have the zipped files.
Now my phone is stuck on the Samsung Icon. I just tried to use Odin to flash the stock gingerbread again, but there it gets stuck on "Setup Connection".
Please help! Total newb at this, and clearly it failed.
---
My phone wouldn't turn off even with Odin closing, so I took out the battery -- so now my startup screen is
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
How do I fix this?
That is kind of a secondary download mode.. odin or heimdall should detect your phone.
Make sure you have a good usb cable and maybe try switching usb ports.
Sent from my SGH-I997 using xda app-developers app
Right. To add to andros11's post, was the top left box yellow in Odin before you clicked start? Odin will acknowledge that your phone is connected immediately (the box should be yellow if you your phone is connected properly). Of course, make sure you have all of the appropriate drivers (i.e. download Kies for the Infuse).
Also, for future reference, I have a fix for situations like yours so you don't have to go back to stock. Basically, you can use adb to push the correct zip file to your sdcard. What you do is:
Download and install the Android SDK: http://developer.android.com/sdk/index.html
Make sure to install platform tools (a separate download from within SDK)
In Mac and Linux, open up Terminal. I can't remember how Windows works, sorry! Navigate to wherever the platform tools folder is. You have to do this using command line, so, cd <the/path/to/your/folder> (the easiest way is to just type cd, hit the space bar and then drag the folder to the Terminal window).
Once there, connect your phone to your computer. It can be in CWM or Download mode
Type in Terminal: adb devices
The next line - the response - should tell you if your phone is recognized. If it's blank, try again. If it's still blank, you might try disconnecting usb phone cable and reconnecting again. You might also try going into download mode.
Okay. Next type: adb push <here, just drag the zip file to your terminal window> /sdcard/
Give it time to push the file to the sd card. Repeat if necessary (if you have more than one zip)
Exit terminal, disconnect phone from computer, go back into recovery, navigate to the sdcard to flash and lo and behold! The proper zip file is there for you!
This might sound long, but it's so easy. Getting SDK set up is probably the biggest pain and it's not really that much of a pain!
You may want to give Heimdall a try rather than Odin.
Put the phone into download mode and try this:
http://forum.xda-developers.com/showthread.php?t=1331381
Thanks so much everyone. Seriously.
So, Whizzpopper -- I *think* I installed SDK, but since my phone still says, "Firmware upgrade encountered issue. Please select Recovery mode in Kies and try again." I tried connecting it to Kies -- and it says "connecting" but never connects.
And even if I try the key combo to get to Download Mode or Recovery, it never gets away from that Firmware message.
How can I just get out of that mode?
how to keep fb sync on custom rom?
Hi I am a fairly new member, I have been following different threads for a long time but have recently signed up, so if i am posting in the wrong thread I sincerely apologize. moving on...
I have been using the Aeon 1.4 rom for awhile now and have been loving it. I first downloaded the rom without the stock libs and found that it is much faster than the stock libs rom, even after manually removing most of my stock apps via sd maid pro. But it has been the only way to keep the option to share with FaceBook. and being able to add facebook in my accounts and sync are in system settings. system settings>accounts and sync>add account.
You won't be able to get out of there until you are able to flash with either odin or heimdall.
You may also try a tool called one-click unbrick (google it)
Sent from my SGH-I997 using xda app-developers app
andros11 said:
You won't be able to get out of there until you are able to flash with either odin or heimdall.
You may also try a tool called one-click unbrick (google it)
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
ONE CLICK UNBRICK HAS GOTTEN ME OUT OF THAT GODFORSAKEN FIRMWARE MESSAGE.
Thank. You. So. Much.
... Now to follow the rest of the steps to try and get it back to some sort of operating phone!
and please note that it would be best to uninstall kies- it has been a source of problems for a countless number of users.
Thank you so much for your help!
So the terminal adb push worked -- and I installed my ROM (went through all the installation wizard parts, etc.) but now at reboot, I'm still stuck at the Samsung logo.
What happened?
@andros11 -- I saw your comment on how to best get from GB to JB
http://www.android.gs/install-unoff...pdate-to-ice-cream-sandwich-4-0-3-custom-rom/
I tried to follow those instructions to install ICS first, (I was previously too eager and went straight to JB!) and still I'm stuck at the Samsung screen.
Anybody have any threads, recos to get my phone to bootup to any system?
Sorry for the newbness!
Enter download mode to Go back to stock gb and then work your way up again up to jb.
Sent from my SGH-I997 using xda app-developers app
To add to that, use qkster's link to get back to stock.
http://forum.xda-developers.com/showthread.php?p=23118134
Sent from my SGH-I997 using xda premium
Okay so I tried the Heimdall One Click Stock --
unfortunately, it stops working at the "clearing interface" stage -- says it failed. And I've changed the cables but still the same result.
You are on the right track... just that something is missing.
Be sure to get rid of kies.
Be sure you have the latest version of Java. http://www.java.com/en/
Use the link in post 13 that psal gave you - read at least posts 1 and 2 all the way through, then go through and perform each step.
The first time is a process, after that it is quick and easy. Thanks to qkster. :good:
Here is an award winning-less video of the process that you might want to watch as you may see a step in the video that you are missing. Hope this helps.
http://www.youtube.com/watch?v=sHyY7WHx4zc
Nothing in this world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated failures. Persistence and determination alone are omnipotent.
Calvin Coolidge
I've read the Ace guide, researched unlocking bootloaders, Rooting, flashing ROMs, and have more questions, but I'll start here.
At the risk of stepping on the grass, I have been researching the rooting of an Inspire I bought used. The phone is already SIM unlocked. However, I haven't found clear answers to a couple basic questions.
1. I'm running windows XP Pro, when I installed the Easy Ace Root Tool windrivers I get a message that says I need WMP 11.
Don't have it, I use VLC.
When I plug in the USB to phone I can browse the files on the SD card in debug mode if I select mount as Disk Drive.
All I can tell is that my USB drivers are loading the phone. What should I see if the windriver is working properly, and can run the root tool from XP?
Note: I do have a new process called PassThruSvr.exe running.
2. The other option is the LiveCD. I've used Ubuntu in the past and have a couple Live CDs around.
What is the procedure for Easyacerootool with the LiveCD (minus the windrivers)? Same?
All I came up with here was http://forum.xda-developers.com/showthread.php?t=741824 which isn't applicable to the Inspire.
Thank you for your time and patience. And holy crap, a ton of great work.
Cremnomaniac said:
I've read the Ace guide, researched unlocking bootloaders, Rooting, flashing ROMs, and have more questions, but I'll start here.
At the risk of stepping on the grass, I have been researching the rooting of an Inspire I bought used. The phone is already SIM unlocked. However, I haven't found clear answers to a couple basic questions.
1. I'm running windows XP Pro, when I installed the Easy Ace Root Tool windrivers I get a message that says I need WMP 11.
Don't have it, I use VLC.
When I plug in the USB to phone I can browse the files on the SD card in debug mode if I select mount as Disk Drive.
All I can tell is that my USB drivers are loading the phone. What should I see if the windriver is working properly, and can run the root tool from XP?
Note: I do have a new process called PassThruSvr.exe running.
2. The other option is the LiveCD. I've used Ubuntu in the past and have a couple Live CDs around.
What is the procedure for Easyacerootool with the LiveCD (minus the windrivers)? Same?
All I came up with here was http://forum.xda-developers.com/showthread.php?t=741824 which isn't applicable to the Inspire.
Thank you for your time and patience. And holy crap, a ton of great work.
Click to expand...
Click to collapse
WMP has nothing to do with ADB nor Rooting. I have never heard that. Uninstall all the HTC software first and then with the phone unplugged install the driver in the tools folder.
Anyway, the Root Tool won't work in Linux but you can do the process manually.
glevitan said:
WMP has nothing to do with ADB nor Rooting. I have never heard that. Uninstall all the HTC software first and then with the phone unplugged install the driver in the tools folder.
Anyway, the Root Tool won't work in Linux but you can do the process manually.
Click to expand...
Click to collapse
Okay thanks. FYI, when I install the HTC windriver there is a message box that pops up "..to access files and folders... install WMP 11".
I should have made it clear that I did follow the procedure as stipulated, and with the phone unplugged.
What I found after running EasyAceRoot.cmd, it verifies the connection with my phone. So it looks like its working. Haven't rooted it yet, but will give it a go later.
Thanks
Done, thanks
Thanks for the help glevitan,
I ran the easyrootool, and there was some problem with the SuperSU flash. I re-ran the tool and re-flashed just the SuperSU and all seemed good.
I tried to start Titanium BU and it hung at "asking for rights". I went back and tried to open Super SU and it wasn't responding.
Removed Titanium BU and reflashed Super SU. Super SU seems to be okay now. after I reinstalled Titanium BU everything was working.
Then, I rebooted it again to make sure, and Titanium BU went back to being hung at "Asking for Root..". I do get notification that it has been granted super user permission.
Dunno, any thoughts?
Cremnomaniac said:
Thanks for the help glevitan,
I ran the easyrootool, and there was some problem with the SuperSU flash. I re-ran the tool and re-flashed just the SuperSU and all seemed good.
I tried to start Titanium BU and it hung at "asking for rights". I went back and tried to open Super SU and it wasn't responding.
Removed Titanium BU and reflashed Super SU. Super SU seems to be okay now. after I reinstalled Titanium BU everything was working.
Then, I rebooted it again to make sure, and Titanium BU went back to being hung at "Asking for Root..". I do get notification that it has been granted super user permission.
Dunno, any thoughts?
Click to expand...
Click to collapse
I'm going to post this as a new thread if I can't figure it out. The device or SuperSu doesn't allow root access. Exploring options
Cremnomaniac said:
I'm going to post this as a new thread if I can't figure it out. The device or SuperSu doesn't allow root access. Exploring options
Click to expand...
Click to collapse
RESOLVED - Issue seems to have been resolved. The only thing I did of significance was to boot into CWM recovery and run "Fix permissions". Titanium backup and other root required apps will now run, even after I reboot.
Jees, talk about a steep learning curve.
:good:
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!