Database Info

[Q][SOLVED] Upgrading from Canadian Wifi 3.0.1 to US Wifi 3.1

Hi All!
I would like to convert my completely stock non-rooted Canadian Wifi Xoom (MZ604) into a US xoom so that I can install the 3.1 software on it, as well as root, sdcard capable kernel, and CWM recovery.
Unfortunately, after reading many many of the threads here, I am totally confused as to what order to follow. Here is what I'm thinking, but please please correct me if I am wrong:
[steps removed]
Is that it? I feel like I'm missing something or that I may brick my device since it is not a US-rom that I am using as a base.
Thanks for the help!
[update 28th May]: The steps that I followed to get 3.1 with CWM & Tiamat on my Canadian Xoom are below, in post #7.

1. boot the device into fastboot and unlock it. Erase all cache and wipe the userdata.
2. Flash the complete US 3.0.1 HWI69 ROM. (yes, do this)
2.1 Root the 3.0.1 Rom
3. Install CWM recovery from http://forum.xda-developers.com/show....php?t=1074979 using the fastboot method.
4. Install the 3.1 update from http://forum.xda-developers.com/show....php?t=1074609, skipping the 3G step since I only have Wifi.
5. Install Tiamat 1.4.2 from http://forum.xda-developers.com/showthread.php?t=978013. (update to one of the newest kernels)
6. Install International Language Pack from http://forum.xda-developers.com/show....php?t=1083612 to get back all languages from 3.0.1 ROM.
Click to expand...
Click to collapse
Note the comments and you should be fine. Good luck.

jase33 said:
Note the comments and you should be fine. Good luck.
Click to expand...
Click to collapse
For your suggested step "2.1 Root the 3.0.1 Rom", would the thread at http://forum.xda-developers.com/showthread.php?t=1010568 be the suggested strategy?

that will work

So did you do all that you said ? Did it work ?
i'm about to do my candian wifi xoom !
Thanks

I was hesitant to do that since I am reading a lot of bricking stories lately, I have a canadian MZ604 stock too, will do the same if you succeed!

Alright folks, It's been a few days now since I've updated my Xoom, so here's the process that I used. Note that it is different from the steps I listed in the original post:
1. Unlock the device via fastboot. Instructions here. DO NOT RE-LOCK EVER!!
2. Flash the Official & complete US 3.0.1 HWI69 ROM. Links here. Every time I tried to download the "does not require login" version from mediafire I got a corrupted zip, so instead I downloaded from the Motorola developer site (with instructions) here.
3. Once the 3.0.1 Rom was up and running, and I had an internet connection, I got the OTA notification for the 3.1 update and installed it. It took about 10 minutes to notify me once I had connection, probably because it had to download it before notifying me. After the install and reboot process, I had a stock 3.1 install, but still didn't have sdcard access. So, I kept going.
4. Install CWM 3.0.2.8 recovery, using the fastboot method. Instructions here.
Once CWM was installed and I had the ability to backup the rom, I immediately made a backup before EACH of the following steps was performed. I know it is overkill to make that many backups, but I wanted to be sure I wasn't going to screw up my device at any given step and have to start over again.
5. Root the 3.1 rom from here. After rooting I had sdcard access within honeycomb at /sdcard/external.
6. Installed Tiamat 1.4.2 kernel. Instructions here.
7. Installed the Language Pack from here, but when I rebooted the system it went into a loop on the purple animated honeycomb logo. So, I rebooted into recovery again, and did a "wipe data / factory reset" - this allowed my machine to reboot normally, but I had to reconfigure all my settings and reinstall all my apps.
So as of right now I'm on 3.1 HMJ37, rooted, with CWM recovery, Tiamat kernel, and have international languages! It's great!!
Mike.

Thanks for the detailed info... I flashed the complete US 3.0.1 ROM on my canadian xoom and got the 3.1 OTA update as well. So now my canadian wifi xoom is on US 3.1 !
I will not root it for now since i don't really need the external SDcard for now.

