[Q] [Solved] Noob Root Questions - Seeking Guidance - AT&T, Rogers HTC One X, Telstra One XL

[Q] [Solved] Noob Root Questions - Seeking Guidance - AT&T, Rogers HTC One X, Telstra One XL

Hello all,
I know everyone hates people who post without searching the forums first, but I did and I am still very lost on what all I need to do to root my device and get going flashing ROMs with the new 2.20 Root Method.
I have used this thread to get me started (http://forum.xda-developers.com/showthread.php?t=1684382&highlight=root+guide) and I have already downloaded Android SDK from google + Platform-tools + Google USB Driver but I don't want to get going on root because in the instructions from 2.20 Root it states:
10. After unlocking the bootloader, you can flash a custom recovery partition via fastboot, boot into recovery mode, and use a recovery ADB shell or install from an update.zip to install Superuser and su (I do not provide support for custom recoveries, but this is a straightforward process that other people can help with).
I have searched the above linked thread and cannot determine how to generate a custom recovery partition (unless I did when I used the command "adb -backup all" in the platform-tools folder of the Android SDK..Furthermore, I do not know what "Superuser and su" is referencing.
If anyone could point me in the right direction, I dont mind doing the reading myself but I have gotten bogged down in the details. Basically, I want to save all of you the trouble of another noob who has bricked their phone because they didn't do their homework. Thanks all for your help!

TheEmpyre said:
I have searched the above linked thread and cannot determine how to generate a custom recovery partition
Click to expand...
Click to collapse
You don't need to "generate" anything, not sure where you got that terminology from. Just install Goomanager from the Play Store and use that to install TWRP recovery.
---------- Post added at 09:20 AM ---------- Previous post was at 09:12 AM ----------
TheEmpyre said:
Furthermore, I do not know what "Superuser and su" is referencing.
Click to expand...
Click to collapse
In plain terms a superuser = a root user. But when discussed here, it usually references the app that manages what other apps have root access.
Superuser is required to perform root functions.
You can obtain the app various ways, all discussed here: http://forum.xda-developers.com/showthread.php?t=1954361

TheEmpyre said:
Hello all,
I know everyone hates people who post without searching the forums first, but I did and I am still very lost on what all I need to do to root my device and get going flashing ROMs with the new 2.20 Root Method.
I have used this thread to get me started (http://forum.xda-developers.com/showthread.php?t=1684382&highlight=root+guide) and I have already downloaded Android SDK from google + Platform-tools + Google USB Driver but I don't want to get going on root because in the instructions from 2.20 Root it states:
10. After unlocking the bootloader, you can flash a custom recovery partition via fastboot, boot into recovery mode, and use a recovery ADB shell or install from an update.zip to install Superuser and su (I do not provide support for custom recoveries, but this is a straightforward process that other people can help with).
I have searched the above linked thread and cannot determine how to generate a custom recovery partition (unless I did when I used the command "adb -backup all" in the platform-tools folder of the Android SDK..Furthermore, I do not know what "Superuser and su" is referencing.
If anyone could point me in the right direction, I dont mind doing the reading myself but I have gotten bogged down in the details. Basically, I want to save all of you the trouble of another noob who has bricked their phone because they didn't do their homework. Thanks all for your help!
Click to expand...
Click to collapse
ctennenh said:
I second this request. I feel like there are loads of helpful threads but after searching for a long time I don't see anything that leads someone new to Android rooting from stock 2.2 to having something like CM10 on their device. All of the write-ups I've found assume more experience than I have. Is there a general guide somewhere that I'm missing? Maybe something that explains rooting, backing up, flashing, etc. from start to finish where we can replace "this is where you root your device" with the new rooting method? I'm assuming it's out there but I can't seem to find it anywhere.
Click to expand...
Click to collapse
They are many simple tutorials for rooting but do not know why you guys having hard time. Ok here is
1) You got Android SDK from google + Platform-tools + Google USB Driver -
2) Only for windows - Download htc sync ( It will install necessary htc drivers) - Link
3) Just to check if htc drivers installed properly , open "C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists).
4) In command window type " adb devices" and see output - If you get output then htc drivers installed properly.
You can skip step 3 and step 4 - These steps are only for verification
5) Goto [ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit and follow the instructions there.
6) Once you successfully root your device using above exploit then goto - [How To] Flash Custom recovery and ROMS after 2.20 root complete the steps to flash custom recovery and if you want to flash ROMS
7) To unlock BOOT LOADER use this link - [INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up , follow the instructions under " BOOTLOADER UNLOCK, SUPER CID, AND S-OFF"
You can also goto this link - [ROOT][2.20] One XL Bootloader unlock & Root guide By XsMagical - Very nice tutorial, if you find above links difficult to follow
Note* : During exploit or flashing recovery they talk about using fastboot commands, In order to execute them you need goto C:\android-sdk\platform-tools" ( Or folder where adb and fastboot exists) then "Press shift + right click and select "Open command window here" ( open command prompt and cd "folder where adb and fastboot exists) and then execute the commands ..
Advice - Do not flash any roms apart from xda

Thank you, abhipati. I haven't seen any simple tutorials that are complete. Everything seems to assume the user knows how to do something mentioned in another thread, which in turn seems to assume something else. Your post seems like a very clear start-to-finish explanation. Maybe it should be made into a stickie in Q&A. I can surely handle step 1 but maybe that could be explained (or at least a link added to an appropriate thread).
If all this is out there somewhere already then I certainly didn't know where to find it. I appreciate your help.

ctennenh said:
Thank you, abhipati. I haven't seen any simple tutorials that are complete. Everything seems to assume the user knows how to do something mentioned in another thread, which in turn seems to assume something else. Your post seems like a very clear start-to-finish explanation. Maybe it should be made into a stickie in Q&A. I can surely handle step 1 but maybe that could be explained (or at least a link added to an appropriate thread).
If all this is out there somewhere already then I certainly didn't know where to find it. I appreciate your help.
Click to expand...
Click to collapse
No problem.
Regarding step 1)
1) Download Android SDK from here {For Windows}
2) Download java you need it - here

