Database Info

[Q] No boot loader after one-click root

Can anyone help with
1. the following problem and
2 providing advice for best (easiest) way to go from stock 3G Xoom to Android 3.1?
When I type "adb reboot bootloader" from my windoze PC, I get the following messages on my Xoom console:
Starting Fastboot protocol support.
Failed to process command error(0x120000)
repeat previous line until forced reboot.
This is a real show-stopper since it is the first step in all of the instructions. Any advice??? By the way, I have done a hard reset and rerun the one-click root.
I have ClockWorks ROM Manager installed... Is booting into recovery mode an alternative for the bootloader???
Background:
What I am really trying to do is get my stock 3G Xoom to Tiamat 1.4.2 and Android 3.1, in a rooted state, in the most efficient manner possible. Any suggestions would be welcome!!!
Background:
I am an experience developer, but new to Android development. Jason Tyler's one-click method leaves my Xoom at Tiamat 1.1.6 (2.6.36.3Tiamat_Xoom-v1.1.6...). I also installed BusyBox via Titanium Backup, but that didn't have any effect.
If I can get the bootloader to work I am planning to upgrade to Tiamat 1.3.1 as an intermediate step so that I can upgrade to Android 3.1, since Tiamat 1.4.2 upgrade says "For Android 3.1 Only". If not for that I'd try to go directly to 1.4.2. Of course all of this is a moot point if I can't get into the bootloader!!!
Help!!!!!
Any advice would be appreciated!

Look at the instructions here for updating to 3.1 from recovery...
http://forum.xda-developers.com/showthread.php?t=1074609
Then you can flash tiamats' kernel from recovery.
As for the rest, it sounds like a problem with your fastboot. Maybe download the fastboot.exe again and make sure it is in the folder you open the command prompt in.
Sent from my GT-I9000 using XDA Premium App

i one clicked to 1.16 and it was a pain. I then used a adb to get to 1.31 and used this very clear, very good guide:
http://www.xoomforums.com/forum/mot...09-flashing-kernel-through-adb-lots-pics.html
I found I really liked upgrading via adb and it was easier than one click.
From there I downloaded cwm and installed kernels and boot images from there and am now on 1.42. I used the guide noted by the second poster to upgrade to hc3.1. Note the cwm version is something like 3.0.28 not 3.0.25 which is found in ROM manager. To boot in to cwm I now reboot, when the motor logo comes up I press volume down. It shows recovery. I then press volume up to enter recovery. Power button executes an option in cwm.
Let us know how it goes.

Thanks very much for the reply! I do have a couple of issues...
Since I am at Tiamat 1.1.6, I don't have SD card support... I am just looking at whether there is a one-click for Tiamat 1.3.1, which would give me sd card support...
Also, my fastboot.exe worked previously and so I think that the problem is likely on the Xoom side, but I will look into getting a new fastboot.exe. I think it came with my Android SDk and I hope not to have to reinstall the whole thing! If it is on the xoom side, do you know of a way of restoring fastboot support on the Xoom?
CLARIFICATION: I realize that I am confusing "adb reboot bootloader" and fastboot.exe... sorry! What is the relationship? I am not currently runing fastboot.exe. Should I be? Is it an alternative to running "adb reboot bootloader" ?

one-click dose cause many problems. Adb it via the guide above.

In this thread are instructions for enabling the SD card...assuming you are able to get the bootloader sorted.
http://forum.xda-developers.com/showthread.php?t=1010568
Sent from my GT-I9000 using XDA Premium App

rschenck said:
Look at the instructions here for updating to 3.1 from recovery...
http://forum.xda-developers.com/showthread.php?t=1074609
Then you can flash tiamats' kernel from recovery.
As for the rest, it sounds like a problem with your fastboot. Maybe download the fastboot.exe again and make sure it is in the folder you open the command prompt in.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Just to clarify... the instructions at the link you sent refer to the need to have a microSD card (which I have), but to use it I would already need to be running Tiamat 1.3.1 or some other ROM that enables the micro SD card reader???? I don't think that I can flash those changes from my internal SD card, can I?
Thanks for any explanation!

RoryPG said:
one-click dose cause many problems. Adb it via the guide above.
Click to expand...
Click to collapse
I am confused... the guide looks really good, but it seems to require that "adb reboot bootloader" be working.
It is not on my machine. I may try to do another hard reset... ugggg.
Is there an adb guide that would allow me to go from a stock 3G Xoom to rooted without one-click? Thanks!