When you say Flash US 3.0.1 ...do you have steps to do that? I'm just wondering how to do it...since I don't have a functional SD Card I guess its not the flash update.zip method...
Can't wait to be running the US rom and not care for motorola Canada anymore!!!

Just saw that the steps to flash the rom are on moto website! Sorry!

How to flash
I've spent hours on this and I guess I must be stupid, but I can NOT figure out how to flash a ROM! I've tried the ADB commands, I've download the ROM manager, etc, etc, etc...I cannot find any instructions on how to do this! It must be very simple because every time I look for instructions, they always just say "flash the ROM" like it's nothing. But HOW???
Very frustrating...there appears to be no single place that outlines all the steps in one place - it takes a dozen web pages to do the simplest things...
I also want to update my Canadian ROM to a US ROM. I'm unlocked, I'm running Tiamat 1.3.0 but I don't know what to do now...?
It seems as though having an external micro SD card supported is a prerequisite, but I cannot figure out how to get that to work either. The frustrating part of all this is that I do (Windows) computer support - I'm not new to technology in any way, but I have seldom been more frustrated than this trying to find one set of clear instructions...!
HELP!
Thanks.

after flashing using the instructions on post number 7 with the HRI39 bin images and fastboot my tablet doesnt boot. it just sits at the motorla logo for ages and ages and ages...
do I maybe have to wait like an hour or something?

Converted my MZ604 Singapore version to US & OTA update to 3.1
I managed to reflash International images to US and OTA update to 3.1 using a mod microUSB cable. I didn't need to root my xoom to do it rather a hardwired method.

2. Flash the Official & complete US 3.0.1 HWI69 ROM. Links here. Every time I tried to download the "does not require login" version from mediafire I got a corrupted zip, so instead I downloaded from the Motorola developer site (with instructions) here.
Click to expand...
Click to collapse
Can you please elaborate on how we do this? How do we flash a ROM? I only know how to do it in CWM Recovery, but not elsewhere.

Enhanced said:
Can you please elaborate on how we do this? How do we flash a ROM? I only know how to do it in CWM Recovery, but not elsewhere.
Click to expand...
Click to collapse
Ok, hook your xoom up to your computer and open up a command line. Then CD to your tools directory of the android sdk and input these commands.
adb reboot fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
And your good to go..... continue from the next step just be carefully to input the commands exactly, and for the love of Pete DONT UNPLUG your xoom while flashing

And do NOT relock!!
Sent from my Xoom using XDA Premium App

I will be attempting this in the next day or so but had a few newbie questions (coming over from the apple world):
1) For step two, the img files all come from HWI69.zip?
2) For step four, do I want to do it with CWM or without? Is there more risk to one vs. the other?
3) For step six, to boot into recovery mode, is the following sequence correct?
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
Thanks,
masterslacker said:
Alright folks, It's been a few days now since I've updated my Xoom, so here's the process that I used. Note that it is different from the steps I listed in the original post:
1. Unlock the device via fastboot. Instructions here. DO NOT RE-LOCK EVER!!
2. Flash the Official & complete US 3.0.1 HWI69 ROM. Links here. Every time I tried to download the "does not require login" version from mediafire I got a corrupted zip, so instead I downloaded from the Motorola developer site (with instructions) here.
3. Once the 3.0.1 Rom was up and running, and I had an internet connection, I got the OTA notification for the 3.1 update and installed it. It took about 10 minutes to notify me once I had connection, probably because it had to download it before notifying me. After the install and reboot process, I had a stock 3.1 install, but still didn't have sdcard access. So, I kept going.
4. Install CWM 3.0.2.8 recovery, using the fastboot method. Instructions here.
Once CWM was installed and I had the ability to backup the rom, I immediately made a backup before EACH of the following steps was performed. I know it is overkill to make that many backups, but I wanted to be sure I wasn't going to screw up my device at any given step and have to start over again.
5. Root the 3.1 rom from here. After rooting I had sdcard access within honeycomb at /sdcard/external.
6. Installed Tiamat 1.4.2 kernel. Instructions here.
7. Installed the Language Pack from here, but when I rebooted the system it went into a loop on the purple animated honeycomb logo. So, I rebooted into recovery again, and did a "wipe data / factory reset" - this allowed my machine to reboot normally, but I had to reconfigure all my settings and reinstall all my apps.
So as of right now I'm on 3.1 HMJ37, rooted, with CWM recovery, Tiamat kernel, and have international languages! It's great!!
Mike.
Click to expand...
Click to collapse

