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.
Related
hey fam i was running virus rom Eternity 3.0 with stock kernel then i flashed the cm7 rom by joelz yesterday but had to change kerenls to get it to work. i used the apk to do that i think its gui i think, but anyway i tried to restore back from nadroid and my phone wont boot. im on 1.5 with s-on
thanks if any one can help.
evoguy404 said:
hey fam i was running virus rom Eternity 3.0 with stock kernel then i flashed the cm7 rom by joelz yesterday but had to change kerenls to get it to work. i used the apk to do that i think its gui i think, but anyway i tried to restore back from nadroid and my phone wont boot. im on 1.5 with s-on
thanks if any one can help.
Click to expand...
Click to collapse
I guess you have flashed a 2.3.3 kernel so you are experiencing issues.........so now just boot your phone in bootloader then select fastboot > connect your phone to pc (it should say fastboot usb on phone)> now open cmd > head to your fastboot folder in cmd> then type fastboot boot xxxxx.img (xxxx = your recovery img (cwm/twrp) ) > Now your phone will boot into recovery > then restore your Nandroid backup .......
Hope this helps
If the above didnt work try to flash boot.img from your nandroid backup using fastboot (not recovery) with command "fastboot flash boot boot.img"
press thanks if i helped you
is there a way i can do it without my computer im at work,so i don't have all my files on hand...thanks this has got me stomped......
I m sorry you cannot do it without a pc .....you know the limitations of htc unlock method...you can only flash kernels made for 2.3.4 from flash image gui......you can always download those fastboot/adb files from here or google for it.They are just a few kb's
evoguy404 said:
is there a way i can do it without my computer im at work,so i don't have all my files on hand...thanks this has got me stomped......
Click to expand...
Click to collapse
Yes, as long as all the nandroid backup files are on your sdcard. Steps below.
mnomaanw said:
I m sorry you cannot do it without a pc .....you know the limitations of htc unlock method...you can only flash kernels made for 2.3.4 from flash image gui......you can always download those fastboot/adb files from here or google for it.They are just a few kb's
Click to expand...
Click to collapse
This isn't true. Flash Image GUI will flash the kernel for any version, but if your system OS is not also updated at the same time, the device will not boot.
If you're looking to do a nandroid restore w/o using fastboot (or being attached to a computer), here are the steps I would suggest:
1) From Flash Image GUI, select the boot.img from inside of the custom recovery backup directory on the /sdcard. Flash this kernel.
2) Reboot directly into recovery mode. Run the nandroid restore for that SAME backup as the boot.img was pulled from and flashed via Flash Image GUI.
3) After nandroid restore finishes, reboot and the device should be back to the previous state found in the backup.
Remember, this is a work around for the HTC unlock and might not always be the best solution.
Keep us updated and let us know. Hope that helps!
joeykrim said:
Yes, as long as all the nandroid backup files are on your sdcard. Steps below.
This isn't true. Flash Image GUI will flash the kernel for any version, but if your system OS is not also updated at the same time, the device will not boot.
If you're looking to do a nandroid restore w/o using fastboot (or being attached to a computer), here are the steps I would suggest:
1) From Flash Image GUI, select the boot.img from inside of the custom recovery backup directory on the /sdcard. Flash this kernel.
2) Reboot directly into recovery mode. Run the nandroid restore for that SAME backup as the boot.img was pulled from and flashed via Flash Image GUI.
3) After nandroid restore finishes, reboot and the device should be back to the previous state found in the backup.
Remember, this is a work around for the HTC unlock and might not always be the best solution.
Keep us updated and let us know. Hope that helps!
Click to expand...
Click to collapse
hey joey i know we can use flash image gui to flash boot.img from a rom.zip but evoguy cannot boot his phone at all.So how will he be able to use Flash image GUI? I m only telling him what he can do now........
mnomaanw said:
hey joey i know we can use flash image gui to flash boot.img from a rom.zip but evoguy cannot boot his phone at all.So how will he be able to use Flash image GUI? I m only telling him what he can do now........
Click to expand...
Click to collapse
If the device won't boot past the splash screen, chances are the issue is kernel related. For kernel related issues, the ONLY method provided by HTC via their unlock is to use fastboot to boot the recovery. This is the only accessible mode HTC grants write access to the kernel partition.
This is the only way HTC provides write access to the kernel for a device that is not booting properly. The command using fastboot is as follows: fastboot boot c:\recovery.img .
This command will temporarily load the custom recovery with kernel write access allowing a proper recovery to take place.
One reason the device is not booting could be the android OS version mismatches with the kernel, therefore the kernel's ramdisk is looking for files which are not present and cause the device to either freeze or reboot.
There are other reasons too, probably too many worth detailing out as the easiest route to solving the issue is to restore back to a known good working nandroid or cleanly load another known working ROM/kernel combination.
Hope that helps clarify! Best of luck!
Thanks to all you guys. Got it back running XDA is the best.
sent from my Rooted & Boosted 3VO.
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
Hi Everybody,
I unlock the bootloader of my HTC view, I also did install the recovery as
http://forum.xda-developers.com/showthread.php?t=1414137
Then I jumped to install the custom rom (forgot to the S-off first), and I could not! and the existing rom is gone as well.
Now I am restarting into a black screen. I do not have a nandroid backup!
I saw a thread:
http://forum.xda-developers.com/showthread.php?t=1038638
that means I need to install a ruu! but the links are not working, if that is the case, can anybody please provide me with a working link?
Thanks,
I believe you can download a ROM, has to be same android version as the one you were on last, so GB or honeycomb. Copy the boot.IMG from the ROM into the same directory as your fast boot commands
Get into recovery flash ROM
Get into fast boot and
Open cmd on PC
Get to your adb directory
Enter
Fastboot flash boot boot.IMG
Or
Find a ROM that does not have a custom kernel
Or hope someone will upload your ruu
Flyer
If you unlocked your bootloader at htcdev.com you don't need to s-off your device! Just download any custom ROM that meet the requirements of your Flyer, enter into recovery by pressing power and volume down button, wipe everything, copy custom ROM you downloaded into the flashcard and flash it. That's it. Smooth flashing!!!
mcord11758 said:
I believe you can download a ROM, has to be same android version as the one you were on last, so GB or honeycomb. Copy the boot.IMG from the ROM into the same directory as your fast boot commands
Get into recovery flash ROM
Get into fast boot and
Open cmd on PC
Get to your adb directory
Enter
Fastboot flash boot boot.IMG
Or
Find a ROM that does not have a custom kernel
Or hope someone will upload your ruu
Flyer
Click to expand...
Click to collapse
Thanks, it was difficult to find a HC rom! apparently everybody is moving to other devices... I am downloading DesensedView
-2.1.zip hope that works. Thanks for the suggestion. I have been busy with this from yesterday and tried almost everything come into my mind. will let you know if that worked.
Keioboy said:
If you unlocked your bootloader at htcdev.com you don't need to s-off your device! Just download any custom ROM that meet the requirements of your Flyer, enter into recovery by pressing power and volume down button, wipe everything, copy custom ROM you downloaded into the flashcard and flash it. That's it. Smooth flashing!!!
Click to expand...
Click to collapse
Yes, I unlocked it on htcdev.com, and I have two roms (ICS and GC) but none works, after flashing those in recovery, a black screen comes up right after htc logo and nothing happens! I deleted everything, all the cashes and data and flashed these roms, no good, stuck on the black screen. any suggestions? I am even looking for a way to at least go back to my HC!
Thanks
OK. In this case let's try to revert everything back. Make shure what ROM was installed in your device (GB or HC) 1. go to http://htcruu.com/?dir=Flyer_View. 2. Download proper RUU installer. 3. Make Gold Card (just in case if downloaded wrong region RUU). 4. Boot into bootloader and start flashing downloaded RUU.
I am telling you that you can not flash an ICS or CG's JB rom because the boot.img will not flash through recovery with HTC dev unlock. were you on HC or GB prior
Hi all! Just done unlocking bootloader, flash Amon Ra recovery and root. Now I want to flash custom rom but i am lost about flashing the boot.img in hboot, i really don't know how to flash it. I am at S-ON.. Any help would be appreciated. Tnx in advace!
you know what I don't know how to do it too. but there are some roms that will do it for you even if you are s-on
There's two possible ways you might have to do it.
1. If the ROM makes a PH98IMG file and puts it on your sd card then it will take you to hboot after it's done flashing and all you have to do is say "yes" to accept the "update". It will flash the kernel and then you can boot up the phone. After it's booted up make sure you delete that PH98IMG file so you can boot up again.
I think that if it's going to do this it will give you the option to select s-off or s-on when flashing the ROM.
2. If it doesn't do the above you will have to pull the kernel from the ROM. Just look in the ROM zip file in explorer on your pc 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
Some ROMs, like EclipticRez, give you the option of a few kernels. You can just pull the one you want and when you flash it change "boot.img" to whatever the name of that kernel is.
feralicious said:
There's two possible ways you might have to do it.
1. If the ROM makes a PH98IMG file and puts it on your sd card then it will take you to hboot after it's done flashing and all you have to do is say "yes" to accept the "update". It will flash the kernel and then you can boot up the phone. After it's booted up make sure you delete that PH98IMG file so you can boot up again.
I think that if it's going to do this it will give you the option to select s-off or s-on when flashing the ROM.
2. If it doesn't do the above you will have to pull the kernel from the ROM. Just look in the ROM zip file in explorer on your pc 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
Some ROMs, like EclipticRez, give you the option of a few kernels. You can just pull the one you want and when you flash it change "boot.img" to whatever the name of that kernel is.
Click to expand...
Click to collapse
Thank you so much for your help! I'm now running custom rom. I even flashed to the latest firmware.
Okay so i bought my rezound recently then I unlocked it Rooted it and tried installing a rom Im on S on with the unlocked bootloader
im using the amon ra recovery
i wipe then i install the rom and then i reboot the phone but it always gets stuck on the bootanimation
can someone give me the detailed steps to install this rom please
http://themikmik.com/showthread.php...nse-4-5-ICS-4-0-4-(9-29-12)-Stable-and-smooth
thank you
Sounds like you need to flash the kernel. When s-on you need to flash the kernel separately after flashing the ROM.
Some ROMs make the PH98IMG of the kernel for you and if so it will be on the root of your external card. If you boot into bootloader it should ask you if you want to take the update, say yes, that's the kernel. You should be able to boot after that.
If there's no PH98IMG left for you, pull the boot.img from the ROM and flash in fastboot.
fastboot flash boot boot.img
If it's not the kernel issue then post back.
Followed your link to the ROM. Looks like you can just download the kernel from the thread. From the install directions:
**Installation of boot.img**
-download boot.img
-copy to pc to your fastboot directory
-cd to the directory
-type these commands
-"fastboot flash boot boot.img"
That is for if you are s-on, which you are. I'm sure this will get you going.
Yes !! it worked thank you alot :laugh:
just one more question do i have to do the same thing every time i install a new rom?
Yes. Since you are s-on you must flash the kernel that goes with the ROM after you flash the ROM.
If you s-off you won't have to but it makes it easier to brick the phone. I've also read where some people have lost the use of their usb ports trying to s-off. I'm s-on and it doesn't bother me to flash the kernel separately. The ROM I'm using puts it on the sd card and puts the phone in hboot so all I have to do is accept the update. Easy peasy.