post 6 has instructions for a DB similar to the picture step-by-step guide I posted. Pick your poison. Once you upgrade to 1.31 via a DB, you can then upgrade to 1.42 via cwm. That's your simplest route.

seancallahan said:
I am confused... the guide looks really good, but it seems to require that "adb reboot bootloader" be working.
It is not on my machine. I may try to do another hard reset... ugggg.
Is there an adb guide that would allow me to go from a stock 3G Xoom to rooted without one-click? Thanks!
Click to expand...
Click to collapse
Do you have fastboot.exe in your platform-tools folder on your PC. Note this step in the instructions. If you set everything up correctly, you should be okay.

Problem Solved!!!
As usual in these cases it was simple.... I just needed to ignore the error message and go ahead and run the commands to upgrade to 1.3.1.
Thanks for all of the help. With luck I will soon be done upgrading for a bit!
Best regards.

rschenck said:
Look at the instructions here for updating to 3.1 from recovery...
http://forum.xda-developers.com/showthread.php?t=1074609
Then you can flash tiamats' kernel from recovery.
As for the rest, it sounds like a problem with your fastboot. Maybe download the fastboot.exe again and make sure it is in the folder you open the command prompt in.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Thanks so much. After getting Tiamat 1.3.1 the fast BRD approach to getting to 3.1 worked wonderfully!!!! I am finally there... thanks again!

[Q] Sprint Nexus S 4g running 2.3.5 (can or can it not be rooted)?

I am looking for some input as if the Sprint Nexus S 4g running 2.3.5 can be rooted. I have rooted an EVO before (running an older version of android) but I am having tons of trouble rooting this phone. Any input would be greatly appreciated.

My Nexus S 4G is running stock 2.3.5, and is rooted. After the GRJ90 OTA, I had to re-install clockworkmod and reflash the su.zip, but with the bootloader unlocked, that's a pretty trivial task.
If you're starting with a brand-new NS4G, like, just bought it this morning and all that's happened is the 2.3.4 -> 2.3.5 OTA, then you'll need to start by unlocking the bootloader. Search is your friend; there are definitely full unlock/root guides here on XDA. If you're looking for an executive overview, the command is "fastboot oem unlock". Then it's just a matter of flashing clockworkmod or another appropriate recovery for this device (crespo4g, not plain crespo), followed by flashing a zip with the su binary and Superuser.apk. Don't forget to disable /etc/install-recovery.sh

assuming the phone is new the bootloader is probably locked? Either way would you be able to point me in the right direction?

Check the General section. You'll find a step by step guide.
Sent from my Nexus S 4G

I have tried this- http://forum.xda-developers.com/showthread.php?t=895545
When I get to step 2 the files are not in the directory, I then copied everything from "Platform tools" (I could be wrong in regards to the exact name of file) and placed into the android-sdk-windows\tools it does not find it and I can not proceed. Am I using the right process?

jgreene1014 said:
I am looking for some input as if the Sprint Nexus S 4g running 2.3.5 can be rooted. I have rooted an EVO before (running an older version of android) but I am having tons of trouble rooting this phone. Any input would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1071500
everything you need.
you may need to rename install.recovery.sh in /etc to something else to prevent the stock recovery from being installed.
edit: if you need drivers and such, you can find them here...
http://forum.xda-developers.com/showthread.php?t=1088494

I was gunna ask the exact same question.. about to pick up my NS4G in an hour or so

jgreene1014 said:
I have tried this- http://forum.xda-developers.com/showthread.php?t=895545
When I get to step 2 the files are not in the directory, I then copied everything from "Platform tools" (I could be wrong in regards to the exact name of file) and placed into the android-sdk-windows\tools it does not find it and I can not proceed. Am I using the right process?
Click to expand...
Click to collapse
So you've downloaded the sdk and installed all the drivers for windows?
Sent from my Nexus S 4G

I chose this method http://forum.xda-developers.com/showthread.php?t=935819 Phone is now unlocked but when I get to step 2 number 19 it does not boot into clockwork a green droid with a caution sign in a triangle appears! I need help!!!
Thanks

I just rooted mine with the 1 click method found on the NS4G section. Didnt mattered it was running 2.3.5

jgreene1014 said:
I chose this method http://forum.xda-developers.com/showthread.php?t=935819 Phone is now unlocked but when I get to step 2 number 19 it does not boot into clockwork a green droid with a caution sign in a triangle appears! I need help!!!
Thanks
Click to expand...
Click to collapse
Prolly gotta unlock it, boot up, drag su zip to USB storage then boot into bootloader and flash clockwork. Immediately select the recovery option and flash su from cw. Reboot. Using root explorer or the like, rename install.recovery.sh to something else. Add a .bak to it. Reboot into bootloader and flash cw. Then it should stick. Easier and faster to do than typing this on my nexus.