rezadue said:
I will be attempting this in the next day or so but had a few newbie questions (coming over from the apple world):
1) For step two, the img files all come from HWI69.zip?
2) For step four, do I want to do it with CWM or without? Is there more risk to one vs. the other?
3) For step six, to boot into recovery mode, is the following sequence correct?
Turn your XOOM off
Press Power to turn your XOOM back on
When the Motorola Dual Core boot screen appears tap Volume Down repeatedly until "Android Recovery" is displayed
Press Volume Up to enter Recovery
Thanks,
Click to expand...
Click to collapse
1) Correct - also, I know I keep saying this, but on the Moto site instructions for flashing they tell you to relock. Don't!!
2) I used the fastboot method (without). Make sure to download the img and not the zip.
3) I tend to wait on the Moto logo for about 3 secs then just press down once. Then up once you get the recovery option. Never fails.
Good luck.

Great. Thanks for the quick response. One additional question. This procedure seems a fair bit shorter in length than this one:
http://forum.xda-developers.com/showthread.php?t=1073884
Is there a reason? Is there a place where I can read some sort of a beginner's guide to rooting so I can understand the steps I am going to be following better?
Thanks again.
burden010 said:
1) Correct - also, I know I keep saying this, but on the Moto site instructions for flashing they tell you to relock. Don't!!
2) I used the fastboot method (without). Make sure to download the img and not the zip.
3) I tend to wait on the Moto logo for about 3 secs then just press down once. Then up once you get the recovery option. Never fails.
Good luck.
Click to expand...
Click to collapse

Relock
masterslacker said:
1. Unlock the device via fastboot. Instructions here. DO NOT RE-LOCK EVER!!
Click to expand...
Click to collapse
Question : why shouldn't we "RE-LOCK EVER" ?
I ask because I've relocked mine after flashing Europe stock on my US Xoom (I [stupidly] did what I saw on motorola dev instructions...).

[Q] Still no update available

I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?

chrisgeller said:
I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?
Click to expand...
Click to collapse
It's not a problem. It can take up to 2-3 months for updates to roll out completely to all regions and serial numbers.

Yeah, I dont have it either.
I do know it takes time though
which is why most of the time we force it with a ROM update

chrisgeller said:
I'm on Acer_AV043_A700_1.026.00_EMEA_GB.
Still no update available - is any one else having this problem?
Click to expand...
Click to collapse
I don't know if you did it, but you won't get the update once you unlocked the bootloader and rooted your tab.

....That wouldn't prevent the OTA from being showing as available and downloading, though. It just prevents install. That can be remedied, though...I was rooted and unlocked and just returned to stock to get the last OTA.

Returning to stock...
ExtremeRyno said:
....That wouldn't prevent the OTA from being showing as available and downloading, though. It just prevents install. That can be remedied, though...I was rooted and unlocked and just returned to stock to get the last OTA.
Click to expand...
Click to collapse
Can you please post how you returned the bootloader to stock, or "locked" ? My A700 is rooted and unlocked. I can "hide" the root with OTA Rootkeeper, but I am not sure how to return the unlocked bootloader back to stock.
Any help is much appreciated and thanks in advance!

