Back from Moto-land with Rezound. I've flashed several ROMS and one I would like to flash now says that I must firs be on the leaked 3.11.605.22 firmware.
I thought that when I flashed a rom and it rebooted into bootloader to install the PH98IMG.zip file, that it was installing the necessary firmware. I'm confused.
How do I get to the necessary Leaked firmware. I've searched and googled, but everything I find, indicates that I cannot install the leak, because I have already used the HTC unlock tool. Again, confused
I appreciate your help!
ruu isn't a Tom that loads the kernel afterwards. the leak is flashed all at once which appears to be how kernels are flashed. flashing the leak requires the lock then it flashes everything together but remember it wipes all data with exception of external sd
Followup Q1: So is it possible to get to the RUU 3.11.605.22 firmware, WITHOUT re-locking and flashing the leak? (not concerned at all about full wipe, do it with each rom)
Q2: If I do have to re-lock and then flash the leak, do I first have to return to a 100% stock state (ie, restore all the bloat-ware and such)? (if you've ever had a Bionic you know what I'm talking about)
http://forum.xda-developers.com/showthread.php?p=23700622
Sent from my ADR6425LVW using Tapatalk
nukeboyt said:
Followup Q1: So is it possible to get to the RUU 3.11.605.22 firmware, WITHOUT re-locking and flashing the leak? (not concerned at all about full wipe, do it with each rom)
Q2: If I do have to re-lock and then flash the leak, do I first have to return to a 100% stock state (ie, restore all the bloat-ware and such)? (if you've ever had a Bionic you know what I'm talking about)
Click to expand...
Click to collapse
Originally Posted by JoelZ9614 View Post
Here are the instructions...
Download...
rename the zip to PH98IMG.zip
put on your sdcard
reboot to bootloader
fastboot oem lock
reboot to bootloader again
flash.
reboot to bootloader
[if it says security warning and tampered at the top flash again..after continue to next step]
fastboot flash unlocktoken Unlock_code.bin [of course only if u have ur original Unlock_code.bin if not do the whole htc thing again]
reboot......
A little confused. Android Police says you have to be fully stock with a locked bootloader to install 605.22. According to this, I don't have to be stock, I just have to relock it, and be aware that the full RUU install with radios will wipe my entire phone except external SD? (I wouldn't ask this except that it directly contradicts the AP post.)
And do we have the ability to re-root the resulting ICS installation?
And there's no other way to apply just the radios and the pre-rooted (Non-RUU?) version?
Does the pre-rooted version also do a full wipe?
cpurick said:
A little confused. Android Police says you have to be fully stock with a locked bootloader to install 605.22. According to this, I don't have to be stock, I just have to relock it, and be aware that the full RUU install with radios will wipe my entire phone except external SD? (I wouldn't ask this except that it directly contradicts the AP post.)
And do we have the ability to re-root the resulting ICS installation?
And there's no other way to apply just the radios and the pre-rooted (Non-RUU?) version?
Does the pre-rooted version also do a full wipe?
Click to expand...
Click to collapse
So far no other way to get the new radios , sounds like the only reason the OTA leak worked was the way it was packaged. This new leak isn't packaged the same way so you would have to relock and run the RUU to get the new radios.
Personally, all I did was reflash stock recovery before hand, but I had to run it a few times to get it to work fully and at one point I just relocked with amon recovery installed and ran it and it worked just fine. It wipes recovery as part of the installation and installs the updated stock recovery.
andybones said:
Originally Posted by JoelZ9614 View Post
Here are the instructions...
Download...
rename the zip to PH98IMG.zip
put on your sdcard
reboot to bootloader
fastboot oem lock
reboot to bootloader again
flash.
reboot to bootloader
[if it says security warning and tampered at the top flash again..after continue to next step]
fastboot flash unlocktoken Unlock_code.bin [of course only if u have ur original Unlock_code.bin if not do the whole htc thing again]
reboot......
Click to expand...
Click to collapse
Sorry for the questions, but when I do all of this, will I still have the Amon Ra recovery, or does this return to the stock recovery (which I assume it does)?
When the PH file is flashed in recovery it will overwrite whatever recovery you had flashed previously and leave you with stock everything...including recovery.
Sent from my ADR6425LVW
I was able to upgrade to the new ROM and then re-unlock my phone. But when I put Amon Ra in SD folder as PH98IMG.zip and reboot to the loader, I am never prompted to install it. Furthermore, attempts to get into recovery result in a green circular icon followed by a red triangle with exclamation point.
I tried all sorts of resets and reboots. Right now I have a green recovery option, but no working recovery. The top line says "UNLOCKED".
I've tried Amon Ra 3.13 and 3.14.
Download this file.
Place it in the same folder that you setup for the HTCdev unlock.
Rename it to "recovery."
Go to the command prompt and type in this command: cd c:\nameoffolder (mine is c:\Android for example)
Boot into Hboot
Select Fastboot
Connect to PC
Then type this exactly : fastboot flash recovery recovery.img
That should get you loaded with Amon Ra.
http://forum.xda-developers.com/showthread.php?p=19205213
Installation instructions are in the OP.
What you see now when you select recovery in hboot is what is considered stock recovery
Sent from my ADR6425LVW using Tapatalk
EmerikL said:
Download this file.
Place it in the same folder that you setup for the HTCdev unlock.
Rename it to "recovery."
Go to the command prompt and type in this command: cd c:\nameoffolder (mine is c:\Android for example)
Boot into Hboot
Select Fastboot
Connect to PC
Then type this exactly : fastboot flash recovery recovery.img
That should get you loaded with Amon Ra.
Click to expand...
Click to collapse
Thank you. I had already figured it out, and this is exactly what the problem was. Last time I flashed with a PH98IMG version of recovery, but this latest version that I have is for Fastboot. Thanks!
Never thought it would be such a relief to see the "TAMPERED" warning, lol.
All is good!
ZIP to fix mainver problems
http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
Related
i was previously running Meanrom 6.4 rooted S-ON and i decided to S-OFF my phone
i have RUU my phone and unlock the bootloader through dirtyracun s-off but when i was about to run the final step which is RabiesShot.exe(to S-OFF), my laptop have barely any battery left so i decided to not do that for the time being.
after that, I am still running the RUU 2.13.651.1 - HBOOT 1.19 without Root or any mods.
I decided to flash the "PJ75IMG - Stock Kernel". i renamed it to PJ75IMG and put it on my sdcard and it did successfully flash.
the problem is that my phone wont boot past Sprint Logo(it would suddenly black screen of death).
also, since i have no way of removing the PJ75IMG on the SD card, everytime i try to access recovery, it automatically tries to flash that file then it would exit and reboot automatically.
the only way for me to skip that part is to remove the sdcard.
my TWRP is also gone so i cannot flash any roms.
i have no card reader so i cannot place any stuff on my micro sd. :crying:
i though about downgrading the kernel to the previous working version through fastboot but when i looked for the files, they say downgrading would result in a brick.
is there any way i can maybe fastboot jellybean or ics or the kernel to make my phone work again?
edit:
if i did flash the Jellybean with my current kernel, is there a way to achieve S-OFF?
i also havent found stock jellybean rom that isnt rooted
Just...
raclimja said:
i was previously running Meanrom 6.4 rooted S-ON and i decided to S-OFF my phone
i have RUU my phone and unlock the bootloader through dirtyracun s-off but when i was about to run the final step which is RabiesShot.exe(to S-OFF), my laptop have barely any battery left so i decided to not do that for the time being.
after that, I am still running the RUU 2.13.651.1 - HBOOT 1.19 without Root or any mods.
I decided to flash the "PJ75IMG - Stock Kernel". i renamed it to PJ75IMG and put it on my sdcard and it did successfully flash.
the problem is that my phone wont boot past Sprint Logo(it would suddenly black screen of death).
also, since i have no way of removing the PJ75IMG on the SD card, everytime i try to access recovery, it automatically tries to flash that file then it would exit and reboot automatically.
the only way for me to skip that part is to remove the sdcard.
my TWRP is also gone so i cannot flash any roms.
i have no card reader so i cannot place any stuff on my micro sd. :crying:
i though about downgrading the kernel to the previous working version through fastboot but when i looked for the files, they say downgrading would result in a brick.
is there any way i can maybe fastboot jellybean or ics or the kernel to make my phone work again?
edit:
if i did flash the Jellybean with my current kernel, is there a way to achieve S-OFF?
i also havent found stock jellybean rom that isnt rooted
Click to expand...
Click to collapse
If i were you, i would go back through the s-off process if you can, that will get you back to stock and s-off, then install latest twrp, and then instal OMJ's custom release of the new JB update, it will give you root and the new update, Install the radios since you are s-off and you are good to go.
You need to finish that last step to gain s-off though lol. You should have waited.
Also, im not sure if that is just the kernel, but if it is, just the kernel and nothing else. Then you should be able to do s-off fine still.
Someone correct me if im wrong, i just learned this whole s-off process today so i could do the update.
igotlostintampa said:
If i were you, i would go back through the s-off process if you can, that will get you back to stock and s-off, then install latest twrp, and then instal OMJ's custom release of the new JB update, it will give you root and the new update, Install the radios since you are s-off and you are good to go.
You need to finish that last step to gain s-off though lol. You should have waited.
Also, im not sure if that is just the kernel, but if it is, just the kernel and nothing else. Then you should be able to do s-off fine still.
Someone correct me if im wrong, i just learned this whole s-off process today so i could do the update.
Click to expand...
Click to collapse
the thing is the phone wont even boot past the HTC Logo then it would display black screen of death
edit: i found through google saying the error is rekated to the kernel version and i should downgrade first.
is there any safe/reliable method of downgrading the latest kernel from ota (i did not flash the one with the latest hboot but i am still s-on)
i tried to Fastboot RUU but i got an error saying FAILED (remote: 43 main version check fail)
Fix boot loop after jellybean firmware update via bootloader
raclimja said:
the thing is the phone wont even boot past the HTC Logo then it would display black screen of death
edit: i found through google saying the error is rekated to the kernel version and i should downgrade first.
is there any safe/reliable method of downgrading the latest kernel from ota (i did not flash the one with the latest hboot but i am still s-on)
i tried to Fastboot RUU but i got an error saying FAILED (remote: 43 main version check fail)
Click to expand...
Click to collapse
I had the same problem.
1.remove the PJ75IMG file from exrtenal sd card.
2.reboot to fastboot pres factory reset
3. immidietly press and hold volume down, this should get you to recovery.
4. wipe
5. restore a backup rom
6.reboot
It worked for me after hours of trying other methods.
I just went through a bootloop mess. What i did to get my phone back was to use fastboot and use commands (on my pc) like
fastboot flash recovery recovery.img (for TWRP)
fastboot flash boot boot.img (for Kernel)
That got my phone back up and working.
Have you tried this?
raclimja said:
the thing is the phone wont even boot past the HTC Logo then it would display black screen of death
edit: i found through google saying the error is rekated to the kernel version and i should downgrade first.
is there any safe/reliable method of downgrading the latest kernel from ota (i did not flash the one with the latest hboot but i am still s-on)
i tried to Fastboot RUU but i got an error saying FAILED (remote: 43 main version check fail)
Click to expand...
Click to collapse
ok i believe, fastboot should get you twrp. As will it get you the boot flash.
Fastboot flash zip (latest twrp)
Fastboot flash boot (ICS sense rom's boot.img extracted from zip) (this will get you the kernel)
Reboot hold vol down and power to get to bootloader
select recovery
Twrp wipe and flash ICS rom you got the boot img from. (this will take a bit because it wont install kernel, but you already have it from step 2)
you should boot into the rom. then re-do Dirty Raccoon installation, go all the way through, and you should now be s-off
re-install twrp
Flash radios in bootloader (fastboot flash zip (.zip for radios) (link one from Original android development jelly bean flashables post) (optional)
Go to twrp, factory reset, wipe cache, wipe dalvic, wipe syste.
Twrp Flash OMJ's custom JB release of this update, or stock with goodies, or jewel-swag.
Wipe cache/Dalvic
reboot.
I think this should work but i would immagine you've tried it already. Im running the new kernel and am experiencing no problems with it.
If you're s-off just use fastboot to flash a new kernel, no need to do a factory reset or anything else.
The kernel and ROM must be installed as a pair, just upgrading one isn't going to work.
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
I was on 4.0.3 and I flashed the zip through AromRa recovery.
Now, when booting up, its stuck at the 4G screen.
The update was the OTA update released to update radios to Global. THIS
It didn't gave any error at all, it said "Reboot to complete installation or update". But when I clicked the reboot option, I saw a line saying something like "Can't write....." then the screen went off and it rebooted. This line was not there, or atleast not visible before I clicked the reboot option.
I am new to rezound and android, so please let me know what I can do. I wasn't able to get a nandroid backup before doing this, had no ext. SD card.
All I did before flashing the zip was flashing the custom recovery. Nothing else. No SU or anything else.
Can I RUU 4.0.3 to fix this problem?
Yes you need to ruu to get it back. I'm assuming your s on. You need to be s off in order to flash radios by themselves.
Sent from my ADR6425LVW using xda app-developers app
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
lamborg said:
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
Click to expand...
Click to collapse
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
feralicious said:
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
Click to expand...
Click to collapse
I relocked but then tried flashing the zip twice.
Here's what comes in cmd:
sending....
OKAY
writing
<bootloader>adopting sig ....
<bootloader>checking sig
failed <remote: not allowed>
finished
After rebooting, it gets stuck on the white HTC screen.
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
mike7728 said:
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
Click to expand...
Click to collapse
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You don't flash this in fastboot since it's a zip file.
EDIT: Looks like you can flash in fastboot as mentioned in the above post. Cool, I like that. I would flash it twice as I've read several times that you need to to make sure it gets all the system files.
If htat doesn't work for whatever reason, just put it on the sd card of your phone, detach your phone from your pc and reboot. hboot should find it (it looks for the PH98IMG.zip file) and flash it. Flash it twice to be sure it gets all the system files.
When it's done and you're rebooted use a file explorer and delete the PH98IMG file so it doesn't flash again on the next reboot.
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 was trying to ruu'ing and my sd card would not mount through the android recovery. So i wiped Dev/cache, cache, and system, thinking that it would fix the problem. Now i can not get into recovery mode and factory reset doesn't work and my phone is not being recognized by my PC. Anything i press in bootloader just reboots my device back to bootloader. I also locked my bootloader with the command "fastboot eom lock" i was experimenting and now i can not unlock it it say "relocked". What do i have to do to fix this?
Slax. said:
I was trying to ruu'ing and my sd card would not mount through the android recovery. So i wiped Dev/cache, cache, and system, thinking that it would fix the problem. Now i can not get into recovery mode and factory reset doesn't work and my phone is not being recognized by my PC. Anything i press in bootloader just reboots my device back to bootloader. I also locked my bootloader with the command "fastboot eom lock" i was experimenting and now i can not unlock it it say "relocked". What do i have to do to fix this?
Click to expand...
Click to collapse
If you place a Sense ROM PH98IMG on an external microSD card, does it install? Try that.
I cant seem to find an PH98IMG that will work. At this point do i have to flash boot or install an OTA (3.14.605.12)
I can not flash anything from the recovery. I also can not find an PH98IMG that would work at this point. the only think that im able to do is to get into bootloader which is relocked and i have s-on.
Do i need to unlock my bootloader to get into recovery?
How do i reinstall the whole system file?
Slax. said:
I can not flash anything from the recovery. I also can not find an PH98IMG that would work at this point. the only think that im able to do is to get into bootloader which is relocked and i have s-on.
Do i need to unlock my bootloader to get into recovery?
How do i reinstall the whole system file?
Click to expand...
Click to collapse
What is your current firmware/radio version from the bootloader screen?
My current radio version is 2.23.10.0123r
HBOOT is 2.28.0000
OpenDSP is v14.6.0.7708.00.0507
Slax. said:
My current radio version is 2.23.10.0123r
HBOOT is 2.28.0000
OpenDSP is v14.6.0.7708.00.0507
Click to expand...
Click to collapse
You are on current OTA firmware, and you said you were S-On so you can't RUU, there isn't one available and you can't go down a version.
You need to unlock your boot loader, get a ROM zip (any stable ROM will do, but I suggest Tachyon or Infection), download TWRP/CWM/PhilZ recovery, and you will need working adb/fastboot on a Win7/XP machine (Win 8/8.1 will not work).
Extract boot.IMG from ROM and recovery.IMG (name might vary) from recovery zip and place them in the directory with fastboot. Now start phone and fastboot and boot recovery with 'fastboot boot recovery.img', now in recovery wipe/format everything except external microSD, then Install/flash ROM zip. Reboot.
If you follow these instructions it should just boot now.
If you want stock, there is a ROM zip that the complete stock image with root applied in the development forum, its a page or two back though.
Sent from my Nexus 4 using Tapatalk
What are the TWRP/CWM/PhilZ recovery for?
Custom recovery, you need one, not all three... To wipe/format partitions and install custom zips
Sent from my Nexus 4 using Tapatalk