I renamed the install.recovery.sh to recovery.img the first time around. Should I change to recovery.bak? I can now start my phone and I am showing the lock but when ever I go into recovery mode i get the droid with the caution sign in the triangle

jgreene1014 said:
I renamed the install.recovery.sh to recovery.img the first time around. Should I change to recovery.bak? I can now start my phone and I am showing the lock but when ever I go into recovery mode i get the droid with the caution sign in the triangle
Click to expand...
Click to collapse
If you follow my instructions directly, your recovery will stick.
Sent from my Nexus S 4G using XDA Premium App

Thanks A bunch!!!!! That did it all set with root!

jgreene1014 said:
Thanks A bunch!!!!! That did it all set with root!
Click to expand...
Click to collapse
No problem.
Sent from my Nexus S 4G via XDA Premium

[Q] I unlocked bootloader but can't seem to root my nexus s 4g

I see a few other posts similar to mine but there is a few differences. My Sprint nexus s 4g has been unlocked by me a few days ago. I used SDK manager and did the unlock oem command through command line. I then installed SU on my phone and don't have root still. I am not sure what I am doing wrong but I have tried many different things....Rom manager cant write where it wants to update or install things. One click acts like it worked but never changes anything. Of course my binaries are out of date with su but it cant find the binaries to update when it tries. I wouldn't doubt that the issues I am having might be because I didn't do something correctly when I unlocked bootloader.
I am running 2.3.7 droid os
kernel version 2.6.35.7
build gwk740
if that helps...Any info would be very much appreciated.

Get the su zip and put on your phones internal storage.
Reflash cwm in with fastboot on.your computer.
Boot into the recovery. Do not boot up the os or it will overwrite cwm.
In recovery flash the su zip from step 1.
That's it. You have root. Boot up phone. Launch su from app draw. Launch app that needs root and you can now grant it su permissions.

gooru11 said:
I see a few other posts similar to mine but there is a few differences. My Sprint nexus s 4g has been unlocked by me a few days ago. I used SDK manager and did the unlock oem command through command line. I then installed SU on my phone and don't have root still. I am not sure what I am doing wrong but I have tried many different things....Rom manager cant write where it wants to update or install things. One click acts like it worked but never changes anything. Of course my binaries are out of date with su but it cant find the binaries to update when it tries. I wouldn't doubt that the issues I am having might be because I didn't do something correctly when I unlocked bootloader.
I am running 2.3.7 droid os
kernel version 2.6.35.7
build gwk740
if that helps...Any info would be very much appreciated.
Click to expand...
Click to collapse
There's literally no way you can not correctly unlock the boot loader, either it's locked or it's not.
fastboot oem unlock
Don't select no
Finished
When you flash the su binary, mount /system through CWM first

I had the same problem but i just used the one click nexus root instead going thru the sdk manager and manually doing the adb commands , just look up one click nexus root in the nexus 4g development section and plug in ur phone follow directions it will do all the work for you

Thanks for the replys
For some reason my recovery mode just reboots the phone. If i could restore the phione I would have just started over.

I guess there is no new information for me?

Why can't you undo it? I would think you could download the zip with the stock images and follow the steps to unroot, you just would need to turn on your phone to the bootloader and skip the step to reboot bootloader. Then afterwards you could just go back through the rooting steps or just do the one click suggested above. To boot to bootloader you just hold volume up and the power button from an off state I believe, or volume down... Don't remember
Sent from my Nexus S 4G

Downgrade to lower version to use revolution

Im trying to get my desire s downgraded, rooted and be able to install a custom rom on it. I have searched and tried all guides on here but none of them seem to work anymore there are always files missing, web sites down or just things out of date I already have a gold card on my memory card.
I cant use revolution as my version is too high and needs to be downgraded can someone help me plz with the files or destination of them thanks.

Re. Downgrade....
Hallo...I am attaching zip with the files i`ve downloaded someday long ago,
,there is also file without extension which you can open wirh any text editor-
- it is description i`ve got from the original thread about the downgrading procedure..
I hope this is all you need to proceed to tthe fruitful end...
Good luck
And one more thing, those files were ment for versions lower than ics
so if you are running ics, they might be useless...No harm in trying though
Edit. I do not have the ruu but there is a beautifull thread in development section:
INDEX of ROMS/RECOVERY/ROOT/GUIDES/HBOOT/RADIOS/TWEAKS etc
you can find many answers there ...