Even though this worked for me, you should still do this at your own risk....I'm not an expert, I just got lucky.
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html & http://support.acer.com/product/default.aspx?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 (6.0.1.4) recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT (5.5.0.4) LINK! It will brick you. Replace it with the one from the first thread above ( CWM v.6.0.1.4).
4. Download the appropriate FULL ROM for your device. http://forum.xda-developers.com/showthread.php?t=1720157
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. http://forum.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.

Thanks!
ExtremeRyno said:
1. Get Android SDK & the official Acer USB Drivers http://developer.android.com/sdk/index.html & http://support.acer.com/product/default.aspx?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 (6.0.1.4) recovery.img using the BAT file from this post. IMPORTANT! DO NOT INSTALL THE recovery.img FROM THAT (5.5.0.4) LINK! It will brick you. Replace it with the one from the first thread above ( CWM v.6.0.1.4).
4. Download the appropriate FULL ROM for your device. http://forum.xda-developers.com/showthread.php?t=1720157
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. http://forum.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! I was able to get the 1.0.29 flashed back and have stock bootloader with no root. I did NOT install CWM because I am going to wait for JB before I do any root or recovery modes. I am looking to try to find the Acer ROM AV043.RV23RC03_PA_CUS1 ROM because it was what I had on the tablet and was an update over 1.0.29. If you know where I can get it, I would appreciate it. I can't find it anywhere!- Thanks again!

is there an alternate method to root this tablet?

I've searched everywhere and it seems that the only method is to root is debugsf. For some reason it doesn't work. I've ran the tool 50 times and failed with different results. I'm on stock 4.03 and I already unlocked, but i don't see how that will effect it as I've tried to root before the unlock. Why does it not work? How can I root a different way?

If you're unlocked, then you can flash a custom recovery via fastboot. Check out the all-in-one thread in the general section...

If you do not want to unlock just yet, you can downgrade using the .30 ICS update from Asus.com than you can root, use OTA rootkeeper to backup the root, and update to .18 again. There are several posts on this forum, explaining how to do exactly that in great detail.

Firebrazer said:
If you do not want to unlock just yet, you can downgrade using the .30 ICS update from Asus.com than you can root, use OTA rootkeeper to backup the root, and update to .18 again. There are several posts on this forum, explaining how to do exactly that in great detail.
Click to expand...
Click to collapse
The OP is on version 4.03 and already unlocked.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Well, guess I should have read the OP more carefully then ˆˆ

I took a look at the fast boot option and went to the thread you pointed me out to and the instructions are not clear at all. Its says that I have to put the twrp.blob in the same directory as fastboot.exe. Well where the hell is the fastboot.exe directory? I tried to update to the official jb so I use that rooting method, but noooo the stock recovery is retarded and can't find the internal sd, so I only have the option to factory reset, wipe cache or reboot. Can anyone help me? WTF am I doing wrong? I've rooted 5 android devices so far and this is the only time where it seems impossible.

Iandv said:
I took a look at the fast boot option and went to the thread you pointed me out to and the instructions are not clear at all. Its says that I have to put the twrp.blob in the same directory as fastboot.exe. Well where the hell is the fastboot.exe directory? I tried to update to the official jb so I use that rooting method, but noooo the stock recovery is retarded and can't find the internal sd, so I only have the option to factory reset, wipe cache or reboot. Can anyone help me? WTF am I doing wrong? I've rooted 5 android devices so far and this is the only time where it seems impossible.
Click to expand...
Click to collapse
Maybe I could give some insight.
Just went thru this recently.
For myself I used fastboot while connected to a Windows PC.
A PC will need to have Google SDK installed (might be best to search Google for the SDK installion procedure)
You can also get what you need in something called Platform Tools.
Fastboot from the stock recovery connects via USB to the Advanced Developer Bridge thru a command window.
Once this command window (ADB) on the PC is open boot to stock recovery on the tablet.
Select the USB option using the volume button.
The PC bridge window should show device available with the serial number of the tablet (if I remember correctly)
From the prompt you can type the appropriate command to write or flash things to the tablets system.
Hope other smarter guys chime in here because I really don't want to lead you in the wrong direction...
http://forum.xda-developers.com/showpost.php?p=30147660&postcount=1
This link is kind of intimidating, yet it may be of some use...it refers to another device.
SDK works for all Android phones and tablets tho...

