Related
What do I have to do to install a custom recovery and get root?
Where do I get the ASUS specific drivers for all of normal, recovery
and boot-loader modes, for adb, fastboot and 'disk drive'?
I can use ADB and fastboot SDK utilities from the Win7 console prompt.
the appropriate dll's and exe's are in windows path.
Are there special things to do like HTC's hboot unlock procedure?
I saw an apk file on ASUS's website for unlock, how does that work?
I found 1-click root script that is supposed to install an CWM
custom recovery and get root for you. Do I need to do anything prior
to running that to unlock the boot loader, so it will accept the fastboot
commands? Besides setting usb debug and any allowing any apk?
I don't know how to interact with the ASUS boot loader for
loading updates. For HTC I only needed a specially named zip
file on the root of the ext sd card and push buttons to start
the process. Is it similar? :fingers-crossed:
Try reading this.
http://forum.xda-developers.com/showthread.php?t=1697227
All of your questions and answers have been posted a long time ago and is readily available for your reading enjoyment. At least make an attempt to research on your own. Reading is your friend....
Sent from my SGH-I777 using Tapatalk 2
OK -- RTFM *sigh*
Can I flash cwm via fastboot w/o unlocking? I just want to root
to be able to run Titanium backup and Root Explorer tools.
Stock ROM is fine, only need cwm to get root.
The device was purchased a few days ago, (waiting for it
to arrive), so its probably .29 or .30 from factory.
I discussed the issues with ASUS and they kept reading
the text of the warning message about unlocking
instead telling me how / what to do to root.
If I understood correctly, after turning off 'fast boot'
and turning on 'USB debugging', I should be able to get the
stock boot loader into fastboot USB mode following the power on
volume button presses, then use fastboot flash recovery to
store the cwm recovery.img in the recovery partition.
I'm unsure what it is that unlock boot loader apk actually does ?
With HTC it was the hboot software version that determined
if fastboot commands were accepted. Perhaps when I actually
have the device, I'll understand better.
With that done, flash the root-signed.zip from cwm to root?
Cavsoldier already advised you to do your own research. All your questions have been answered, both for your first post and your second.
I'm not entirely sure why you seem so determined to flash CWM for root. They are completely unrelated. You only flash CWM when you unlock the bootloader. You do not have to unlock your bootloader to root the device. Just use this thread.
Also not sure why you're asking Asus how to root their product. That's a big no no. Companies don't like when you root their products. Even if the CSR knows how to root the device, they're not allowed to tell you. They'll just read from a script like they did to you.
Honestly, I'm not sure why I'm bothering to answer this. All the info you could possibly need is in the thread that was linked in the second post. All of it, for every question you've asked in both of your posts in this thread. Anything root or ROM related is in that thread. It links to several rooting methods, most of which do not require CWM, let alone an unlocked bootloader. So, basically, why haven't you clicked the link in the second post? Do it.
*sigh* sorry for being dumb
Alright -- I admit I couldn't find the search forum
button on the phone interface. After I looked via a
laptop (so I had the desktop view) it was where I
thought it was.
In any case, I found the utility script debugfs-root-v1.8
which uses all adb commands so it doesn't need to be able
to run fastboot boot loader commands. It looked like the
tricky stuff was being run on the tablet via adb shell
commands and adb control commands. If I understood
it, it leaves the tablet rooted without unlocking the boot
loader. So if I can live without nandroid backups, I can just
leave the OEM stock recovery alone.
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
fuzzynco said:
*snipped*
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
Click to expand...
Click to collapse
To unroot, there's an option in superuser. Installing the new firmware will not wipe data.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Thank you.....:good:
As I have no succes in installing the OTA update for my A700, and cant get the solution offered somewhere else here to work, i have a question:
Is it possible to lock an unlocked A700 again? After which - i think - it should be able to install the OTA.
Anyone here knows if this is possible?
I was in the same situation, until I flashed an emea_cus1 version. I hope you get this answered, or someone comes up with a flashable pa_cus1 version.
Consider this a bump...
Sent from my A700 using XDA Premium HD app
Can you or anyone tell me what is the difference between emea_cus1 & pa_cus1 versions?
As above, anyone with flashable pa_cus1 version?
i heard that 'unlock' is unrecoverable. Maybe it's work if you can use Flash Tool to flash the whole system by computer.
but there'r no any resources available by now.
I had to do this myself a couple days back so I could return to stock. I made this quick link-list.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318
2. Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
3. Install Clockwork Recovery: http://forum.xda-developers.com/showthread.php?t=1791165
- I had to install this recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT LINK! It will brick you. Replace it with the one from the thread above (6.0.1.0).
4. Download the appropriate ROM for your device. You'll want the first CUS1 as it is 1.0.29: http://forum.xda-developers.com/showthread.php?t=1729692
5. Follow the directions in this link. If you can't get update.zip to run from an external SD (I couldn't) then try it from the root directory of your internal SD (I just noticed the post was updated after I messaged him). http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1812635
After you've done it all, be sure to choose "NO" when you reboot the system from CWM, otherwise CWM is still going to be there and you're probably going to be unable to get future updates.
It took me about two hours of trial and error to figure all this out, and in the end my bootloader was relocked, my root was unrooted, and I was on stock 1.0.29 and able to get OTA updates.
ExtremeRyno said:
I had to do this myself a couple days back so I could return to stock. I made this quick link-list.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318
2. Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1710755
3. Install Clockwork Recovery: http://forum.xda-developers.com/showthread.php?t=1791165
- I had to install this recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT LINK! It will brick you. Replace it with the one from the thread above (6.0.1.0).
4. Download the appropriate ROM for your device. You'll want the first CUS1 as it is 1.0.29: http://forum.xda-developers.com/showthread.php?t=1729692
5. Follow the directions in this link. If you can't get update.zip to run from an external SD (I couldn't) then try it from the root directory of your internal SD (I just noticed the post was updated after I messaged him). http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1812635
After you've done it all, be sure to choose "NO" when you reboot the system from CWM, otherwise CWM is still going to be there and you're probably going to be unable to get future updates.
It took me about two hours of trial and error to figure all this out, and in the end my bootloader was relocked, my root was unrooted, and I was on stock 1.0.29 and able to get OTA updates.
Click to expand...
Click to collapse
Thanks for your answer. Now I just am left with one question. I have image version Acer_AV043_A700_1.026.00_WW_GEN1
The CUS1 you mention can be flashed over that without a problem, after which I should be able to use the OTA from Acer?
CheopsChefren said:
Thanks for your answer. Now I just am left with one question. I have image version Acer_AV043_A700_1.026.00_WW_GEN1
The CUS1 you mention can be flashed over that without a problem, after which I should be able to use the OTA from Acer?
Click to expand...
Click to collapse
Whoops..I originally posted this on another forum where someone asked the same question. They had the US tablet. Get the appropriate file for your country/device. After you flash your country's stock, you will be able to get OTA updates. This relocks and unroots your device back like new.
ExtremeRyno said:
Whoops..I originally posted this on another forum where someone asked the same question. They had the US tablet. Get the appropriate file for your country/device. After you flash your country's stock, you will be able to get OTA updates. This relocks and unroots your device back like new.
Click to expand...
Click to collapse
i need to take my a701 back to acer so i have flashed my a701 back to ICS with Acer_AV043_A701_1.015.00_WW_GEN1 (got from somewhere in this forum i think, i forgot ... sorry). the process went without any trouble.
but my bootloader is still unlock.
when i try the fastboot oem lock .. it showed the lock lock and the door icon on the display ... choose the lock ... and the display show "Please wait.."
wait for more than half an hour .. still "Please wait" and i decided to turnoff the device.
my question is how long does it take to relock (fastboot oem lock) the bootloader? please advice. Thanks
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:
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
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.
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
I have done a quick search but with no joy so was wondering if anyone would be able to help.
A couple of weeks after installing this ROM I opened up Super SU where I was notified the Binary needed updating but when I clicked to update my phone just reset.
Every time I've tried since has been an 'update failed'.
I'm not sure if it's related but a couple of apps which require root have been playing up since. One even saying my phone isn't possibly rooted, AdAway I think it was.
Can I just try reinstalling Super SU or is it not as simple as that?
Any help would be gratefully appreciated!
Sent from my HTC One S using Tapatalk 2
I had the same issue.
Go here: http://forum.xda-developers.com/showthread.php?t=1903752
Download the attached file, and copy it to your sdcard. Then follow these steps:
1. Relock the bootloader,
2. Flash the stock recovery
3. Unlock bootloader again, and reflash your recovery (I use TWRP)
4, Immediately (without booting into the ROM, just restart right back into the bootloader), flash that zip file from the recovery
5. Fix the permissions (within TWRP it should be listed in "Advance" I think, not sure on others.)
I fail to see the reason for the first 3 steps....
Goatshocker said:
I fail to see the reason for the first 3 steps....
Click to expand...
Click to collapse
I don't either. But I'm just listing the steps that worked for me mate. I tried installing it without the first three steps. It didn't work. Hence this.
firefiber said:
I don't either. But I'm just listing the steps that worked for me mate. I tried installing it without the first three steps. It didn't work. Hence this.
Click to expand...
Click to collapse
I've just tried it without the first three steps and it hasn't worked for me either
I'm a bit unsure how to do the first 3 steps. I've noticed Hasoons All in One One S kit has a 'Relock Bootloader' and 'Unlock Bootloader' option so I'm assuming I can use them but I am unsure of where to get the Stock Recovery from.
Any help with providing a link to it would be gratefully received?
Dunno if you're running the One S S3 or S4. I've got the S3, so assuming you have the S3, this is the stock recovery for that: http://forum.xda-developers.com/showpost.php?p=28087059&postcount=18.
1. Get to your bootloader. Then into fastboot.
2. fastboot oem lock (in cmd). It'll restart, get back into the bootloader.
3. fastboot flash recovery recovery_signed.img (in cmd) (assuming your recovery is in your platform-tools folder).
4. Restart the phone into bootloader, then fastboot.
5. fastboot flash unlocktoken Unlock_code.bin
IMO, that's a lot simpler than using that all-in-one thingy. It confuses me.
Just reflash the rom and then right after flash the zip that firefiber linked too.
Darknites said:
Just reflash the rom and then right after flash the zip that firefiber linked too.
Click to expand...
Click to collapse
I am tempted to try this but don't want to lose all my data and have to re-install all my apps.
Steveh8204 said:
I am tempted to try this but don't want to lose all my data and have to re-install all my apps.
Click to expand...
Click to collapse
Sod it I've done it, seems like the simplest way to do it even with the app re-installs.
Thanks for everyone's advice!
Sorted now, rooted again.
Just out of interest why did it just become 'unrooted' and what's the chances of it happening again?
Sent from my HTC One S using Tapatalk 2
It happened a couple times to me for no apparent reason. So, it may happen again. Best insurance is 2 nandroids on sdcard. Just in case one is bad. Obviously not of same rom. And copy of nandroid/s and sdcard bu on pc. This practice has saved me numerous times over several years of flashing.
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.