For A701 users only running Jelly Bean Only.
Boot image used: AV051_A701_1.021.00_WW_GEN1. Should work fine on other JB builds.
New Version 3 uploaded 23/10/2012
Should fix ADB commands for /System Remount Thanks Vorbeth
2 Parts. Part 2 is full /system RW.... also know as ROOT for the A701 on JB who took the OTA
Part 1 is For people using the previous "andlommy" image flash..... For JB OTA see part 2...
Part 1
This is meant to replace your boot.img after performing the Root image flash from this thread by andlommy;
http://forum.xda-developers.com/showthread.php?t=1911437
Ok people, as some may realize, the current "root" procedure of fastbooting images doesn't allow full /system remount. This can be seen if you try to update your superuser binary. Superuser can't remount /system. Yes, you can probably delete some files via file manager, however, if you use a root app that calls for a /system remount, well, it's not going to happen. Not like it should be.
Also, the 701 doesn't have a reliable CWM, so we do things the old fashioned (and safer) way.
This method has been around in the 500 forums for some time now. Recently, I gave info to the 210 users to get the /system remount working on their tabs. I currently use the same. Why nobody tried it here, well.....
Basically it involves modifying the zimage to change security, and allow remounts. It does not involve the kernel itself, as it remains stock.
Replaces Stock A701 Boot.img
1. Allows for full /System RW
2. Increased IO over stock.
And yes, I do use the modified boot image, 2nd revision.
As always, you have to thank people who helped you in the past and present:And I owe a lot to these guys. (which is why I hit the Donate button for them)
Vorbeth
Civato
EZTerry
Skrilax_CZ
LinuxSociety
NOTE" You must have unlocked bootloader"
Also, you do this at your own risk.Most of you know this already.
Installation:
For previous somewhat Rooted JB installations.
Download the following package and unzip to your system.
FIX-JB-ROOT
1. Connect your tablet
2. USB Debugging is on
3. Open a command window where you unzipped the Fix-JB-Root
4. Type: adb reboot bootloader
after tab reboots to bootloader download, Type;
5. fastboot flash boot JB_701V3_boot.img
6. After success, reboot tablet.
7. Start Superuser and update binaries.
Part 2
AS A ROOT PROCESS. 701 only After OTA to JB.
Note that this is an alternative to the image flash method. You need only to OTA to JB, then follow the instructions.....
Needs Testing on a Stock JB 701 Make sure you've unlocked your bootloader
1. Follow the above procedures in part 1
2. After restart, with tab connected, open a CMD Window where you unzipped the package.
3. Type the following commands;
a. adb devices (and hit Enter. You should see your device listed)
b. adb remount /system (and hit Enter. You should see remount successful)
c. adb push su /system/xbin
d. adb shell chmod 6755 /system/xbin/su
e. Get Superuser and Busybox from the Playstore. Start Superuser, check for updating binaries. Install Busybox.
Hopefully this roots and grants /system RW. I don't have a stock 701JB, so would appreciate feedback if this works or not.
MD
Works perfect Thank you. Now we only nee CM10 for our 701
Thanks MD! Going to give the 4.1.1 another go this weekend, using this boot. Will let you know how it goes )
MD are you able to delete apk from "/system/vendor/app"?
IronFly said:
MD are you able to delete apk from "/system/vendor/app"?
Click to expand...
Click to collapse
Absolutely. Just moved Solitaire.apk into /Data/app
Use your root explorer and check for RW.
Remember, this just fixes a shortcoming in the original "pre-rooted image flashing" from 4.0.4 to 4.1.1 where you can't get system remounts from some root apps.
As stated near the end of the post, I haven't tried it on a "stock non-rooted" JB build.
MD
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
fishwood said:
I installed a update.zip(Acer_AV043_A701_0.006.00_WW_GEN1.zip).
then,My A701 restarted, but it's stuck at the ACER logo.
I hook up this device to the PC ,but not go to fastboot mode , "MTB drivers" is no found.
I pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Who can help me? thks.
Click to expand...
Click to collapse
fishwood said:
Hi,MD,Can you help me for the problem:
http://forum.xda-developers.com/showthread.php?t=1934569
Click to expand...
Click to collapse
I answered in your original thread.
MD
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
misteral1970 said:
Hi MD,
Slightly off-topic, but just to let you know. Tried this with the flawed 4.1.1 install we've discussed in the other thread, still no joy!! It was a long shot that I thought was worth a go anyway
Click to expand...
Click to collapse
Yeah, I meant to tell you yesterday it won't help your situation. Your issue, is you're stuck on the ICS bootloader and it won't update to the JB one. Not to mention now, you have that "Hybrid Mix". Maybe one day can come up with a solution for it. Trying to get my hands on a 701 Service Rom.
Acer won't fess up the SBK (Secure Bootloader Key), so it sort of makes NVFlash non-usable unless we have it.
The service rom uses NVFlash, which in theory will change bootloaders (it's what we used in the 500 forums).
But until then, we're sort of stuck. I still have one trick up my sleeve, but's it's a long shot, and not even sure it'll work. Might perma-brick your tab. Will look at my old files.
MD
MD got your method working thanks for sharing this MOD!
RiceDie said:
MD got your method working thanks for sharing this MOD!
Click to expand...
Click to collapse
Which method? Experimental Root? Or just the full System RW?
Also, which build Rom are you running Mate?
MD
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
bschrib said:
MD -- Any chance to get this working on the A700 with OTA 4.1.1? Your post seems very specific about being only for the A701, so I don't want to risk it.
I tried looking into the exploit involving adb restore, but it looks like the A700 must have this fixed as "ADB Restore xxx" results in being told how to use ADB commands.. (a la http://forum.xda-developers.com/showthread.php?t=1886460)
Also I looked into symlinking, like they do for the Kindle HD exploit but that only works since 4.0 let you rename tmp to tmp.bak and then do a link exploit.. :\
Also I was thinking if we could somehow maybe apply this root, if it's still applicable in 4.1?
http://sed.free.fr/root_android.html
My problem is I don't know how to get the init.rc file to read what's going on -- does anyone have a stock init.rc file and can provide the contents?
--edit--
Oh I see, this may not work for the A700 as there hasn't been a "full ROM" released, therefore we don't have the boot.img to modify? Is that correct? As I can see the kernel is actually blocking the system remount, right?
Click to expand...
Click to collapse
The root method should work the same as with ICS and JB.
Basically need an 700 ICS and JB boot.img. to do the mod. Takes about 10 minutes. Fastboot the boot image, download SU and BB. Should be good to go.
MD
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Vorbeth said:
I've posted a full A700 JellyBean ROM in the general section - http://forum.xda-developers.com/showthread.php?t=1946415
I extracted the boot.img and made the required changes but it didn't seem to work.
Either it failed to boot (tested using fastboot boot) or "adb remount" failed.
I will have another try later today once I get time on the laptop again.
Sent from my A700 using Tapatalk HD
Click to expand...
Click to collapse
Should have a modded boot image in a day or so. Seems the boot images are the same for all builds for 700 JB.
It's the weekend, so some family time is on order.
Thanks for the GB full update rom.
MD
Hi,
I was one of the first people who updated their A701 with the unrooted JB ROM which was posted on XDA forums. The update was flawless and smooth using the external SD card and normal recovery method. Last night I tried to unlock my device and root it using step by step instructions given on OP. Device has unlocked but it is still not rooted. I checked using Root Checker app. Have I missed any steps in performing the root operation? Please help.
Additionally after doing all the steps in the OP I reinstalled the original JB update ROM using external SD card and recovery method. Bootloader is still unlocked and device is still not rooted. Device is working fine as far as I can tell.
Awaiting expert advice and help!
Best regards,
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
farazjk said:
So how can I revert back to the original locked boot image as the current boot image cannot be locked using "fastboot oem lock"?
Click to expand...
Click to collapse
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Moscow Desire said:
Did you try updating your superuser binaries after you completed? Start Superuser, select the "i" icon at the top, and tap the "update binaries" from the menu.
Did you install BusyBox?
I haven't had a lot of feedback on the JB stock alternative root.
The alternative "root" process was reported successful by one member who did 2 tabs. However, it doesn't mean it works on all it seems. The original intent, was to fix the inability to update binaries (/system remount) when using the "image flash" of the pre-rooted JB image andlommy provided us in his thread. Which it does indeed fix.
As for reinstalling the locked bootloader, there is only one way to do it. And that is, to install a full rom, not an update. The patch update probably sees the unlocked bootloader, and just ignores it. EDIT: Seems Acer hasn't released a FULL JB Rom for the 701 yet.
Or, you can fastboot install the pre-rooted JB image that andlommy posted. It's what I used after I took the OTA.
Or, you can install the German JB CWM, and use zero-nulls CWM root install Option 3 from HERE. I have it (German JB CWM) installed, but personally only use it for flashing an install, and NOT for making a recovery backup or doing wipes. So far, the Germans haven't had any issues with it. (this is probably the method I would use).
The working version of JB CWM can be found HERE
Also, you can use the Superuser CWM install from HERE
Until Acer gives us the SBK (secure bootloader key), we can't use NVFlash to flash an unlocked bootloader back unfortunately.
Understand though, the 51x and 70x are extremely temperamental. Some of us already found out the hard way a few months ago. They are not so forgiving as the 50x tabs were.
So I would be very careful about major changes.
MD
Click to expand...
Click to collapse
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
farazjk said:
Thanks MD for your informative reply. I tried to update SU binaries but there was no option to do it. superuser app only states su binaries not found. Busybox cannot start because it does not get all the required permissions.
I could flash rooted JB ROM by andlommy but that would wipe all my apps and data. As you have suggested that only full stock ROM can restore bootloader so till Acer releases this getting back to original state is not possible.
I guess if the unlocked boot image is not harmful in anyway and if any future updates pushed by Acer will still be receivable and applicable then best thing to do would be to let the device stay with unlocked boot loader.
Once again thank you for your help and support.
Best regards,
Faraz
Click to expand...
Click to collapse
The unlocked bootloader will have no effect on normal day to day operations.
I'll try and get a 700 or 701 stock user to run a couple of things to get the SU issue sorted out. Shouldn't take that long. Probably a matter of using adb to push it through.
The 700 already has a JB Full rom update package, so hopefully the 701 will get one soon as soon as somebody locates it
Think it's time to bother Acer, and see about a SBK......
MD
Related
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
microi said:
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
Click to expand...
Click to collapse
How about reverting to stock 3.0.1, then OTA updating to 3.2 and then rooting/flashing recovery and custom rom/kernel. I would think the issue is with the 3.2.1 OTA update itself.
I'm not completely sure I understand but if u can try this,
Download the universal root update zip and put it on your xoom
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Flash the universal root.zip and boot up and use a root file manager to delete those two file and clockwork should stick through a reboot
Sent from my ADR6400L using Tapatalk
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
bandit197 said:
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
Click to expand...
Click to collapse
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
okantomi said:
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
Click to expand...
Click to collapse
Cheers, I went ahead with it and it worked out no problems, unlocked, rooted and I can access recovery. Ill post the details in the guide thread to keep everything in the one place.
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Click to expand...
Click to collapse
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
microi said:
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
Click to expand...
Click to collapse
by not letting it boot I mean don't let it boot into the rom, and both of those methods u stated will work just fine to reboot
And flash it using whatever method you desire, but I forgot to mention that you may need to flash clockwork again after you boot and delete those files because the install recovery.sh obviously flashes the stock recovery and the point of my method is to keep a custom recovery on your device
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Sent from my Xoom using Tapatalk
superchilpil said:
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Click to expand...
Click to collapse
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
teameos said:
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
Click to expand...
Click to collapse
I'm getting more and more confused the more times I read this.!!
I have done the update then unlocked to find I now have the green bot!!!!!
Someone please send a simple step by step with some file links to revert back to stock 3.2!
Thanks
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
willysp said:
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
Click to expand...
Click to collapse
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
okantomi said:
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Click to expand...
Click to collapse
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
bwcorvus said:
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
willysp said:
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
ydaraishy said:
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
Click to expand...
Click to collapse
Thanks, that helps explain what they are. So, if an OTA (like 3.2 apparently) wants to patch/replace stock recovery, those are the files that do it on next boot. Would be nice if they deleted themselves when done (from a hacker's POV), but for people running stock, I guess it makes sense for the OS to check the recovery partition at each boot and overwrite it with stock recovery if needed.
willysp said:
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
okantomi said:
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
Click to expand...
Click to collapse
Sure - glad to.
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
bwcorvus said:
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Thanks for the info.
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 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?
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&A] [HowTo] Restore Stock Recovery and Install .26 OTA Manually with Unlocked Boot
Q&A for [HowTo] Restore Stock Recovery and Install .26 OTA Manually with Unlocked Bootloader
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HowTo] Restore Stock Recovery and Install .26 OTA Manually with Unlocked Bootloader. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Restore TF700 back to stock rom/recovery
eoh7678 said:
All credit goes to original posters- this information was compiled from a few different threads to make things easier.
Info came from the following threads:
http://forum.xda-developers.com/showthread.php?t=1803090
http://forum.xda-developers.com/showthread.php?t=1492887
** As always, this has risks. You could brick your device. Do this at your sole discretion. This worked just fine for me, but it might not work for everyone.
** What this does is replace TWRP with the stock recovery, enabling OTA updates to be applied again. It does NOT re-lock your bootloader. It also overwrites your /system image and build.prop with the original .22 image, which should enable the .26 update to be successful.
** This did NOT overwrite any of my settings or apps- that may not always be the case. It's best to expect that this will result in a factory reset, even though in my experience it didn't. Better to be prepared and pleasantly surprised.
** This assumes you installed TWRP or another recovery and need to revert to Stock recovery. Although I'd recommend running the full process anyway, as this ensures you have a fully stock /system partition, build.prop, etc. You can try skipping to step 10 if you're still on stock recovery.
1: Run a TWRP and/or Titanium backup, just in case. Grab everything including recovery if using TWRP.
1a: To be on the safe side, make sure you don't have any other update zips at the root of your external SD or internal storage.
2: Download the appropriate 9.4.5.22 file for your device from here:
3: Extract files from within zip
4: Extract files again from the extracted zip
5: Copy extracted "blob" file to root of folder of the removable Micro SD card or some other folder
6: Through ADB shell or Terminal Emulator, run the following: (May take from 5 to 20 minutes)
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
If copying the "blob" file to the SD card in the keyboard dock, use: dd if=/Removable/SD/blob of=/dev/block/mmcblk0p4
If copying it to the internal memory, use: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
7: Reboot only if the following is displayed (exact numbers may be different):
Code:
1068769+1 records in
1068769+1 records out
547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
Update process will automatically launch
8: Once booted up, root device by using debugfs root here
9: Do not make any other changes to build.prop or the /system directory
10: Download the appropriate dlpkgfile. The US version of the update can be downloaded here. I'll add any others as they are posted.
11: Use root explorer to copy "dlpkgfile" into /cache/ directory. Alternatively you could save the "dlpkgfile" in a microSD then open up a adb shell session.
Code:
su
cat /Removable/MicroSD/dlpkgfile > /cache/dlpkgfile
12: Create the file called "command" under /cache/recovery/ directory.
13: Write this statement in the file /cache/recovery/command
Code:
--update_package=/cache/dlpkgfile
14: Finally reboot into recovery kernel by shutting down first, then press and hold "Volume down" + "Power" once it vibrates release "Power" keep holding "Volume down" until there are some text shown on the boot logo screen. Then press "Volume up" within 5 seconds after releasing "Volume down". The update process should start... wait for it to complete. (This will take a little while, as the dalvik-cache will be rebuilt and your camera firmware will be updated. Once it completes, you should have the updated firmware installed on your tablet
15: Once the update is complete and you're at your home screen, you'll need to re-root. Just follow step 8 again.
16: Once rooted again, you can reinstall TWRP according to the original instructions, or just leave stock recovery on for now to avoid having to do this again once the next OTA comes out.
Click to expand...
Click to collapse
I am not even able to begin this procedure for the fact that i cannot find the (9.4.5.22) file at the given link. Is there another place I can download it or is there a direct link?
Shadow Assassin said:
I am not even able to begin this procedure for the fact that i cannot find the (9.4.5.22) file at the given link. Is there another place I can download it or is there a direct link?
Click to expand...
Click to collapse
Did you look at the date of this thread??? :cyclops:
It's hopelessly outdated and what's described here can''t be done anyway since you cannot downgrade from JB to ICS.
What's your situation?
What are you trying to do?
berndblb said:
Did you look at the date of this thread??? :cyclops:
It's hopelessly outdated and what's described here can''t be done anyway since you cannot downgrade from JB to ICS.
What's your situation?
What are you trying to do?
Click to expand...
Click to collapse
What im trying to do is revert my asus tf700 tablet back to stock. The stock rom i can install no problem. But i just cant get a stock recovery installed to it.
Shadow Assassin said:
What im trying to do is revert my asus tf700 tablet back to stock. The stock rom i can install no problem. But i just cant get a stock recovery installed to it.
Click to expand...
Click to collapse
What do you have installed now?
Bootloader:
Recovery:
ROM:
Shadow Assassin said:
What im trying to do is revert my asus tf700 tablet back to stock. The stock rom i can install no problem. But i just cant get a stock recovery installed to it.
Click to expand...
Click to collapse
What do you mean with 'stock recovery'? Stock normally has only a crippled 'recovery' you can only install official updates. After installing stock, you have to fastboot a working recovery (CWM or TWRP).
das chaos said:
What do you mean with 'stock recovery'? Stock normally has only a crippled 'recovery' you can only install official updates. After installing stock, you have to fastboot a working recovery (CWM or TWRP).
Click to expand...
Click to collapse
I mean the original recovery that was installed on my tablet when i got it. I need to re-install it so i can get offical OTA updates.
Shadow Assassin said:
I mean the original recovery that was installed on my tablet when i got it. I need to re-install it so i can get offical OTA updates.
Click to expand...
Click to collapse
Nobody knows, what recovery you had installed when you got your tablet. In any case stock ROM installs the factory 'recovery' which is unusable for other than factory update which never will come anymore.
Fastboot some custom recovery and you will be able to do things.
Shadow Assassin said:
I mean the original recovery that was installed on my tablet when i got it. I need to re-install it so i can get offical OTA updates.
Click to expand...
Click to collapse
You won't get any OTA updates for an unlocked tablet.
_that said:
You won't get any OTA updates for an unlocked tablet.
Click to expand...
Click to collapse
You won't get any OTA updates for for a locked tablet of that age. Guess why we are here!