Yay I finally got twrp on here and I'm about to flash clean rom. Searched the pc for fastboot.exe and there it is. I had to install twrp through fastboot and it took 3 times before I realized I needed to update my sdk tools. Tried again with profit.

Iandv said:
Yay I finally got twrp on here and I'm about to flash clean rom. Searched the pc for fastboot.exe and there it is. I had to install twrp through fastboot and it took 3 times before I realized I needed to update my sdk tools. Tried again with profit.
Click to expand...
Click to collapse
Excellent!

HTC One SV Revert to Stock Help (for update)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

5.0.1 update lost root and recovery

Just downloaded and flashed the full OTA from the Nvidia website in CWM. After it updated it asked me if I wanted to keep root (because it lost it during the update), and I said yes but after rebooting the tablet I cannot get into custom recovery or have root access (can't get it with TowelRoot on 5.0.1)
Is there any painless way that I can get the recovery and SU flashed without wiping the device?
Cheers in advance

Only way to achieve root and and recovery is go back and do the adb flash recovery n root deal.
Sent from Bad Azz VZW LG G3 Cyan Tapatalk

Yes mate. Download the cwm recovery. Also the latest SuperSU.zip from Chainfire. Reboot into boot loader. Then run from adb (whilst connected by USB and have copied the recovery.IMG into the same directory as adb/fastboot) fastboot boot recovery.img then flash the supersu.zip and reboot. You keep official recovery and get root. Worked for me. Easier and less trouble than it sounds.
Recovery here: http://forum.xda-developers.com/attachment.php?attachmentid=2921222&d=1409611452
Latest SuperSU here: http://download.chainfire.eu/644/SuperSU/BETA-SuperSU-v2.42.zip
If you want to keep custom recovery then once done the above return to bootloader and run: fastboot flash recovery recovery.img

tcardozo said:
Just downloaded and flashed the full OTA from the Nvidia website in CWM. After it updated it asked me if I wanted to keep root (because it lost it during the update), and I said yes but after rebooting the tablet I cannot get into custom recovery or have root access (can't get it with TowelRoot on 5.0.1)
Is there any painless way that I can get the recovery and SU flashed without wiping the device?
Cheers in advance
Click to expand...
Click to collapse
Guess I am having a brain fart, I can't find a flashable zip of the ota anywhere on the Nvidia site, could you please link?
***nm, found it...too much eggnog

wrich73 said:
Guess I am having a brain fart, I can't find a flashable zip of the ota anywhere on the Nvidia site, could you please link?
***nm, found it...too much eggnog
Click to expand...
Click to collapse
Could you post that link for me? I've literally spent 30 minutes trying to look for it on the NVIDIA website. I can only find their 1.2.0 and 1.2.1 versions.
(I know I can easily find a user uploaded copy here, but that's besides the point. I just need to know where to grab it on the official website for next time.)

HSuke said:
Could you post that link for me? I've literally spent 30 minutes trying to look for it on the NVIDIA website. I can only find their 1.2.0 and 1.2.1 versions.
(I know I can easily find a user uploaded copy here, but that's besides the point. I just need to know where to grab it on the official website for next time.)
Click to expand...
Click to collapse
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip
always look for the wx_na_wf
If if doesn't have that it isnt for the wifi version

http://forum.xda-developers.com/showthread.php?p=57731631
See this post from jim380 for details and required links to update to 5.01 and put root back on. Be sure to thank him!

Sick. Thanks for the link. Thanked both of you. About to flash wx_na_do (32GB LTE model) on my shield, then root it and install PhilZ.
Next we need kernels. Going to start coding.