• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Not seeing this problem so asking you guys

B

Blewis13

Member
I'm not well versed at rooting and kernels but will try to explain my problem. I followed option 1 from this thread http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html .

when i tried to reboot i get stuck on the screen that says htc quietly brilliant.
I am using the charmeleon rom. I found out that I can replace the boot.img from the charmeleon file in the android-sdk directory on my laptop and then use the "fastboot boot boot.img" instruction in the command prompt and the system reboots perfectly.

My problem is anytime I try to reboot the phone i get stuck on the screen i mentioned above and need my laptop and have to repeat the command prompt thing.
Has anyone ran into this? Does anyone even now what I'm trying to say and know how to fix it?
 
so are you saying that when you boot up you are stuck at the splashscreen (that is what the htc screen is called). and to get unstuck you have to enter the fastboot command to get it to finally boot up the phone?
 
hmmmmm interesting.

so after the second time of entering the fastboot command, does the kernel stick? everything works? can you reboot with no issues?
 
No. That's the problem. The new kernel seems to overide the original one. I have to do the command prompt things everytime i reboot. If I'm away from my laptop and would have to reboot I'd have a brick instead of a phone until I get back to the laptop.
 
not sure why the fastboot command has to be done twice and what is happening upon rebooting. never had any issues with fastboot before. and just to be sure you have all the adb files and fastboot in the same folder along with the boot.img file, correct? and you get no errors the first time you do the commands, right?
 
Very strange. Can you verify a few more things for me?

You are HTC unlocked with H-boot 1.15 correct?

And this was using charmeleon ROM? Have you tried flashing a different ROM from recovery? Are you sure you pulled the boot.img from teh ROM you're using?


Do you have any nandroid you could restore?

What kernel were you originally trying to flash?
 
HTC unlocked and 1.15 correct

I don't have a nandroid. I only have the charmeleon backed up. I've tried everything I can think of. I've restored the backup. I've done a factory reset.

tried to install CM-10 which was the original reason for messing with the kernel in the 1st place. the phone will boot fine with the new ROM but i get a Phone forced closed message right away and can't get into the rom at all.

sorry, don't understand the kernel question. This is the 1st time i was messing with a kernel. i saw in the cm-10 thread that I needed to install a new kernel because i had 1.15 and this is where my problem came from.
 
ocnbrze said:
not sure why the fastboot command has to be done twice and what is happening upon rebooting. never had any issues with fastboot before. and just to be sure you have all the adb files and fastboot in the same folder along with the boot.img file, correct? and you get no errors the first time you do the commands, right?
Click to expand...
Right
 
Blewis13 said:
HTC unlocked and 1.15 correct

I don't have a nandroid. I only have the charmeleon backed up. I've tried everything I can think of. I've restored the backup. I've done a factory reset.

tried to install CM-10 which was the original reason for messing with the kernel in the 1st place. the phone will boot fine with the new ROM but i get a Phone forced closed message right away and can't get into the rom at all.

sorry, don't understand the kernel question. This is the 1st time i was messing with a kernel. i saw in the cm-10 thread that I needed to install a new kernel because i had 1.15 and this is where my problem came from.
Click to expand...

Ok, so from what I'm seeing you tried to install cm10 and flashed the kernel via fastboot. CM10 booted, so you had the correct ROM/kernel at that point.

I understand CM10 gave you issues and you wanted to go back to charmelean. What did you do at that point?
 
Rxpert83 said:
Ok, so from what I'm seeing you tried to install cm10 and flashed the kernel via fastboot. CM10 booted, so you had the correct ROM/kernel at that point.

I understand CM10 gave you issues and you wanted to go back to charmelean. What did you do at that point?
Click to expand...
I went to twrp and restored the charmeleon. I ran into this problem. i went through the forum and found someone with the same problem. that's how i found out that i could replace the boot.img from the charmeleon file into the sdk directory and do the fastboot boot boot.img thing with the charmeleon boot.img and the phone reboots fine. Until........... I try to reboot and I'm back to the splashscreen/brick. It seems that the person who had the same problem as me didn't have the problem with the next reboot unless he hasn't rebooted since then.
 
Blewis13 said:
I went to twrp and restored the charmeleon. I ran into this problem. i went through the forum and found someone with the same problem. that's how i found out that i could replace the boot.img from the charmeleon file into the sdk directory and do the fastboot boot boot.img thing with the charmeleon boot.img and the phone reboots fine. Until........... I try to reboot and I'm back to the splashscreen/brick. It seems that the person who had the same problem as me didn't have the problem with the next reboot unless he hasn't rebooted since then.
Click to expand...

Ok, that was the correct thing to do. Fastboot flashing the charmeleon boot.img put the right kernel back on with your charmeleon ROM.

It should have stuck though. I would try re-flashing the ROM

If all else fails, you can always re-lock, run an RUU, and then run regawmod again to get root and TWRP back. Then restore your charmeleon backup
 
Rxpert83 said:
Ok, that was the correct thing to do. Fastboot flashing the charmeleon boot.img put the right kernel back on with your charmeleon ROM.

It should have stuck though. I would try re-flashing the ROM

If all else fails, you can always re-lock, run an RUU, and then run regawmod again to get root and TWRP back. Then restore your charmeleon backup
Click to expand...
This is not my original lte. I got one when they 1st came out. Rooted it using the regawmod one button thing. when i had to replace the phone the new one had the update and rooting it was a choir. I followed the way to do it from you great guys here and now I'm super happy with the phone with the way it is except, of course, for this booting problem.
i'm not sure how to relock and flash the original ruu. the 1st one i downloaded, with the 1st phone. doesn't work with the new phone. Do you know where i can find instructions to do the relock and rom flash with a phone that has the update?
 
This kind of sounds like the problem I had getting back from cm 10 or aokp.

I had neglected to check off Boot in TWRP as things I wanted it to backup.

I always had a rom on my phone I could just flash fresh and then I would be good to go after nands failed to work.

so a few suggestions, have you tried just flashing a rom fresh? maybe charmeleon over itself if you have it on your phone.

Then make sure you have Boot checked to backup in TWRP.
 
dustwun77 said:
This kind of sounds like the problem I had getting back from cm 10 or aokp.

I had neglected to check off Boot in TWRP as things I wanted it to backup.

I always had a rom on my phone I could just flash fresh and then I would be good to go after nands failed to work.

so a few suggestions, have you tried just flashing a rom fresh? maybe charmeleon over itself if you have it on your phone.

Then make sure you have Boot checked to backup in TWRP.
Click to expand...
boot is checked
 
You must log in or register to reply here.
Back
Top Bottom