This is one of the few sites that you can still get the RUUs http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
Intel Inside: The world's most widely used warning label. - Jim Hooper.

jugg1es said:
This is one of the few sites that you can still get the RUUs http://www.tsar3000.com/Joomla/inde...-stock-roms&catid=65:htc-downloads&Itemid=107
Intel Inside: The world's most widely used warning label. - Jim Hooper.
Click to expand...
Click to collapse
My phone is branded to o2 but unlocked do i have to get a o2 ruu it will be used on tmobile when done but i don't want any branding on it. Sorry used to my sgs3 this is so different
Sent from my HTC Desire S using xda app-developers app

--> please notice: if you have a branded device, use a branded RUU to downgrade!
I strongly encourage you to read full tutorial first
Our desire s -> development-> Index, roms, recoveries...
Click to expand...
Click to collapse

got an issue already the first line adb push zergRush /data/local/tmp adb is saying cannot stat zergrush no such file or directory I have cd to the folder its in. ?????
got past that line now stuck at adb shell chmod 777 /data/local/tmp/misc_version
now

Re: downgrade...
torres76 said:
got an issue already the first line adb push zergRush /data/local/tmp adb is saying cannot stat zergrush no such file or directory I have cd to the folder its in. ?????
got past that line now stuck at adb shell chmod 777 /data/local/tmp/misc_version
now
Click to expand...
Click to collapse
are you rooted- if so then after adb shell you shall press enter
,and if you see a $ sign, type su
then in your device superuser app will ask you for superuser rights for the shell-
you grant it there
then in the terminal the sign should change to #
then you are ready for chmod 777[space]/data/local/....
Edit:
after you`l have succeded this procedure to the very end and have rebooted the device succesfuly!!
to flash ruu you need to relock your bootloader( you know this)
fastboot oem lock
I you are stuck along the way then write again- better be safe than sorry

asgardr said:
are you rooted- if so then after adb shell you shall press enter
,and if you see a $ sign, type su
then in your device superuser app will ask you for superuser rights for the shell-
you grant it there
then in the terminal the sign should change to #
then you are ready for chmod 777[space]/data/local/....
Edit:
after you`l have succeded this procedure to the very end and have rebooted the device succesfuly!!
to flash ruu you need to relock your bootloader( you know this)
fastboot oem lock
I you are stuck along the way then write again- better be safe than sorry
Click to expand...
Click to collapse
no im not rooted need to downgrade first don't I, seriously doing this is so hard so many different things to try it is confusing.

but you are unlocked aren`t you- by htc dev?
if this is so now it is time to get the recovery for saga,
flash it from fastboot fastboot flash recovery recovery.img...
then you ought to get superuser zip for saga and flash it from your newly installed recovery
and then your live with downgrading will be much easier
Edit: in the attachment yoou have
1. recovery.img flash from fastboot,,, fastboot flash recovery recovery.img
2. superuser.zip flash from recovery
any doubts? write...

torres76 said:
no im not rooted need to downgrade first don't I, seriously doing this is so hard so many different things to try it is confusing.
Click to expand...
Click to collapse
im not unlocked from htcdev registered but got no email so cant use the site 8-(

Re. Downgrade....
hoooo... pull the horses... when i read my post, it looks bit chaotic,
let us organise it ....
first:
you said before that you are unlocked- if that is true then either by htc dev or your device is natively
opened by manufacturer..either way you can flash recovery and root your phone.
Second:
if the first line in your bootloader(phone off then symultanously pressing power and volume down)
states >> locked<< then your phone is in an untouched state- stock
Third:
if your device is stock, and unrooted, without custom recovery
then the files from the downgrade zip are needed,
- zerg rush which is an exploit that lets us get temporary root for the shell,
and it is gone after you reboot the phone.
- misc_version that lets us change-or fool the phone about the software version that we have on board
Now, there is much more to it but.... see first what you can do with what you know already

asgardr said:
hoooo... pull the horses... when i read my post, it looks bit chaotic,
let us organise it ....
first:
you said before that you are unlocked- if that is true then either by htc dev or your device is natively
opened by manufacturer..either way you can flash recovery and root your phone.
Second:
if the first line in your bootloader(phone off then symultanously pressing power and volume down)
states >> locked<< then your phone is in an untouched state- stock
Third:
if your device is stock, and unrooted, without custom recovery
then the files from the downgrade zip are needed,
- zerg rush which is an exploit that lets us get temporary root for the shell,
and it is gone after you reboot the phone.
- misc_version that lets us change-or fool the phone about the software version that we have on board
Now, there is much more to it but.... see first what you can do with what you know already
Click to expand...
Click to collapse
Thanks mate I am now unlocked through htcdev had to reregister now everything is completed, so next step root ???? correct

Re: downgrade...
torres76 said:
im not unlocked from htcdev registered but got no email so cant use the site 8-(
Click to expand...
Click to collapse
I am not in your skin so it is realy difficult for me to advise you
either way but:
you can try again htc dev (or wait for email from them-check if you`ve followed their procedure to the letter)
procedure that is easier for all of us with less expearience
you can try to downgrade and s-off with another procedure- which is more difficult but works for many people,
have to decide yourself
I am s-on again- with an unlocked bootloader, because i am comfortable with it- not need s-off for now really,
but can speak only for myself

