Anyone out there with the Stock ICS Nandroid backup from a Wind Mobile Amaze 4G I need your files!
Long story short I lost my Nandroid back up and now can't return to stock. Please help! Thank you in advance.
Just download an ruu or rooted ota from dev section and flash. Nandroid backups have personal information as well so I doubt anyone will offer that
Sent from my HTC_Amaze_4G using xda premium
I have tried that, it fails every time, gets to parsing PH85IMG then goes back hboot. From what I have read it seems that because the ICS update for Wind, Telus, Mobilicity, was OTA it can only be installed as an update. I can't install a previous version because I already updated to ICS while I was using stock. I have found threads of the Nandroid backups for other Canadian Carriers, just not Wind.
If I am wrong and you have any suggestions as to why the stock RUU's would fail to install please share them! I ran out of options and getting a Nandroid was the only other idea I could find that might work.
Thank you!
koroth said:
I have tried that, it fails every time, gets to parsing PH85IMG then goes back hboot. From what I have read it seems that because the ICS update for Wind, Telus, Mobilicity, was OTA it can only be installed as an update. I can't install a previous version because I already updated to ICS while I was using stock. I have found threads of the Nandroid backups for other Canadian Carriers, just not Wind.
If I am wrong and you have any suggestions as to why the stock RUU's would fail to install please share them! I ran out of options and getting a Nandroid was the only other idea I could find that might work.
Thank you!
Click to expand...
Click to collapse
Are you S-Off? Unlocked? Rooted? Or what? We need more information.
I am unlocked, rooted, s-on, using Speed ROM 6.
When trying the install I had the zip file on the SD Card renamed to PH85IMG.zip (only one .zip), with relocked bootloader. I even tried extracting the recovery.img and boot.img and flashing them first. Every time I just ended up at the HTC boot screen.
EDIT: And using 4EXT Recovery
koroth said:
I am unlocked, rooted, s-on, using Speed ROM 6.
When trying the install I had the zip file on the SD Card renamed to PH85IMG.zip (only one .zip), with relocked bootloader. I even tried extracting the recovery.img and boot.img and flashing them first. Every time I just ended up at the HTC boot screen.
Click to expand...
Click to collapse
You could try unlocking your bootloader, then extracting the OTA zip, and then grab the img files, and then flashing the boot.img, system.img, and data.img (and recovery.img if you want to restore it to as stock as possible)
You would effectively have a stock ROM.
The commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
fastboot flash recovery recovery.img
That sounded very straight forward before I got the OTA update downloaded and extracted. The boot and recovery files are obvious. The data and system files not so much.
There are two files that could be the data ones, called rcdata and mdmrcdata. Then there is only directories called system, no image files. One is in the root directory and the other is in a patch directory. Can I just compress the root system directory into an image file? Will it function the same? And do you know which data file I should use?
Thanks again for your help.
Thanks for the help, finally gave up and gained S-OFF. Flashed an old hboot and ran the wind mobile ruu.exe from the wiki. Currently downloading OTA update from a stock wind mobile ROM!
Related
Before I dive into the pool, I have a couple of things I'm still not clear on. (I've Been reading for weeks).
I'm on the original-firmware. I'm unlocked, S-ON, Stock Rom, De-bloated (Titanium frozen). I have Amon Ra 3.15 installed and have made a nand backup. The backup consists of 4 image files: boot.img, cache.img data.img and system.img. I've verified it's a good backup by verifying the md5 for each image file.
So if I install a ROM that flashes a new "kernel" via a PH98IMG.ZIP file, does that mean it is flashing that ROM's boot partition?
If I later decide that I want to restore my nand backup, Am I correct in understanding that because I'm still s-on, I cannot restore the boot.img directly from Amon Ra, but rather I would need to convert it to a flash-able PH98IMG.ZIP file and flash it from fastboot? Or am I completely misunderstanding the terminology? Assuming I'n not all messed up, how would I go about converting my boot.img into a PH98IMG.ZIP file? I presume it's not simply zipping it and renaming it...
Thanks for your help.
What do I check to make a NAND backup?
Since it's related to the question above, I didn't want to clutter the forum with a new thread:
Previously a CWM user on the Incredible, there weren't a lot of options to create a backup. On AmonRa, however, there are a bunch of checkboxes -
Boot
System
Data
Cache
Recovery
sd-ext
.android-secure
.android_secure_internalsd
compress_backup
I am S-off, on latest firmware, CleanRom 4.4 Pro.
Which of these checkboxes should I be using?
Thanks,
Alan
adsbar said:
Since it's related to the question above, I didn't want to clutter the forum with a new thread:
Previously a CWM user on the Incredible, there weren't a lot of options to create a backup. On AmonRa, however, there are a bunch of checkboxes -
Boot
System
Data
Cache
Recovery
sd-ext
.android-secure
.android_secure_internalsd
compress_backup
I am S-off, on latest firmware, CleanRom 4.4 Pro.
Which of these checkboxes should I be using?
Thanks,
Alan
Click to expand...
Click to collapse
You should check all except recovery..sd-ext...and compress... This will make it easier for u
Sent from my Dinc... I mean Rezound
nukeboyt said:
I'm on the original-firmware. I'm unlocked, S-ON, Stock Rom, De-bloated (Titanium frozen). I have Amon Ra 3.15 installed and have made a nand backup. The backup consists of 4 image files: boot.img, cache.img data.img and system.img. I've verified it's a good backup by verifying the md5 for each image file.
Click to expand...
Click to collapse
You will need a PC til you gain S-Off. Copy out the boot.img and in fastboot do "fastboot flash boot boot.img" or alternatively ....
http://forum.xda-developers.com/showthread.php?t=1547496
Or you could just keep a copy of the boot.IMG for each Rom you have backups for in a folder on your sd card. Rename them so its easy for you to know which is which and before you restore just rename again to PH98IMG.ZIP and drop it on the root of your sd card. Boot to recovery to wipe and restore then to bootloader so the boot.IMG can flash. No pc needed. Hope this helps.
sent from my Clean Rezound
Also, most Roms are still set up to drop the boot.IMG on the sd card. So just use that one so there is no searching around for the file. Some new roms are coming without this because they flash with the Rom install. So in this case the dev most likely provided the boot.IMG or you may need to unzip the Rom and flash through fastboot. Make sure you read install instructions usually in post 2 or 3 of the Rom thread so you understand the procedure for the setup you have. Might be time to s-off and then you don't have to worry about any of this.
sent from my Clean Rezound
i didn't work for me....:-(
Mark-- said:
i didn't work for me....:-(
Click to expand...
Click to collapse
What didnt work?
Mark-- said:
i didn't work for me....:-(
Click to expand...
Click to collapse
Need more information... Also nandroid helper from con supposedly works well for this
Sent from my Dinc... I mean Rezound
Took the Plunge!
Thanks. It was time. I went ahead and S-OFF'd and expressed my gratitude to to the Drunken Bear.
I have HBoot 1.15, and it was a bit of a struggle but I got my bootloader unlocked, flashed TWRP, and pushed superuser.zip to the phone to get root. However, when I went to install Deck's port of CM10, it hung at the boot animation. I then tried viper ROM and that is doing the same thing. I would like to get CM10 (or some other Jellybean ROM) working on my phone, but barring that, just getting it back to stock would be an ok solution right now, as I am currently stuck with a very flashy paperweight.
I'm not 100% positive but I believe since you are unlocked on the new bootloader, your going to have to manually flash the kernel to get boot. Read this http://forum.xda-developers.com/showthread.php?t=1794867. Also check out TWRP htc dumblock feature
http://teamw.in/project/htcdumlock
Sent from my ELTE using Tapatalk 2
Are you using twrp to install the Rom? Can you tell use exactly what you are doing? I also had the 1.15 and have flashed several Rom no problem. Nothing special required.. are there any error messages?
Sent from my EVO using xda app-developers app
---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------
I do not know what all the hoopla is about about having the update no manual stuff required.. I flash Rom everyday using twrp and goo manager
Sent from my EVO using xda app-developers app
cherylbaker said:
I do not know what all the hoopla is about about having the update no manual stuff required.. I flash Rom everyday using twrp and goo manager
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
So you're saying you are able to flash ROMs with a custom kernel (CM1O, CM9 etc..) with the newest Hboot, s-on unlocked? If you are flashing ROMs with the stock kernel you won't have any issues, but it seems the op problems started after trying to flash a non stock kernel... Which leads me to believe he/she is s-on unlocked.
Sent from my ELTE using Tapatalk 2
crump84 said:
So you're saying you are able to flash ROMs with a custom kernel (CM1O, CM9 etc..) with the newest Hboot, s-on unlocked? If you are flashing ROMs with the stock kernel you won't have any issues, but it seems the op problems started after trying to flash a non stock kernel... Which leads me to believe he/she is s-on unlocked.
Click to expand...
Click to collapse
That is correct I am s-on. Used HTCDev unlock.
Are you using twrp to install the Rom? Can you tell use exactly what you are doing? I also had the 1.15 and have flashed several Rom no problem. Nothing special required.. are there any error messages?
Click to expand...
Click to collapse
I am using TWRP to flash the ROM from zip files on my SD card. No error messages are reported. First I flashed CM10, next I flashed gapps.
Also, I did try using fastboot boot boot.img using the boot.img file I extracted from the cm10.zip ROM file. Perhaps I didn't do that correctly? I first did fastboot, then flashed the ZIP file on using TWRP. Was I only supposed to do fastboot?
CSobol said:
That is correct I am s-on. Used HTCDev unlock.
I am using TWRP to flash the ROM from zip files on my SD card. No error messages are reported. First I flashed CM10, next I flashed gapps.
Also, I did try using fastboot boot boot.img using the boot.img file I extracted from the cm10.zip ROM file. Perhaps I didn't do that correctly? I first did fastboot, then flashed the ZIP file on using TWRP. Was I only supposed to do fastboot?
Click to expand...
Click to collapse
You will need to use fastboot to flash the kernel separate if going to a non stock rom/kernel and back to a stock from from for example CM9/10.
If your s-on htc dev unlock on 1.15 HBOOT NO kernels will flash through recovery when flashing a rom. It will hang for a while on the boot.img install and then complete but NOTHING kernel related is actually changed. You MUST do it through fastboot. Peeps that are s-on htc dev unlocked 1.15 hboot and dont use fastboot or the strange dumlock in twrp (i tried with no success with dumlock) are using only the original stock htc kernel.
motcher41 said:
You will need to use fastboot to flash the kernel separate if going to a non stock rom/kernel and back to a stock from from for example CM9/10.
If your s-on htc dev unlock on 1.15 HBOOT NO kernels will flash through recovery when flashing a rom. It will hang for a while on the boot.img install and then complete but NOTHING kernel related is actually changed. You MUST do it through fastboot. Peeps that are s-on htc dev unlocked 1.15 hboot and dont use fastboot or the strange dumlock in twrp (i tried with no success with dumlock) are using only the original stock htc kernel.
Click to expand...
Click to collapse
Well this isn't particularly good news, as I'm fairly certain I have already done this. Please let me know if i'm doing the process correctly:
Unlock Bootloader
Install TWRP
Extract boot.img from CM10.zip
Root Device
Flash CM10
fast boot the boot.img file that was extracted earlier
Reboot and all should be well
This is how I understand the process, but that does not appear to be working for me?
CSobol said:
Well this isn't particularly good news, as I'm fairly certain I have already done this. Please let me know if i'm doing the process correctly:
Unlock Bootloader
Install TWRP
Extract boot.img from CM10.zip
Root Device
Flash CM10
fast boot the boot.img file that was extracted earlier
Reboot and all should be well
This is how I understand the process, but that does not appear to be working for me?
Click to expand...
Click to collapse
Did you fastboot the boot.img exactly as described in this thread? I have been using this since I took the OTA http://forum.xda-developers.com/showthread.php?p=29282299#post29282299
---------- Post added at 11:51 AM ---------- Previous post was at 11:31 AM ----------
What sense setup are you running?
From new phone I would do these.
Root
htc dev unlock
install twrp
install sense rom
remove boot.img from cm10
reboot to bootloader flashing boot.img in fastboot
reboot to recovery flash cm10 in recovery
reboot and enjoy
did you wipe data and caches?
Alright... presently I have a phone with HTCDev Unlock, TWRP, and a non-functioning copy of CM10 from Deck's 08/06 build. I am going to do this process right now and tell you what happens...
1) Extract boot.img from CM10.
2) Fastboot flash boot boot.img
(Reports finished writing 'boot')
3) Reboot to bootloader
(Rebooted successfully)
4) Go to Recovery.
(TWRP has loaded successfully)
5) Flash CM10.zip and gapps.zip
6) Clear Cache and Dalvick
7) Reboot
And at the end of all that, I am still in a boot loop, however, I noticed some errors that were probably there the whole time, but that I didn't see before. Here is the output in the console during the flash process:
* Verifyign filesystems...
* Verifying partition Size...
E:Unable to stat '/sdcard2/'
Running boot script...
Finished running boot script.
E: Failed to mount /sdcard2 (no such file or directory)
-- Install /sdcard/cm10.zip
Finding update package...
Opening update package...
Installing update...
--install sdcard/gapps.zip
Finding update package...
Opening update package...
Installing update...
Google apps for android 4.1.1
Mounting system...
Copying files...
Fixing permissions...
Unmounting system...
Installation complete!
* Verifying file system...
* Verifying partition sizes...
Click to expand...
Click to collapse
And it reports success.
CSobol said:
Alright... presently I have a phone with HTCDev Unlock, TWRP, and a non-functioning copy of CM10 from Deck's 08/06 build. I am going to do this process right now and tell you what happens...
1) Extract boot.img from CM10.
2) Fastboot flash boot boot.img
(Reports finished writing 'boot')
3) Reboot to bootloader
(Rebooted successfully)
4) Go to Recovery.
(TWRP has loaded successfully)
5) Flash CM10.zip and gapps.zip
6) Clear Cache and Dalvick
7) Reboot
And at the end of all that, I am still in a boot loop, however, I noticed some errors that were probably there the whole time, but that I didn't see before. Here is the output in the console during the flash process:
And it reports success.
Click to expand...
Click to collapse
I have never seen the sdcard2 error. it doesn't appear your flashing from that but are you? Check in twrp advanced options for internal or external card being used. I personally use the internal for everything.
OP, I am having the same exact problem. I followed the same steps you did and can't seem to get it working.
I get to the CMX boot screen but after about a minute the whole screen starts blinking on and off. Do you have anything similar to that happening for you?
Auzo said:
OP, I am having the same exact problem. I followed the same steps you did and can't seem to get it working.
I get to the CMX boot screen but after about a minute the whole screen starts blinking on and off. Do you have anything similar to that happening for you?
Click to expand...
Click to collapse
U might have a bad download
S-ON Dev Unlocked 1.15 HBOOT Garbage LTE XD
edit.... so I somehow miraculously now have it working again.... installed amon-ra recovery, then unsuccessfully flashed Neo, but was able to get Ecliptic Rez to work... can't seem to delete this thread though...
Hi,
So I was running the most recent RUU re-locked, S-on.
I went through the unlock process successfully, then got TWRP on my phone (not even sure how this worked... was using the Rezound all-in-one tool, it didn't seem to work properly the first time, but was able to pull up TWRP through Recover later on) then used TWRP to flash SuperSU and was rooted. Then feeling cocky I went ahead and did a clean wipe (note: I was very dumb and never setup a Restore... I thought, oh everything is going great, I'll just flash real quick, no reason to create a backup.... lesson learned haha) and tried to flash Ecliptic Rez. The first time it didn't work... it almost instantly said it was "installed" but didn't work. I tried to Flash it again, this time it looked good, took a while to install, everything looked great. I rebooted and the EclipticRez splash screen came up.... but then it stayed up, and it's still up. I can go back to recovery/hboot/whatever.
If it matters I pretty much flashed Ecliptic with all the options as default (except I chose S-on)...
I also tried just now to flash NeoMax2.0 but this is stuck at the splash screen as well. I tried to flash this rom first by having it as PM98IMG.zip on my root, but it didn't seem to install properly (it went through an initial phase on hboot for about a minute then went back to the hboot screen. So I then flashed it using TWRP, it said it was "injected successfully" (or something like that) but then when I rebooted it went to the splash screen and is stuck there...
If it matters too, my phone is "unlocked" and "tampered" on hboot.
My questions are...
Where should I go from here?
I really don't wanna mess with S-OFF..
I'm trying to learn more about amon-ra recovery but it's gonna take a while for me to digest all that info.
Could it be a TWRP issue in some way?
Any help/ideas would be greatly appreciated, thanks!
For future reference, since you are s-on (as am I) you need to flash the kernel after the ROM.
Some ROMs you have to pull the kernel out and do it in fastboot, or some, like Ecliptic, will put a PH98IMG on your sd card and put you in hboot after the ROM flashes. Then you accept the update if it doesn't start automatically and it will flash the kernel and then you should be able to boot.
You shouldn't need to rename the ROM to PH98IMG, just select flash zip in recovery and navigate to it.
feralicious said:
For future reference, since you are s-on (as am I) you need to flash the kernel after the ROM.
Some ROMs you have to pull the kernel out and do it in fastboot, or some, like Ecliptic, will put a PH98IMG on your sd card and put you in hboot after the ROM flashes. Then you accept the update if it doesn't start automatically and it will flash the kernel and then you should be able to boot.
You shouldn't need to rename the ROM to PH98IMG, just select flash zip in recovery and navigate to it.
Click to expand...
Click to collapse
That's dead on! Thank you. That was the difference I noticed. I'm not sure why, but amon-ra after flashing EclipticRez sent me back to hboot and there I realized that I was supposed to do another step, and at that point I thought, hey this might work this time lol
Out of curiosity.... so you say some ROMs have you "pull the kernel out" - what exactly does that mean? Would I have to download (or perhaps just located the kernel in the SD card) and change that to PH98IMG and put it on SD Root so it loads that update in hboot? Thanks
Since I download everything to my pc then transfer to my phone, what I do is just look in the ROM zip file in explorer and then copy the boot.img out of it into my fastboot folder. Then I just flash it from there using:
fastboot flash boot boot.img
There's probably a way to get it out using Root Explorer or ES File Explorer, but I don't know how you would put it into a PH98IMG file on the phone.
I avoid PH98IMG files whenever possible. Those could be anything packaged up into a file named PH98IMG and I feel safer flashing something using the real name. Would hate to use the wrong PH98IMG file by accident and do something I regret later.
feralicious said:
Since I download everything to my pc then transfer to my phone, what I do is just look in the ROM zip file in explorer and then copy the boot.img out of it into my fastboot folder. Then I just flash it from there using:
fastboot flash boot boot.img
There's probably a way to get it out using Root Explorer or ES File Explorer, but I don't know how you would put it into a PH98IMG file on the phone.
I avoid PH98IMG files whenever possible. Those could be anything packaged up into a file named PH98IMG and I feel safer flashing something using the real name. Would hate to use the wrong PH98IMG file by accident and do something I regret later.
Click to expand...
Click to collapse
Ok cool, so you'd flash your ROM first using the command prompt, then after the ROM has finished installing and you're back in hboot you would then flash the boot.img (aka Kernel right?)?
Flash the ROM in recovery - on the phone, not fastboot. I just download to my pc and store everything there then copy what I need to my phone when I want. So when I flash a ROM I copy it to my sd card to use in my phone.
Then you may or may not have to flash the kernel in fastboot. Only need to use fastboot if the ROM doesn't make a PH98IMG file for you and put it on your sd card. If it does make one I believe it will put you in bootloader and ask you if you want to update and you just select yes with no need to use pc.
I am running a rooted Rez with Amon Ra Recovery which is otherwise stock ICS. I have tried three times to install the latest Global OTA. Each time the install fails after an attempt is made to install the downloaded package. The phone reboots into Amon Ra and I see the following messages.
Installing Update
Wrong Task ID 221384E: Error in /cache/fumo/OTAPkg.zip
Status 1
Installation Aborted
Anyone know what is happening? Thanks in advance for the help.
You need the stock recovery to do update....
Sent from my SCH-1605 / Galaxy Note 2 using Tapatalk v 2.4.13
more
Found out hard way: you can't just be on the last official RUU (3.14.605.12) to get the new update from Verizon.
ALSO dammit you have to have previously taken the small February update to 3.14.605.13. The update's name mentions
605.13 in its title. The problem is that you can't get that little update anymore!!!!
Those of us with only 605.12 may have to wait until the next RUU is issued. Gripes me.
You realise someone posted the full ruu zip in this thread. You don't have to get it from software update thing
Sent from my ADR6425LVW using xda app-developers app
tried that
still looks for 605.13 and craps out with an error message!
how to solve that
In February, Flyhalf205 uploaded the 605.13 OTA.zip in another thread.
The one I could not find anywhere.
You take that little one, rename it update.zip, and flash in hboot.
Do a factory reset and it'll boot up.
Then you can get the current OTA from Verizon.
13 zip is here
13 zip
http://forum.xda-developers.com/showthread.php?p=40819479
Sent from my SCH-1605 / Galaxy Note 2 using Tapatalk v 2.4.13
Here is the FIX
michaelbsheldon said:
still looks for 605.13 and craps out with an error message!
Click to expand...
Click to collapse
Download the PH98IMG.zip in the Attachment and put it on your SD Card
1. Flash the above file in Hboot and delete it after done flashing
2. Put the new update.zip on to your SD card.
3. Reboot into Bootloader and choose Recovery
4. It will flash the new update.
5. Download the new.global.firm.PH98IMG.zip from HERE ,rename it to PH98IMG.zip and flash it in Hboot to get the latest Hboot, Radio, ......
6. Done
Just to Be Sure
I managed to get the OTA getting me to 605.13. So if I want to get to 605.14, do I just get the new firmware zip file, rename it, place it onto the sd card, and install it in HBoot and I am good to go? Just checking to be sure. Thanks.
rjr1049 said:
I managed to get the OTA getting me to 605.13. So if I want to get to 605.14, do I just get the new firmware zip file, rename it, place it onto the sd card, and install it in HBoot and I am good to go? Just checking to be sure. Thanks.
Click to expand...
Click to collapse
I just tried but no go. It said there is no update script or something. Any solution?
nbhnohome said:
Download the PH98IMG.zip in the Attachment and put it on your SD Card
1. Flash the above file in Hboot and delete it after done flashing
2. Put the new update.zip on to your SD card.
3. Reboot into Bootloader and choose Recovery
4. It will flash the new update.
5. Download the new.global.firm.PH98IMG.zip from HERE ,rename it to PH98IMG.zip and flash it in Hboot to get the latest Hboot, Radio, ......
6. Done
Click to expand...
Click to collapse
Is this the same process if the device is s-on?
nissmo66 said:
Is this the same process if the device is s-on?
Click to expand...
Click to collapse
You can only use the official update with your bootloader locked and a non modified stock rom or you need to wait for a new RUU to come out.
mjones73 said:
You can only use the official update with your bootloader locked and a non modified stock rom or you need to wait for a new RUU to come out.
Click to expand...
Click to collapse
-or- s-off if s-off and on the latest ota it doesn't matter if you are locked or unlocked. You will need to flash a custom recovery and su when the ruu is done but the update will complete. You can also downgrade the bootloader (hboot) back to a modified one such as vinyl freaks if and only if s-off.
Sent from my Nexus 7 using Tapatalk HD
dottat said:
-or- s-off if s-off and on the latest ota it doesn't matter if you are locked or unlocked. You will need to flash a custom recovery and su when the ruu is done but the update will complete. You can also downgrade the bootloader (hboot) back to a modified one such as vinyl freaks if and only if s-off.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
If you're s-off, you can flash the firmware on it's own and not have to touch the recovery...
mjones73 said:
If you're s-off, you can flash the firmware on it's own and not have to touch the recovery...
Click to expand...
Click to collapse
True also.....
Sent from my Nexus 7 using Tapatalk HD
to get stock recovery open the zip take the recovery and use fastboot and flash recovery.img right guys?
dcasun said:
to get stock recovery open the zip take the recovery and use fastboot and flash recovery.img right guys?
Click to expand...
Click to collapse
yes... put the recovery.img in the same directory as your fastboot command and from a command prompt (at the same directory as your fastboot.exe) issue the command fastboot flash recovery recovery.img
dottat said:
yes... put the recovery.img in the same directory as your fastboot command and from a command prompt (at the same directory as your fastboot.exe) issue the command fastboot flash recovery recovery.img
Click to expand...
Click to collapse
place the recovery.img in platform tools
type fastboot flash recovery recovery.img
and lock the bootloader
run the update
reunlock the bootloader
flash custom recovery
and done
dottat said:
yes... put the recovery.img in the same directory as your fastboot command and from a command prompt (at the same directory as your fastboot.exe) issue the command fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I was on 605.13 stock ICS, rooted and with Amon Ra recovery. I grabbed the 605.12 recover and flashed it and relocked the boot loader. I have tried multiple times to run the OTA (both pulling from Verizon and by putting it on the SD card). It keeps failing with the same 'Wrong Task ID' error mentioned by OP. I even wiped the SD Card, did clear storage from stock recovery, a couple of factory resets to no avail.
Can someone help? Is it possible that the 605.13 OTA a month or so ago didn't install properly since I had Amon Ra. In Software it shows I am at 605.13 so I doubt that. But would you suggest running the 605.13 Update.zip manually and then try to pull the OTA?
misalies said:
I was on 605.13 stock ICS, rooted and with Amon Ra recovery. I grabbed the 605.12 recover and flashed it and relocked the boot loader. I have tried multiple times to run the OTA (both pulling from Verizon and by putting it on the SD card). It keeps failing with the same 'Wrong Task ID' error mentioned by OP. I even wiped the SD Card, did clear storage from stock recovery, a couple of factory resets to no avail.
Can someone help? Is it possible that the 605.13 OTA a month or so ago didn't install properly since I had Amon Ra. In Software it shows I am at 605.13 so I doubt that. But would you suggest running the 605.13 Update.zip manually and then try to pull the OTA?
Click to expand...
Click to collapse
You will need to relock the bootloader then run the 605.12 RUU and let that boot up and not modify anything then you will get the 605.13 update first and then the latest after that, that is how I got the update and had no problems at all.
I have no os on my phone anymore, i have no idea where to even start. Ive been searching and searching forever now.
S-On
Hboot- 2.28
No Backup and Non-Root as well
Bootloader Unlocked
Is there anything i can do? I know the Hboot 2.28 RUU hasnt came out yet that i know of and researched of as well....Thanks in advance!
Your fine, did you just wipe everything or re-did the ruu?
If your did the ruu than you need to get your recovery back in your phone
If you just wiped everything in recovery than you need to download the ROM you want to use than install the zip in recovery but don't boot into it yet. Pull the battery and boot into bootloader and go into fastboot. Than on your PC take the boot.img file out of the ROM zip you just installed and flash it over ADB.
Fastboot flash boot boot.img
If you need any more help or questions I can continue to help or others will pop in
Edit: IF your trying to get back to just stock than you need to ruu again http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
You need to have a locked bootloader when flashing the ruu,
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Than boot into bootloader and it should load it up and install it, make sure to just leave it be. The phone might turn off than back on by itself once during the installation and that's normal, it'll continue installing and it will let you know when its finished
Sent from my ADR6425LVW using xda app-developers app
Add a rom zip file to your external sd card via your computer. And install it via yiur custom recovery. If for some reason you don't have a custom recovery, use Odin to go back to stock.
sent from a small tablet aka N2
Ok ive got a ROM installed but every time i try to flash the Boot.img it says "Failed (data transfer failure)"