Thank you all for helping gather some resources for me that I know are up to date etc. - Thankfully I do know a few unix commands so that I can navigate the command prompt aspects...I'm sure these threads get annoying so thank you very much for getting a new-to-root user up and running. I'll try this all later this evening and throw an update to let you all know how it goes -- hopefully no "bricked my phone" thread in the future

Excellent I have successfully unlocked my bootloader and achieved perm-root! Now on to flashing roms and I have some questions:
1) I have read GuyIncognito's instructions here (http://forum.xda-developers.com/showthread.php?t=1952076) on Flashing ROMs and how to go about doing that and i fully understand the process but I want to confirm (Yes I Have TWRP recovery installed and running) I only need to extract the boot.img out of the winRAR file of the ROM that I downloaded? (CM10 seems to be popular so I'm starting with that as my first ROM) There are so many other files in the package and I'm wondering why do you only need the boot.img file to be present with your adb and fastboot files from the google dev SDK -- the boot.img is only 5 MB and I can hardly believe that it constitutes the whole OS?
2) How do I go about installing gapps after I have flashed my ROM? I have downloaded Gapps so I have the file...do I place it in my SD Card and then enter recovery to install it? or Do have to use adb to flash it
Edit: I also have Superuser app on my stock ROM right now
Any further help is much appreciated, thank you very much.

Boot.img is technically just the kernel, it's the heart of the OS you are installing. Once extracted, rezip rom. Flash boot.img first using fastboot command prompt. Then flash the Rom itself that you rezipped through twrp
You can easily just flash gapps through twrp.
Sent from my HTC One XL using xda premium

InflatedTitan said:
Boot.img is technically just the kernel, it's the heart of the OS you are installing. Once extracted, rezip rom. Flash boot.img first using fastboot command prompt. Then flash the Rom itself that you rezipped through twrp
You can easily just flash gapps through twrp.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the reply, the community on XDA kicks a$$, doing some additional reading just plz tell me if I understand this correctly...
1) Copy CM10 zip and Gapps zip into phone storage
2) Follow GuyIncognito's instructions on flashing boot.img
3) Boot into recovery AFTER Flashing boot.img
4) Select "Install" in TWRP
5) Install CM10 zip First
6) Install Gapps zip next
7) Reboot
8) profit?

TheEmpyre said:
Excellent I have successfully unlocked my bootloader and achieved perm-root! Now on to flashing roms and I have some questions:
1) I have read GuyIncognito's instructions here (http://forum.xda-developers.com/showthread.php?t=1952076) on Flashing ROMs and how to go about doing that and i fully understand the process but I want to confirm (Yes I Have TWRP recovery installed and running) I only need to extract the boot.img out of the winRAR file of the ROM that I downloaded? (CM10 seems to be popular so I'm starting with that as my first ROM) There are so many other files in the package and I'm wondering why do you only need the boot.img file to be present with your adb and fastboot files from the google dev SDK -- the boot.img is only 5 MB and I can hardly believe that it constitutes the whole OS?
2) How do I go about installing gapps after I have flashed my ROM? I have downloaded Gapps so I have the file...do I place it in my SD Card and then enter recovery to install it? or Do have to use adb to flash it
Edit: I also have Superuser app on my stock ROM right now
Any further help is much appreciated, thank you very much.
Click to expand...
Click to collapse
follow his instructions and you'll be fine
flash the boot.img in flashboot, reboot in recovery, flash your nameofrom.zip, flash your gapps pkg just like the rom (on your sd card), enjoy...
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
TheEmpyre said:
Thanks for the reply, the community on XDA kicks a$$, doing some additional reading just plz tell me if I understand this correctly...
1) Copy CM10 zip and Gapps zip into phone storage
2) Follow GuyIncognito's instructions on flashing boot.img
3) Boot into recovery AFTER Flashing boot.img
4) Select "Install" in TWRP
5) Install CM10 zip First
6) Install Gapps zip next
7) Reboot
8) profit?
Click to expand...
Click to collapse
yes that;s correct you may wanna backup your sd card 1st as well and do a full wipe before flashing the rom.

Just in case your not familiar with fastboot, the command is fastboot flash boot boot.img
Sent from my HTC One XL using xda premium

Crappyvate said:
follow his instructions and you'll be fine
flash the boot.img in flashboot, reboot in recovery, flash your nameofrom.zip, flash your gapps pkg just like the rom (on your sd card), enjoy...
Click to expand...
Click to collapse
By Flash do you mean using TWRP recovery "install" feature and selecting the CM10.zip I have in my SD Card, and gapps? Just making sure I dont have to do it via command prompt cuz then I may have to do some additional reading
Edit: Just saw you all beat me to it, thanks all, will get back to you after I am running a ROM *crossfingers*

TheEmpyre said:
By Flash do you mean using TWRP recovery "install" feature and selecting the CM10.zip I have in my SD Card, and gapps? Just making sure I dont have to do it via command prompt cuz then I may have to do some additional reading
Click to expand...
Click to collapse
yes install. you dont need to do it from command prompt, additional reading is always good
even though it was put together a while back this http://forum.xda-developers.com/showthread.php?t=1678308 is a very good guide and covers a lot of things of course you should absolutely start here in redpoint indispensable guide to all the resources available to one xl http://forum.xda-developers.com/showthread.php?t=1671237
happy flashing

Alright Looks like I successfully flashed CM10! I flashed gapps with it at the same time but I have run into a problem -- It keeps telling me that all these gapps processes have failed and I have no access to a keyboard! Do I have to reflash gapps?

Hmm ok I think I messed up here....
My phone was essentially non-functional with CM10 -- Nothing worked and it took me a while to navigate to enable USB Debugging on the given mod. One I enabled USB Debugging in CM10 I ran the following:
adb reboot recovery
Once I was in recovery, I Restored a backup of my device that I made BEFORE I obtained permanent root via the toolkit as it was recommended during this time to make a recovery.
Recovery worked successfully, now after reboot it hangs on the HTC screen and then goes black, then reboots again, and again, and again...
I haven't been able to use the volume down + power button to even get back into the bootloader.....hopefully I am not screwed here...Any suggestions?

TheEmpyre said:
Hmm ok I think I messed up here....
My phone was essentially non-functional with CM10 -- Nothing worked and it took me a while to navigate to enable USB Debugging on the given mod. One I enabled USB Debugging in CM10 I ran the following:
adb reboot recovery
Once I was in recovery, I Restored a backup of my device that I made BEFORE I obtained permanent root via the toolkit as it was recommended during this time to make a recovery.
Recovery worked successfully, now after reboot it hangs on the HTC screen and then goes black, then reboots again, and again, and again...
I haven't been able to use the volume down + power button to even get back into the bootloader.....hopefully I am not screwed here...Any suggestions?
Click to expand...
Click to collapse
I think u need to flash that backups boot IMG

omario8484 said:
I think u need to flash that backups boot IMG
Click to expand...
Click to collapse
Yes that would make sense, but the problem is A) How do I access that backup's .img file? B) How can I enter bootloader again? It won't let me using Power+Vol Down, no matter how long I hold it for --- unless I need to hold it longer?

You have to hold it till the buttons flash and goes black... Hold for about 2-3 more seconds and release the power button, but keep the volume down held until you get to a white hboot screen. (it'll have three skating droids)
Sent from my HTC One XL using xda premium

InflatedTitan said:
You have to hold it till the buttons flash and goes black... Hold for about 2-3 more seconds and release the power button, but keep the volume down held until you get to a white hboot screen. (it'll have three skating droids)
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok got it, did a factory reset then re-flashed CM10 boot.img...Flashed CM10 BY ITSELF this time, without doing gapps at the same time, rebooted into recovery after CM10 rolled up, then flashed gapps alone, everything is working smoothly! Now, time to restore my apps
Panicked momentarily, but now I'm back at it.
THANK YOU EVERYONE! Huge ups to all of you for helping a noob find his way

Related

[Q]rooting problem

Hello,
I have tried to root my sensation device, I used a guide to do that(forum didn't allow me to link cause I'm a new user), and everything looks fine, my phone says s-off and everything looks alright, however I tried to use titanuim backup, said it requires busybox, installed busybox, says "the su binary was not found on your phone", installed superuser, and tried to update the su binary, and it fails at "checking current install path" and I hit a wall. where have I gone wrong?
also I accidentally hit the SIM lock option on bootloader screen, I don't know what that does, so is this bad? and if so how I fix it.
If you have guessed that I'm a noob, you're right, I just got my first android phone a month ago.

come on people, give me something

reading more on the subject, i'm trying to redo installing recovery described in step 2 here as I said yes when the revolutionary utility asked me to..but the link is dead, so if anyone has another link..
also is it ok to do that? running another recovery..

dARTillery said:
reading more on the subject, i'm trying to redo installing recovery described in step 2 here as I said yes when the revolutionary utility asked me to..but the link is dead, so if anyone has another link..
also is it ok to do that? running another recovery..
Click to expand...
Click to collapse
Perform step2 and step3 in revolutionar s-off guide.

thanks for the answer.
Is that the same guide that I referred to? if so the links are dead and I can't post there yet. if not can you provide a link to the guide you mean.

dARTillery said:
thanks for the answer.
Is that the same guide that I referred to? if so the links are dead and I can't post there yet. if not can you provide a link to the guide you mean.
Click to expand...
Click to collapse
Yes that page . An older version of recovery is attched on that page. It can be downloaded here.
Now,
1. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
2. Turn off your phone FUlly and reboot into the Bootloader/HBOOT screen
3. Press Volume up to Accept when it asks" Do you want to start the update"
4. Press Power Off
5. Delete PG58IMG from your memory card
6. Reboot
Alternatively ,
If you have fastboot and adb setup on your pc then download the recovery from here.
Then flash it by the following command in fastboot
"fastboot flash recovery your-recovery-file.img"
After flashing recovery download the flashable su binary from here.
Put it the root of your sdcard.
Flash it via recovery.
Now you are root.
Note: **** If you get installation aborted while flashing su binary , do toggle signature 3 or 4 times . Then try again ****

oh thank you very much, you've been a great help, I'm now rooted, now onto trying to install a new ROM, god help me

try using the guide on the cyanogenmod website! It's the one i used and the one that seemed the most helpful

I've searched there for a while but couldn't find one, could you provide a link if its not too much trouble?

dARTillery said:
oh thank you very much, you've been a great help, I'm now rooted, now onto trying to install a new ROM, god help me
Click to expand...
Click to collapse
Great it worked. Hit some thanks button.

CWM Recovery v5.5.0.4 for A70x

EDIT FROM THE ARCHANGEL: DO NOT USE THIS RECOVERY IT WILL BRICK YOUR TAB,btw i pulled the links
CWM Recovery v5.5.0.4 for A70x
Attention!
At the moment CWM recovery is not workable! Its use can lead to non-functionality of your tablet! For details see here.
Original article is published on this site and created by ZeroNull and steaven_zw (4pda.ru).
How to:
1. Boot your device.
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on. Connect the tablet to your PC. Be sure to install the latest driver for the tablet.
3. Download the archive and extract it to any convenient location on your computer.
4. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
5. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator:
Code:
flash-cwm.bat
Recovery is installed.
Reboot again with Volume- and see whether you can still access recovery (or use the following command):
Code:
adb reboot recovery
PS: If you can not use this instruction, look here.

You're the man.
Sent from my GT-N7000 using xda app-developers app

should the boot image be patched our does that not matter

Works great thanks for your awesome work again.:good:

Quick questions for you ZeroNull:
Do we have to unlock bootloader first (I suppose we do) ?
Do we have to be rooted first (I suppose we don't) ?
If we don't have to be rooted first, can we root after just by flashing the supersu.zip by Chainfire from recovery (I would suppose we can) ?
Thanks a lot, again.
EDIT: I just checked and saw that the recovery in this package is the same size as the "rooting.img" in the generic root package from you. I suppose that means it is a temp recovery that you use to root the tab ? Which means we can gain root from recovery so flashing supersu from this recovery should work... just trying to understand what's going on, for my own knowledge
EDIT 2: I just opened the .bat file and saw there was some disabling at the end for recovery.sh
I also opened an Acer rom and saw inside the zip that there was some stuff about recovery.sh
From what I can understand, it looks like you disable something that Acer wants to do. What is it exactly ?
If I reflash an Acer stock rom from CWM recovery, will the recovery be reflashed with stock one, or does your script takes care of that ?
Again, just trying to understand.

Still looking for a stock .017 US ROM image...
Latoc said:
Quick questions for you ZeroNull:
Do we have to unlock bootloader first (I suppose we do) ?
Do we have to be rooted first (I suppose we don't) ?
If we don't have to be rooted first, can we root after just by flashing the supersu.zip by Chainfire from recovery (I would suppose we can) ?
Thanks a lot, again.
EDIT: I just checked and saw that the recovery in this package is the same size as the "rooting.img" in the generic root package from you. I suppose that means it is a temp recovery that you use to root the tab ? Which means we can gain root from recovery so flashing supersu from this recovery should work... just trying to understand what's going on, for my own knowledge
EDIT 2: I just opened the .bat file and saw there was some disabling at the end for recovery.sh
I also opened an Acer rom and saw inside the zip that there was some stuff about recovery.sh
From what I can understand, it looks like you disable something that Acer wants to do. What is it exactly ?
If I reflash an Acer stock rom from CWM recovery, will the recovery be reflashed with stock one, or does your script takes care of that ?
Again, just trying to understand.
Click to expand...
Click to collapse
Since you are apparently still running the stock .017 US ROM, could you make (and post or PM me) a backup copy that could be used to re-flash to stock?
Thanks,
I am currently flashed and running the .025_EMA_CUS1 ROM with teh new CWM recovery... all went very well!

You'll have to unlock the boot-loader to flash a recovery, but you don't need to be rooted for this to happen.You root the operating system to gain access behind the scenes....A recovery such as CWM (this) is the first step for you to flash non signed ROMs (modified) without the system denying you. Then you can flash an already rooted (or tweaked) ROM once they are available, but as of right now there aren't any.
So unlock boot-loader, flash this, then root your ROM...

bucklyv said:
Since you are apparently still running the stock .017 US ROM, could you make (and post or PM me) a backup copy that could be used to re-flash to stock?
Thanks,
I am currently flashed and running the .025_EMA_CUS1 ROM with teh new CWM recovery... all went very well!
Click to expand...
Click to collapse
Sorry, but I'm currently running this: SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip
It is a french leak, but you can get it from the rom thread so I'm not going to be able to help you much on this.
By the way, did you root before pushing this recovery or did you just unlock the bootloader ?

Itchiee said:
You'll have to unlock the boot-loader to flash a recovery, but you don't need to be rooted for this to happen.You root the operating system to gain access behind the scenes....A recovery such as CWM (this) is the first step for you to flash non signed ROMs (modified) without the system denying you. Then you can flash an already rooted (or tweaked) ROM once they are available, but as of right now there aren't any.
So unlock boot-loader, flash this, then root your ROM...
Click to expand...
Click to collapse
Ok cool.
Last question then: can I root by just flashing supersu.zip from CWM ?

Latoc said:
Ok cool.
Last question then: can I root by just flashing supersu.zip from CWM ?
Click to expand...
Click to collapse
No, you'll have to use one of the scripts in the rooting threads unless someone creates a flashable root.
The script I used automatically installed su and busy box.

Latoc said:
Sorry, but I'm currently running this: SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip
It is a french leak, but you can get it from the rom thread so I'm not going to be able to help you much on this.
By the way, did you root before pushing this recovery or did you just unlock the bootloader ?
Click to expand...
Click to collapse
Mine was both rooted and s-off... I am hoping the ROM development for the ACER takes off now that it is rooted and a recovery is working. Bought this over waiting for the Infinity to drop later this month (July)... hope it wasn't a mistake I will regret!
Thanks for the response.
Cheers!

ZeroNull said:
CWM Recovery v5.5.0.4 for A70x
Original article is published on this site and created by ZeroNull and steaven_zw (4pda.ru).
How to:
1. Boot your device.
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch on. Connect the tablet to your PC. Be sure to install the latest driver for the tablet.
3. Download the archive and extract it to any convenient location on your computer.
4. Unlock your bootloader for fastboot, follow here. Then reboot a tablet.
5. Open the directory with the unpacked archive. Execute file:
for windows with the rights of administrator:
Code:
flash-cwm.bat
Recovery is installed.
Reboot again with Volume- and see whether you can still access recovery (or use the following command):
Code:
adb reboot recovery
Click to expand...
Click to collapse
Awesome, thanks ZeroNull!
---------- Post added at 08:44 PM ---------- Previous post was at 08:20 PM ----------
I have one question, is the stock Recovery out there somewhere? I am just curious, in case I had to flash the original one back.

ZeroNull, you're the ****. Awesome work, again. Tanks!
californiarailroader said:
I have one question, is the stock Recovery out there somewhere? I am just curious, in case I had to flash the original one back.
Click to expand...
Click to collapse
You mean "stock rom", right?
If someone would make a nandroidbackup of a stock-Version, then You could recover from that Backup and would be on Stock.
You just need someone to be so kind, but i guess that ont take too long.
Gesendet von meinem A700 mit Tapatalk 2

After backup using the cwm and reboot then reboot again to recovery it will boot the original acer recovery!
Is this temporary cwm recovery?
After connecting the charger when the tablet off it will restore the original recovery

doanb555 said:
ZeroNull, you're the ****. Awesome work, again. Tanks!
You mean "stock rom", right?
If someone would make a nandroidbackup of a stock-Version, then You could recover from that Backup and would be on Stock.
You just need someone to be so kind, but i guess that ont take too long.
Gesendet von meinem A700 mit Tapatalk 2
Click to expand...
Click to collapse
You are right, my bad. It's late here, 11:37 PM, my brain is slowly fading in and out lol

moom999 said:
After backup using the cwm and reboot then reboot again to recovery it will boot the original acer recovery!
Is this temporary cwm recovery?
Click to expand...
Click to collapse
In the original of Acer firmware there is a function restore original (stock) recovery. In my instruction at one stage of the script executes the CWM recovery. This is necessary, that would disable the restoration of the original (stock) recovery. If for some reason the launch has not occurred or the user manually exited from the CWM recovery, then system restore will not be disabled. And after rebooting the system will automatically be restored to the original recovery.

When it executes
Disable script /etc/install-recovery.sh
error: device not found
error: device not found

moom999 said:
When it executes
Disable script /etc/install-recovery.sh
error: device not found
error: device not found
Click to expand...
Click to collapse
1. Do you have your device connected to your PC?
2. Have you enabled USB debugging from the settings?
3. Have you installed the Acer drivers on your computer?

TomONeill said:
1. Do you have your device connected to your PC?
2. Have you enabled USB debugging from the settings?
3. Have you installed the Acer drivers on your computer?
Click to expand...
Click to collapse
yes
yes
yes

Version bootloader
moom999 said:
yes
yes
yes
Click to expand...
Click to collapse
I think the problem in version bootloader, which is installed on your tablet.
This problem can be solved in two ways:
Option 1. Change to another the firmware version, in which works command bootloader - "fastboot boot recovery.img"
Option 2. After running the installation script CWM recovery, when comes to message:
Booting recovery.img
Click to expand...
Click to collapse
turn off the tablet. And then perform the following steps:
1. Press and hold down the 'Volume -'. Power on the tablet. After starting the CWM recovery - releasing button 'Volume -'.
2. Open the directory with the unpacked archive. Launch from this directory the Windows command prompt. And enter the following commands:
Code:
adb shell "mount -a && cd /system/etc && mv install-recovery.sh install-recovery.old"
adb reboot
Now CWM recovery will not be overwritten with the original recovery.
PS: Google Translate forever.

HTC One SV Revert to Stock Help (for update)

Hi All,
Of course the first thing I did after getting my new HTC One SV is root it and install LBE privacy protection to stop data leakage. However recently ive been getting a notification of an update to jelly bean through my phone provider (Vodafone Australia). However this will not install due to custom recovery image so the pre-install check fails. I cannot find stock recovery images anywhere and even if I did, due to presence of clockwork mod cant push images via Android SDK (skips straight past hboot to clockworkmod so isn't detected as an available device).
Can anyone help me get my phone back in a state where I can install the new update and the re-root?
Am not 100% noob, am familiar with custom roms and basics required to root and use SDK, this is my 3rd android device ive played with so hopefully this question is not tooooo SIGH.
Seems like HTC one SV is too new to have its on page in XDA support?

Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV

Not helpful
marceli-szpak said:
Try find here something or sombody who can help. http://forum.xda-developers.com/showthread.php?t=2292432
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Hi there,
Unfortunately I don't have permission to post messages in that thread, nor does it seem the appropriate place to ask my question as it is an area for resources not help.

You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV

RE HTC One SV Revert to Stock Help (for update)
marceli-szpak said:
You must have 10 posts to write in some threads. Try ask in thread root for One sv. Have you bootloader unlocked ? What is your hboot number? For now when you update to JB via OTA you can't make s-off and next you can't back to previous hboot version.
Wysłane z mojego HTC One SV
Click to expand...
Click to collapse
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000

snorglamp said:
Yes bootloader is unlocked, I have clockworkmod working, in fact I think that is the problem. If I could get back to original recovery image I think the OTA would work
HBOOT number is 1.01.000
Click to expand...
Click to collapse
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.

old.splatterhand said:
What you have to do is, download the OTA Update (will be located to sdcard/download/), copy to pc and unzip it. You will find another firmware.zip, there is the jelly bean recovery inside. Flash this JB recovery over fastboot.
Boot.img/Kernel also have to be stock and maybe bootloader also locked (for this i'm not sure), then you should be able to install JB.
But think about, if you need S-Off, cause you only get this on ICS.
Click to expand...
Click to collapse
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.

snorglamp said:
Thanks this sounds like the best advice I have had yet. MANY THANKS SIR!
However at the moment I have problems getting ADB/fastboot to recognise the phone is connected (using command line). Just says waiting for device and nothing happens. Is this because I have clockworkmod installed? I just got a new PC and installed latest ADB/SDK and latest HTC sync software so everything should be latest. I cant do much if I cant give commands unfortunately. If I solve this I will post an update.
Click to expand...
Click to collapse
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.

?????????????*

ismailnayir said:
?????????????*
Click to expand...
Click to collapse
If's there anything you don't understand, ASK!
So nobody knows, what you want, sorry.

old.splatterhand said:
Can be related to cwm! Look into my index thread, there is a link to cwm with working adb or use TWRP2.5.
Good luck.
Click to expand...
Click to collapse
Yes I thought that might be the case but was not having any luck with search results to find out what to do. Thank the internet gods for you! Going to your thread now XD!

I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!

madpausa said:
I had similar issue with an update, the reason is that the stock recovery has some commands that neither cwm nor twrp have.
Here's what I did to fix it and update succesfully:
- extracted recovery.img from the update itself
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
- after that I was able to update without problems
note that you need to flash back twrp or cwm if you want root.
Of course you need unlocked bootloader, android-sdk's platform tools and adb drivers to do this, but you should already have them if you flashed cwm
good luck!
Click to expand...
Click to collapse
DUDE! THATS TOTALLY WHAT I WANNA HEAR, however, ive been having enormous trouble getting fastbood/ADB to recognise the phone is attached, I have tried the universal clockwork mod ADB driver which didnt work, and I havent had any luck folloing the instructions on Splatterhand's other threads in getting it recognised. The command fastboot devices just leaves a flashing cursor FOREVER! Other commands leave the message "waiting for device". According to splatterhand ADB/Fastboot wont recognise the phone as attached because of clockworkmod and therefore I cant push any commands or files...how did you solve this?

OMG
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!

snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhead for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help

madpausa said:
Just a thought, if you're upgrading from ics to jb, I think you should use ics recovery (I guess you can grab it from another ruu)... anyway, glad to be of any help
Click to expand...
Click to collapse
So I took your advice and pulled a recovery image from the ICS Cricket (using the link in splatterhand's thread to stock resources) image. Downloaded the OTA and went to apply it, got past boot/recovery screen checks and all was looking good until i got to a screen with what looked to be an SD card icon and a loading bar under a larger phone icon with a green recycle type circle over it. That loading bar stopped about half way with a red triangle and exclamation mark (i.e. during the update process). Fortunately not bricked. It may be that I need the original Vodafone AU recovery image, or that there was something about the ICS OTA image that I used that made it fail. Not sure. Will try to find another stock recovery image.

Applied recovery from EU RUU stock and while that went fine and can boot into htboot no problem, when applying the OTA update it skips the fastboot and gets stuck on HTC One screen like normal loading except stuck.
I think I will try old.splatterhand's recommendation now that I am able to push things to the phone through adb/fastboot, so thanks for your commandline tip but now I must try flashing the JB recovery etc as outlined in his post.
The problem may be that the OTA is expecting a vodafone australia stock recovery as i seem to be getting different outcomes depending on which stock recovery image I apply...
I have sent Old.Splatterhand the Vodafone Australia JB OTA file for the main thread collection in case anyone wants it or the images therein, but at the moment it is of little use to me hehe.

SUCCESS! How to update to Jelly Bean from modded/rooted HTC One SV ICS
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!

Good to see you got your problem sorted out!:highfive:
And the download of OTA was succesful, thanks!:good:

snorglamp said:
Ok so I should probably post this somewhere else so old.splatterhand can just post the summary. But here is what happened and a combination of your advice helped me so super thanks to both of you (madpausa and old.splatterhand)!
So I was in a situation where having rooted my stock HTC One SV and flashed clockworkmod I couldnt apply the Jellybean update that was constantly in my notifications bar (referred to as OTA update). When I tried to reboot into recovery clockworkmod would take over instantly and I was unable to run commands from fastboot command lines.
I was however able to download the update which could be found in (internal memory) "Downloads" folder "OTA_K2_UL_JB...zip".
In order to apply the advice of madpausa I had to first revert to stock recovery image before applying the recovery image from the OTA. So I got a stock recovery image from the cricket version (see old.splatterhand's thread) and flashed that first.
- put it in the same directory as fastboot program
- attached the device with debug usb mode on on the pc (select HTC Sync) and fire up the CMD interface for command line time (cd Android)
- command 'adb reboot bootloader' which actually did boot the phone into Hboot and not clockworkmod, so that solved the ADB/fastboot issue for me
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Once I had reverted to stock recovery I was then able to apply the rest of madpausa and old.splatterhand's advice
What finally worked for me was copying that OTA JB update zip to pc my and unzipping it. Inside there was firmware.zip, which also needed to be unzipped and inside is the jelly bean version recovery.img.
- put it in the same directory as fastboot program (and remove the other recovery.img or overwrite)
- attached the device with debug usb mode on on the pc
- command 'adb reboot bootloader'
- when the device rebooted in fastboot: 'fastboot flash recovery recovery.img'
Then when I booted up my phone again it asked me if wanted to download and install the update, which I did. The phone rebooted, update applied, all good!
Hboot did not have to be re-locked, so dont go as far as locking your phone again.
Thanks to everyone's help for this one, I am now a happy use of Jellybean on my previously modded HTC One SV...now to get superuser back and stock that data leakage with LBE again!!!
Click to expand...
Click to collapse
This is the exact problem I had. I started trying to root my HTC One SV (Boost Mobile) a couple of months ago. I got past the HTC unlock bootloader, but I got confused by the rest of the rooting guide, so eventually I gave up on finishing the rooting process. Ever since then, it has said ***TAMPERED*** in hboot when I go in there. Well, just like you, I started getting the JB update notification in the OTA. I tried to install it like 15 times, but it always just rebooted into the existing image I had, which was the stock image.
So today I decided to try and finish the root and then find a JB ROM to install. old.splatterhand helped me out with getting it rooted, and it was a success. But when I asked him about JB ROMs, he said I had to have S-off. When we spoke a little more about it, he pointed me here, telling me that he helped you get the root back after you got through the OTA update.
So now, I guess I need to try and follow your instructions on getting the OTA update, and then go back to the thread where he helped you get the root back.
I'm a complete n00b to rooting android devices, but I'm pretty confident that I can do this with the proper guidance. I have rooted 2 Samsung SCH-i500s and today I finally got this HTC One SV rooted. I'm starting to see how it all works.
If you don't mind, let me know of any details of issues you faced that may not be in the guides you followed. That would be a great help.
Congrats on getting yours all done.
Thanks.
---------- Post added at 07:32 PM ---------- Previous post was at 07:15 PM ----------
snorglamp said:
'adb reboot bootloader'
THATS THE MISSING PIECE OF THE PUZZLE!!!! THAT TOTALLY WORKED AND GOT ME TO FASTBOOT ON THE PHONE!
Because the phone wasnt booting into booloader (CWM instead) I just assumed the same would happen if I used that command from adb but no, it totally worked....i wonder if the CWM universal driver i installed had anything to do with that...
anyway, CHAMPION YOU!
Good tip on extracting the recovery from the OTA itself, will do, and I will try to get a copy to Old.Splatterhand for other vodafone Australia users so they have the OTA and recovery at hand.
Will report back if I have full success to confirm your steps!
Click to expand...
Click to collapse
Do you type "adb reboot bootloader" in the command line? I wanna be clear on this before I make any moves.

Screen went blank after flashing boot.img

Meaning to install CyanogenMod I followed CyanogenMod wiki instructions (can't post link here)
Only that I have TWRP instead of CWM.
When I got to installing "CyanogenMod from recovery" I got a message saying that the pushing had failed because permissions did not allow it.
So I tried a solution they suggested for a similar message which did not work, and then I read the note at the bottom that says the kernel should be flashed via fastboot, I flashed it but now it's just blank (I guess because it has an alien kernel and the rest is the same)
I dont have a copy of my previous boot.img

Not enough information provided, please provide the following:
-Your bootloader details
-Your current TWRP version
-The exact filename of the ROM zip you flashed
-Is the phone powering on at all
Sent from my Evita

timmaaa said:
Not enough information provided, please provide the following:
-Your bootloader details HBOOT 2.15.0000 S-OFF
-Your current TWRP version 2.6.3
-The exact filename of the ROM zip you flashedcm-10.2.1-evita.zip I tried to flash it but couldnt do it on adb only flash the boot.img
-Is the phone powering on at all yes it is, it goes through the start screen and when it would show the icons it's just black with the backlight on
Sent from my Evita
Click to expand...
Click to collapse
Answers

What do you mean you couldn't do it on adb? Do what on adb? You don't use adb to flash a ROM.
Sent from my Evita

timmaaa said:
What do you mean you couldn't do it on adb? Do what on adb? You don't use adb to flash a ROM.
Sent from my Evita
Click to expand...
Click to collapse
I mean to push the rom on the root of the sdcard: look at the instructions I followed:
Place the CyanogenMod rom .zip file on the root of the SD card using adb:
Transfer your file(s): adb push YOURROMZIP.zip /sdcard/
If you boot directly to recovery and have an internal sdcard, you may need to run adb shell mount /sdcard or mount data through the recovery menu before transferring.
If you see "error: device not found" there is likely a driver issue on the PC.
If you see "error: insufficient permissions for device", try "adb kill-server" and then run "adb devices" to see if the device is attached.
On some devices, the zip file can be copied to the device using standard USB Mass Storage or MTP support. Boot the device normally and transfer the file to it.
Optional: Place any supplemental packages (e.g. Google Apps[1] or kernel) .zip file(s) on the root of the SD card.
Boot to recovery mode on the device by holding With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key..
Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a "back" button to go up one level, in which case the home button is used to confirm the selection.
Optional/Recommended: Select backup and restore to create a backup of the current installation on the device. If this option is missing, it's likely because the stock ROM has overwritten your custom recovery on boot.
Select the option to wipe data/factory reset.
Select install zip from sdcard.
Select choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.
Optional: Install any additional packages you wish using the same method.
Once the installation has finished, return back to the main menu, and select the reboot system now option. The device should now boot into CyanogenMod.
Click to expand...
Click to collapse
And the note I mentioned:
Note:
This device, if unlocked with HTC Dev Unlock, MUST have its kernel flashed via fastboot! Extract the boot.img from the rom zip and flash using fastboot flash boot boot.img
Click to expand...
Click to collapse

dvdmrn said:
I mean to push the rom on the root of the sdcard: look at the instructions I followed:
Click to expand...
Click to collapse
So you never actually flashed the ROM but you flashed the boot.img from the ROM zip anyway? No wonder it isn't working, you've flashed an incompatible boot.img onto whatever ROM you previously had installed (which is still installed by the way because flashing a boot.img does not flash a ROM).
All you needed to do was mount your sd card using TWRP (menu/mount/mount usb storage) and copy the ROM zip across, then install it. You have s-off so you don't ever need to flash the boot.img separately.
I really think you need to do some research, it seems you lack even a basic understanding of what you're doing. You don't know what a boot.img is or what it does or how or why you would need to flash it. You don't seem to know how to use your custom recovery. You don't seem to know how to install a ROM.
A lack of knowledge is almost always what leads to somebody bricking their phone, which I'm sure you don't want to happen. Do yourself a favour and spend the next couple of days reading up so you have a better understanding of modified devices. A great place to start would be my Evita FAQ thread and my How-To Guide For Beginners thread, you'll find both in my signature.
Sent from my Evita
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
dvdmrn said:
And the note I mentioned:
Click to expand...
Click to collapse
I'm not sure where you found that note but it isn't entirely correct. Only Evitas with s-on and a hboot greater than 1.09 need to flash the boot.img via fastboot.
Sent from my Evita

timmaaa said:
So you never actually flashed the ROM but you flashed the boot.img from the ROM zip anyway? No wonder it isn't working, you've flashed an incompatible boot.img onto whatever ROM you previously had installed (which is still installed by the way because flashing a boot.img does not flash a ROM).
All you needed to do was mount your sd card using TWRP (menu/mount/mount usb storage) and copy the ROM zip across, then install it. You have s-off so you don't ever need to flash the boot.img separately.
I really think you need to do some research, it seems you lack even a basic understanding of what you're doing. You don't know what a boot.img is or what it does or how or why you would need to flash it. You don't seem to know how to use your custom recovery. You don't seem to know how to install a ROM.
A lack of knowledge is almost always what leads to somebody bricking their phone, which I'm sure you don't want to happen. Do yourself a favour and spend the next couple of days reading up so you have a better understanding of modified devices. A great place to start would be my Evita FAQ thread and my How-To Guide For Beginners thread, you'll find both in my signature.
Sent from my Evita
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
I'm not sure where you found that note but it isn't entirely correct. Only Evitas with s-on and a hboot greater than 1.09 need to flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
This is where it's from
wiki cyanogenmod org / w / Install_CM_for_evita
I'm sorry for having hurried and done that but I couldn't flash the ROM and there were no more instructions, I've been reading for the last months, and even though I thought replacing the kernel could not be the best idea, it was the only idea I could get from those instructions and I thought maybe the kernel would have to be moved first for some reason. Anyway, thank you very much for your patience, I have to do it today because I have to travel and at&t limitations on the network -since it forces 4G- won't allow me to use my current carrier. I tried just moving the ROM by mounting and it worked. Thanks man

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...

Database Info

welcome