asgardr said:
I am not in your skin so it is realy bifficult for me to advise youeither way but:
you can try again htc dev (or wait for email from them-check if you`ve followed their procedure to the letter)
procedure that is easier for all of us with less expearience
you can try to downgrade and s-off with another procedure- which is more difficult but works for many people,
have to decide yourself
Click to expand...
Click to collapse
you didn't read my last message I am now unlocked via htcdev, but still have problems when trying to run the adb shell chmod 777 /data/local/tmp/misc_versionnow command it says permission denied is it because im not rooted ???

torres76 said:
Thanks mate I am now unlocked through htcdev had to reregister now everything is completed, so next step root ???? correct
Click to expand...
Click to collapse
Recovery first from fastboot
then root from recovery
congrats

asgardr said:
Recovery first from fastboot
then root from recovery
congrats
Click to expand...
Click to collapse
I rooted with oneclickroot what now
adb shell is showing # not $ now so all good now how too downgrade

Re. Downgrade....
torres76 said:
I rooted with oneclickroot what now
adb shell is showing # not $ now so all good now how too downgrade
Click to expand...
Click to collapse
1. if i were you I`d flash recovery from fastboot-just in case- you`l need it anyway
2. make backup of your curent rom -from recovery-just in case something goes wrong
3. try if the root remains after reboot- if not- then flash su (you`ll find in the second attachment) from recovery
4.push misc_version and do the rest of downgrade procedure to the letter
5.make sure you have the right ruu after you have lowered your software version number- run it and wait till it finishes
6. keep the unlock token from htc in a safe place- just in case
7. go to the revolutionary site, download the needed program and follow their procedure to remove
s-on
8. should also flash eng. hboot(should br extremely carefull with that-get as much info as you can) but it may be later
9. choose custom or stock ROOTED rom you want to flash- and flash it
10. enjoy your free saga
Steps: 1,2,3,4,5,6,7,9,10- important
8- best get some info and confidance first before you do it
Seems to much- i know- but it isn`t... remember: rush is the bad advisor
Edit:
almost forgotten: between step 4 and 5
to flash ruu you must relock bootloader- this is important
command fastboot oem lock
check this http://forum.xda-developers.com/showthread.php?t=1318919

torres76 said:
im not unlocked from htcdev registered but got no email so cant use the site 8-(
Click to expand...
Click to collapse
u search in the spam folder? i had the same problem

zgabi28 said:
u search in the spam folder? i had the same problem
Click to expand...
Click to collapse
yeah I did mate cheers it wasn't there I reregistered. cant wait to get my sgs3 back

asgardr said:
1. if i were you I`d flash recovery from fastboot-just in case- you`l need it anyway
2. make backup of your curent rom -from recovery-just in case something goes wrong
3. try if the root remains after reboot- if not- then flash su (you`ll find in the second attachment) from recovery
4.push misc_version and do the rest of downgrade procedure to the letter
5.make sure you have the right ruu after you have lowered your software version number- run it and wait till it finishes
6. keep the unlock token from htc in a safe place- just in case
7. go to the revolutionary site, download the needed program and follow their procedure to remove
s-on
8. should also flash eng. hboot(should br extremely carefull with that-get as much info as you can) but it may be later
9. choose custom or stock ROOTED rom you want to flash- and flash it
10. enjoy your free saga
Steps: 1,2,3,4,5,6,7,9,10- important
8- best get some info and confidance first before you do it
Seems to much- i know- but it isn`t... remember: rush is the bad advisor
Edit:
almost forgotten: between step 4 and 5
to flash ruu you must relock bootloader- this is important
command fastboot oem lock
check this http://forum.xda-developers.com/showthread.php?t=1318919
Click to expand...
Click to collapse
hey mate good so far just need to install the engineers hboot do you have it

Helppppppp

I hope there is still people on this mytouch forum lol? I need help rooting my mytouch 4g slide its on kitkat I looked around how to on kitkat first time tryna root. Also any help out there that can guide me to not brickin it or if other steps need to be takin because of kitkat?

Ive read 20+ pages so far and this is frustrating lol I want same rom just want to be perm rooted to be able to mount to sd card screenshot and use other rooted apps.

SOEBOMB said:
Ive read 20+ pages so far and this is frustrating lol I want same rom just want to be perm rooted to be able to mount to sd card screenshot and use other rooted apps.
Click to expand...
Click to collapse
Did you lose superuser, or did the bootloader relock?
If it's the former, you could try this:
...you could try pushing su to the device with adb (depends on how you lost root):
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
adb push su /system/xbin/
adb shell chmod 06755 /system/xbin/su
... with this file (extracted).
Source (with mount point changed)
Click to expand...
Click to collapse

joel.maxuel said:
Did you lose superuser, or did the bootloader relock?
If it's the former, you could try this:
Click to expand...
Click to collapse
Thanks fpr the reply I never had root nor have I rooted a phone noob here lol ive read also that kitkat needs to be downgraded.that true to root?

SOEBOMB said:
Thanks fpr the reply I never had root nor have I rooted a phone noob here lol ive read also that kitkat needs to be downgraded.that true to root?
Click to expand...
Click to collapse
I don't think it's possible to be able to install a ROM without the bootloader unlocked (prerequisite for CWM, and in turn KitKat ROM). Unless you got the phone with KitKat (eBay special?) but no root (which would be weird for a seller to do), you must have lost root along the way (it can happen).
In either case, we are not talking about the bootloader. The way to check that though, is to turn on the device while holding the Vol-Dn button. This will take you into fastboot. If it says ** RELOCKED ** up top, then you're in trouble. If it says ** UNLOCKED ** or * JuoPunutbear *, it looks like you just need superuser reinstalled, and you don't need to downgrade for that.
To do this, download and install the adb binary and drivers (if you're a linux user, all you need to do is an 'apt-get install adb' or whatever your distro uses). Turn on the device normally, go into Developer under settings (may need to go into About phone first and tap Build Number 7 or 8 times for Developer menu to appear). Turn on USB debugging. Now connect a cable between your device and your PC. Fire up a command prompt on the PC (can be left open after installing ADB, as you want to be in the same folder as it) and type:
Code:
adb devices
If you get a device, and is listed as online, you are ready to enter the commands for the second part, in the order as they appear in my previous post.
If the first command does not work (as I cannot find the appropriate folder on my 10.1 distro), try:
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/mmcblk0p22 /system
Or to see if that folder exists for you first, try:
Code:
adb shell ls /dev/block/platform/msm_sdcc.1/by-name/
If you get a list of partitions, (including system) you should be good to proceed with that command. If not (by-name not found), use the above command. Hope this helps.

Ok looked im on android 2.3.4 and also looked at the boot loader things says locked and I did get it off ebay lmao good call. 1.45.0013 bootloader also

SOEBOMB said:
Ok looked im on android 2.3.4 and also looked at the boot loader things says locked and I did get it off ebay lmao good call. 1.45.0013 bootloader also
Click to expand...
Click to collapse
Okay, so that's Gingerbread, not KitKat.
I used this guide when I did mine (second pin down in the MT4GS Developer forum):
http://forum.xda-developers.com/showthread.php?t=1801106
jjbz said:
Here’s a breakdown of the process:
1. INSTALL HTC DRIVERS ON YOUR PC.
2. INSTALL ADB AND FASTBOOT ON YOUR PC.
3. REGISTER AT HTC DEV.
4. UNLOCK BOOTLOADER THROUGH HTC DEV.
5. INSTALL A CUSTOM RECOVERY.
6. ROOT YOUR DEVICE.
7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).
-PREREQUISITES-
Before getting started, please visit the MT4GS Compendium and read over Section One to learn the XDA Lingo. You really need to know this stuff if you’re going to tinker with the MT4GS.
Also, all information in the guide assumes you are using a Windows PC and a MT4GS with the STOCK ROM AND HBOOT-1.45.0013. If you are not on the Stock ROM, please use Blue6IX’s post “How-To: Restore to Stock.” Be sure to use the latest OTA (1.63.531.2). Once you're all set, let’s begin, shall we?
Disclaimer: I am not responsible for anything that happens to your phone. You assume all risks associated with modifying your phone.
-1. INSTALL HTC DRIVERS ON YOUR PC.-
Install the HTC Drivers on your PC from here.
Before connecting your phone, make sure USB Debugging is enabled (Settings>Applications>Development>USB Debugging).
Tip: to save time later, turn off your phone, hold down Power & Volume Down simultaneously until you reach the bootloader. Use the volume buttons to navigate to FASTBOOT and select it with the power button. Connect your phone via USB and the bootloader should now say FASTBOOT USB mode. Allow your PC to install the required drivers automatically. It may take a few minutes for your PC to search for and install drivers, so be patient.
-2. INSTALL ADB AND FASTBOOT ON YOUR PC.-
Installing ADB and fastboot on your PC is easy. Follow this guide and you’re good to go. To confirm that you have successfully installed ADB and fastboot, connect phone (with USB Debugging enabled) to PC via USB, open command prompt, and type “adb devices”. Your device ID number should be listed. Here are some useful commands for ADB and fastboot.
-3. REGISTER AT HTC DEV.-
Self-explanatory. Visit HTCDev.com and sign up with a valid e-mail address, as you’ll be receiving your Unlock_code.bin from HTC through this e-mail. Use an alternate browser such as IE, Google Chrome, or Mozilla Firefox if HTC Dev doesn’t play nice with your current browser of choice. Personally, I had to switch between Chrome and Firefox to get the HTC Dev website to cooperate.
-4. UNLOCK BOOTLOADER THROUGH HTC DEV.-
Make sure you’re logged in to HTC Dev and follow on-screen instructions to unlock bootloader. FYI, our device is listed as “myTouch 4G Slide (T-Mobile US)”. You can skip HTC’s instructions until step 5 since they're just telling you how to install ADB and fastboot, but you should already have ADB and fastboot installed .
After you finish unlocking the bootloader, the first line in your bootloader should read “*** UNLOCKED ***”.
-5. INSTALL A CUSTOM RECOVERY.-
Download official ClockworkMod Recovery 5.0.2.7 from the ROM Manager website or download another custom recovery from the MT4GS Development section. For instruction purposes, I will assume that you use official CWM Recovery 5.0.2.7. Save the img file to C:\.
Put your phone in bootloader FASTBOOT mode and connect to PC. Go to command prompt on PC and type “fastboot devices”. Once your device ID is listed, type “cd\” to get to “C:\” directory. Then type “fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img”.
After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping.
NOTE: Use volume buttons or trackpad to navigate through CWM Recovery 5.0.2.7. Select items by pressing the trackball. Power button may make your screen go blank and Back button returns you to the previous menu.
-6. ROOT YOUR DEVICE.-
Now that you have a custom recovery, you can flash custom ROMs. These custom ROMs are already rooted with Superuser and binary files.
NOTE: If you are S-ON, installing a custom ICS ROM will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
HOWEVER, if you want to root the STOCK ROM and/or continue to step 7 to achieve JuopunutBear S-OFF, you’ll have to root the device yourself. This is very simple. Download Superuser ZIP from androidsu.com/superuser. I can only recommend version 3.0.7 efgh because that is the only one I have tested, but newer versions may work.
Place the “Superuser-3.0.7-efgh-signed” on the ROOT of your SD card. Go to CWM Recovery and use “install zip from sdcard” to flash the Superuser zip. If installation aborts or fails the first time, try to flash the zip again until installation is complete. Reboot your phone and check in your apps to see if Superuser app is there. If so, congratulations, you have successfully rooted your stock MT4GS!
-7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).-
Achieving S-OFF will make your life a lot easier if you want to flash custom ROMs, especially ICS ROMs. Follow instructions for JuopunutBear at unlimited.io and check out the JB S-OFF thread for other users’ experiences.
As I said before, if you are S-ON, flashing ICS ROMs will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
Click to expand...
Click to collapse
For step two, you can use the adb binary I mentioned earlier. Same thing, different location.
As said above, you don't need to do step 7. If you are afraid of potenitally ruining your phone with the "wire trick" I wouldn't bother with the step, just keep in mind when you do put KitKat on your phone, you will have to extract the boot.img from the package, go into the bootloaders fastboot mode and run the following command (from your PC):
Code:
fastboot flash boot boot.img
And you can apparently do this before or after (get CWM to reboot to bootloader) flashing with CWM (which you will need to upgrade to get KitKat) to avoid a bootloop. If that happens, pull the battery, reinsert, then power up into the bootloader (Pwr+Vol-Dn keys).

Ok bud thanks for all ur help so far I just have a few questions sorry 14 hr days dnt help me check in lol. Question 1 if I don't have kitkat y can't.I move apps to my sd card? Question 2 do I need to downgrade. Anything to root? Question 3 y can't I save apps on my sd?

SOEBOMB said:
Ok bud thanks for all ur help so far I just have a few questions sorry 14 hr days dnt help me check in lol. Question 1 if I don't have kitkat y can't.I move apps to my sd card? Question 2 do I need to downgrade. Anything to root? Question 3 y can't I save apps on my sd?
Click to expand...
Click to collapse
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.

joel.maxuel said:
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.
Click to expand...
Click to collapse
Well ima gna try to root it with what u posted I feel a bit better knowing I dont have to donwgrade and all that etc. im gna follow the steps.hopefully ill be posting in a rooted device in the near future lol paperweights this rookie dnt need

Any other tips I should know?

SOEBOMB said:
Any other tips I should know?
Click to expand...
Click to collapse
Be sure to make a backup in Clockwork Mod or whatever custom recovery you install. This will give you the chance to rollback should you encounter any problems swapping to a custom rom.

Alandra said:
Be sure to make a backup in Clockwork Mod or whatever custom recovery you install. This will give you the chance to rollback should you encounter any problems swapping to a custom rom.
Click to expand...
Click to collapse
Prolly not gna flash a rom should I still do a backup I read rooting clears ur whole phone is that true like sd card n all? I domt care for music n etc jus dnt wanna lose my sons photos off my sd

SOEBOMB said:
Prolly not gna flash a rom should I still do a backup I read rooting clears ur whole phone is that true like sd card n all? I domt care for music n etc jus dnt wanna lose my sons photos off my sd
Click to expand...
Click to collapse
Unlocking the bootloader does, yes, wipe your /data partition, but that should be all (besides /cache). If you are concerned about it wiping your MicroSD as well, can always pull the card before getting to that step.

joel.maxuel said:
...and multitasking makes my responses to the point. I have answered them as they were asked.
1. I cannot remember what stock ROM offered at this point, if they had a Move apps to SD option
2. If your Android Version is truly 2.3.4 then there is nothing to downgrade to. You are on stock Gingerbread. Had your version been 4.4.2 (or anything 4.4), then I can safely say that is KitKat. You will need to root to change that situation.
3. I don't know. As mentioned above, I didn't stay on stock ROM long enough to discover Apps to SD. Have used Link2SD since then, but not in that time frame. Sorry.
Click to expand...
Click to collapse
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?

SOEBOMB said:
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?
Click to expand...
Click to collapse
My H-BOOT is 1.45 as well (1.45.1313 since I went S-OFF) and I had no problem rooting. Probably talking about outdated information, like when everyone rooted their phone with Revolutionary. Rooting is possible, S-OFF is possible (via JuopunutBear). And the last bit about trouble flashing ROMs has to do with having to flash the boot.img file as well because you are still S-ON (please see my earlier post about that).

SOEBOMB said:
Default Read this before posting. MT4G Slide Compendium
The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. Reference thread
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
so i read this on a link is it true i cant root?
Click to expand...
Click to collapse
I am also on H-Boot 1.45.0013 and have had no problems rooting and installing custom roms. I am still S-On, which has caused me no issues, but I simply have to use the method in this post to successfully flash a new rom:
http://forum.xda-developers.com/showpost.php?p=22774848&postcount=1

s off toolkit
has anyone used this to root and s-off there mt4gs???
http://forum.xda-developers.com/showthread.php?t=1532809
http://forum.xda-developers.com/show....php?t=1696373

SOEBOMB said:
has anyone used this to root and s-off there mt4gs???
http://forum.xda-developers.com/showthread.php?t=1532809
http://forum.xda-developers.com/showthread.php?t=1696373
Click to expand...
Click to collapse
Cannot say I have. Mind you I'm a linux user so I avoid windows programs where I can.
The second link was broken. I fixed it in the quote. In regard to version 2.0 (first link), the download links have been pulled and the thread closed. Don't bother asking anyone for it. Version 1.0 appears to be still up, although by the looks of the screenshot and changelog, you would be better off following the guide. It's not that difficult.

SOEBOMB said:
Any other tips I should know?
Click to expand...
Click to collapse
Superuser link appears dead. Here is a live one...