Related
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
So this is my first time doing this, but my device is S-OFF unlocked and had the ICS firmware on it including the 3.14 Kernal.
So i decided to flash Newts rom , i erased the big 3; 3 times and installed the rom from recovery menu, then i used this script http://forum.xda-developers.com/showthread.php?t=1419587 to flash the sense4 boot.img file that is attached.
Now my kernal is version 3.014 or something like that and im getting force closes on the backup assistant and stock email app. Did i mess up somewhere or should i reflash the ICS kernal 3.14?
It probably wouldn't hurt to just reflash the ROM over top of what you have. Wipe cache and dalvik first. If you're S-Off, the boot.img will flash in recovery just fine.
Sent from my ADR6425LVW using Tapatalk 2
I just reflashed both files and the same issues persists, the img.boot file that comes with the rom downgrades my kernal.
Also another issue is that my 32gb card is only showing 100kbps even after reflashing and reformatting.
The kernel should be packaged with the ROM.
Hmmmm. Maybe do a full wipe, then reflash the ROM?
Or you could try Sebastian's ICS kernel. Its working great for me on Venasaur.
Sent from my ADR6425LVW using Tapatalk 2
Yea i see the kernal get installed with the ROM but once everything is done, still the kernal version is lower than when i was on stock ICS RUU.
Since you're S-Off, try it without the script.
That script is for the S-On types.
Sent from my ADR6425LVW using Tapatalk 2
rave_nick said:
Yea i see the kernal get installed with the ROM but once everything is done, still the kernal version is lower than when i was on stock ICS RUU.
Click to expand...
Click to collapse
The kernel version should not matter if the Rom works
Sent from my ADR6425LVW using Tapatalk 2
The kernel that comes with the Sense 4 roms is modified to work with them, it's not going to be the same version level as the RUU most likely. Also, since you're s-off, it gets flashed automatically, stop flashing it separately.
I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!
So I have been using Neo's AOSP Rage Rom since about 1.4, and haven't encountered any serious problems (besides some hiccups such as the Trebuchet FC problem in 1.7, although everyone had that). Now, after I have flashed 1.8, I am unable to turn on my Wifi. I checked my md5s, I did 3 clean flashes, and I also flashed the rom with and without the inverted gapps pack.
My Rezound is currently S-ON, and I have no plans to go S-OFF unless necessary.
I'm not sure if this is a kernel problem, or if it's the wifi module, or perhaps something else, but I figured I should ask here first to see if there were others with he same problem.
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
aftafoya said:
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
Click to expand...
Click to collapse
If your running an ruu and still boot looping, then something else is wrong. It's gotta be a hardware problem, time for an insurance return
Sent from my ADR6425LVW using xda app-developers app
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Lucasonic said:
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Click to expand...
Click to collapse
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
I've got the same issue. Except wifi, gps, and bluetooth won't turn on. Also, I keep getting the message that my SD card is damaged. I pulled the boot file from the ROM, zipped it, and named it PH89IMG.
So far, everything else seems to work, but this isn't really working for me. Any suggestions?
Are you on ICS firmware or GB firmware? If you are on GB still and trying to flash ICS rom, wifi and sdcard won't work until you flash the old firmware patch.
Sent from my Rezound using Tapatalk 2
Squirrel1620 said:
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I second that notion. I've been on 1.8 for a while and I feel like it's been the best version so far (I'm S-OFF). 1.9 is out now, so I'll be trying that later tonight.
Performing S-OFF isn't that bad. I thought it was fun - just follow the directions and you should be fine (like anything else).
After running just about every ROM for this device, I recently flashed my first stock based ROM (cooked 1.8). However since this time I've been unable to flash back to any aosp ROM. I get boot looped on every one. I've tried everything. Yet, I can flash cooked again no problem. I know there's something I'm missing. Any help would be great.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
You have a nandroid backup right? Restore that then flash whatever you want.
Sent from my SGH-I777 using Tapatalk 2
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
adrock74 said:
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Search for Siyah kernel v4.3.3 in the forums and install, restart recovery and flash away. Should take care of it.
T
Sent from my SGH-I777 using Tapatalk 2
I always have kept that kernel on standby but that didn't work. I've tried every kernel. Can't believe backups won't even boot. I flashed cook's ROM wipe before his ROM the first time, wonder if that did something.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Try Odin to stock and start from scratch. A lot of work but hey what do you have to lose. :beer:
Sent from my SGH-I777 using xda app-developers app
First find a compatible Kernel for the AOSP ROM your trying to flash. Flash that Kernel.
Second, after the flashing is done, reformat the device; cache, dalkiv cache and system and system settings.
Third, reboot into recovery mode from the recovery menu itself.
Fourth, flash the kernel one more time.
Fifth, flash the AOSP ROM of your choice.
Sixth, reboot back into recovery menu.
Seventh, reformat once more.
Eigth, reboot the device.
As you should know, the first boot up after flashing a ROM takes the longest. Give it like a minute or two.
If this doesn't work, you have to flash a kernel that was compatible with the "cooked" rom you were using. Then from there do a reformat from the recovery menu. Once reformat is done, flash the AOSP kernel, then flash the AOSP ROM right after. Then reformat once more and reboot as normal.
If that doesn't work, flash compatible kernel with the "cooked" ROM your using now and also relay the cooked ROM, and then use Odin to bring it back to stock un-rooted. From there, do as you wish.
Butchr said:
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
Click to expand...
Click to collapse
That is exactly what needed to be done. Mr cook actually has another thread with cwm flashable wipe scripts that would have done that. Quite handy :thumbup: