Database Info

Untouched stock froyo 2.2 Asia OTA ROM

This is an incremental rom for ASIA HTC aria, do not install it for another models!
http://rapidshare.com/files/4381358...hTC_Asia_TW_2.37.709.4-1.35.709.3_release.zip
just updated my wife's aria to froyo. lost all the custom recovery stuff but still.
Here is the official OTA zip from the phone.
you can flash it in clockwork recovery by toggling the signature setting (you will lose clockwork though, you have been warned)
also do anyone know how to get rid of the superuser 'ninja' icon once you flashed this?
enjoy

looks like I need root permission to remove that superuser thing, should have done that before upgrading...

If this contains the new hboot, I highly recommend not flashing it.
Edit: it does - do NOT flash this if you ever want root.
Bad idea.

attn1 said:
If this contains the new hboot, I highly recommend not flashing it.
Edit: it does - do NOT flash this if you ever want root.
Bad idea.
Click to expand...
Click to collapse
thanks for the heads-up attn1, maybe we can dissect this to find a workaround

attn1 said:
If this contains the new hboot, I highly recommend not flashing it.
Edit: it does - do NOT flash this if you ever want root.
Bad idea.
Click to expand...
Click to collapse
yes its un-modified from HTC. will just have to wait for a new root

one thing I dont quite get is how come this rom is so small (80MB) compare to all the other roms
Is it an incremental update or a full rom?
can anyone shed some light?

zyo said:
yes its un-modified from HTC. will just have to wait for a new root
Click to expand...
Click to collapse
Well until a new method is developed, it's beyond foolish to flash this incremental update over a rom it was never intended for.
zyo said:
one thing I dont quite get is how come this rom is so small (80MB) compare to all the other roms
Is it an incremental update or a full rom?
can anyone shed some light?
Click to expand...
Click to collapse
Yes, it's an incremental update to the Hong Kong ROM that should not be flashed over any other rom.
As OP, you can edit this thread with a warning - please. This is not a complete rom, and because it was not intended for the AT&T ROM or any other than the HK ROM, some of the patches may not be executed correctly. If you start to experience some funkiness, I can probably get your phone flashed to the Gratia leak ROM, but as of now there is no going back to stock.

attn1 said:
Well until a new method is developed, it's beyond foolish to flash this incremental update over a rom it was never intended for.
Yes, it's an incremental update to the Hong Kong ROM that should not be flashed over any other rom.
As OP, you can edit this thread with a warning - please. This is not a complete rom, and because it was not intended for the AT&T ROM or any other than the HK ROM, some of the patches may not be executed correctly. If you start to experience some funkiness, I can probably get your phone flashed to the Gratia leak ROM, but as of now there is no going back to stock.
Click to expand...
Click to collapse
Thats ok I am actually using an Asian model Aria (not ATT)
but if there is a way to get rid of that superuser icon will be nice (even if that means I have to go back to Gratia leaked first)

zyo said:
Thats ok I am actually using an Asian model Aria (not ATT)
but if there is a way to get rid of that superuser icon will be nice (even if that means I have to go back to Gratia leaked first)
Click to expand...
Click to collapse
if you have the HK phone, with a goldcard you could probably flash your original shipping RUU. It's on shipped-roms.com.
That should return the phone to stock, without superuser icons. Let me know what HBOOT you have on it at that point. In any event, after that you should be able to flash the ota again after that, going to a stock 2.2 HK setup. You won't have root, and you won't be able to do custom recovery.
Please let me know if you can downgrade that phone with the this RUU and a goldcard. You will need root access, so if SU does not work anymore, then you will need to use Visionary for temp root.
RUU: http://tinyurl.com/2g8fvs3
VISIONARY: http://www.mediafire.com/?xhwc5m7f273l7b2
Goldcard procedure below:
(procedure from BLAyo)
BlaY0 said:
Here are few easy steps on how to make Goldcard without taking it out of your phone but you have to be root (VISIONary temproot is fine).
You will be doing this from command prompt:
Code:
adb shell
su
First you need to find out sdcard's CID:
Code:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
...copy it into text box on http://hexrev.soaa.me/. Now go to http://psas.revskills.de/?q=goldcard and put in the reversed CID you have got on previous web page. Push goldcard.img to your phone via 2nd command prompt:
Code:
adb push goldcard.img /data/local/
...unmount sdcard via Settings, go back to 1st command prompt and make a backup then make goldcard:
Code:
dd if=/dev/block/mmcblk0 count=1 of=/data/local/sdcard_backup.img
cat /data/local/goldcard.img > /dev/block/mmcblk0
sync
exit
You may also pull that backup to your PC:
Code:
adb pull /data/local/sdcard_backup.img .
Click to expand...
Click to collapse

I think temproot alone is enough to remove that superuser icon? Just need the permission to remove that apk

zyo said:
I think temproot alone is enough to remove that superuser icon? Just need the permission to remove that apk
Click to expand...
Click to collapse
Yes, that should work. The long way may provide you with a full downgrade/root path.

someone in the forum I visit reported that he used Visionary to gain temp root, then downgraded the phone (by modifying misc partition, I guess) and installed 2.1 RUU. But HBOOT didn't be downgraded. Its version is still 1.0, can't be rooted.

attn1 said:
Yes, that should work. The long way may provide you with a full downgrade/root path.
Click to expand...
Click to collapse
hmm that visionary + you gave me didnt work
It went black screen and after 2mins force close

and before you ask yes usb debugging has been turned on,
I have tried in terminal with su, got permission denied

ok did manage to pass that black screen but terminal still shows permission denied and I didnt see that allow permission popup
help anyone?

zyo said:
ok did manage to pass that black screen but terminal still shows permission denied and I didnt see that allow permission popup
help anyone?
Click to expand...
Click to collapse
you have to be rooted to have su and the popup working... And I'm pretty sure you just de-rooted the phone, and installed an hboot that no one knows how to root yet.
Hopefully no one else does the same.

I used visionary which is suppose to grant me temporary su. check previous post please

attn1 said:
if you have the HK phone, with a goldcard you could probably flash your original shipping RUU. It's on shipped-roms.com.
That should return the phone to stock, without superuser icons. Let me know what HBOOT you have on it at that point. In any event, after that you should be able to flash the ota again after that, going to a stock 2.2 HK setup. You won't have root, and you won't be able to do custom recovery.
Please let me know if you can downgrade that phone with the this RUU and a goldcard. You will need root access, so if SU does not work anymore, then you will need to use Visionary for temp root.
RUU: http://tinyurl.com/2g8fvs3
VISIONARY: http://www.mediafire.com/?xhwc5m7f273l7b2
Goldcard procedure below:
(procedure from BLAyo)
Click to expand...
Click to collapse
Just a quick note here I manage to make a goldcard and flashed a hk 2.2 froyo rom onto it. you DO NOT need any root to make a gold card only adb

zyo said:
Just a quick note here I manage to make a goldcard and flashed a hk 2.2 froyo rom onto it. you DO NOT need any root to make a gold card only adb
Click to expand...
Click to collapse
How is it? Fast? Stable? Laggy like the Gratia ROM?

[GUIDE] [UPD][12.dec.12] [TOOLS available] How to Unlock/Root your padfone 2 A68

Hello folks,
just wanted to share with you the subject. I'm not a developer, so I cannot go too deeply in the procedure below. what I can ensure is that is working on my personal device, Padfone 2 model A68, bought in Italy with stock firmware IMM76I.WWE_9.8.8.55-0.
DISCLAIMER
should you decide to go for it, remember, I'm just a simple user willing to share a procedure that worked for him, I'm not a smartphone OEM... Accordingly:
I'll not be held responsible if you brick, melt, destroy your device, by following the below procedure... you are the solely and ultimate responsible of your actions and your property.
if after you unlock or root your phone you need to lock it back, or put it in a Virgin "out-of-the-box" state.... cannot help. consider this procedure irreversible.
If you understand the above and concur, well, you can go for the below procedure. otherwise you're kindly requested to stop reading here and NOT continue. tks a lot.
Backgroung
the rooting method is quite straight-forward, getting a stock boot.img and manipulate its ramdisk so that the device can then boot insecure.
Credits
A HUGE thanks to Schriss for his strong support in letting me understand what I was doin on my device:good:
And also a thanks to ChainFire and his insecure adbd (here)
WHAT YOU NEED
1. a padfone 2 with more than 70% battery available, and the above firmware installed (you might wanna try also if your device has different firmware, but I cannot garantee on the results you'll get.
2. this INSECURE ICS boot.img
OR
2a this insecure JB boot.img
OR
2b. you might wanna try this TW JB boot.img from TW JB
3. a valid ADB and FASTBOOT package (lots available within XDA, or already available if you have andorid SDK installed from http://developer.android.com/sdk/index.html)
4. a valid "su" binary, again you can find it in XDA or attached to this post.
5. Valid usb drivers (see mama ASUS website)
6. the infamous "UnLock.apk" (again kindly provided by ASUS)
ONE CLICK procedure (script based) kindly provided by Padfone.cl
here
OR
STEP BY STEP PROCEDURE (MS WINDOWS OS Only)
0. place all of the files (boot.img, adb and fastboot exe's, SU binary) in one folder of your pc and open a cmd session in it.
1. install drivers at point 5 above
2. Unlock your bootloader: install the apk at point 6. above follows all the instructions to get a bootloader unlocked
3. once done the phone can be put in FASTBOOT mode (black screen with "Fastboot MODE !!!" and ASUS LOGO) , with one of the two methods below.
3a. power off device. then push and hold power on + vol up.
3b. if your device is connected to your pc, verify it is in debug mode (under setup/development) and run "adb reboot-bootloader"
4. if not already done connect the device to your pc and wait the drivers selfconfiguring
5. check if fastboot.exe see your device, type in cmd "fastboot devices", if nothing is shown means you're missing drivers, or using a bad fastboot exe.
6. check if your device boots with the insecure img at point 2. of what-you-need list. type in cmd "fastboot boot boot.img"
6a. if it reboots normally... CONGRATS your device is ok with my boot.img and you can root your phone
6b. if it goes into bootloop or bootlock or in QHUSB_DLOAD state, well sorry you cannot go ahead. just push and hold power on your device. it will reboot using its boot.img Sorry no root for you
7. if you're lucky and you get 6a response, you can now ROOT your device
7a. in cmd session type the below
adb remount (system answer "remount succeded" that's a confirmation you can act as superuser)
adb push su /system/bin/
adb shell
chmod 06755 /system/bin/su
type exit, to get off the adb shell.
7b. Collect superuser.apk at the end of this post and place it in same folders of adb.
In cmd session type
"adb push Superuser.apk /system/app
adb shell chmod 06755 /system/app/Superuser.apk"
IF YOU JUST WANT YOUR DEVICE ROOTED PROCEDURE STOPS HERE FOLLOWING IS JUST an ADDED-ON
8. OPTIONAL just in case you want to keep the insecure adbd onboard, not necessary to mantain root condition.
8a. put the device in FASTBOOT mode as above and type in cmd "fastboot flash boot boot.img", this just overwrite your stock boot.img and inoculate the insecure boot.img in your device on a stable basis.
guess it's all.
let me know if it's working for you gentlemen, and remember the disclaimer above and in general just make sure you always know what you're doin... I'll post the boot.img file shortly during today.

reserved
reserved

Hi,
Thanks for a guide, that should make it very easy for Padfone 2 users to get root
Disclaimer mentions going back to Stock and relocking - this would need a separate Guide with disclaimers because it's a little dangerous IF you have flashed anything non-stock into Boot partition and then re-locked. But if rooting was done by fastboot boot, then I believe the device could be re-locked and you would still have your root. Until you flash some Asus official Update which would overwrite /System/bin, making SU disappear.
as for points 8 and 8a, it is possible, that you don't need to permanently flash insecure boot.img. After SU has been pushed to /System/bin, you can try simply rebooting as normal and the file should remain on System partition, which is separate from boot.img. It's quite likely, that root will remain and so no flashing would be needed at all if you want to stay on Stock ROM and just need root
Root is really all about putting SU in /System/bin folder, the rest are tricks to make it happen.

schriss said:
Hi,
Thanks for a guide, that should make it very easy for Padfone 2 users to get root
Disclaimer mentions going back to Stock and relocking - this would need a separate Guide with disclaimers because it's a little dangerous IF you have flashed anything non-stock into Boot partition and then re-locked. But if rooting was done by fastboot boot, then I believe the device could be re-locked and you would still have your root. Until you flash some Asus official Update which would overwrite /System/bin, making SU disappear.
as for points 8 and 8a, it is possible, that you don't need to permanently flash insecure boot.img. After SU has been pushed to /System/bin, you can try simply rebooting as normal and the file should remain on System partition, which is separate from boot.img. It's quite likely, that root will remain and so no flashing would be needed at all if you want to stay on Stock ROM and just need root
Root is really all about putting SU in /System/bin folder, the rest are tricks to make it happen.
Click to expand...
Click to collapse
yes, I got your points I'm amending the first post. tks

Thumbs up guys. U all did it!

Padfone 2 just got epic! I have been following your thread every single day schriss and ivalex. Well done and heaps of gratitude.

After rooting,do you think its possible to flash jellybean using clockworkmod in the near future?Thanks!
Sent from my PadFone 2 using xda app-developers app

Scarletdeath said:
After rooting,do you think its possible to flash jellybean using clockworkmod in the near future?Thanks!
Sent from my PadFone 2 using xda app-developers app
Click to expand...
Click to collapse
this kind of stuff require time and testing. and as you said first we need a good CWM porting, than someone to port CM10 or a stock-modified JB when it will be available.
we'll see

Ivalex said:
this kind of stuff require time and testing. and as you said first we need a good CWM porting, than someone to port CM10 or a stock-modified JB when it will be available.
we'll see
Click to expand...
Click to collapse
I think getting CWM should be very straightfoward as soon as someone dumps Recovery partition with the commands posted earlier or in the other thread. Testing it should also be simple because it can be booted like insecure boot :victory:

A very good step for our padfone2!
4.1 is coming very soon (within Dec if Asus didn't lie on us) and unlocking at this stage may void the OTA.. (Given CWM is not avail ATM and it is uncertain how soon can the new rom.zip can be made)
even OTA can be performed, boot img is updated and need to be exploited again (with your experience I think it will be much more straight forward later on tho )
These makes me struggling whether I should unlock my padfone2 now or not..
Anyway, as said this is really a good step to our padfone2 at this stage, keep it up and I am looking forward to some point that I have no more struggle and unleash my beast at once!
Greatly appreciated! :good::good:

Hmmm I keep failing at the last step 7b. Keep getting err msg that installation failed when SuperSU tried to update the binary. On WWE stock now and have tried various SU binaries all with same results....
Any suggestions?

kahei036 said:
A very good step for our padfone2!
4.1 is coming very soon (within Dec if Asus didn't lie on us) and unlocking at this stage may void the OTA.. (Given CWM is not avail ATM and it is uncertain how soon can the new rom.zip can be made)
even OTA can be performed, boot img is updated and need to be exploited again (with your experience I think it will be much more straight forward later on tho )
These makes me struggling whether I should unlock my padfone2 now or not..
Anyway, as said this is really a good step to our padfone2 at this stage, keep it up and I am looking forward to some point that I have no more struggle and unleash my beast at once!
Greatly appreciated! :good::good:
Click to expand...
Click to collapse
I'm pretty sure that unlocked Padfone 2 can be relocked with fastboot command just like for example HTC One X. Then it would be possible to use Asus OTA updates.
But I also think Asus OTA could be flashed with CWM. Then, same insecure rooting story starts over.
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
turtle76 said:
Hmmm I keep failing at the last step 7b. Keep getting err msg that installation failed when SuperSU tried to update the binary. On WWE stock now and have tried various SU binaries all with same results....
Any suggestions?
Click to expand...
Click to collapse
So you installed SuperSU, then rebooted just to be sure and then tried updating?
Anyway, in case of such problems, I think we could push latest SuperSU.apk and other files same way as SU, we just push them to /System/app folder where all apk belong, then reboot.

schriss said:
I'm pretty sure that unlocked Padfone 2 can be relocked with fastboot command just like for example HTC One X. Then it would be possible to use Asus OTA updates.
But I also think Asus OTA could be flashed with CWM. Then, same insecure rooting story starts over.
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
So you installed SuperSU, then rebooted just to be sure and then tried updating?
Anyway, in case of such problems, I think we could push latest SuperSU.apk and other files same way as SU, we just push them to /System/app folder where all apk belong, then reboot.
Click to expand...
Click to collapse
Worked finally Thks for the advice pal

turtle76 said:
Worked finally Thks for the advice pal
Click to expand...
Click to collapse
Thanks for the advice. I'll add also push and chmod commands for supersu as add-on In case of problem as the one You had.
Inviato dal mio PadFone 2 con Tapatalk 2

Great news
The only thing I was waiting for before deciding on buying this device was to see how well its supported by this community. Thanks guys, may be finally time to let my good ol HTC HD2 rest now

Great work Padfone 2 community!
Would like to know if anyone has tried this on the IMM761.TW_9.8.8.55-0 firmware?
Did it work?

RagnarokRO said:
Great work Padfone 2 community!
Would like to know if anyone has tried this on the IMM761.TW_9.8.8.55-0 firmware?
Did it work?
Click to expand...
Click to collapse
It shld work. I was trying on tw firmware and didn't encountered issues till step 7b which was due to other issue.

getting mine friday did see on asus site there is a tool for unlock of boot loader.
Is this phone and pad any good? Can not wait for mine

I guess I am stupid because I can't get anything to work.
downloaded everything
but I can't make any commands work
I open the cmd and don't know if the " are suppose to be there or not and nothing works

Burley1 said:
I guess I am stupid because I can't get anything to work.
downloaded everything
but I can't make any commands work
I open the cmd and don't know if the " are suppose to be there or not and nothing works
Click to expand...
Click to collapse
Have you switched to the folder that contains fastboot and those stuffs in command prompt?

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.

[Q] soft bricked my HTC one mini, need help please

OK so I've been researching for days how to unlock boot loader, root and s-off my HTC one mini. I bought the phone in november so im assuming that i updated to 4.3 or it was already installed (relevant later). I htcdev unlocked my boot loader, installed twrp and made a backup, installed superuser and rooted my phone. Then I installed titanium backup pro, made a backup and uninstalled all the system apps/bloatware I didn't need. All was peachy but the apps kept reappearing which I found was down to s-on (despite what I read about htcdev unlock boot loader method making my phone s-off) . So I tried the revone method and got error 1 which apparently is down to having android 4.3 so I looked for an earlier ROM and flashed Magio r1 which worked fine but couldn't find the data/local/temp folder to install revone into. Probably could of put it somewhere else but I wasn't that confident with the s-off process. So I finally found Jmz m4 stock ROM so there was light at end of tunnel. So I read up on twrp factory reset/format data functions and saw people were using both methods. I went with the full format and factory reset afterwards. Looking back now that was pretty stupid as I have no ROM and no backups to restore to. I did manage to chmod 777 the permissions on my twrp backups and copy the to dropbox (after endless scouring of forums). I also know how to flash boot images and use the adb side load functions. So that's my story.
Problem is I can't adb push the file as it returns with error closed, I've tried the following commands:
adb device - my device is attached and side loading.
adb usb - returns error closed
adb kill-server
adb start server - server starts successfully then returns error closed.
adp push rom.zip /data/media/0 - returns error closed
And just to be sure I tried with /data/media/, same error
I've fastboot flashed the jmzM4 ROM image and kernel but no joy as I'm guessing the boot image isn't enough and you need the zip.
If anyone can help out that would be greatly appreciated.
Currently I can load into boot loader and recovery no problem, just freezes on HTC load screen in normal boot up.

STEAKTASTIC said:
OK so I've been researching for days how to unlock boot loader, root and s-off my HTC one mini. I bought the phone in november so im assuming that i updated to 4.3 or it was already installed (relevant later). I htcdev unlocked my boot loader, installed twrp and made a backup, installed superuser and rooted my phone. Then I installed titanium backup pro, made a backup and uninstalled all the system apps/bloatware I didn't need. All was peachy but the apps kept reappearing which I found was down to s-on (despite what I read about htcdev unlock boot loader method making my phone s-off) . So I tried the revone method and got error 1 which apparently is down to having android 4.3 so I looked for an earlier ROM and flashed Magio r1 which worked fine but couldn't find the data/local/temp folder to install revone into. Probably could of put it somewhere else but I wasn't that confident with the s-off process. So I finally found Jmz m4 stock ROM so there was light at end of tunnel. So I read up on twrp factory reset/format data functions and saw people were using both methods. I went with the full format and factory reset afterwards. Looking back now that was pretty stupid as I have no ROM and no backups to restore to. I did manage to chmod 777 the permissions on my twrp backups and copy the to dropbox (after endless scouring of forums). I also know how to flash boot images and use the adb side load functions. So that's my story.
Problem is I can't adb push the file as it returns with error closed, I've tried the following commands:
adb device - my device is attached and side loading.
adb usb - returns error closed
adb kill-server
adb start server - server starts successfully then returns error closed.
adp push rom.zip /data/media/0 - returns error closed
And just to be sure I tried with /data/media/, same error
I've fastboot flashed the jmzM4 ROM image and kernel but no joy as I'm guessing the boot image isn't enough and you need the zip.
If anyone can help out that would be greatly appreciated.
Currently I can load into boot loader and recovery no problem, just freezes on HTC load screen in normal boot up.
Click to expand...
Click to collapse
PM me with your gmail and we can chat on Hangouts to get you sorted - will be easier chatting real-time than posting loads of instructions etc....

If u can flash the att ruu then the problem is fixed. Just flash it throught fasbttboot.

Well hat off to nelvinchi sorted the problem out and she's working like a bewt again what a genuine legend!
*removes tongue from ar-se*

STEAKTASTIC said:
Well hat off to nelvinchi sorted the problem out and she's working like a bewt again what a genuine legend!
*removes tongue from ar-se*
Click to expand...
Click to collapse
Ive kinda had the same issue after using superwipe before insalling a new rom...now my problem is that i cant ADB PUSH (error: closed)
Can i ask how you managed to sort this? I have international version, unlocked bootloader and s-off.
Thanks

Braddison said:
Ive kinda had the same issue after using superwipe before insalling a new rom...now my problem is that i cant ADB PUSH (error: closed)
Can i ask how you managed to sort this? I have international version, unlocked bootloader and s-off.
Thanks
Click to expand...
Click to collapse
I could probably lead you through the same process but I'd advise asking nelvinchi for help as he will get it sorted promptly and correctly. If not pm me

STEAKTASTIC said:
I could probably lead you through the same process but I'd advise asking nelvinchi for help as he will get it sorted promptly and correctly. If not pm me
Click to expand...
Click to collapse
thanks for your prompt reply. yeah i will prob PM him but im going to try a few things first.cheers

Braddison said:
thanks for your prompt reply. yeah i will prob PM him but im going to try a few things first.cheers
Click to expand...
Click to collapse
Hi!
A couple of things to help you get this sorted:
You can't ADB from HBOOT/Bootloader, if you have TWRP boot to recovery then you can adb push - I'd recommend this over trying to sideload (sideload instantly flashes the zip)
You won't be able to boot if you are UNLOCKED and have S-OFF - You can either use the terminal emulator in recovery or adb shell to use revone.
adb push your rom zip and UPDATE-SuperSU-v1.86 zip to /sdcard/ if this returns an error, push to /data/local/ (you can install zip from here in recovery)
Once done, install the rom, install supersu.
Most likely revone will be missing, so do this:
adb push revone /data/local/
adb shell
cd /data/local/
chmod 755 revone
./revone -l
Reboot to recovery and wipe cache and dalvik
Reboot
REBOOT TO BOOTLOADER
Choose FASTBOOT
fastboot flash boot boot.img (boot.img extracted from the rom zip)
Reboot to recovery
Reboot system
* revone download:
download revone from http://revolutionary.io/revone
remove .bin extention
****** REMEMBER to

Thanks, i will try the instructions you've posted. i am unlocked and s-off.
Adb push worked, however Install of rom failed...as you said i will prob have to download revone and take it from there .

Braddison said:
Thanks, i will try the instructions you've posted. i am unlocked and s-off.
Adb push worked, however Install of rom failed...as you said i will prob have to download revone and take it from there .
Click to expand...
Click to collapse
What error did you get when it failed? Which rom are you flashing?

nelvinchi said:
What error did you get when it failed? Which rom are you flashing?
Click to expand...
Click to collapse
Coming from MagioR5 to his Stock sense 4.3(deox) and used SUPERWIPE hoping for a clean install.
so pushing rom via Adb worked but failed to install the rom, said it was unable to open zip file..
I then full wiped and tried pushing the rom (and supersu update zip) via ADB to /LOCAL/DATA/.....this worked and said zip flash was successful however, couldn't find the MD5...??? (weird)
The phone has now rebooted with sense 5.5 android 4.3 and all seems ok...so far!!!
rebooted to bootloader and phone still s-off and rooted...All seems fine and in working order.
slightly concerned about the md5 as i thought this should have some implications
but so far so good.
thanks to nelvinchi for his support and magio for his custom roms....cheers guys

Braddison said:
Coming from MagioR5 to his Stock sense 4.3(deox) and used SUPERWIPE hoping for a clean install.
so pushing rom via Adb worked but failed to install the rom, said it was unable to open zip file..
I then full wiped and tried pushing the rom (and supersu update zip) via ADB to /LOCAL/DATA/.....this worked and said zip flash was successful however, couldn't find the MD5...??? (weird)
The phone has now rebooted with sense 5.5 android 4.3 and all seems ok...so far!!!
rebooted to bootloader and phone still s-off and rooted...All seems fine and in working order.
slightly concerned about the md5 as i thought this should have some implications
but so far so good.
thanks to nelvinchi for his support and magio for his custom roms....cheers guys
Click to expand...
Click to collapse
Don't worry about the md5 hash fail..... If you do a manual check of md5 key for downloads, and all is ok, it's fine to ignore local fail

yep! cheers all seems fine nelvinchi...thanks again
Now to see about slimming down this rom, either rom cleaner or TB. with xposed!!
oh... i know wrong thread but anyone tried gravity box with One mini ?

Braddison said:
yep! cheers all seems fine nelvinchi...thanks again
Now to see about slimming down this rom, either rom cleaner or TB. with xposed!!
oh... i know wrong thread but anyone tried gravity box with One mini ?
Click to expand...
Click to collapse
Gravity box is not a good idea - it's for aosp roms.
Romcleaner is my De-bloatware of choice - check my post in the q&a forum....

yeah just checked out the gravity box thread ,,,ill give that a miss lol.
sure i had a reply from you on the q&a about debloating...cheers again

Hi Guys,
i have bought as second hand used an htc one mini. I live in Italy, so no Us.
The device report the following info, made by the previous owner:
TAMPERED
RELOCKED
M4_UL PVT S-OFF RL
CID-VODAP102
HBOOT-2.19.0000
RADIO 1.20.40d.00.05
It has TWRP recovery and Android 4.2.2.
I would like to restock it, deleting "tampered" and "relocked"
anybody that can help me please? thank you in advance

Hey buddy don't be a **** and post the same question in 3 different non related threads! Make your own thread instead of hijacking others. And READ what's already here in the XDA forum, it's already been discussed!
Sent from my HTC One using Xparent Green Tapatalk 2

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