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
Related
Hey guys.
Yesterday I ran into a problem when I tried to flash RezRom ICS v1.0 over my current ROM (DSB's Bamf Cubed 1.0.2). ROM flashed fine...but the Kernel would give me an error
"Main Version is Older!
Update Fail!
Press <POWER> to reboot"
I have learned this is an issue with the Kernel DSB made being based off of a more recent base than the one in the ICS ROMs.
It was suggested I just manipulate the mainver # in the text file with the Kernel...but I am so glad I did not. Two problems for me
1. I don't want to lose the ability to RUU (http://forum.xda-developers.com/showthread.php?t=1454255 see text in red)
2. I have not desire to edit this file from now one when I must update the kernel.
So whatoptions do I have to downgrade my kernel? Can I HBoot this RUU http://forum.xda-developers.com/showthread.php?t=1338916? and then just us the root method again? Then flash RR ICS v1.0?
Thanks in advance
I think you have to use it now. Until a new ruu comes out I don't think you'll be able to use one
sent from my newly unlocked Rezound
I need some help here also. everything I have tried to do will not work. I have tried reflashing kernels, recoveries, countless numbers of PH98IMG files. I have tried cut and pasting the text.info INTO THE PMG98IMG and nothing works. the ONLY way I can boot my phone is to flash the Clean ICS ROM, let it fail the fastboot, delete the PMG98IMG file from the SDCard and then flash the ICS Kernel from this thread http://forum.xda-developers.com/showthread.php?t=1454255 The phone will now boot up and I can get data and all but I can receive or make a phone call.. If I try to make a phone call as soon as I touch the key pad the phone locks up adn then reboots. I can do everything else including downloading apps I just can't make or receive phone calls.
HELP PLEASE
If you're having this problem reflash the kernel in fastboot. It works every time. Yes you need a PC, but it works. fastboot flash boot boot.img.
MrSmith317 said:
If you're having this problem reflash the kernel in fastboot. It works every time. Yes you need a PC, but it works. fastboot flash boot boot.img.
Click to expand...
Click to collapse
+1
and when at a computer you can edit the android-info.txt so the flashable PB98IMG.zip will work for later use to switch back and forth from ICS to GB without a comp.
MrSmith317 said:
If you're having this problem reflash the kernel in fastboot. It works every time. Yes you need a PC, but it works. fastboot flash boot boot.img.
Click to expand...
Click to collapse
I just want to make sure I understand before I do this.
So you are saying that if I save a copy of the boot.img from the ICS rom I want to flash in the folder with the fastboot.exe file.
I can boot into the bootloader first -> go to fastboot -> flash the boot image via the command above
Then boot to recovery and flash the ROM
Then...I should be good?
jbg25 said:
I just want to make sure I understand before I do this.
So you are saying that if I save a copy of the boot.img from the ICS rom I want to flash in the folder with the fastboot.exe file.
I can boot into the bootloader first -> go to fastboot -> flash the boot image via the command above
Then boot to recovery and flash the ROM
Then...I should be good?
Click to expand...
Click to collapse
Yeah. I always flash the kernel after the ROM but I think it doesn't matter. Just my way of being sure that the kernel I want is loaded. And I never get the mainver error.
Awesome...will try that now
Thanks
kernel before rom, rom then kernel, doesn't make a diff.
kernel must be flashed before rom will boot though.
For ROMs that have kernels in them, that after installing bring you to bootloader to install PB98IMG.zip, you can edit the said PB98IMG.zip in the ROM prior to installing so you can flash the kernel and not get the main ver. sig error.
it sucks, but it will be fixed come the next OTA update.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
If you want to be 100% sure not to get the mainver problem, flash kernel using ADB fastboot.
PAID!!!
Thanks again.
Only reason I flashed kernel first was because with the mainver error...fastboot was not available. every-time bootloader started up...would read the PH98IMG and error with no option but to reboot. Which would have meant I would have had to pull the sdcard and remove that file before I could flash the kernel.
This way I just boot to bootloader...flash kernel...then from bootloader boot to recovery...flash room which will go back to bootloader and fail...but this time on reboot the kernel was already there.
Guys,
I followed this guide to unlock my phone and gain superuser access step by step:
http://forum.xda-developers.com/showthread.php?t=1239821
I then installed Rom Manager, and restarted in Recovery.
I placed this zip: http://forum.xda-developers.com/showthread.php?t=1421065 onto my SD Card, and did not rename it. Once in recovery I installed that ROM. It installed with no errors however now the phone gets stuck at the htc logo screen.
Any thoughts?
What was contained that .zip file you flashed, and did you make a backup of your system before you flashed?
Sent from my Droid Razr Maxx
Did you wipe data cache and dalvik? If not wipe again. If it bootloops again try pushing the kernel with fastboot.
Sent from my PG86100 using Tapatalk
The .zip contains the following files:
data
devices
kernel
META-INF
sdcard
system
CHANGELOG
check_data_app
mike, can you tell me how to push the update with fastboot, I'm kind of new to all of this telephone wizardry
I can get into FASTBOOT/HBOOT/RECOVERY, however nothing I do seems to help me get past the HTC Logo. Any thoughts? Maybe I'm not waiting long enough? Can someone please tell me exactly what I need to do (if I can even do something). I might just be approaching this whole process the wrong way.
Do I install a ROM from ZIP from Recovery? Do I need to fastboot an .img file first?
Sounds like your hboot 1.5 and your phone is hanging due to you need to place a copy of your recovery in your adb folder...
The while in Hboot
Using adb with phone plugged in and debug turned on
fastboot boot recovery.img
Then wipe and flash the rom you were trying to flash...
You can't just flash a rom with recovery since your s-on
Two methods
One is fastboot boot recovery.img which is easy
Other is boot.img pain in the ass
I tried booting directly into recovery like you just said. I am using TWRP recovery.img file.
Can this be caused by the type of ROM that I am trying to install?
Everything works fine, the .zip gets applied and seems to install correctly, but it still hangs at the htc logo.
I also forgot to mention that originally I used Clockwork Recovery Mod, which i got from the market, and selected the option to boot into recovery. I don't know if that makes any difference.
You should Google shooter ruu. Get back to stock. Retry this with another shot at reading the instructions.
You must plug your phone into pc while in fastboot and give it a command to boot recovery recovery.img .
Then reflash a rom.
Read more I'm hboot 1.4 and I can still flash a 1.5 hboot correctly cause I've read how to.
Sent from my PG86100 using Tapatalk
If u haven't figured it out yet, see if this helps:
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
If u have updated your phone to the newest radio in the 2.17.651.5 update you may have problems if the Rom is based on an earlier kernel/radio like I think Warm is, but I could be wrong.
You may have flashed the Rom incorrectly & not had the kernel get flashed causing the boot loop.
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
I'm trying to flash Awesomesauce. I know with HBOOT 1.15 I have been flashing the boot.imgs from ROMs through fastboot. I'm currently on SuperLTE ROM, HBOOT 1.15. Awesomesauce is supposed to have the S-On installer zip built in. I downloaded the S-ON flavor of Awesomesauce 2.2, flashed in recovery, rebooted into bootloop. I then tried flashing the boot.img from the Awesomesauce zip then flashing the zip again in recovery. No luck, more boot loop. I read the Sticky pertaining to flashing kernels for HBOOT 1.15 but I didn't see anything about flashing a kernel that wasn't already inside the ROM zip.
So what am I doing wrong? Do I need to reflash the ROM since I have decided to change kernels? Or am I just a super nooblet and not doing the process right?
Some roms fail on the kernel installer, you should be able to.just extract kernel and fastboot, I don't think there would be any problem after that
kjcmusic17 said:
I'm trying to flash Awesomesauce. I know with HBOOT 1.15 I have been flashing the boot.imgs from ROMs through fastboot. I'm currently on SuperLTE ROM, HBOOT 1.15. Awesomesauce is supposed to have the S-On installer zip built in. I downloaded the S-ON flavor of Awesomesauce 2.2, flashed in recovery, rebooted into bootloop. I then tried flashing the boot.img from the Awesomesauce zip then flashing the zip again in recovery. No luck, more boot loop. I read the Sticky pertaining to flashing kernels for HBOOT 1.15 but I didn't see anything about flashing a kernel that wasn't already inside the ROM zip.
So what am I doing wrong? Do I need to reflash the ROM since I have decided to change kernels? Or am I just a super nooblet and not doing the process right?
Click to expand...
Click to collapse
I'm guessing fastboot flash doesn't work. You could try to manually place the kernel into the rom by replacing the kernel folder in the rom with that from awesome, copy/paste the contents from system>lib>modules into the same location in the rom. Zip the rom and flash.
om4 said:
Some roms fail on the kernel installer, you should be able to.just extract kernel and fastboot, I don't think there would be any problem after that
Click to expand...
Click to collapse
Extract kernel and fastboot? Does that mean extract the kernel folder from the Awesomesauce zip and flash that through fastboot? What would be the command for that? "fastboot flash kernel kernel.zip"?
It's the boot.img, it is pretty much the fail safe way to flash a kernel and components. I have yet to have it fail unless I didn't have full access to fastboot
kjcmusic17 said:
I'm trying to flash Awesomesauce. I know with HBOOT 1.15 I have been flashing the boot.imgs from ROMs through fastboot. I'm currently on SuperLTE ROM, HBOOT 1.15. Awesomesauce is supposed to have the S-On installer zip built in. I downloaded the S-ON flavor of Awesomesauce 2.2, flashed in recovery, rebooted into bootloop. I then tried flashing the boot.img from the Awesomesauce zip then flashing the zip again in recovery. No luck, more boot loop. I read the Sticky pertaining to flashing kernels for HBOOT 1.15 but I didn't see anything about flashing a kernel that wasn't already inside the ROM zip.
So what am I doing wrong? Do I need to reflash the ROM since I have decided to change kernels? Or am I just a super nooblet and not doing the process right?
Click to expand...
Click to collapse
Try this it's a boot.img flasher right from your PC
http://forum.xda-developers.com/show....php?t=1917106
om4 said:
It's the boot.img, it is pretty much the fail safe way to flash a kernel and components. I have yet to have it fail unless I didn't have full access to fastboot
Click to expand...
Click to collapse
That's what I had tried first and got stuck in boot loop. I'll try it again after class today.
bigdaddy619 said:
Try this it's a boot.img flasher right from your PC
http://forum.xda-developers.com/show....php?t=1917106
Click to expand...
Click to collapse
Tried the Flash Img GUI app if that's what you mean. The link you posted gives me a 404 error. I just tried flashing via Flash Img GUI and still no dice. I've tried flashing a different (Enoch) via fastboot, next I'll try flashing it via Flash Img GUI. Any other ideas?
kjcmusic17 said:
Tried the Flash Img GUI app if that's what you mean. The link you posted gives me a 404 error. I just tried flashing via Flash Img GUI and still no dice. I've tried flashing a different (Enoch) via fastboot, next I'll try flashing it via Flash Img GUI. Any other ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1917106 sorry here it is again
I confirmed it's working now
bigdaddy619 said:
http://forum.xda-developers.com/showthread.php?t=1917106 sorry here it is again
I confirmed it's working now
Click to expand...
Click to collapse
I even tried this, still getting a boot loop after trying to flash any kernel other than the one that is baked into SuperLTE. Any ideas guys? At this point, I've tried Awesomesauce, Enoch, and EvilZ and have flashed using various methods: recovery (with S-On installer kernels), fastboot, Flash Img GUI, desktop boot img flasher. All of these send me into boot loop.
Try meanrom, evilz kernel runs fine on that one
kjcmusic17 said:
I even tried this, still getting a boot loop after trying to flash any kernel other than the one that is baked into SuperLTE. Any ideas guys? At this point, I've tried Awesomesauce, Enoch, and EvilZ and have flashed using various methods: recovery (with S-On installer kernels), fastboot, Flash Img GUI, desktop boot img flasher. All of these send me into boot loop.
Click to expand...
Click to collapse
Some devices don't play nice when being OC'ed MeanRom v4.8.1 is coming with a stock kernal OC'ed to 1.7 ghz with option to OC to 1.8ghz and it has a kernal installer built ito the script
---------- Post added at 09:21 PM ---------- Previous post was at 09:20 PM ----------
om4 said:
Try meanrom, evilz kernel runs fine on that one
Click to expand...
Click to collapse
Using EvilZ kernal breaks mikeys tweaks refer to my last post
Runs fine for me and it seems to me op is trying to flash a kernel separate from the one packed into rom
Figured it out. My phone won't play nice with 2.1GHz OC. My friend suggested I try the 1.89 flavor of Awesomesauce. Flashed in recovery (S-On Installer Script), boot looped once then rebooted to the ROM. I should have thought of this before.
Yeah things like that slip my mind, sorry I didn't think of that. I even had to check my phone to see if I'm overclocked lol
Hey guys
I've only just got into this stuff so please forgive my ignorance, but I need a hand understanding what might have gone wrong. I've got a GSM Evo 3D which I've unlocked through htcdev, phone is still S-ON, hboot 1.53.007. I flashed CWM recovery but have since switched to 4ext.
I downloaded Viper3D, ran a backup using 4ext recovery so I could go back to stock when I feel like it, then flashed the new ROM to test it out (mainly just testing the process). The phone booted fine - no problem. On that success, I went to restore the backup I made before flashing Viper3D. The restore completed successfully from 4ext recovery, but on trying to boot my phone it just hangs on the first HTC boot screen.
Tried rebooting a few times, tried restoring a second time, did wipe/factory reset first, tried clearing cache and dalvik cache, still just hangs on that HTC boot screen. I probably left it for about 20 minutes on that screen but it didn't go anywhere.
I flashed Viper3D again, and it worked again and my phone boots up fine. So the question is, what's going wrong when I try to restore my original backup? I haven't upgraded hboot or changed the kernel.
Would appreciate if someone could shed some light on this, cheers.
Ok so I think I've figured it out but could still do with a little clarification from someone.
I've read around and found that people have fixed the HTC screen hang by flashing the boot.img with fastboot from the PC, so I decided to give it a go. I copied the boot.img from my original backup to my PC, then booted the phone up into 4ext recovery and restored the backup. After restoring had completed, I rebooted into fastboot and hooked up to my PC, then flashed the boot.img from there. Once that was done, disconnected the phone from the PC and rebooted and the phone booted up fine into my stock ROM.
One thing I noticed when flashing Viper3D is that immediately after flashing, the phone would boot to the HTC screen, then reboot a second time by itself. I now understand this is where 4ext is flashing the boot.img with Smartflash, and it didn't reboot this second time when I was trying to restore my backup so I'm guessing that's where the problem lies.
So it looks to me like 4ext/Smartflash is not doing the whole process for some reason, perhaps a bug? Smartflash is enabled permanently on my phone, so I can't think of another reason why it didn't work except that it's bugged.
Can anyone confirm this issue or have any other comments? Cheers.
zaphodalive said:
So it looks to me like 4ext/Smartflash is not doing the whole process for some reason, perhaps a bug? Smartflash is enabled permanently on my phone, so I can't think of another reason why it didn't work except that it's bugged.
Can anyone confirm this issue or have any other comments? Cheers.
Click to expand...
Click to collapse
Read the requirements for the SmartFlash feature to work on the OP of the 4EXT Recovery thread, and in particular the limitations section. My guess is that you didn't have a bootable kernel when trying to use the SmartFlash option.
An easier way to re-flash the ROM in that situation is to start recovery with this fastboot command:
fastboot boot recovery.img (where recovery.img is the name of your 4EXT recovery file)
Click to expand...
Click to collapse
That command will boot any custom recovery in a mode that will let it flash the entire ROM from recovery, but for 4EXT you have to make sure that the SmartFlash/S-ON option is disabled in the tools menu and then flash the ROM zip file.
ramjet73
Ok thanks, just to clarify - by doing fastboot boot recovery.img, that would reboot the phone into 4ext recovery and allow it to flash both boot.img and recovery.img when flashing the ZIP? What exactly is the fastboot command doing that allows this?
Cheers
zaphodalive said:
Ok thanks, just to clarify - by doing fastboot boot recovery.img, that would reboot the phone into 4ext recovery and allow it to flash both boot.img and recovery.img when flashing the ZIP? What exactly is the fastboot command doing that allows this?
Cheers
Click to expand...
Click to collapse
The "fastboot boot" command starts the recovery as an OS image and just like Android it has the ability to flash the boot partition (kernel) when loaded that way. When started in the "recovery" mode it is not able to flash the boot partition when the phone is S-ON.
SmartFlash uses the same principle to flash the boot partition after the existing kernel is booted, but if the current kernel is not bootable SmartFlash doesn't work.
ramjet73
Ok, I kinda understand (without quite understanding)... can the same command be used for flashing ROMs in a ZIP? e.g. fastboot boot yourromhere.zip
Thanks
zaphodalive said:
Ok, I kinda understand (without quite understanding)... can the same command be used for flashing ROMs in a ZIP? e.g. fastboot boot yourromhere.zip
Thanks
Click to expand...
Click to collapse
No. The "fastboot boot" command only works with bootable images and not zip files.
ramjet73
Thanks very much for your help. A couple of final questions...
How can you flash a custom ROM in a ZIP with fastboot? e.g. the Viper3D ZIP didn't have a recovery.img, only a boot.img
Also, I'm downloading Cool ICS and CoolZ kernel, and this is my first time flashing a kernel. Checked the CoolZ ZIP file and there's no boot.img which I was expecting, so I'm hoping that 4ext won't have any problems flashing it..? Also not sure whether to flash CoolZ or Cool ICS first.
Cheers
The fastboot commands are part of the bootloader (hboot) and custom ROM's are flashed by recovery.
There are guides in the general forum that cover ROM flashing procedures including this one by mpgrimm2.
ramjet73
Thanks, getting stuck installing the CoolZ kernel. I rebooted into 4ext with fastboot boot recovery.img, disabled Smartflash, tried flashing the ZIP, and after extracting files I got the error message:
assert failed: write_raw_image(" /tmp/newboot.img", "boot")
I assume this means it failed writing to the boot partition... any thoughts why?
zaphodalive said:
assert failed: write_raw_image(" /tmp/newboot.img", "boot")
I assume this means it failed writing to the boot partition... any thoughts why?
Click to expand...
Click to collapse
If the assert fails that usually means you are trying to flash something that's not intended for your device. Make sure you are flashing the correct version since there are CoolZ kernels for both the CDMA and GSM Evo 3D models.
Edit: I just checked and it looks like the CoolZ v4.5 kernel has one installation file for both Evo 3D models.
Make sure you can boot into the ROM you flashed before you try to flash the kernel.
ramjet73
Ok, a little weird...
I tried installing the CoolZ kernel, that failed (as mentioned before), then I installed the v14 ROM and v14b update. Booted up the phone, had no WIFI (just said error). So I flashed the boot.img from the v14b ZIP after that to see if I'd get WIFI back, got a couple of bootloops on the splash screen, and it then booted up with WIFI working and the CoolZ kernel installed.
I originally downloaded the CoolZ kernel separately from the Cool ICS ROM, but it appears that the kernel is part of the ROM package so I didn't need to do that.
Anywho, seems to be working now so I'll have a fiddle around. Thanks very much for your help.
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.